Get Data for ArcPad crashes ArcMap

AimeeMiller · ‎08-01-2012

I am using ArcMap 10.0 with an ArcInfo license. I am using ArcPad version 10.0.

I am setting up field maps for our crews to go out and gather data, including data points. I have made a very simple feature class in a personal geodatabase. Whenever I try to use the Get Data for ArcPad to export this layer as part of the map for the crews to use, ArcMap crashes without any warning or error messages. If I don't include this layer, the rest of map will export into .apm format just fine. If I try to edit the feature class in an edit session in ArcMap it works fine.

This process worked fine earlier this summer, but no longer does. The problem seems to coincide with my upgrade from ArcView to ArcInfo, but I'm not actually sure if doing that and this problem are correlated at all.

I know sometimes it is a problem if the feature class is too large, but mine only contains 1 additional field from the defaults, a 50 character comments section.

Any suggestions for why this crash could be happening?

JuanLuera · ‎08-02-2012

Hola Elizabeth,

I would suggest a few items to try to see if we can troubleshoot what you are seeing, when ArcMap crashes in attempting to check out data. If these items do not help the crash below, and you are current on your maintenance, please log a Support webform to work with a ArcPad Support Specialist. I would be glad to work with you on this further, to see if we can come up with a resolution on this issue. Gracias, Elizabeth!

Suggestion:
1. Install ArcMap 10.0.5 latest service pack for ArcMap
http://support.esri.com/en/downloads/patches-servicepacks/view/productid/17/metaid/1876
2. Install the latest version of ArcPad 10.0.4, from Esri Customer Care Portal
3. https://customers.esri.com/index.cfm?event=login.show
4. If you are able to isolate the feature class, then run a Check and Repair Geometry on the feature class
Check Geometry (Data Management)
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//001700000034000000
Repair Geometry (Data Management)
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Repair_Geometry/00170000003v000000/
5. If this does not resolve the issue, I would suggest turning off a few fields from within the dataset, and then see if your data will check out. Once you isolate the field causing the issue, you can then re-create it and if data resides inside. Then you can create a new field and use the field calculation option, to copy over all the attributes.

In looking into this further with one of our Development Technical Leads, we thought this would also assist you.

Also as another suggestion on this, you run Editor > Validate Features prior to attempting ArcPad check out to see if any specific feature(s) is causing ArcMap to crash. They should also check the checkbox to Validate feature classes before checking out in Select Output Options display of Get Data For ArcPad tool. When checked, the geodatabase layers and features selected for check-out will be validated before checking out. The validation process will stop at the first occurrence of invalid data and report the invalid data. The invalid data should be corrected, and the check-out process runs again (with the validate option checked) until no invalid data is reported. All invalid data will need to be corrected in order to check out the layer.

The validation occurs in the following sequence:
1. Validate any subtypes.
2. Validate any attribute rules (such as domains).
3. Validate any network connectivity rules.
4. Validate any relationship rules.
5. Perform any custom validation (using optional class extensions).

ArcPad requires that all data be valid according to the defined domains. Although the validation process takes some time for larger datasets, it is highly recommended that you validate your data when using Get Data For ArcPad for the first time. This will detect and report any invalid data and provide you with an opportunity to correct the data.

Support Service
1-888-377-4575
http://support.esri.com/en/webform/s...275/chat/false

AimeeMiller · ‎08-03-2012

1) I updated to the latest service pack and
2)I already had the latest version of ArcPad.
4) Check Geometery didn't seem to come up with any issues.
5) I only have 4 fields in the feature class, the default OBJECTID and SHAPE, as well as two I added Site and Comments. Turning off any of those fields didn't make it check out.

There are currently no features in the feature class (and won't be unless I can figure out how to get it to check out to ArcPad), so I was unable to validate features. If I created one using Edit, and then attempted to validate it, everything validated just fine.

Any more suggestions?

JuanLuera · ‎08-03-2012

Hola Elizabeth,

Thanks for the updated information and testing results, from the information we provided. If you would like further assistance and current on ArcPad maintenance, please submit support request to Esri Support to work with ArcPad Support specialist. You are always welcome to add my name, and I will be glad to work with you on this issue. I can look to resolve this issue with you. Gracias, Elizabeth!

Support Service
1-888-377-4575
http://support.esri.com/en/webform/s...275/chat/false

LaurenYee · ‎08-08-2012

Hi,

I am having a similar issue - did you ever figure it out?

Thanks

noamrozenfeld · ‎08-12-2012

When it happenned to me, it was some kind of bug in the MXD, from which i export the data to ArcPad.
I've created a new MXD, with setting the data sources of the layers again, and it solved it.

Hope it helps.
Noam

JuanLuera · ‎08-13-2012

Hola Noam,

I would agree with this, where a new .mxd, re-adding the data set's, and then re-checking the data back out. This sometimes resolves the issue, where ArcMap will crash when checking data out. Gracias, Noam!

LaurenYee · ‎08-20-2012

Thanks for your suggestions - upon further digging I found out it was occuring due to my drives. I needed to save my files locally on the C: drive rather than on the shared network.

RyanMendieta · ‎08-20-2012

fwiw, it kept crashing me for as well. the reason: symbology. it was having a hard time with one of the more 'obscure' icons. I changed it to a simple point marker and no errors. hm. yup.

DanielHowes · ‎11-29-2012

I had the same issue. After trying all sorts of fixes, it turned out that the feature class that was giving me issues was joined to another table. The join was set to "keep only matching records", and no records matched. I removed the join and it exported perfectly. Hope this helps.