Unfortunately i don't remember the solution and I should have updated this string with the solution. I guess you are trying to run the NMSQL client from the client in the above screenshots. Have you tried to switch of UAC in Windows or try to run the NMSQL as Administrator?
Yes, I've tried to run the NMSQL as Administrator.
We cannot switch of the UAC because we cannot reboot the server at this moment.
The strange thing is that the instance name in the "Select SQL Instance" window seems to be wrong.
It shows me <physikal hostname>\<instance name> but ist should be <virtual name>\<instance name>.
Have you tried adding *`@* to all the nodes? This test will determine wether this is permissions related or not.
Also, have you created a client entry per SQL instance?
I would suggest to create one client per SQL instance as follows:
Client for inst1
Client for inst2
Client for inst3
Client for inst4
do you mean adding this to the Remote Access field?
I've added this to all nodes (physical and virtual) but it did not help.
Yes, I've created one client per SQL instance.
What user are you loged in as? Did you use a SQL admin to login on to the SQL server and then mopen NMSQL?
What do you have in the list of NW admins in NMC?
I've tried with SQL service user (domain user), lokal admin and own domain user. All users have sysadmin rights.
I've added the physical hosts to the administrators list in NMC... doesn't work.
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?
nsrsqlsv.exe -D5vvv -s NW_SERVER_NAME -c client_name -a virtual_name -g group_name -l full DBNAME
nsrsqlsv.exe -D5vvv -s nwserver01 -c instance1 -a instance1 -g SQL_full -l full ITDB