New England Security User Group

 View Only
  • 1.  ServiceDesk 7.1 Installation failure...still!

    Posted Mar 27, 2011 08:53 AM

    So its been 2 weeks and I still can't get ServiceDesk 7.1 installed and I've tried everything. The ServiceDesk pre-reqs all pass, we are installing SD on a server 2008 R2 machine with a domain service account. The database is off-box on a server running SQL 2008 R2. I've followed all of the KB articles and made the SD server an admin on the SQL box, I've logged in remotely to the SD server with mstsc /admin ( as the SD box is virtual, the SQL server is not ) and I've tried running the install as the service account (which is an admin on the server as well) and as myself (and I am a Domain Admin). Both accounts also have SA rights on the SQL Server. 

    It looks like everything is in order but I get the same error over and over again:

     

     

    Installing Workflow Server..
    Checking Server Extensions service running
    Default server is not local
    Process timeouts and escalations
    Checking Server Extensions service running
    Copying Workflow Server installer..
    Workflow Server role installed.
    Workflow SymQ Setup completed
    Enabling SMP Log Writer..
    Installing ServiceDesk ITIL Core..
    Checking Server Extensions service running
    ProcessManager portal role added to default server
    ServiceDesk ITIL Core role installed.
    Installing ServiceDesk Portal..
    Checking Server Extensions service running
    Writing MSSQL connection instance to web configuration file..
    Writing Report snapshots location to web configuration file..
    ServiceDesk Portal role installed.
    Preparing SQL scripts to execute..
    Checking Server Extensions service running
    SMP server credentials saved.
    Executing database integration strategy..
    Checking if database ProcessManager already exists..
    Creating new database ProcessManager..
    Granting system accounts access to database..
    Processing: bowdoincollege\servicedesk_srvc
    Granting DB access to BOWDOINCOLLEGE\servicedesk_srvc
    Creating new database..
    Proceed Tables..
    Proceed Data..
    Database integration completed.
    Writing OLAP connection instance to web configuration file..
    Do not send welcome messages to users as they're added to the portal
    Use Process Manager for Critical Errors
    Creating administrator user..
    Writing administrator login information to web.config..
    Checking Server Extensions service running
    Server with IP servicedesk was not found
    Setting up ActiveDirectory authentication..
    Failed to fetch user: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
    Failed to fetch user: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
    System.Data.SqlClient.SqlException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Symantec.Workflow.Installer.Core.MSSQL.MSSQLDataProvider.GetConnection(Boolean onDatabase, Boolean withTimeout)
       at Symantec.Workflow.Installer.Core.MSSQL.MSSQLDataProvider.Execute(String sql, Boolean keepConnectionOpen, Boolean onDatabase)
       at Symantec.Workflow.Installer.Core.MSSQL.MSSQLDataProvider.Execute(String sql)
       at Symantec.Workflow.Installer.Strategy.AuthenticationStrategy.CreateDomainAdminUser(ActiveDirectoryServer server)
       at Symantec.Workflow.Installer.Strategy.AuthenticationStrategy.Execute()
       at Symantec.Workflow.Installer.WizardPages.AuthenticationPage.Run()
       at Symantec.Workflow.Installer.InstallerManager.Run()
    Installation Failed.
     
     
    This line " Failed to fetch user: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." doesn't make sense. Both machines are on the sam domain, I have unbound and re-bound the SD server to AD just in case and again all of the tests during pre-install succeeded. We have to use Windows authentication and the same install parameters worked fine when I installed NS 7.1.
     
    I know there's a lot of information but would love any suggestions!


  • 2.  RE: ServiceDesk 7.1 Installation failure...still!
    Best Answer

    Posted Mar 27, 2011 04:56 PM

    Looks like there was an error on the domain controllers. We have a couple of different naming conventions in our domain. The FQDN for AD and a common name for our users. The common name did not have an SPN for the SQL services. There are 2 different ways to fix it, either use SetSPN on the DCs to add the missing attributes OR use the FQDN for installation, verifying that forward and reverse DNS function correctly (which is not something we normally set up with the domain names).