Deployment scanner : Unable to connect to server - for SQL server

[Sarah_Seftel1]

Hi,

Customer installed SQL version  11.0.3393.0 (which is 2012 SP1)

Deployment scanner reports:

At least one of the SQL permissions tests for user Domain\evadmin produced an error.

 
 Domain-ARCHIVE: Unable to connect to server. 

tried all the things I've seen in tech notes here:

Check that evadmin has sysadmin, that default DB set to master, tcp & name pipes are enabled.

Any ideas what else can I check?

BTW - ev & sql are on same server

Sarah

[TonySterling]

Is there an instance?  So instead of SQL it should be SQL\instance name?

Are you running DS as the EV Service account?

[Arjun_Shelke]

You can try using both, NetBIOS and FQDN of SQL Server, sometimes one these does not work.

[Nups]

Hi Sarah,

You may want to have a look at the following technote :

http://www.symantec.com/business/support/index?page=content&id=TECH187542

[RahulG]

Is the windows firewall Enabled on the SQL server ? 

Does your VSA account have local rights on the SQL server ?

[Sarah_Seftel1]

Hi Tony,

No instance, running the DS with VSA account, VSA have sysadmin, dbcreator & public on SQL (and the SQL is installed on EV server)

[Sarah_Seftel1]

Hi,

I've tries both options and get the same result for both of them.

[Sarah_Seftel1]

SQL server is on the EV server. Firewall is on by company poclicy, but since they are on same server - can FW affect the deployment scanner?

VSA is sysadmin, dbcreator & public on SQL.

SQL is installed on EV server - all running under VSA account.

[Sarah_Seftel1]

Hi,

I've tried this as well before posting here, all steps there are configured correctly (masterdb) and ODBC checks OK.

[Arjun_Shelke]

You can DTrace DeploymentScanner process while you run to get more information about the error.

[Sarah_Seftel1]

Installed the binaries.

rebooted server after install.

run dtrave on Deployment_Scanner.

running deployment scanner, getting file with no logging of anything at all. (attached)

[Shaun_Wright]

Hi

Open SQL Server Management Studio and Expand Security | Logins and Access the properties of Enterprise Vault Service account. Check the Default Database as it has to be Master and not any other database selected.

[Sarah_Seftel1]

Thiw was done in my first checks.

DB is set to Master.

ontacted Symantec, they cannot find the issue.

We will try and do the configuration on a new site and see in real time if he can connect to SQL or not, we are starting to believe it's just a bug in the deployment scanner on server 2012...

Will update.

[Sarah_Seftel1 · Accepted solution]

Hi all,

After investigation we found out the issue.

The SQL was installed by outsource person who used customized SQL for SAP installation.

Unfortunately when we talked to him he assured us that the installation was standard.

we tried to connect to another SQL in the organization and succeeded.

We got the SQL person to uninstall and reinstall the SQL, this time as standard SQL installation and not SQL SAP (which I have no idea what this even means).

Anyway - EV connects to SQL now.

Thanks for all your help and advices!