Home > Archive > SQL Anywhere Mobile > June 2005 > Upload failed with client error









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Upload failed with client error
Rs

2005-06-27, 7:24 am

Hi all,
ASA 9.0.1.1883
PPC ultralite

I am getting the error below:


I. 06/27 11:21:12. <thread 1.15>: UltraLite synchronization request from: 2
(version: 2)
I. 06/27 11:21:22. <1.15> [2]: ODBC isolation set to: Read Committed
I. 06/27 11:21:22. <1.15> [2]: COMMIT Transaction: begin_connection
I. 06/27 11:21:22. <1.15> [2]: Removing download cache file
" C:\WINDOWS\TEMP\rd00
000021"
I. 06/27 11:21:23. <1.15> [2]: COMMIT Transaction: begin_synchronizatio
n
W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
script defined for table: OrdersLines. Synchronization has the risk of
potentially losing upload data
W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
script defined for table: Orders. Synchronization has the risk of
potentially losing upload data
W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
script defined for table: Items. Synchronization has the risk of
potentially losing upload data
W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 33 row(s) were ignored in
updating table Items
W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
script defined for table: Invoices. Synchronization has the risk of
potentially losing upload data
W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
script defined for table: InvoicesLines. Synchronization has the risk of
potentially losing upload data
W. 06/27 11:21:23. <1.15> [2]: Warning: [10039] Error detected while using
multi-row cursor -- retrying with single row cursor
W. 06/27 11:21:23. <1.15> [2]: Warning: [10044] A row in table
'UserPreferences' could not be updated because it no longer exists in the
consolidated database
W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 1 row(s) were ignored in
updating table UserPreferences
W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 164 row(s) were ignored in
updating table InvoicesLines
W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 15 row(s) were ignored in
updating table Invoices
W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 14 row(s) were ignored in
updating table Orders
W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 165 row(s) were ignored in
updating table OrdersLines
E. 06/27 11:21:23. <1.15> [2]: Error: [-10032] Upload failed with client
error -677587051
I. 06/27 11:21:23. <1.15> [2]: ROLLBACK Transaction: end_upload
I. 06/27 11:21:23. <1.15> [2]: COMMIT Transaction: end_connection
I. 06/27 11:21:23. <1.15> [2]: Disconnected from consolidated database
I. 06/27 11:21:23. <1.15> [2]: Synchronization failed

Any ideas?
Thanks in advance,
R


Nick Elson

2005-06-27, 1:24 pm

At the point of failure, the ML server is reading the upload
stream expecting to read the UL 'success code' but instead
is reading garbage instead. You are seeing what garbage
looks like when it is being treated as an integer.

The fact remains the stream is invalid at that point.

This sounds like a problem that was fixed already (to me).
I would definitely try a recent 9.0.1 ebf or even jump
to 9.0.2 and the latest ebf for that.

I suspect it may even be fixed by

Build #2529 - Engineering Case #372098

Versions affected: 7.x - 9.x
Versions fixed:
802.4502
803.5188
901.1953
902.2529

Modules affected: dbmlsv9.dll
Customer Description:
In rare circumstances, an upload could have failed and reported "Unknown
Client Error XXX", where XXX was some random large number. This error
was
usually followed by another error reporting that "A protocol error
occurred
when attempting to retrieve the remote client's synchronization log".
Although there are circumstances where this is a valid error to report,
an
instance where this error was incorrectly reported has now been fixed.

It may just be a ML server issue, but you may also need to rebuild
the ultralight application to avoid any issues on that side.


HTH

"Rs" <rs@nospam> wrote in message news:42bfc763@forums
-1-dub...
> Hi all,
> ASA 9.0.1.1883
> PPC ultralite
>
> I am getting the error below:
>
>
> I. 06/27 11:21:12. <thread 1.15>: UltraLite synchronization request from:
> 2 (version: 2)
> I. 06/27 11:21:22. <1.15> [2]: ODBC isolation set to: Read Committed
> I. 06/27 11:21:22. <1.15> [2]: COMMIT Transaction: begin_connection
> I. 06/27 11:21:22. <1.15> [2]: Removing download cache file
> " C:\WINDOWS\TEMP\rd00
000021"
> I. 06/27 11:21:23. <1.15> [2]: COMMIT Transaction: begin_synchronizatio
n
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
> script defined for table: OrdersLines. Synchronization has the risk of
> potentially losing upload data
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
> script defined for table: Orders. Synchronization has the risk of
> potentially losing upload data
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
> script defined for table: Items. Synchronization has the risk of
> potentially losing upload data
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 33 row(s) were ignored in
> updating table Items
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
> script defined for table: Invoices. Synchronization has the risk of
> potentially losing upload data
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10057] There is no upload data
> script defined for table: InvoicesLines. Synchronization has the risk of
> potentially losing upload data
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10039] Error detected while using
> multi-row cursor -- retrying with single row cursor
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10044] A row in table
> 'UserPreferences' could not be updated because it no longer exists in the
> consolidated database
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 1 row(s) were ignored in
> updating table UserPreferences
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 164 row(s) were ignored in
> updating table InvoicesLines
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 15 row(s) were ignored in
> updating table Invoices
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 14 row(s) were ignored in
> updating table Orders
> W. 06/27 11:21:23. <1.15> [2]: Warning: [10040] 165 row(s) were ignored in
> updating table OrdersLines
> E. 06/27 11:21:23. <1.15> [2]: Error: [-10032] Upload failed with client
> error -677587051
> I. 06/27 11:21:23. <1.15> [2]: ROLLBACK Transaction: end_upload
> I. 06/27 11:21:23. <1.15> [2]: COMMIT Transaction: end_connection
> I. 06/27 11:21:23. <1.15> [2]: Disconnected from consolidated database
> I. 06/27 11:21:23. <1.15> [2]: Synchronization failed
>
> Any ideas?
> Thanks in advance,
> R
>



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com