Discussion Forum: Thread 351715 |
|
|
| | Author: | LaconicBricks | Posted: | Dec 20, 2023 09:18 | Subject: | Bricksync problems | Viewed: | 124 times | Topic: | Related Software | |
|
| Hi BL Users,
Nothing has changed in my passwords or API's in the last several days but
all of a sudden, I'm getting the error code below. Has anyone come across
a similar issue? I tried putting in the new tokens and resetting but couldn't
figure it out!
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
JSON PARSER: Error, token 7 when token 13 was expected, offset 218100
JSON Parse Errors Encountered
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00000.txt".
WARNING: Bad reply from server, trying again shortly...
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
JSON PARSER: Error, token 7 when token 13 was expected, offset 218100
JSON Parse Errors Encountered
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00001.txt".
WARNING: Bad reply from server, trying again shortly...
ERROR: Too many connection errors, giving up.
ERROR: Failed to fetch inventory from BrickLink.
ERROR: Fatal error encountered.
ERROR: Exiting now.
Press Enter to exit...
|
|
|
| | | | | |
| | | | Author: | SylvainLS | Posted: | Dec 20, 2023 09:22 | Subject: | Re: Bricksync problems | Viewed: | 169 times | Topic: | Related Software | |
|
| In Related Software, LaconicBricks writes:
Hi,
| […]
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00000.txt".
|
Have you looked into this file?
Also, shouldn’t you ask Bricksync’s author?
|
|
| | | | | | | | | |
| | | | | | Author: | Vosblokjes | Posted: | Dec 20, 2023 10:22 | Subject: | Re: Bricksync problems | Viewed: | 35 times | Topic: | Related Software | |
|
| In Related Software, SylvainLS writes:
| In Related Software, LaconicBricks writes:
Hi,
| […]
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00000.txt".
|
Have you looked into this file?
Also, shouldn’t you ask Bricksync’s author?
|
That will not be easy.
Stragius made it open source a few years back and then left. Not sure what he
was going o do, but as I remember it was something far away from computers and/or
internet.
There are some people that maintain it (and doing a very good job a that), but
that is not going much further than making sure new colors get added.
|
|
| | | | | |
| | | | Author: | Vosblokjes | Posted: | Dec 20, 2023 10:09 | Subject: | Re: Bricksync problems | Viewed: | 44 times | Topic: | Related Software | |
|
| In Related Software, LaconicBricks writes:
| Hi BL Users,
Nothing has changed in my passwords or API's in the last several days but
all of a sudden, I'm getting the error code below. Has anyone come across
a similar issue? I tried putting in the new tokens and resetting but couldn't
figure it out!
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
JSON PARSER: Error, token 7 when token 13 was expected, offset 218100
JSON Parse Errors Encountered
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00000.txt".
WARNING: Bad reply from server, trying again shortly...
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
JSON PARSER: Error, token 7 when token 13 was expected, offset 218100
JSON Parse Errors Encountered
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00001.txt".
WARNING: Bad reply from server, trying again shortly...
ERROR: Too many connection errors, giving up.
ERROR: Failed to fetch inventory from BrickLink.
ERROR: Fatal error encountered.
ERROR: Exiting now.
Press Enter to exit...
|
The issue is in
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
There is a small c where BrickSunc expets a capital C.
On Bricklink you will not see the difference.
Try the set for sale that this is about (probalbly the last added one), punt
in a capital i, save and then change to capital C and save again.
If this doesn't help, delete the set from your inventory and re-add it (with
the capital C)
This is for the sub-condion of the set
|
|
|
| | | | | | | | | |
| | | | | | Author: | LaconicBricks | Posted: | Dec 20, 2023 10:23 | Subject: | Re: Bricksync problems | Viewed: | 50 times | Topic: | Related Software | |
|
| In Related Software, BasKrie writes:
| In Related Software, LaconicBricks writes:
| Hi BL Users,
Nothing has changed in my passwords or API's in the last several days but
all of a sudden, I'm getting the error code below. Has anyone come across
a similar issue? I tried putting in the new tokens and resetting but couldn't
figure it out!
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
JSON PARSER: Error, token 7 when token 13 was expected, offset 218100
JSON Parse Errors Encountered
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00000.txt".
WARNING: Bad reply from server, trying again shortly...
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
JSON PARSER: Error, token 7 when token 13 was expected, offset 218100
JSON Parse Errors Encountered
WARNING: BrickLink JSON Parse Error - Saving server reply (692+3318923 bytes)
at path "data\errors-2023-12-20\00001.txt".
WARNING: Bad reply from server, trying again shortly...
ERROR: Too many connection errors, giving up.
ERROR: Failed to fetch inventory from BrickLink.
ERROR: Fatal error encountered.
ERROR: Exiting now.
Press Enter to exit...
|
The issue is in
BL JSON PARSER: Error, unknown item completeness "c", offset 218100
There is a small c where BrickSunc expets a capital C.
On Bricklink you will not see the difference.
Try the set for sale that this is about (probalbly the last added one), punt
in a capital i, save and then change to capital C and save again.
If this doesn't help, delete the set from your inventory and re-add it (with
the capital C)
This is for the sub-condion of the set
|
WOW! You're an absolute GENIUS!!!
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | Vosblokjes | Posted: | Dec 21, 2023 00:40 | Subject: | Re: Bricksync problems | Viewed: | 24 times | Topic: | Related Software | |
|
| In Related Software, LaconicBricks writes:
| WOW! You're an absolute GENIUS!!!
|
Well thank you
But this is something I had myself some time ago and just remembered the solution
|
|
|
|
|
|