Cannot access PowerShell or EMC
Anyone can tell me what the deal is here. Yesterday my production server went offline. So I immediately shut down DAG passive copy server in DR site. I brought back online in orderly fashion and both DB's copies eventually went back to healthy. This morning I saw that one DB copy was suspended - the other was healthy. So I went to the passive DAG server and cannot open EMC or connect locally or remotely to powershell - Access denied. I shut this exchange server down. Rebooted the local DC controller, forced AD replication, waited, then brought it back online. Same thing - Not getting any errors, all exchange services are running. Any help suggestions - I see similar problems on these boards, but no resolution. VERBOSE: Connecting to gbdrml.domain.com [gbdrml. domain.com] Connecting to remote server failed with the following error message : Access is denied. F or more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to GBDRML. domain.com [gbdrml. domain.com] Connecting to remote server failed with the following error message : Access is denied. F or more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to gbmail02. domain.com [gbmail02. domain.com] Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to gbmail02. domain.com [gbmail02. domain.com] Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed VERBOSE: Connecting to GBDRML. domain.com [gbdrml. domain.com] Connecting to remote server failed with the following error message : Access is denied. F
June 16th, 2011 12:13pm

Did you verify that all services are running?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2011 5:36pm

"brought it back online. Same thing - Not getting any errors, all exchange services are running. " It is working now.
June 16th, 2011 5:37pm

What about Windows Remote Management?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2011 5:54pm

What happens if you try a command on your active mail server like: Get-MailboxDatabaseCopyStatus -Server gbmail02 ? Does this yield any results?
June 17th, 2011 1:11am

Hi, First please ensure that IIS server is running normally. Then please verify if the Time on the Exchange Server is in sync with the Domain Controller by running following from cmd prompt: Net time \\DCNAME <file://\\dcname> If the time is not in sync, run: Net time \\dcname <file://\\dcname> /set Please try to manually load EMS via the following steps: 1. Start normal Windows PowerShell. 2. Navigate to c:\Program Files\Microsoft\Exchange\V14\bin 3. Run remoteExchange.ps1 If all the above do not help, then please try to run ExBPA to check the server health. Also please check event log and then post the relevant error event here. Regards, Xiu
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2011 3:20am

It had something to do with good ole FSW and Quorum - updating things to quickly and then not quick enough. We lost power the other day. And once active copy went down - quorum does its thing and screws up the DAG. I have activation policy blocked because we use DAG for DR not HA. But when you have a two server DAG quorum seems to act up. It would not mount active database after bringing server back online. I tried to manually mount them and got quorum errors - then I brought the passive back online - and was then able to manually mount the active copy. So basically if my active goes down even though I have activation set to blocked FSW / quorum still goes ahead on the DAG side and moves to the passive - even though both the active and passive server will not let them be activated by the FSW. If you are allowed to disabled auto-activation of a passive / active copy - then you should be able to remove the FSW from you ENV - it serves no purpose.
June 17th, 2011 9:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics