topic Re: JSON error on enrollment in Workspace ONE Discussions

JSON error on enrollment

troysp — Tue, 25 Apr 2023 19:32:05 GMT

We started getting this error today and not sure what is causing it. This error is happening when trying to enroll a device. We are not using any custom JSON files so I am sort of at a loss on what is happening. I have a ticket open with VMware on this issue but was curious if anyone else has seen this error before?

Re: JSON error on enrollment

Afshin_Lak — Wed, 26 Apr 2023 08:12:48 GMT

Maybe try this:

https://discussions.apple.com/thread/250483274

Re: JSON error on enrollment

troysp — Wed, 26 Apr 2023 11:28:13 GMT

Yes, I saw this before posting to the forums and it does not help in this situation. Have tried deleting and reinstalling several times including rebooting between installations.

Re: JSON error on enrollment

troysp — Thu, 27 Apr 2023 15:29:12 GMT

I believe this issue is related to IIS on my device services server and not iOS specific. I am getting an error also trying to enroll Android devices, but not the JSON error. Also, if I try to install an app from the catalog it will never install. The IIS worker process on the device services server will be at high CPU and take up all available memory over time until it crashes and restarts. This is happening over and over.

Re: JSON error on enrollment

troysp — Tue, 09 May 2023 13:07:59 GMT

This issue started due to the drive on the DS server filling up. VMware support had us remove key files from a folder per this KB article. [Resolved] CRSVC-8778: Machine Key accumulation results in low disk space on Workspace ONE UEM application servers (82553) (vmware.com) This deleted over 2 million files which seems to be an issue in some versions of VMware Workspace ONE. This resolved some of the issues but with regards to devices checking in but we still could not enroll new devices or install software from the catalog. After running the Sysinternals tool procmon we noticed that the w3wp process was showing name collisions trying to write to a temp folder. We stopped IIS on the DS server and moved all of the temp files (65,000+) from this folder to a folder on the desktop and restarted IIS. This resolved our issue and things are back to normal.