Environment
ZENworks Configuration Management 2017
ZENworks Configuration Management 11
ZENworks Configuration Management 11
Situation
ERROR (from zmd-messages.log):
[DEBUG] [11/26/2013
10:37:06.708] [1140] [ZenworksWindowsService] [37] [] [CommonCasa]
[] [ObtainAuthToken took exception: -939720701 System.Exception:
-939720701
at
Novell.Casa.Client.Auth.Authtoken.ObtainAuthToken(String sService,
String sHost, WinLuid luid, String()& extraData, IntPtr
micasaContext, String& AuthMech)
at
Novell.Zenworks.Zmd.Common.CasaHelper.ObtainAuthToken(String
SessionID, String RealmName, String Host, String& AuthToken,
String()& ExtraAttribs, IntPtr MicasaContext, String&
AuthMech)] [] []
[DEBUG] [11/26/2013
10:37:06.708] [1140] [ZenworksWindowsService] [37] [] [CommonCasa]
[] [Stack Trace: at
Novell.Casa.Client.Auth.Authtoken.ObtainAuthToken(String sService,
String sHost, WinLuid luid, String()& extraData, IntPtr
micasaContext, String& AuthMech)
at
Novell.Zenworks.Zmd.Common.CasaHelper.ObtainAuthToken(String
SessionID, String RealmName, String Host, String& AuthToken,
String()& ExtraAttribs, IntPtr MicasaContext, String&
AuthMech)] [] []
[DEBUG] [11/26/2013
10:37:06.708] [1140] [ZenworksWindowsService] [37] [] [CommonCasa]
[] [ObtainAuthToken returning -939720701] [] []
Resolution
Restarting the zenserver service on the failing primary resolved
the problem.
Cause
Since no logs were enabled for server side ats.log and ats.trace
the cause is not yet determined. But the casa service was
failing to return a valid auth token policy until restart of the
service.
Additional Information
casatester.exe showed unexpected error connection reset when trying
to get authtokenpolicy from a primary.