Microsoft SQL server agent connection problem

[zheka]

Hi folks!

Do I need a regular BrightStor Client Agent for Windows installed at the server hosting Microsoft SQL 2000 server on top of the Microsoft SQL Server Agent?

I successfully installed the SQL server agent and have it configured with Windows Integrated Authentication. When I try to connect to the server from BrightStor Manager console I end up with an error: Failed to login to the Agent.

Same happens if I configure the SQL agent with SQL native authentication using sa username and respective password.

Thanks in advance,
Eugene

 

[GSC]

Hi,
No you don't. I also have a SQL 2000 without the client agent for windows and it's working splendid without it.
When you set the rights on the job first you need to set the rights for the server (i use a domain account to connect to my server) and then you'll need to set up the rights for the SQL server (i use the sa account here)


I hope you find this post helpful.

Regards,
GSC

 

[zheka]

Great advice, GSC, thanks, but I went through all of this. Doesn't work. I tried both domain administrator username and sa.
Speaking about the rights for the server. Does it mean that the account that I use is able to connect to the server if I am able to connect remotely with its credentials using Enterprise SQL Manager? All in all, I use the account that is a member of domain administrators group. The SQL server itself is using both SQL native and Windows integrated authentication.

Could there be anything else that I can check to troubleshoot it?

Eugene

 

[GSC]

Regarding the rights:
Before arcserve can connect to the SQL server it need to connect to "Windows". Is this server on the domain?
When you modify the backup job and go to the source tab and right click on the SQL server here you should set your "Windows account" security, a account that has is member of the local administrators group on your SQL server. Domain admin account is OK if your server is on a domain.

What you also can try is to use windows authentication for your SQL server, see if it works with that.


I hope you find this post helpful.

Regards,
GSC