Video Screencast Help

Problems accessing Service Desk 7.1 sp2

Created: 20 Jun 2012 • Updated: 13 Feb 2013 | 4 comments
This issue has been solved. See solution.

Cannot open database "ProcessManager" requested by the login. The login failed.<br>Login failed for user 'sa'.Server
Error in '/ProcessManager' Application.

Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'sa'.
Description: An unhandled exception occurred during the execution of the current
web request. Please review the stack trace for more information about the error
and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Cannot open database
"ProcessManager" requested by the login. The login failed.
Login failed for user 'sa'.

Source Error:

      The source code that generated this unhandled exception can only be shown
      when compiled in debug mode. To enable this, please follow one of the
      below steps, then request the URL:

      1. Add a "Debug=true" directive at the top of the file that generated the
      error. Example:

        <%@ Page Language="C#" Debug="true" %>


      2) Add the following section to the configuration file of your

             <compilation debug="true"/>

      Note that this second technique will cause all files within a given
      application to be compiled in debug mode. The first technique will cause
      only that particular file to be compiled in debug mode.

      Important: Running applications in debug mode does incur a
      memory/performance overhead. You should make sure that an application has
      debugging disabled before deploying into production scenario.

Stack Trace:

[SqlException (0x80131904): Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'sa'.]
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +6244425
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +245
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2811
   System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +53
   System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +248
   System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +6260362
   System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +6260328
   System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +354
   System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +703
   System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +54
   System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +6261592
   System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +81
   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +1657
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +88
   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +6265031
   System.Data.SqlClient.SqlConnection.Open() +258
   LogicBase.Framework.DataLayer.DALProxy.ExecuteCommandMultipleRecords(IDbCommand cmd, Type entityType) +198

[DataLayerException: Error executing sql query.]
   LogicBase.Framework.DataLayer.DALProxy.ExecuteCommandMultipleRecords(IDbCommand cmd, Type entityType) +1009
   LogicBase.Framework.DataLayer.DALProxy.ExecuteQuerySingleRecord(DatabaseQuery query) +559
   LogicBase.Ensemble.Settings.DataLayer.MasterSettings.LoadByID(String MasterSettingsID) +414
   LogicBase.Ensemble.Settings.DataLayer.SettingsHelper.GetSettings() +58
   LogicBase.Ensemble.Settings.EnsembleSettings.get_Settings() +86
   LogicBase.Ensemble.GlobalHelper.InitializeGlobal() +765

[TypeInitializationException: The type initializer for 'LogicBase.Ensemble.Global' threw an exception.]
   LogicBase.Ensemble.Global..ctor() +0
   ASP.global_asax..ctor() +9

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +146
   System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +298
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +79
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +10362891
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +258
   System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext context) +11308241
   System.Web.HttpApplicationFactory.EnsureAppStartCalled(HttpContext context) +161
   System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +115
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +196

Version Information: Microsoft .NET Framework Version:2.0.50727.4963; ASP.NET

Comments 4 CommentsJump to latest comment

Luis.Silva's picture

It's possible to login on database with "SA" cradential?

brunoyep's picture

You need to reinstall it

Bruno Bacelar

toomas's picture

Bruno, no.

The error message clearly states what it is about:

Cannot open database "ProcessManager" requested by the login. The login failed.
Login failed for user 'sa'.

ServiceDesk is configured to use the 'sa' account for database access. Something about the account has now changed, the likely changes are either a password change for the 'sa' account in SQL Server or disabling the SQL Authentication on the SQL Server.

Luis is correct, the first step in troubleshooting this would be to login to SQL Server with 'sa' account. If you can not log in, your DBA would be a good person to nudge about this.

Jeanne's picture

In fact our Operations guru changed the password once he reset it we are back in business.