Error "Unable to connect to the database. Login failed for user 'DOC1Login" in EngageOne Designer

Product Feature: Installation / Upgrade



When opening EngageOne Designer using the default admin login credentials, the following error is returned:
SQL Login Error
Windows Event Viewer log error:
Login failed for user 'DOC1Login'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: <local machine>]
General Information
Additional Info:
ExceptionManager.MachineName: XXXMachineName
ExceptionManager.TimeStamp: 29-08-2013 13:31:21
ExceptionManager.FullName: Microsoft.ApplicationBlocks.ExceptionManagement, Version=6.0.1564.0, Culture=neutral, PublicKeyToken=null
ExceptionManager.AppDomainName: BusObjService.exe
ExceptionManager.WindowsIdentity: NT AUTHORITY\NETWORK SERVICE
1) Exception Information
Exception Type: G1.Wolf.Helpers.DataObjectException
-- Get Major and Minor version Nos for a Repository (Format: Major.Minor)
   ISNULL(G_MAJOR.[Value], '0') + '.' + ISNULL(G_MINOR.[Value], '0')
   [Global] G_MAJOR
   ,[Global] G_MINOR
WHERE   G_MAJOR.[Name] = 'MajorVersion'
    AND G_MINOR.[Name] = 'MinorVersion'
Database: DOC1_Repository
MachineName: XXXMachineName
CreatedDateTime: 29-08-2013 13:31:21
AppDomainName: BusObjService.exe
Message: Exception in DataObject VersionChecker
Data: System.Collections.ListDictionaryInternal
TargetSite: Void ThrowExecuteException(System.Exception, G1.Wolf.DSL.DslCommand, System.Data.SqlClient.SqlCommand)
HelpLink: NULL
Source: DSL
StackTrace Information
   at G1.Wolf.DSL.DataObject.ThrowExecuteException(Exception p_exception, DslCommand p_dslCommand, SqlCommand p_SqlCommand)
   at G1.Wolf.DSL.DataObject.ExecuteScalar(DslCommand p_dslCommand, Int32 iCommandTimeout)
   at G1.Wolf.DSL.VersionChecker.GetRepositoryVersionPrivate(String strRepositoryName)
   at G1.Wolf.DSL.VersionChecker.GetRepositoryVersion(String strRepositoryName)
   at G1.Wolf.DSL.VersionChecker.EnsureServerAndRepositoryVersionsMatchPrivate(DataObject dataObject)
   at G1.Wolf.DSL.VersionChecker.EnsureServerAndRepositoryVersionsMatch(DataObject dataObject)
   at G1.Wolf.DSL.DataObject.EnsureOpenConnection()
   at G1.Wolf.DSL.DataObject.BeginTransaction(TransactionControl p_transactionControl)
   at G1.Wolf.BSL.RepositoryInfo.GetDatabaseName()
2) Exception Information
Exception Type: System.Data.SqlClient.SqlException
Errors: System.Data.SqlClient.SqlErrorCollection
Class: 14
LineNumber: 65536
Number: 18456
Server: (local)
State: 1
Source: .Net SqlClient Data Provider
ErrorCode: -2146232060
Message: Login failed for user 'DOC1Login'.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void ThrowIfCannotRetryToConnect(System.Exception)
HelpLink: NULL
StackTrace Information
   at G1.Wolf.DSL.SqlProvider.ThrowIfCannotRetryToConnect(Exception exception)
   at G1.Wolf.DSL.DataObject.EnsureOpenConnection()
   at G1.Wolf.DSL.DataObject.ExecuteScalar(DslCommand p_dslCommand, Int32 iCommandTimeout)


The SQL Server has been left in it's default "Windows authentication only" mode. Designer requires the SQL Server to be configured in mixed mode.  Another possibility is that the database is set to "Restricted User" and this need to be amended to "MULTI_USER".. 

See the EngageOne Designer Release Notes:

Other SQL Server considerations
The default installation of EngageOne Designer requires SQL Server 2005, 2008, 2012 and 2014 to be configured in SQL Mixed Authentication mode. If you use a firewall, you must ensure that the SQL Server ports are open. If you are running a distributed install ensure that your Database Engine has the TCP/IP protocol enabled.


UPDATED: October 23, 2019

Configure the SQL Server for "SQL Mixed Authentication Mode"

User-added image

If the database when restored shows "Restricted User" this need to be set to "MULTI_USER", select the database involved, and from the highlighted parameter in the "options" drop down menu, change this to "MULTI_USER":

User-added image

Following the change to mixed mode and/or MULTI_USER, restart the SQL Services as well as the BusObjService (EngageOne Template Design Application Service in latest V6 releases) and then try to login to EngageOne Designer again.

If the same issue occurs, contact