Share via

Enter the server fqdn where you want to connect exchange 2013

  • Article

Question

Wednesday, November 18, 2015 7:50 PM

*VERBOSE: Connecting to PNL-EX2013.petenetlive.net.
New-PSSession : [pnl-ex2013.petenetlive.net] Processing data from remote server pnl-ex2013.petenetlive.net failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully.
Change the request including a valid shell handle and try again. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1

  • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
  • CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
  • FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:*

All replies (3)

Thursday, November 19, 2015 3:05 AM ✅Answered

Hi,

For your question, please open IIS management and switch to Site, right-client Exchange Back End and select Bings, then select HTTPS and click Edit to change the SSL Certificate to "Microsoft Exchange". Figure as below:

Then reopen EMS to double check.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Allen Wang
TechNet Community Support

Sunday, August 25, 2019 3:58 PM

I try opening EMS and I get the same error. I follow your direction and still get the same error. Any ideas?

     Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Show quick reference guide: QuickRef
VERBOSE: Connecting to Exchange2019.XXX.local.
New-PSSession : [exchange2019.xxx.local] Connecting to remote server exchange2019.xxx.local failed with the following
error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using
Kerberos authentication: A specified logon session does not exist. It may already have been terminated.
 Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
 After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or
use HTTPS transport.
 Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more
information, see the about_Remote_Troubleshooting Help topic.
 Other Possible Cause:
  -The domain or computer name was not included with the specified credential, for example: DOMAIN\UserName or
COMPUTER\UserName.
At line:1 char:1

  • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : 1312,PSSessionOpenFailed
VERBOSE: Connecting to Exchange2019.xxx.local.
New-PSSession : [exchange2019.gcs.local] Connecting to remote server exchange2019.xxx.local failed with the following
error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using
Kerberos authentication: A specified logon session does not exist. It may already have been terminated.
 Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
 After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or
use HTTPS transport.
 Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more
information, see the about_Remote_Troubleshooting Help topic.
 Other Possible Cause:
  -The domain or computer name was not included with the specified credential, for example: DOMAIN\UserName or
COMPUTER\UserName.
At line:1 char:1

  • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : 1312,PSSessionOpenFailed
VERBOSE: Connecting to Exchange2019.XXX.local.
New-PSSession : [exchange2019.xxx.local] Connecting to remote server exchange2019.xxx.local failed with the following
error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using
Kerberos authentication: A specified logon session does not exist. It may already have been terminated.
 Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
 After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or
use HTTPS transport.
 Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more
information, see the about_Remote_Troubleshooting Help topic.
 Other Possible Cause:
  -The domain or computer name was not included with the specified credential, for example: DOMAIN\UserName or
COMPUTER\UserName.
At line:1 char:1

  • New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : 1312,PSSessionOpenFailed
Exception calling "FindAll" with "0" argument(s): "Unknown error (0x80005000)"
At C:\Program Files\Microsoft\Exchange Server\V15\bin\ConnectFunctions.ps1:253 char:2
+     $search.FindAll()
+     ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : COMException

_AutoDiscoverAndConnect : No Exchange servers are available in any Active Directory sites. You can't connect to remote
Powershell on a computer that only has the Management Tools role installed.
At C:\Program Files\Microsoft\Exchange Server\V15\bin\ConnectFunctions.ps1:45 char:4
+             _AutoDiscoverAndConnect $credential $Forest -useWIA:$useW ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,_AutoDiscoverAndConnect

Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:





Friday, June 12, 2020 11:27 AM

- Open CMD and enter the command :- whoami

  • Once the login username *** is confirm.
  • Open the Active Directory Console.
  • Search for the server ***.
  • Now go into Member Off and add the Group:- Organization Management
  • Click Okay.

Now, you shall be able to access the Exchange Power Shell Console. 

Second Method:-

  • You can use the windows power shell into order to access the Exchange Power Shell console. 

Please use the below command in the windows powershell.

Add-PSSnapin *exch*
Get-MailboxDatabaseCopyStatus

Please mark it resolved once the issue is fixed.