Link to home
Start Free TrialLog in
Avatar of Asfour Crystal
Asfour CrystalFlag for Egypt

asked on

exchange2010 test connectivity error

hello,
i've exchange 2010 sp34 on windiows 2008 r2 i get this error in my monitor program (SCOM) {tcp connectivity against local server - rpc client access failure (logon) and HTTP:connectivity against local server - rpc client access failure (logon) } how can i fix that i don't need to change the service logon name from network service to local system i tried it but nothing changed
SOLUTION
Avatar of Ajit Singh
Ajit Singh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,
SCOM uses powershell cmdlets(EMS) to monitor Exchagne environment, it will triggers operations manager alerts if a problem is detected.
In your case, Test-OWAConnectivity cmdlet triggers this event.

Test-OwaConnectivity cmdlet triggers this alert. The Test-OwaConnectivity cmdlet can be used to test the connectivity of all Microsoft Exchange Server 2010 Outlook Web App virtual directories on a computer that is running Exchange 2010 and that has the Client Access Server (CAS) server role installed.
This cmdlet can also be used to test the connectivity of a single Exchange 2010 Outlook Web App URL.
SCOM rule could not call the Test-OWAConnectivity cmdlet that triggered alert.

To see more about RPC/Http issues ,please have a look
https://technet.microsoft.com/en-us/library/hh361493(v=exchg.140).aspx

Thanks
Avatar of Asfour Crystal

ASKER

thanks guy for trying help, do you mean Dinesh Babu that the scom has its own that can't test it in right way also because the users didn't complain from any issue related to the outlook can't connect or retrieve the data from exchange server
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial