000034779 - After a fresh install of RSA Archer, unable to login with sysadmin account: Bad Token

Document created by RSA Customer Support Employee on Mar 2, 2017Last modified by RSA Customer Support on Mar 27, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000034779
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.x, 6.x
IssueAfter a fresh install of RSA Archer 6.2, unable to login with sysadmin account

Sample exception from the Archer w3wp log file:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <Description>Bad Token
SQL statement: usp_get_admin_workspace @userToken = '2D812A35FA2AEBF6561CE66ED788726B'</Description>

                        <ExceptionType>ArcherTech.Kernel.Utility.Data.ArcherDbException, ArcherTech.Kernel, Version=, Culture=neutral, PublicKeyToken=null</ExceptionType>
                        <Message>Bad Token
SQL statement: usp_get_admin_workspace @userToken = '2D812A35FA2AEBF6561CE66ED788726B'</Message>

   at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.WrapDatabaseCall(DbCommand command, Action methodToWrap)
   at ArcherTech.Kernel.Utility.Data.ArcherSqlDatabase.ExecuteScalar(DbCommand command)
   at ArcherTech.Kernel.DataSource.Db.WorkspaceDataSource.GetAdministration()
   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.GetQuickReference(Int32 workspaceId, Boolean pruneEmptyFolders)
   at ArcherTech.Kernel.Managers.WorkspaceManager.GetQuickReference(SessionContext sessionContext, Int32 workspaceId, Boolean pruneEmptyFolders)</StackTrace>

CauseThe Windows Server is missing the 'HTTP Activation' feature for .NET Framework.
  1. Run Server Manager (on task bar and start menu).
  2. Choose the server to administer (probably local server).
  3. Scroll down to "Roles and Features" section.
  4. Choose "Add Role or Feature" from Tasks drop down.
  5. On "Add Role or Feature Wizard" dialog, click down to "Features" in list of pages on the left.
  6. Expand ".NET Framework 4.5 Features".
  7. Under "WCF Services", check the box for "HTTP Activation". You can also add non-http types if you know you need them (tcp, named pipes, etc).
  8. Click "Install" Button.

User-added image