Network Path Not Found Error in Exchange 2010 Management Console

by Mike Pfeiffer on May 9, 2010

I've seen this issue mentioned a couple times now, so I figured I'd post about it here in case anyone is searching for a solution. When accessing the properties of a transport server in the Exchange Management Console (EMC), you may receive an error similar to the following:

An error occurred while accessing the registry on the server "CONTOSO-EX01". The error that occurred is: "The network path was not found". It was running the command 'Get-AntispamUpdates -Identity 'CONTOSO-EX01'.

This will happen either on an Edge Transport server, or a Hub Transport server with the Antispam agents installed. The resolution is typically one of the following:

  1. Enable File and Printer Sharing – go into the properties of the network connection on the server and make sure that File and Printer Sharing is enabled. You may notice that even after enabling File and Printer Sharing, you still get the error when launching EMC. If you are still getting the error after enabling File and Printer Sharing, a server reboot should resolve the issue.
  2. Start the Remote Registry Service – open the services panel and make sure that the Remote Registry Service is running and configured for automatic startup. I tested this out in my lab; I set the startup type for the service to manual and rebooted the server. Of course, I was able to reproduce this error when launching EMC, but even after starting the service I was still getting the error. Configuring the service to start automatically and rebooting the server resolved the issue.

If you have multiple transport servers, you should verify these settings on each one. Also, please come back and comment on whether or not these steps resolve the issue.

Related Posts

{ 1 trackback }

Tweets that mention Network Path Not Found Error in Exchange 2010 Management Console -- Topsy.com
May 9, 2010 at 11:37 am

{ 2 comments… read them below or add one }

Scott Daniel May 21, 2010 at 8:18 am

Thanks! All I did was set remote registry to automatic and started the service, no restart was required. By the way, this error happened after I installed Update Rollup 3 (thank microsoft for another update that broke exchange).

Reply

Mike Pfeiffer May 21, 2010 at 8:33 am

Great, thanks for your comment Scott. Glad you were able to solve the issue.

Reply

Leave a Comment

Previous post:

Next post: