Gregg,
What Marika suggests is to remove the applet from ArcPad itself. On my 64bit computer it is located at C":\Program Files (x86)\ArcGIS\ArcPad10.2\Applets". Remove all the files that start with "QuickField" (save them somewhere else in case you need them in the future) and give it a try. It worked for me.
Fantastic!!!
I have been working on this since Monday!
Our set up is: A GeoXT 6000 running Windows Mobile 6.1, ArcPAD 10.2 for Mobile, Trimble Positions Add-in for ArcPAD 10.2.
On PC: Windows 7 64bit SP1, ArcGIS Desktop 10.2, ArcPAD 10.2 for Desktop, Trimble Positions Add-in for Desktop 10.2.
I was receiving the same SQL error:
In order to remedy this solution I had to remove the QuickField Applets from the GeoXT 6000's program files.
Located at DeviceStorage/Program Files/Arc Pad/Applets
I created a sub directory called quickFieldBackup and moved all of the Files that started with QuickField into this.
Everything work great after that!
Thank you a ton!
James Hickey
Appears this problem is corrected in the latest release of ArcPad. (10.2.2)
Hi Guys!
I obtained the same error using ArcPad 10.2.2:
16:43:08 Synchronization started
16:43:08 AXF_FEATURE_SERVER_SOAP: http://srvgivsig01:6080/arcgis/services/OCP/inspeccionesDDV/MapServer/FeatureServer
16:43:08 AXF_FEATURE_SERVER_REST: http://srvgivsig01:6080/arcgis/rest/services/OCP/inspeccionesDDV/FeatureServer
16:43:08 AXF_TOKEN_URL: http://srvgivsig01:6080/arcgis/tokens/generateToken
16:43:08 Generating Token
16:43:08 Token: ZAyclYan1RhXaeTFrB_6AciCEVDZEx0HoiDZfh6xxaI.
16:43:09 Create unique constraint: UQ_Sitios
Inestables_Identifier
16:43:09 C:\Program Files
(x86)\ArcGIS\ArcPad10.2\System\Scripts\Common\sync.js(1204, 7) Microsoft SQL
Server Compact Edition OLE DB Provider: 0x80040e37: Major Error 0x80040e37,
Minor Error 0. The specified
table does not exist. [ ]
16:43:09
Synchronization completed
sorry for the delay in spotting this quesiton - still getting used to geonet.
Oswaldo the error you show here is quite different to the one displayed at startup that the others describe. Yours is to do with synchronization. Is your service secured perhaps? Are they point, line or polygon features and do they have z values? Some detail about your service will help pin point the problem.