Start a Conversation

Unsolved

This post is more than 5 years old

721

June 9th, 2015 01:00

Exchange 2013 Standalone with NMM 8.2.1 problems

Hello,


I am currently facing issues with the setup of a standalone Exchange 2013 Server with NMM 8.2.1:

When running the config checker; it always has 1 failure:

USER_SEND_AS_RECEIVE_AS_CHECK

The user SVC-Mail-Backup@essent-be.net does not have Send-As and Receive-As permissions. 
To fix the problem, open the Exchange Management Shell and execute the following command at the prompt: 
get-ExchangeServer ESSENTV-MAIL-02 | Add-AdPermission -user SVC-Mail-Backup@essent-be.net 
-extendedrights Receive-As, Send-As


We have performed the required command (see attached Add-ADPermission result.jpg).

But the configchecker keeps on saying that the permission has not been set.

Also when I run a backup job I get


100049:nsrsnap_vss_save: Unable to determine jobd version, assuming version 7.3: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

65208:nsrsnap_vss_save:d:\views\nw\8.2.1\nsr\vssclient\snapvsssave\nsrsnap_vss_save.h(225): Error initializing the job.

    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

    NetWorker Server XXXXXXX-bck-01.XXXXXXX is unavailable or does not support Jobs Daemon.


But the job continuous and somewhat later it gives:

The term 'Get-DatabaseAvailabilityGroup' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

...

136584:nsrsnap_vss_save:NMM .. Exchange Shell Exception Object reference not set to an instance of an object. in function GetServersDAG

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

...

The term 'Get-MailboxDatabaseCopyStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

...

136558:nsrsnap_vss_save:NMM .. Exchange Shell Exception Object reference not set to an instance of an object. in function IsMounted

136553:nsrsnap_vss_save:NMM .. Exchange2010 Shell interface is unavailable. This may indicate that the EMC powershell library was not properly registered.

...

regards and thanks for any help

Steven

1 Attachment

No Responses!
No Events found!

Top