Hello FolksI have been on exchange 2007 since Nov 2008, since October my Hub server displays errors and errors out when I open EMC or EMS. It works fine on clinet workstations and my exchange database server.Errors: at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.ClosePipeline(MonadAsyncResult asyncResult) at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult) at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.Execute(WorkUnit[] workUnits) at Microsoft.Exchange.Management.SnapIn.Esm.MasterDataSet.ExecuteWithWorkUnit(MonadCommand command, WorkUnitCollection workUnits) at Microsoft.Exchange.Management.SnapIn.Esm.MasterDataSet.LoadServers(MonadConnection connection, String serverName, Boolean& needLoadUMServers, Boolean& isEdge, Boolean& isHubTransport, Boolean& isMailbox, Boolean& isClientAccess, WorkUnitCollection refreshWorkUnits) at Microsoft.Exchange.Management.SnapIn.Esm.MasterDataSet.InternalLoad(IProgress progress, String serverName) at Microsoft.Exchange.Management.SnapIn.Esm.MasterDataSet.loadWorker_DoWork(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) The term 'get-ClientAccessServer' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again. at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName) at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin) at System.Management.Automation.CommandFactory._CreateCommand(String commandName, CommandOrigin commandOrigin) at System.Management.Automation.CommandFactory.CreateCommand(String commandName, CommandOrigin commandOrigin) at System.Management.Automation.Runspaces.Command.CreateCommandProcessor(ExecutionContext executionContext, CommandFactory commandFactory, Boolean addToHistory) at System.Management.Automation.Runspaces.LocalPipeline.CreatePipelineProcessor() at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper() at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()[PS] H:\>get-clientaccessserverThe term 'get-clientaccessserver' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.At line:1 char:22+ get-clientaccessserver <<<<I can run it anywhere else get vaild answer; but on the hub server itself I get it an invaild cmdlet.Any ideas???

I would run ExBpa against the server.ANything in the event logs?What SP and rollup level?Personally, if you cant solve it in a reasonable time, I would just build another hub transport server, and then uninstall Exchange from this one, wipe it clean and rebuild.

Hi,Please ensure that all the exchange server has been in the same version.Besides,please check the value on the following registry,it should be Microsoft.Exchange.Management.PowerShell.AdminPSSnapInHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Excha nge.Management.PowerShell.Admin\CustomPSSnapInTypeRegards,Xiu

Andy,No - nothing in the logsSP1 rollup 9===============I wish; my company would rather run it to the ground before something gets done

Xiu,I did a [PS] H:\>Get-ExchangeServer | fl name,edition,admindisplayversion Name : HUB <---Displayed answerEdition : Enterprise AdminDisplayVersion : Version 8.1 (Build 240.6) Name : EXCHQ <----Displayed answerEdition : EnterpriseAdminDisplayVersion : Version 8.1 (Build 240.6)But when I do on the HUB: But works on exchq our DB server [PS] H:\>get-clientaccessserverThe term 'get-clientaccessserver' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.At line:1 char:22+ get-clientaccessserver <<<<The registry shows Microsoft.Exchange.Management.PowerShell.EdgePSSnapIn for the client access server instead of the Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn you mentioned. On the exchq DB server the it shows the correct one: Microsoft.Exchange.Management.PowerShell.AdminPSSnapInDo I add this in and reboot?ThanksJoe

Hi,Please modify the value to Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn and then check the issue again.Regards,Xiu