Symantec Enterprise Vault Installation on SBS 2003

Hi all - first post.

I've got users rapidly approaching 1GB Exchange mailbox sizes and trying to teach them email management practices is all too hard for them, so I've taken the plunge on advice given on other posts and purchased Symantec Enterprise Vault. I researched it pretty extensively and it seemed to be able to solve all our troubles automatically at the server level. After all the excitement with this product, I'm now in sheer frustration during install.

So it's on an SBS Server (which I found out after purchase is technically not supported although I've heard people getting it to work). For now, we're using MS SQL Server 2005 Express even with its limitations, however Symantec have advised me that Express Edition is supported.

Using the Enterprise Vault Configuration wizard I have set the Enterprise Vault Services account as Administrator. However I'm getting stuck on the SQL Server location screen. I installed SQL Express on the data partition (D:) at D:\Microsoft SQL Server\. I've tried entering the following into the SQL Server location field:
      D:\Microsoft SQL Server\MSSQL.1\MSSQL\Data

However I get the following error dialog:

"Failed to connect to SQL Server 'D:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\'. Check that: - this SQL Server exists and is running - your Vault Service account has the correct privileges.

Any help is hugely appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you sure you should be entering the physical database location, and not the server connection information (which would be <servername>:1433 by default, or \\<servername\pipe\sql\query if you're using named pipes)?
swannporAuthor Commented:
Thanks for the suggestions RWigley. Tried both \\SERVER\pipe\sql\query and SERVER:1433 with the same results. How should I check that port 1433 is connected to SQL?
By following the information in this article!  :)
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

swannporAuthor Commented:
Well that certainly was part of the problem, I guess, but still getting the error. Went into SQL configuration and realised that both TCP and Named Pipes protocols were disabled. I enabled them and then restarted the SQL service but I'm still getting the same error with both \\SERVER\pipe\sql\query and SERVER:1433
swannporAuthor Commented:
More to add. I've installed SQL Server Management Studio Express to ensure it's not an access permissions problem. I have added the relevant account (Windows authentication) into the Logins list with a dbcreator role. However, I still can't connect to the SQL Server.

Here's the error messages:

SQL Server Connectivity -> SERVER:1433: NamedPipes (NO), TCP/IP (NO)

SQL Server Permissions -> Test Failed for the following reason:[DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection
When Enterprise Vault configuration asks for the SQL server *location*, it wants the *name* of the SQL Server, not the local path fo rthe database files. That got me the first time I installed it too!

If you want to use the default instance of SQL, then it's just the NETBIOS name of your SQL Server (eg: SERVER) in the example above. If you are using named instances (eg: SERVER\MYINSTANCE), then use the name of the instance SERVER\MYINSTANCE.

Once the connection is established, and you move to the next Wizard dialog box, Enterprise Vault will ask for the location of the databases and logs. At that point, you enter the local path of where you want EV files *on the SQL server* (eg: D:\MSSQL\SQL_DATA\EnterpriseVault\ and D:\MSSQL\SQL_LOGS\EnterpriseVault). Enterprise vault will then create the filenames according to its own naming conventions on the SQL server.

- make sure the Vault Service Account has DB CREATOR privileges
- make sure the local paths on the SQL server exist and are allow full control effective rights for the Vault Service account

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
swannporAuthor Commented:
Problem solved. Ended up loading MS SQL Server Management Studio Express, given that I am running this on SQL Express Edition. This let me get in and fix the permissions issue. Enterprise Vault now happily running and users now happily using declogged Outlook inboxes!

Thanks all for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.