Posted on 07-19-2024 07:52 AM
While fetching policy using sudo jamf policy, we are getting the error:
Any idea what might be causing this issue?
Posted on 07-19-2024 07:56 AM
I would check to see if you have a policy running that's using an API call in it. The parser errors typically happen when the result of an API call failed to get proper XML and it was being parsed with something like xmllint or another similar tool. Maybe the policy is running an out of date script that isn't getting a token first before doing the rest of the API calls. Just a guess.
Posted on 07-22-2024 02:38 AM
Thanks. I am new JAMF admin so I will have to figure out if the script is out of date or if it is getting the proper XML.
Posted on 07-19-2024 08:25 AM
Can you post more details about this policy?
Posted on 07-22-2024 02:38 AM
The policy was created by an old employee and since I am new to JAMF stuff, I am kind of clueless of what it does. :(
Posted on 07-22-2024 11:43 AM
Well, it's easy to find out. Figure out what policy it is, then locate it in Jamf Pro under the Policies section and open it. See what's included in the policy. My guess would be there's at least one script in it being run at execution time. Locate the script under Settings > Computer Management > Scripts, and examine them from there to see what they may be doing.