Bad Token Errors
I am facing unexpected error issue intermittently(how ever frequency is a good number) when some users of system are trying to go to users-> select any user and click on it.
When we checked, the issue was with some bad token. Here is the trace:
SQL statement: usp_get_admin_workspace @userToken = 'C6E6158182D83F4416BD85538FD60EF1'</Description>
<ExceptionType>ArcherTech.Kernel.Utility.Data.ArcherDbException, ArcherTech.Kernel, Version=188.8.131.529, Culture=neutral, PublicKeyToken=null</ExceptionType>
SQL statement: usp_get_admin_workspace @userToken = 'C6E6158182D83F4416BD85538FD60EF1'</Message>
<StackTrace> at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.WrapDatabaseCall(DbCommand command, Action methodToWrap)
at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.ExecuteScalar(DbCommand command)
at ArcherTech.Kernel.Brokers.WorkspaceBroker.GetPermissionIds(IList`1 workspaceIds)
at ArcherTech.Kernel.Brokers.WorkspaceBroker.LicensePermissionIdsInternal(IList`1 workspaceIds, Boolean checkLicensing, Boolean checkReadPermission, Boolean checkCreatePermission, Boolean checkUpdatePermision, Boolean checkDeletePermission)
at ArcherTech.Kernel.Brokers.WorkspaceBroker.Get(IList`1 workspaceIds, Boolean checkLicensing, Boolean checkReadPermision, Boolean checkCreatePermision, Boolean checkUpdatePermision, Boolean checkDeletePermision)
at ArcherTech.Kernel.Managers.WorkspaceManager.Get(SessionContext sessionContext)</StackTrace>
- archer administrator
- archer admins
- archer technical
- archer to archer
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
This error is telling you that the session token of the user is no longer valid, so the request is rejected. A session can become invalid in a number of ways, a few of which I'll list here:
- Session Timeout
- Open a second browser session and login
- Sharing credentials (between users or processes like feeds/api)
That error is telling you that the session is already dead. There's nothing to do besides re-login as that user.
If this is occurring often, it means that users are being shared in some capacity, you have a very short session timeout, or something else is going on causing sessions to become invalid.
We have installed Archer 6.2 and we have the same issue. Could you please give some insights on how you would solve it? Thanking you in advance for your help,
We have a native install of 6.2 - not upgraded, with no users and this rolling / invalid session token issue with the sysadmin user right after install with Windows Integrated and SSL. Doing this login via Anonymous works but we need to get Windows/SSL working.
Is more than one individual trying to login with the sysadmin account at a time? If so, whoever logs in last will kill the sessions of the others.