Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Session launch failing - Windows on prem

BrandonLucas_BF
Regular Contributor III
Regular Contributor III

I am trying to set up Windows on-prem for the first time. Bootstrap is successful and everything looks good up until session launch. During session launch, I get an error to contact my administrator. The logs show that "logoff" is happening as soon as the session launches:

2023-09-24T19:00:36-04:00-ecm-domain.EcmConfigController-http-nio-8080-exec-134-DEBUG-Saving attribute::: LogOffBySessionIdJSON
 
2023-09-24T19:00:36-04:00-ecm-domain.EcmConfigController-http-nio-8080-exec-134-DEBUG-Saving attribute::: LogOffBySessionIdJSON done
 
2023-09-24T18:49:43-04:00-connectorms-c.s.ssm.winsadapter.util.AdapterHelper-http-nio-8980-exec-3-DEBUG-response_data_str data before convert is { "status": "200", "data": "LogOff completed succesfully"}
 
2023-09-24T18:49:43-04:00-connectorms-c.s.ssm.winsadapter.util.AdapterHelper-http-nio-8980-exec-3-DEBUG-WinService Response Object = {"data":"LogOff completed succesfully","status":200}
 
2023-09-24T18:49:43-04:00-connectorms-c.s.s.c.controller.ConnectorController-http-nio-8980-exec-3-DEBUG-Exit getLogOffDiscSessions
 
2023-09-24T18:49:43-04:00-windows-connectorms----"data": "LogOff completed succesfully"
 
2023-09-24T18:49:43-04:00-windows-connectorms----"data": "LogOff completed succesfully"
 
2023-09-24T18:49:42-04:00-windows-connectorms----22:49:42 [Debug] Endpoint [89] LogOffDiscSesssionsScript called...Logging Off process initiated...LogOff completed succesfully...
 
 
 
I'm not sure what this means exactly but noticed the CPAM torubleshooting guide has a callout similar to this,
 

Cause 4: On Windows connection, the GetLogOnIdBySessionIdJSON and LogOffBySessionIdJSON fields are blank.

Resolution: If the session launch fails, verify JSON under the corresponding Windows connection. Ensure that GetLogOnIdBySessionIdJSON and LogOffBySessionIdJSON fields contain the following JSON configuration:

{ 'clientName':'${clientName}'}

 

 

I have verified this setting in the connection and it's specified as indicated. I have tried this with both JIT and a credentialless account in local admins. All connectivity is good because bootstrap is successful.

Has anyone seen this?

2 REPLIES 2

NageshK
Saviynt Employee
Saviynt Employee

@BrandonLucas_BF Please share the logs prior to the Logoff logs. Also, please validate if all the pre-requisites for windows targets are provisioned. And verify the ports 3389 and 5985 are open. 

Thanks

Nagesh K

BrandonLucas_BF
Regular Contributor III
Regular Contributor III

@NageshK I have a case open that is close to resolution. Will update thread once complete.

 

INC-2002314 and INC-2002315 (similar issues in different environments)