Forum Discussion

EVGuy's avatar
EVGuy
Level 4
16 years ago

Can't connect to SQL Server when running config.

Anyone else run into this issue when running the initial configure for an EV server? (This is the first server)

 

When prompted for the SQL server name I get an error saying that EV failed to connect to SQL Server...

 

I ran a DTrace while this was going on and there's a mention of a failure when creating the DSN at line 18 of the trace.

 (Trace was Directory Service - verbose)

 

9    14:04:58.133 [1,884] (DirectoryService) <1972> EV:M CMonitorAzStore::DownloadAuthorizationStore
IfNecessary: Authorization Store not accessable: The directory database does not exist
10   14:04:58.133 [1,884] (DirectoryService) <1972> EV:M CMonitorAzStore::ThreadRoutine - Waiting fo
r 60 seconds or until service exits.
11   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M DIR_ADMIN_FN: CDirectoryServiceObject::IsDi
rectoryDatabaseExists
12   14:05:12.421 [1,884] (DirectoryService) <1876> EV:H DirectoryService: Method call: CheckPermiss
ions()

13   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::HasServerClientGotPermiss
ion, Admin Operation: 1002
14   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::IsServerClientTheVSA
15   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::IsServerClientTheVSA - hr
=0 InClientCOMCall:T VSA:T
16   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::HasServerClientGotPermiss
ion: VSA: Allowed
17   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M CDatabaseService::CreateSystemDSN DSN:Enter
priseVaultDirectory Desc:Enterprise Vault Configuration Database DbName:EnterpriseVaultDirectory Ser
ver:
18   14:05:12.421 [1,884] (DirectoryService) <1876> EV:M CDatabaseService::CreateDSN failed [Code=64
876168 Message=
] DSN:EnterpriseVaultDirectory Desc:Enterprise Vault Configuration Database DbName:EnterpriseVaultDi
rectory
19   14:05:13.503 [1,884] (DirectoryService) <2536> EV:M DIR_ADMIN_FN: CDirectoryServiceObject::get_
SQLServer
20   14:05:18.725 [1,884] (DirectoryService) <1876> EV:M DIR_ADMIN_FN: CDirectoryServiceObject::IsSQ
LServerOnComputer
21   14:05:18.725 [1,884] (DirectoryService) <1876> EV:H DirectoryService: Method call: CheckPermiss
ions()

22   14:05:18.725 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::HasServerClientGotPermiss
ion, Admin Operation: 1002
23   14:05:18.725 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::IsServerClientTheVSA
24   14:05:18.725 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::IsServerClientTheVSA - hr
=0 InClientCOMCall:T VSA:T
25   14:05:18.725 [1,884] (DirectoryService) <1876> EV:M CSecurityWrapper::HasServerClientGotPermiss
ion: VSA: Allowed
26   14:05:18.757 [1,884] (DirectoryService) <1876> EV:M CDatabaseService::CreateSystemDSN DSN:TMP_M
ASTER_TMP_FOR_51990656 Desc:TEMPORARY_MASTER_TMP DbName:MASTER Server:W2K3-SQL
27   14:05:35.297 [1,884] (DirectoryService) <1876> EV:M CDatabaseService::DeleteDSN DSN:TMP_MASTER_
TMP_FOR_51990656

  • Are you sure that Named Pipes and TCPIP is working?

    And have you configured Remote Access to SQL?

5 Replies

  • Check the Vault Account has the correct SQL priveleges and can connect (you could try an ODBC connection test). Run Deployment Scanner - that will tell u
  • Ran the Deployment Tool and I'm getting the following: Enterprise Vault requires database creator or higher permissions on SQL Server. Test Failed for the following reason:[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation. The SQL servers listed below support the following network protocols: W2K3-SQL.VMWARE.LOCAL: NamedPipes (NO), TCP/IP (NO) thing is, the EVAdmin account has dbcreator on the SQL Server as well as Sys Admin. I even gave it Domain Admins membership. The client tools in SQL list Named Pipes and TCP/IP as the available protocols. Permissions look good, network connectivity looks good. (Ping by name, tracert, etc) I even put the SQL server's name in the HOSTS file just in case there were any DNS issues. Still no joy. :(
  • Are you sure that Named Pipes and TCPIP is working?

    And have you configured Remote Access to SQL?

  • Thanks, that was it!

     

    Haven't used SQL 2005 outside of running it in a dev lab. (With all queries run locally) I wasn't aware they had it locked down as much as they do.

     

    Thanks again. 

     

  • I am getting the same issue with all the pre-requisites met...

     Named Piped and TCP/IP is enabled...

    vaultadmin has the following rights on SQL: -
    dbcreator
    sysadmin
    Server Admin

    Still getting the following error in Deployment Scanner: -

    SQL Server Permissions

     

    Warning

     
    Enterprise Vault requires database creator or higher permissions on SQL Server. 
     
    PRODSQL.WORKS.GOV.BH: Test Failed for the following reason:[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

    SQL Server Connectivity

     

    Failed

     
    The SQL servers listed below support the following network protocols: 
     
    PRODSQL.WORKS.GOV.BH: NamedPipes (NO), TCP/IP (NO)

    SQL Server Version

     

    Failed

     
    At least one test for the SQL server version has failed. 
     
    PRODSQL.WORKS.GOV.BH: Unable to connect to server.

    SQL Server Reporting Services

     

    Warning

     
    At least one test for SQL Server Reporting Services has failed. 
     
    PRODSQL.WORKS.GOV.BH: Microsoft SQL Server Reporting Services is not installed on this computer.

    SQL Collation

     

    Failed

     
    Unable to connect to at least one of the SQL servers listed. 
     
    PRODSQL.WORKS.GOV.BH: Unable to connect to server.  

     
    Please advise.

    Regards,

    GauravAditya