Error while doing user mapping in MSSQL: Create failed for User (Microsoft.SqlServer.Smo)

Issue: After restoring the axpert database in mssql, there is an error as shown below when mapping the db user login with the default database.

Steps to resolve:

Run the below command on the restored database using SA login.

exec sp_change_users_login 'auto-fix', @userVar

• Related Articles

• Error Activation Failed, Try later

  If you experience the below issue, when activating license or refreshing license. It may be due to agile' license server not reachable. You may check by using the below url over browser to see, if it opens without any error. Sometimes local network ...

• ADR: Schema Getting Locked Due to "Ora-01017 Invalid user name/password"

  ADR: Schema Getting Locked Due to "Ora-01017 Invalid user name/password" Issue: ADR sometimes keep connecting, though there is an error code ORA-01017, which makes the user schema getting locked after x no of tries. You can download the latest ...

• Report (Iview) is not working for a specific user but for others it is working

  It may be due to custom views sometimes and delete the record in "axcustomviews" table for the user whom it is not working. eg. delete from axcustomviews where name = ‘<iviewname>’ and username = '<username>'

• Error: License / App key invalid. Please contact Agile Support Team

  It could be due to following reasons. User may be trying to refresh the partner license using old exe. Use of latest exe may fix this problem The license may be originally activated from one windows login and user may be trying to refresh the same ...

• Error: Please try later... when login from specific IPs

  It may be possible that the source IP may be lengthier than 20 characters and axpert will fail to insert in connections, axaudit tables. The login trace in such scenarios would show up something like below and to resolve this, the IP field width has ...