I'm seeing this error as well despite having complete admin access for the account I'm using.

After upgrading from 9.65 -> 9.82 we've had this issue. It's also worth noting that our NBIs are having difficulties seeing the JSS. The DNS hostname of the JSS resolves fine in the terminal, but casper imaging will not communicate with the JSS unless you enter the IP in the JSS location box. Once you connect using the IP instead of the hostname, we get this error when we try to image.

Edit: We're also using autoDMG and AutoCasperNBI for NBI creation.

I had this issue today on 9.92
Added our jss to the hosts file of the Netboot image. Fixed it!!

I had this issue today with Casper Imaging. The message appeared once when I clicked "Image." I simply re-clicked "Image" and it went through.

So if anyone hit this in 10.3 Support says there is a error in JSS that special characters makes this error show. If you change the account password to just numbers and letters than the issue goes away.

I am now seeing this issue for the first time, and we just upgraded to 10.3.

So, @anickless , Are you saying that the special character in my AD password is causing this problem? Basically, I have to change my password to not include special characters just to get Jamf imaging to work. Not cool. Anyone else have an update on this?

We have upgraded our to Jamf Pro 10.3.0 on 6/4/2018 and using LDAP accounts to do imaging and seeing the same error due to special characters in the passwords. Work around now by using local JSS account without special characters in the password and just alphabet and numbers

@jamfnc Have you heard back from support on this?

Yep, special character issue popped up after we upgraded from 9.101.0 to 10.3.0. We basically relayed the workaround to our affected techs vs. creating a local JPS account. Hope this gets fixed, that a big ‘bug’!

I actually just got off the phone with Jamf regarding this...

It's bug PI-005660 and is fixed in 10.4 that was just released today.

I'm on 10.5.0 and I've got this issue...not fixed in 10.4?

Should be related to a special character in the Users password..

@benducklow Yeah, I'm assuming that too. Going to try it...but it's a big issue that I need to make my password less secure to use Jamf. Hopefully that's it. Was supposed to be fixed...