2 Replies Latest reply: May 18, 2013 1:47 AM by Marco V
nloui Level 1 Level 1 (0 points)

Hi, for some reason I'm getting this error when trying to Enroll a Device using the profile manager:

 

0::Feb 20 11:27:10.626 [2458] <192.168.2.101> VerifyDeviceBail: 500 Internal Server Error - auth server error 0

0::Feb 20 11:27:10.626 [2458] <192.168.2.101> LogoutUser FAILED: no valid user session

0::Feb 20 11:27:25.643 [2740] <192.168.2.101> EXCEPTION: 500 Internal Server Error - auth server error 0 at

0::Feb 20 11:27:25.643 [2740] <192.168.2.101> #0 /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/php/ot a_bootstrap.php(55): VerifyAuthToken('')

0::Feb 20 11:27:25.643 [2740] <192.168.2.101> #1 {main}

0::Feb 20 11:27:25.643 [2740] <192.168.2.101> VerifyDeviceBail: 500 Internal Server Error - auth server error 0

0::Feb 20 11:27:25.643 [2740] <192.168.2.101> LogoutUser FAILED: no valid user session

 

in the server logs

 

On the client side, when logging in and pushing "Enroll", the page refreshes but nothing actually happens.

 

Has anyone seen this before? Any help is greatly, greatly appreciated.

 

Thanks,

Nick     


OS X Server
  • 1. Re: Device enrollment not doing anything?
    PSMacMin Level 1 Level 1 (0 points)

    Did you ever resolve this?  I'm seeing the same error on a new 10.8.3 deployment.

  • 2. Re: Device enrollment not doing anything?
    Marco V Level 1 Level 1 (0 points)

    Yesterday I encountered the same problem.

     

    In our case the problem was the binding of the OS X server with the Microsoft AD server.

    I followed the following steps to resolve it:

    1. Stop Profile Manager in Server.app

    2. Stop Open Directory in Server.app

    3. Remove AD binding from System Preferences, Users and Groups, Login Options (This took quite some time and eventually I Force quited System Preferences after noticing that the green LED from the AD binding was removed from the list)

    4. Bind to AD again with system preferences

    5. Started Open Directory in Server.app

    6. Started Profile Manager in Server.app

     

    If you have a similar setup you might give it a try.