The name resolution is good.

nsrsqlsv.exe from command line is working.

Hi Daniel,

Is there a good name resolution for all the SQL instances?

Have you tried to run the commands from command line in debug mode to see what is going on?

For instance:

nsrsqlsv.exe -D5vvv -s NW_SERVER_NAME -c client_name -a virtual_name -g group_name -l full DBNAME

for example_

nsrsqlsv.exe -D5vvv -s nwserver01 -c instance1 -a instance1 -g SQL_full -l full ITDB

Thank you.

Carlos.

Have you tried to configure the backup as follows?:

In order to back up a named instance, specify the following saveset in the SQL client's instance:

MSSQL$(instance_name)

To back up a database in the named instance, specify saveset:

MSSQL$(instance_name):(database name)

Thank you.

Carlos.

Did you ever find the solution for this?  One of my SQL clusters has exactly the same symptoms, however 2 of the instance names are detected correctly and working, the remainder aren't and they are all setup identically in NetWorker.

no, I don't remember the solution and it's been a while. It was stupid of me not updating this thread with the solution. Sorry

Are you sure you have MSSQL license for all the instances? As I seem to remember each unique instance uses 1 MSSQL license

With the same username/password are you able to login to all the instances via the SLQ Management studio ?

Hi all,

Was working with EMC support on another issue today and brought this up with them.  It was a basic DNS reverse lookup error.

When resolving the hostname it was fine, when resolving the IP it was pointing to an incorrect host.  Updated the DNS records and the Networker client for SQL worked fine.

Should have been the first thing I looked at, Networker client issues are usually DNS related.

Problem solved.

Hi Team,

We are facing similar issue in our environment, and everything on DNS end looks perfect......do you have anyother point that can cause this error?

Hi Suraj,

Can you test DNS like so:

C:\Users\xxxx>ping xxxx Pinging xxxx.local [xxx.16] with 32 bytes of data: Reply from xxxx.16: bytes=32 time<1ms TTL=254 Reply from xxxx.16: bytes=32 time<1ms TTL=254 Ping statistics for 1xxxx.16:     Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\xxx>

Then check reverse DNS:

C:\Users\xxx>ping -a xxx.16 Pinging xxx.local [xxx.16] with 32 bytes of data: Reply from xxx.16: bytes=32 time<1ms TTL=254 Reply from xxx.16: bytes=32 time<1ms TTL=254 Ping statistics for xxx.16:     Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\xxx>

If the ping -a doesnt resolve the IP to a hostname then you have something wrong with DNS.  Could you confirm that please?

Failing DNS, make sure you run the client as administrator.

Hi Callump,

Thanks for your quick reply....We have done a through check of DNS, everything is good. Also run as administrator didnt bring any change...have tried doing every possible step, but all in vain. Strange thing is backups are working perfectly fine. Only issue is with opening GUI.

EMC has recommended to re-register SQLVDI.dll and check. if this doesnt work, we will have to disable IPv6 which is enabled today in our SQL server and continue searching for a solution

Hi ,

We are facing similar issue in our environment , how did you managed to fix it ?

Thanks and regards

Alex