No Active SQL Servers found in this system

Question

Hi all, We are having a issue with the new installation of BSM of SQL on DSN.Our enviorenment is the following: Backup Server: Windows 2003 SE SP2 x86 NetWorker 7.3.3 DSN Windows 2003 SE SP2 x86 NetWorker 7.3.3 BSM for MSSQL 5.1 MSSQL 2005 EE x86 After installing the module, we checked as the backups of MSSQL worked fine by Backup Server initiated backups but when we tried to open the nwmssql to make a restore, we could see the message error: No Active SQL Servers found in this system The DNS resoltion works fine and the MSSQL Server isn't a Cluster. Thanks in advance.

HabibG2 · Answer

Where did you initiate the Restore? On the Server?The Restore has to be initiated on the Client where the SQL module is installed.

HabibG2 · Answer

Try initiate a backup from the SQL server.On the server initiated backup what save command are you using?What Save set have you specified?

smora1 · Answer

The Restore was initiated on the Client where the BSM for SQL is installed.

smora1 · Answer

When I try to initiate a backup from SQL Server NetWorker shows me the same error:

No Active SQL Servers found in this system

This message is just showed when the nwmssql is opened and no actions are permitted.

The Server initiated backup works fine because it's perfectly configured. It isn't the first time that I have configured the BSM for MSSQL but it's the first time that I'm getting this error

Thanks for your response.

smora1 · Answer

The SQL Agent has always be running.One thing I have just discovered is that if I install the BSM for MMSQL 3.1 the nwmssql is opened rightly and it doesn't show the mentioned error.

dgreggs1 · Answer

I would venture a guess and say that we you attempt to do the restore or backup and you receive that message that the SQL Server Agent is not running. The NMSSQL uses the agent for certain actions like discovering an active instance of SQL.

Check and start the SQL agent if it is not running then try the restore or backup that you attempted before.

Thanks,

Dana

smora1 · Answer

What is your opinion about the problem could be due to the ODBC connector is pointed to a wrong location? I know now this SQL Server firstly had a MSSQL 2000 before updating to MSSQL 2005 and this could make a missconfiguration on the system. Do you agree?

Thanks a lot.

ble1 · Answer

I wonder if you would get the same error if you would have 7.4 installed... I know it sounds strange, but I still wonder

smora1 · Answer

I have installed 7.4 but it hasn't resolve the issue.Thanks.

smora1 · Answer

Any new idea?

ble1 · Answer

If it works for you under 3.1 and not 5.1 then it is either something with configuration or bug in module build you have. AFAIK there is a different build for initial one for 5.1 so you may wish to check it out.

smora1 · Answer

We have installed the same build on other SQL Server and it is working fine without showing this 'bug'. I don't know where I can see anything more that can help me...

ble1 · Answer

It is probably some sort of configuration that differs... have support give closer look to identify what is causing it.

NetWorker

Was this post helpful?