Unable to connect to server:RPC send operation failed

Yes you have to run client side. You can download it support.emc.com . Also its included on NMM 2.4

Ahmet KEÇECİLER

Teknik Danışman

e-Çözüm Bilişim

Hi Ahmet,

I dont find this NMM config checker. I have uninstalled NMM and installed netowrker module for microsoft.SQL server : Ver: 5.2.2

But still when I open networker user for SQL getting below error

66212:nwmssql: cannot login to SQL server

Please help

Ok . This about the user that you use for login to server. This user must have acces to sql . just give your user to acces rights to be able to login to sql .

Ahmet KEÇECİLER

Teknik Danışman

e-Çözüm Bilişim

Srinu943 wrote: I dont find this NMM config checker. I have uninstalled NMM and installed netowrker module for microsoft.SQL server : Ver: 5.2.2 But still when I open networker user for SQL getting below error 66212:nwmssql: cannot login to SQL server Please help

This is most likely your user who doesn't have proper SQL right.  For example, I just removed myself from SQL admin list and in that case I get:

This is an issue when your user doesn't gave access to SQL - talk to SQL admin for details.  Also, bare in mind, when running scheduled backup then access is done via SYSTEM which also means that local admin level should also be allowed to access SQL.

Last hint, make sure you use 5.2.2 build 28 and not 23 (GA) as there are some fixes inside which will make your life easier (not related to your original topic).

I have checked with SQL Admins, they also getting the same error below

Ok just try to logon to the sql management studio with the user .

Ahmet KEÇECİLER

Teknik Danışman

e-Çözüm Bilişim

It might be your color scheme, but screenshots you showed seem to indicate this is windows 2012?  So, what is OS and SQL version that you run on that box?  daemon log, is that from client?  Inside we see some name resolution issue, but I also saw few names which made me wonder if this is cluster?

I can see from daemon log that "

39076 9/20/2013 8:30:50 PM  0 0 2 3392 13608 0 edvxedwsqlcp02b.redmond.corp.micr

osoft.com nsrexecd SYSTEM warning: DNS lookup failed for 10.245.119.40       EDV

XINFNTWCP01.redmond.corp.microsoft.com: No such host is known."

But RPCinfo, ping & nslookup is working fine

C:\Users\v-srgand>rpcinfo -p  EDVXINFNTWCP01.redmond.corp.microsoft.com

   program vers proto   port

    100000    2   tcp   7938

    100000    2   udp   7938

    390436    1   tcp   8505

    390435    1   tcp   8742

    390113    1   tcp   7937

    390402    1   tcp   9001

    390103    2   tcp   8599

    390109    2   tcp   8599

    390110    1   tcp   8599

    390120    1   tcp   8599

    390109    2   udp   9399

    390105    5   tcp   8366

    390105    6   tcp   8366

    390433    1   tcp   8552

    390438    1   tcp   9146

    390107    5   tcp   8443

    390107    6   tcp   8443

    390111    1   tcp   8906

    390104  505   tcp   9608

    390104  405   tcp   9521

    390104  205   tcp   9347

    390104  305   tcp   9434

   program vers proto   port

    100000    2   tcp   7938

    100000    2   udp   7938

    390436    1   tcp   8505

    390435    1   tcp   8742

    390113    1   tcp   7937

    390402    1   tcp   9001

    390103    2   tcp   8599

    390109    2   tcp   8599

    390110    1   tcp   8599

    390120    1   tcp   8599

    390109    2   udp   9399

    390105    5   tcp   8366

    390105    6   tcp   8366

    390433    1   tcp   8552

    390438    1   tcp   9146

    390107    5   tcp   8443

    390107    6   tcp   8443

    390111    1   tcp   8906

    390104  505   tcp   9608

    390104  405   tcp   9521

    390104  205   tcp   9347

    390104  305   tcp   9434

Yes it's a SQL cluster and windows OS is 2012, SQL also 2012

Daemon is from client side only

First, what to use.  Since you have win2k12 and with SQL2012, if you check compatibility guide then you see that you must use NMM.  That means either NMM 2.4SP1 with NW8SP1/SP2 or NMM 3 with NW8.1 on client side.  So, forget NMSQL 5.2.2.

When you get NMM package, it comes with config checker so you may wish to start that one first,

As for name resolution, rpcinfo is not relevant (besides, you can have also program registered to RPC service and not responding for example).  What it says in logs is that at certain point your backup server could not be resolved on client and this may have been intermediate error - you may wish to update local hosts table to be on safe side.

Yes . I  have installed networker 8.0.2 only .. I have uninstalled and installed nw 7.6 to test.

Again installed nw 8.0.2 software in client.

Ran NMM config checker version 1.1.2.0

Please find the attachement for failures

It says :

Microsoft Windows Server 2012 Datacenter 6.2.9200 Current operating system is not supported.

Current installed version: 8.0.2 (Client) is not supported.

??

Kindly restart the daemon and check once again.

Before that cross check once again that Networker server Ip is pingable

then check the networker daemon services from the command nsr...

No. It looks it doesn't support for NMM 2.4.

I dont find NMM config checker nmm241_win_x64 package.

Please help

It's clear now . I ran NMM config checker for NMM 2.4 .

I am only getting error:

FAIL:  NETWORK_ADAPTER_STATUS

But there is no issue with network