NetWorker: Exchange backup fails with error: nsrnmmsv Exchange2010 Shell interface is not initialised

The NMM Exchange backup or the command "nsrnmmsv -P" fails with the error:

Exchange2010 Shell interface is not initialised.

As example:

C:\Users\Administrator>nsrnmmsv -P
17092:nsrnmmsv: Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrnmmsv.exe: Original file name: nsrnmmsv.exe Version: 9.1.1 (ntx64)
Comments: Supporting Microsoft Volume Shadow Copy Service
Changing backup name EX01N3 to primary name ex01n3.group.com for multi-NIC configured client.
136553:nsrnmmsv: NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.
111867:nsrnmmsv:Exchange2010 Shell interface is not initialised.
145370:nsrnmmsv: Initialization error -- Exchange shell failed to initialize. Required for Exchange.
117296:nsrnmmsv: Failed to list supported save sets.
102332:nsrnmmsv: Exiting with success.

The error message "Exchange2010 Shell interface" is not initialised it is basically due:

• NetWorker lib cannot initialize the Exchange Powershell (See KB 493540 - Exchange 2010 DAG fails due to powershell issues).
• The user invoking the lib does not have the right permissions to run the shell.
• Very rare cases the Exchange Powershell is broken under IIS configuration that cannot be performed.

Check if the registry entry exists and in this case compare the entry with one of the working Exchange node:

reg query HKEY_LOCAL_MACHINE\software\legato\networker\vssclient

If it does not exist, proceed with these steps:

1. Create the following registry keys under: HKEY_LOCAL_MACHINE\software\legato\networker\vssclient

   *** N.B. Put the appropriate username and domain name.
   Exchange Username        REG_SZ                admin
   Exchange Domain          REG_SZ                fall.localdomain
   Exchange Password        REG_BINARY

   <example>
   Username= just the username ex: backup.manager
   Domain= ex: BWK.com

   Note: Exchange Domain is the domain level of the Exchange server, not the user account. If the domain account is at a different level (that is, child.fall.localdomain), edit the domain to match the user domain, or create a new user in the exact same domain level as exchange server.

2. Then run the NMM Exchange Admin configuration tool and choose Update admin password. If this is successful, it should update the Exchange Password registry key.

3. Then run the command to test the Exchange node connectivity:

   nsrnmmsv -P