topic Re: Script Error 8004E37 in ArcPad Questions

Script Error 8004E37

DonaldVetterling — Wed, 04 Sep 2013 22:32:02 GMT

I have an ArcPad project that runs fine in ArcPad 10.0.4 but I get the attached "script error 80040E37" when I open it in ArcPad 10.2 on a Win 7 64bit desktop. When I clear the error it seems to work fine. Any thoughts?

Re: Script Error 8004E37

BrysonWebber — Fri, 06 Sep 2013 11:31:55 GMT

Last time I got a similar error is when we upgraded to ArcGIS 10.1 and it was renaming the length field. ArcPad didn't like the symbols used in the new default length field. All I did is hide the field and it didn't export to ArcPad. Don't know if this is the problem but I would look into it and see if it is one of Esri's default fields that ArcPad 10.2 doesn't like.

Bryson

Re: Script Error 8004E37

DonaldVetterling — Mon, 09 Sep 2013 00:15:49 GMT

Further investigation into my issue shows that the script error shows up when a feature class is renamed in the ArcMap document and then that feature class is exported to an axf file (editable or non editable).

Re: Script Error 8004E37

mrmark — Thu, 12 Sep 2013 16:17:07 GMT

Thanks for confirming my suspicions. We just started pushing out ArcPad 10.2 and immediately started seeing this error. It didn't help when I re-exported the files from ArcMap 10.2. After seeing this I asked around and discovered that one of the feature classes had been given a new name in the map document that was different from the actual feature class in the geodatabase.

I think this is a huge issue as this is a quite common occurrence, e.g. feature class is named TDS_union but someone renames it to "Inspection Points" or something in the table of contents.

Re: Script Error 8004E37

MatthewCarey — Thu, 10 Oct 2013 18:28:03 GMT

I'm getting this error message but it doesn't seem to be related to the renaming of layers.

Here's what I've been doing:
In ArcMap 10.2 (Win 7 64 bit), check out data from a feature class in a versioned 10.1 SQL Server Express geodatabase to an axf file.
On opening the axf file in ArcPad 10.2 I get the Script Error.

But if I do this:
With the same setup, check out data from a feature class in a 10.2 file geodatabase to an axf file.
It opens fine in ArcPad 10.2.

In neither case have I changed any layer names in the TOC; both are simple point feature classes, and I didn't use a checkout template.

Anyone have any further thoughts or different scenarios to offer?

Re: Script Error 8004E37

MohamedNaeem — Sun, 13 Apr 2014 11:26:37 GMT

I'm getting this error message but it doesn't seem to be related to the renaming of layers.

Here's what I've been doing:
In ArcMap 10.2 (Win 7 64 bit), check out data from a feature class in a versioned 10.1 SQL Server Express geodatabase to an axf file.
On opening the axf file in ArcPad 10.2 I get the Script Error.

But if I do this:
With the same setup, check out data from a feature class in a 10.2 file geodatabase to an axf file.
It opens fine in ArcPad 10.2.

In neither case have I changed any layer names in the TOC; both are simple point feature classes, and I didn't use a checkout template.

Anyone have any further thoughts or different scenarios to offer?

This worked for me: Ensure that your feature class name and alias is the same and DO NOT change it when you drag it into your mxd (feature class name = alias = layer name)

Re: Script Error 8004E37

BarbaraHammond — Mon, 21 Apr 2014 19:51:25 GMT

I'm having the same issue (10.2.1) and I haven't changed anything in the two feature classes that I extracted (schema only). The script error appears as a pop-up, but if I close it, the extract does open in ArcPad. However, after I've collected the data and attempt to load the .afx file (Get Data from ArcPad wizard) I'm getting an error message that the .afx file didn't contain a transaction log. Are these two issues related?

Re: Script Error 8004E37

roemhildtg — Wed, 06 Aug 2014 15:18:32 GMT

Just updated our devices to 10.2 and are currently experiencing this error. Our layers are in a an SDE database powered by Microsoft SQL server. I tried looking into the layer name issue and everything appears the same. As a simple test I added just one layer to the project, exported it directly to arcpad, and opened it up. The same error keeps occuring.

Similar to what another poster mentioned, we are still able to ignore this error and add data, so maybe this isn't an issue worth pursuing.

Any news on this topic?

Re: Script Error 8004E37

MarikaVertzonis — Thu, 09 Oct 2014 22:49:30 GMT

The dev team have been looking at this and believe its related to the Quick Fields implementation. Changes have been made and will be available in the next ArcPad release. You can confirm this yourself by disabling Quick Fields. To do this, delete (or move to a sub folder) the Quick Fields applet, and re launch your data in ArcPad.

Re: Script Error 8004E37

roemhildtg — Fri, 10 Oct 2014 12:29:55 GMT

Where do I remove this applet from? We are using the Get Data For ArcPad Extension.

Re: Script Error 8004E37

DonaldVetterling — Fri, 10 Oct 2014 17:25:01 GMT

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.

Re: Script Error 8004E37

jameshickey — Fri, 19 Dec 2014 17:53:59 GMT

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

Re: Script Error 8004E37

DonaldVetterling — Thu, 19 Feb 2015 20:14:22 GMT

Appears this problem is corrected in the latest release of ArcPad. (10.2.2)

Re: Script Error 8004E37

OswaldoSandoval — Wed, 22 Apr 2015 22:36:17 GMT

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

Re: Script Error 8004E37

MarikaVertzonis — Thu, 09 Jul 2015 23:13:11 GMT

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.