I am doing a lot of conversions from CAD drawings to GIS and every so often I am running into a problem. After adding the CAD drawings to a geodatabase, I then use spatial adjustment to move the prints to the correct coordinates as they aren't accurately placed by default. I then choose to Save Edits from the Editor toolbar. On certain geodatabases, this will go to Not Responding and never save the changes, while on others it works fine. I noticed that when I analyze the wait chain on the ArcMap process, it shows that it's waiting on splwow64.exe. That's the print spooler for 32-bit apps in a 64-bit environment. I'm not trying to print anything, so why would it be waiting on that? I see that there are comments about having a default printer and I do have a local (USB) default printer set up. Also, all files I'm working with are local rather than on a network drive. The license server is on a network drive, however.
ArcGIS for Desktop 10.1 SP1
Windows 7 64-bit
4 GB RAM
3 GHz CoreDuo CPU
Any help would be appreciated. Any geodatabase that has this problem always has the problem no matter how many times I try it. It even has the problem if I recreate the geodatabase with the same data. Yet some other geodatabases with different data work fine, while others also fail with this same problem.
To reproduce this, I am just adding the geodatabase layers (2), starting editing on all layers, spatially adjust the map, and saving edits. Everything works fine until I choose to save the edits.
Edit: It would be nice if there was some option to see a progress of what's being done when saving edits so you know if it's working or locked up. I let one of these run overnight (about 14 hours) just in case it was actually doing something, but it was still not responding in the morning. It shouldn't be hard to add an optional display of what record it's on -- Processing record 5 out of 150,000 or something like that. Anytime there is a long process that could potentially take hours, a progress bar or data of some sort is really useful. I'm surprised at the lack of that in ArcMap. Background processing at least has something, but it's not really all that useful and doesn't affect things like spatially adjusting a map or saving changes.
ArcGIS for Desktop 10.1 SP1
Windows 7 64-bit
4 GB RAM
3 GHz CoreDuo CPU
Any help would be appreciated. Any geodatabase that has this problem always has the problem no matter how many times I try it. It even has the problem if I recreate the geodatabase with the same data. Yet some other geodatabases with different data work fine, while others also fail with this same problem.
To reproduce this, I am just adding the geodatabase layers (2), starting editing on all layers, spatially adjust the map, and saving edits. Everything works fine until I choose to save the edits.
Edit: It would be nice if there was some option to see a progress of what's being done when saving edits so you know if it's working or locked up. I let one of these run overnight (about 14 hours) just in case it was actually doing something, but it was still not responding in the morning. It shouldn't be hard to add an optional display of what record it's on -- Processing record 5 out of 150,000 or something like that. Anytime there is a long process that could potentially take hours, a progress bar or data of some sort is really useful. I'm surprised at the lack of that in ArcMap. Background processing at least has something, but it's not really all that useful and doesn't affect things like spatially adjusting a map or saving changes.
Hi Jeremy,
How did you get your CAD data into the geodatabase. Did you use the CAD to geodatabase GP tool?
Thanks,
Lisa
Hi, It seems that this issue was over, but I am having the same problem right now. My issues began after installing and working with ArcGIS Pro and I updated graphic card's driver (because ArcGIS Pro was unstable), and I wanted to begin working again with ArcMap.
Any suggestion? I desperately need some help.
Just curious, if you pull Pro back off does ArcMap work again?
Can you tell me what you have tried to do already?
Thanks,
Lisa
Hi Lisa,
Here is what I have tried:
(a) Update my graphic card NVIDIA driver and Enable/disable both graphics card in my system:
(b) Repair installation of ArcGIS Desktop 10.5
(c) Cleaning my computer registry entries
(d) Change the splwow64.exe file from the version 10.0.16299.15 to a older version 6.1.7601.17514 (which is working properly in another computer)
(e) Disable the Background Processing in ArcMap
(f) Clearing diaplay cache
(g) Uninstall/install my Adobe printer (with no printer in the system ArcMap disappears):
(h) Avoid AGOL connection from ArcMap
Also, just in case it might be useful at this time, I have sent multiple system configuration with messages like this:
And always the same message:
ArcGIS Pro seems to continue working properly.
I really appreciate some help. I would send you more information if you need it.
Regards,
Inma.
Attachments
Hi,
I asked around for suggestions. Are you still working with CAD data?
Anyway the only suggestion I have so far is
' to add a physical printer and make it the default versus the Adobe printer.'
Hope that helps, if not it might be time to call support..
Thanks,
Lisa
Hi there,
I also have a similar problem as Immaculada above. Every time I open ArcMap (10.6.1, but it also happened when I had 10.5.1), it calls the splwow64 print spooler, and then waits on the process, causing slowdowns and eventually crashing. I've noticed that it primarily causes slow-downs when an online basemap is loaded, but it also seems to cause slowdowns when large local datasets are loaded as well. So far I can bypass the issue by manually killing splwow64 every time I start ArcMap, but that's less than ideal. I have tried everything Immaculada had tried, including setting the default printer to a local printer which does nothing.
I was experiencing the same thing on 10.6.1, although with no use of CAD data, after months of no problems on a fresh machine with 10.6.1. I am able to get into ArcMap now by killing the splwow64.exe. Not a lot of fun was had spending all day figuring this out.