Upload failed with client error? - 02-09-2006 , 06:23 AM
What can cause error "Error: [-10032] Upload failed with client error
Docs say that this error is reported from remote service, but what should I
check first to fix this problem?
This error is reported during upload of one of tables, containing primary
key on two fields of type integer and datetime.
Because this table is _only_ uploaded, there is only UPLOAD_INSERT cursor
associated with this table.
Trouble started to appear after upgrade from version 8 to 9. At present I am
using version 220.127.116.111 replicating to MS SQLServer2000
Thank you in advance
Re: Upload failed with client error? - 02-09-2006 , 09:13 AM
"Juntek" <ktos (AT) gdzies (DOT) pl> wrote in news:43eb344d$1@forums-1-dub of
J> What can cause error "Error: [-10032] Upload failed with client error
J> Docs say that this error is reported from remote service, but what
J> should I check first to fix this problem?
To look at an issue you start by examining both the MobiLink server log
file and the remote log file.
In this case, since it is an upload issue, you will most likely find an
error reported in the ML log file.
Please ALWAYS include version and MORE importantly BUILD number
with EACH post (dbeng9 -v).
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).
EBFs and Maintenance Releases
Developer Community / Whitepapers
CaseXpress - to report bugs
CodeXchange - Free samples
Re: Upload failed with client error? - 02-09-2006 , 09:41 AM
An occurance of this problem was fixed in the following builds : 802.4502,
803.5188, 901.1953, 902.2529
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.
I would suggest applying the latest v902 EBF, since you indicated that you
were using version 18.104.22.1681.
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"
"Juntek" <ktos (AT) gdzies (DOT) pl> wrote