SQL Server Connection fails on Installing EV

[HolgerMu]

Hey Folks,

although the Enterprise Vault Service account has sysadmin / dbcreator etc. rights on the SQL Server the Deployment Scanner fails with "unable to connect to server"

We checked the firewall (Disabled for Domain Networks), TCP/IP and NamedPipes are activated. SystemDSN Connection Test is successful.

The EVSA is local Admin on the sql-machine and sysadmin on the SQL-Server

Deployment Scanner can connect to SQL and read the sql server version SQL2005 SP3 (64bit)

OS is Windows server 2008 R2 on SQL and EV

EV Version is 9.0

Thanks for ideas

Holger

[GertjanA]

Hello Holger,

Can you try adding the VSA to the Local Admin group on the SQL server.

Is the SQL server by any change NOT using port 1433?

You might have to (on the ev-server)

start, run, type cliconfg.

click tab Alias

specify sql servername, select tcp/ip, UNTICK select dynamic port, and specify the port being used by SQL.

Try again

[Nick_White]

What happens if you explicitly give the DB Creator role to the Vault Service Account in SQL? It may be that there is an override somewhere that is causing this to fail, along the lines of Exchange connectivity failing if the account is a member of the domain admins

[HolgerMu]

Hi Gertjan,

this is a valid point but dynamic ports are by default on SQL 2008 server, this is a default SQL 2005 server, I checked the Config, dynamic ports are NOT used and i checked that only 1433 is used.

Thanks for your help :)

Holger 

[GertjanA]

Hello holger,

Check Installing and configuring guide page 49 and further.

Also make sure that the Vault Service Account is not member of ANY group. It should be a normal user, not member of anything.

From page 45:

At the time the Configuration Wizard runs, the Vault Service account must have

access to administrative shares on the SQL Server computer. One way to ensure

that access is granted is to make the Vault Service account a local administrator

on the SQL Server computer. After the Configuration Wizard has been run you

can remove this access, if required. However, on SQL Server 2005 and later, the

Vault Service account must continue to have at least Viewserverstate permission

after configuration.

Unless you assign the SQL system administrator (sysadmin) role to the Vault

Service account, you must perform some additional steps before you run the

Enterprise Vault Configuration wizard for the first time.

See “Assigning permissions and roles in SQL databases” on page 49.

[HolgerMu]

only assigning dbcreator did not work either.

[GertjanA]

Hi Holger,

Can you edit the hostsfile on the server where you want to install EV, with an entry to the SQL server? Try that?

[HolgerMu]

Hi Gertja,

we checked the installing and configuring guide.

Still no luck, Deployment Scan reports on missing rights and Configuration Tool still can't create databases.

tested with dbcreator rights and the modifications, also with sysadmin rights

I am lost ;)

[HolgerMu]

Hi Gertjan

editing the hostfile had no impact on the issue.

The strange thing is that we can "see" the SQL server we can't conntect to it, the Deploymentscanner can read the settings (Server Versions, Collation etc.)

[JesusWept3]

Just as a matter of interest, do you just have the one SQL instance installed (\archiv) or does the default SQL instance exist along with it?

[HolgerMu]

yes, we HAD only the \archiv instance installed. Now we installed a new SQL Server only with the default SQL instance, same issue.

[GertjanA]

Check this: http://www.symantec.com/docs/TECH63430

and this http://www.symantec.com/docs/TECH75498
and this http://www.symantec.com/docs/TECH55820

and this http://www.symantec.com/docs/TECH52740

and this http://www.symantec.com/docs/TECH48229

 Disable the firewall on the SQL and EV server completely, try again.

If not succesfull, I think you need to call support.

[HolgerMu]

Hi gertjan:

Link1: this is a new installation, no EV Databases and so on available. System-DSN to the SQL says "test successful"

Link2: same thing, we haven't even configured any Databases

Link3: We tried the instance and then reinstalled SQL with default instance. Same thing

Link4: SQL runs on the default port 1433 (udp1434)

Link5: all system databases <8MB size, it's a default new installation of SQL2005

Called Support, no response yet...waiting patiently

[MichelZ]

Can you try enabling & starting the "SQL Browser" service?

(I know this sounds weired, but I had this problem once, I believe)

Additionally, are you able to log on to the SQL Server using the EV Service Account, and then opening up SQL Management Studio and creating a database?

(Or just run the SQL Management Studio somewhere it is installed under the EV Service Account)

Does that work?!

Cheers

Michel

[JesusWept3]

actually thats not weird, i've seen that resolve issues where the EV Reporting deployment utility can't connect to SQL Server when the browser service isnt running

[HolgerMu]

Hi MichelZ

SQL Browser Service up and running,

logging in over Management Studio successful, on local SQL machine and remote from EV-Server as evsa

[MichelZ]

And Database creation?

That's veeeery weird then... and I can't think of more stuff currently to check :(  but I'll keep thinking ;)

[HolgerMu]

Manual Creation of a DB works like a charm, even with the evsa logged into the SQL Management Studio.

Never had any issues like that in an EV Installation....

[HolgerMu]

here's a DTRACE...

[JesusWept3]

ok so its saying that the EnterpriseVaultDirectory database doesn't exist on the server
has the EV Configuration utility been run to create it?