MS SQL Agent: Application connection failed for servername\.

[Sergey_Korshuno]

Hi

We have deployed new server:

OS: Windows Server 2008 R2 x64

DB: MS SQL Server 2008 R2 x64 Express

But netbackup SQL Agent can't connect to the instance with correct sa account:

---------------------------
NetBackup Database Extension
---------------------------
Application connection failed for SERVER01\. Please select a different SQL Server host and instance,
or press 'cancel' to exit the NetBackup for SQL Server Graphical User Interface.
---------------------------
OK   Cancel   
---------------------------

We tried to disable UAC and run As Adminisrator, but without success

We installed update 7.0.3 but id didn't help

We've also checked Remote Registry service, its state is started

This NB SQL Agent can connect to another SQL Server (with win 2003 x86-32), but can't connect to his own server.

[MKT · Accepted solution]

If you are using Windows Authentication mode,SQL Server ignores the user ID and password
that you provided in the SQL Server connection properties dialog box.  The 'sa' account becomes irrelevant as it is not being used.   What is being used is the account you logged into the box with.  Check that account in SQL and give it 'sa' rights and the connection should be successful.

[Sergey_Korshuno]

If you are using Windows Authentication mode

Server in mixed mode

Server ignores the user ID and password that you provided in the SQL Server connection properties dialog box.  The 'sa' account becomes irrelevant as it is not being used.

I can use "sa" accuont from any other apps, it works.

[Marianne]

Have you tried to start NBU client service as SQL admin account?

Do you have dbclient log on this machine to troubleshoot?  See this TN: http://www.symantec.com/docs/TECH73128

Another possibility is when SQL is configured to use a port other than the default 1433.
See this TN: http://www.symantec.com/docs/TECH155299

[Sergey_Korshuno]

After creating new user account in MSSQL (from my windows domain user) and granting sysadmin role to it, the problem was solved. It seems, developers remove windows admin group from MSSQL.

Thanks to ALL