Initialization Error when starting EMC on Exchange 2010
I have recently installed Exchange 2010 and Service Pack 1. I continue to get the error below every time I try to open EMC/Exchange Management Console.
The following error occurred while searching for the on-premises Exchange server:
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
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. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError
$true -CurrentVersion 'Version 14.1 (Build 218.15)''.
I've applied Servcice Pack 1 and Update Rollup 1 and 2 to the Service Pack. I've also been doing alot of reading aobut "WinRM" and I haven't found a soluion to my problem.
C:\Users\Administrator.AZALEA>winrm get winrm/config
Config
MaxEnvelopeSizekb = 150
MaxTimeoutms = 60000
MaxBatchItems = 32000
MaxProviderRequests = 4294967295
Client
NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = false
Auth
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
CredSSP = false
DefaultPorts
HTTP = 5985
HTTPS = 5986
TrustedHosts
Service
RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPerUser = 15
EnumerationTimeoutms = 60000
MaxConnections = 25
MaxPacketRetrievalTimeSeconds = 120
AllowUnencrypted = false
Auth
Basic = false
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
What am I missing?
January 30th, 2011 1:33pm
Hi,
You can try it resolve this problem by removing the feature WinRM IIS Extension from Windows Server 2008 R2 and then readding it.
Look at below post for detail troubleshooting:
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
Use the EMTshooter tool for a test. To download the tool, please refer to the link below:
http://msexchangeteam.com/archive/2010/12/07/457139.aspx
Some more information for WinRM related issue..
http://technet.microsoft.com/en-us/library/dd351136.aspx
http://social.technet.microsoft.com/Forums/en-US/winserverManagement/thread/716593d6-09f3-406a-8682-80b2d6ceb061
Anil
Free Windows Admin Tool Kit Click here and download it now
January 30th, 2011 11:41pm
I've read and blogs I've checked my IIS settings, checked the Exchange 2010 security groups. I've read the error message more closely and notice something that I think maybe key to my problem. Please read the error message below:
Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
I've also used the EMT Tool. It did not solve my problem I got the same message.
What does "The network path was not found" mean?
Where do I investigate the network path?
In my winrm config above there is nothing referencing network path. Where should I be looking?
Is there a winrm command that I should be using that will display the network path?
Thanks
February 1st, 2011 6:43am
When installing Exchange 2010 on a server there will be an Powershell folder installed on your Internet Information server.
Please look if this folder exists.
What happens when you start your Exchange shell. Does it work?
regards Thomas Paetzold visit my blog on: http://susu42.wordpress.com
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2011 11:29am
I usually find this is one of two issues:
Kerberos failures due to time skew (especially in virtualized environments), see this article for tips:
http://exchangeserverpro.com/exchange-2010-management-console-initialization-failed
Proxy settings not correct, see this article (title refers to CRL checks but article applies to management tools connections as well):
http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings
Paul Cunningham (MCITP) Get more Exchange tips and tutorials at: http://exchangeserverpro.com and the Exchange Server 2003 to 2010 Migration Guide: http://exchangeserverpro.com/exchange-2003-2010-migration-guide
February 1st, 2011 7:14pm
I do see the Powershell site under the "Default web Sites".
When I open the command line PowerShell I get the following message:
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> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #22:
Get all Win32 WMI information, such as Perfmon counters and local computer configurations. For example, type:
Get-WMIObject Win32_PerfRawData_PerfOS_Memory
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: cscdserver11.azalea.local
VERBOSE: Connecting to cscdserver11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
[PS] C:\Users\Administrator.AZALEA\Desktop>
I highlited my response above.
Free Windows Admin Tool Kit Click here and download it now
February 1st, 2011 8:09pm
This not a virtual environment for me a real server is in use. What does it mean that the network path not found?
Thanks
February 1st, 2011 8:14pm
I've read everything I can to resolve my issue. I've tried a number to different things. How do I resolve the Network Path not found? Where should I be looking?
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2011 6:25am
can you create a new powershell session from other computer ?
$session =new-pssession -configurationName microsfot.exchange -connectionuri
http://exchangeserver.domian.com/powershell -credential $cred
and supply credentials
Dhruv
February 2nd, 2011 8:46am
Hi,
The “Network Path not found” error is usually related to AD or network settings. At this stage, I suggest you open ADSIEDIT.MSC tool and check whether
any old server is listed in servers container. Also, please open Event Viewer and post the relevant application log here for research.
Thanks.
NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2011 10:08pm
Here is a list of the next steps in order to solve or get an idea of your incident. And give us a report of the result:
Locate listeners and addresses: (No output means WinRM is not installed)
winrm e winrm/config/listener
Localhost Ping:
(Successfully completing this step pretty much insure complete access to WSMan on the local system)
Winrm id
Further:
Check state of configuration settings:
winrm get winrm/config
Check the state of WinRM service:
winrm get wmicimv2/Win32_Service?Name=WinRM
Remote communication:
Locate listeners and addresses:
winrm e winrm/config/listener
Remote Ping:
(Successfully completing this step pretty much insure complete access to WSMan on the remote system)
Winrm id –r:machinename
Further:
Check state of configuration settings:
winrm get winrm/config -r:machinename
Check the state of WinRM service:
winrm get wmicimv2/Win32_Service?Name=WinRM -r:machinename
regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com
February 6th, 2011 8:46am
I used the command above and was able to get a prompt for credenitals. I entered a userid and password which was accepted. It then returned to the "PS" command prompt.
What's next?
thanks
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 4:55am
I went to ADSIEDIT.MSC I did not see a server container. Where should I be looking for this?.
Thanks
February 8th, 2011 5:07am
Here are the results of running "winrm" what is it telling that is is wrong and causing my problem?
C:\Users\Administrator.AZALEA>winrm e winrm/config/listener
Listener
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = 127.0.0.1, 192.168.10.11, ::1, fe80::100:7f:fffe%13, fe80::5ef
e:192.168.10.11%12, fe80::f935:f98b:f781:f29b%11
C:\Users\Administrator.AZALEA>
C:\Users\Administrator.AZALEA>Winrm id
IdentifyResponse
ProtocolVersion =
http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0
C:\Users\Administrator.AZALEA>
C:\Users\Administrator.AZALEA>winrm get winrm/config
Config
MaxEnvelopeSizekb = 150
MaxTimeoutms = 60000
MaxBatchItems = 32000
MaxProviderRequests = 4294967295
Client
NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = false
Auth
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
CredSSP = false
DefaultPorts
HTTP = 5985
HTTPS = 5986
TrustedHosts
Service
RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPerUser = 15
EnumerationTimeoutms = 60000
MaxConnections = 25
MaxPacketRetrievalTimeSeconds = 120
AllowUnencrypted = false
Auth
Basic = false
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
C:\Users\Administrator.AZALEA>
C:\Users\Administrator.AZALEA>winrm get wmicimv2/Win32_Service?Name=WinRM
Win32_Service
AcceptPause = false
AcceptStop = true
Caption = Windows Remote Management (WS-Management)
CheckPoint = 0
CreationClassName = Win32_Service
Description = Windows Remote Management (WinRM) service implements the WS-Management protocol for remote management. WS-Management is a standard web service
s protocol used for remote software and hardware management. The WinRM service l
istens on the network for WS-Management requests and processes them. The WinRM S
ervice needs to be configured with a listener using winrm.cmd command line tool
or through Group Policy in order for it to listen over the network. The WinRM se
rvice provides access to WMI data and enables event collection. Event collection
and subscription to events require that the service is running. WinRM messages
use HTTP and HTTPS as transports. The WinRM service does not depend on IIS but i
s preconfigured to share a port with IIS on the same machine. The WinRM service
reserves the /wsman URL prefix. To prevent conflicts with IIS, administrators s
hould ensure that any websites hosted on IIS do not use the /wsman URL prefix.
DesktopInteract = false
DisplayName = Windows Remote Management (WS-Management)
ErrorControl = Normal
ExitCode = 0
InstallDate = null
Name = WinRM
PathName = C:\Windows\System32\svchost.exe -k NetworkService
ProcessId = 164
ServiceSpecificExitCode = 0
ServiceType = Share Process
Started = true
StartMode = Auto
StartName = NT AUTHORITY\NetworkService
State = Running
Status = OK
SystemCreationClassName = Win32_ComputerSystem
SystemName = CSCDSERVER11
TagId = 0
WaitHint = 0
C:\Users\Administrator.AZALEA>
C:\Users\Administrator.AZALEA>winrm e winrm/config/listener
Listener
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = 127.0.0.1, 192.168.10.11, ::1, fe80::100:7f:fffe%13, fe80::5ef
e:192.168.10.11%12, fe80::f935:f98b:f781:f29b%11
C:\Users\Administrator.AZALEA>Winrm identify -remote:cscdserver11
IdentifyResponse
ProtocolVersion =
http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0
C:\Users\Administrator.AZALEA>winrm get winrm/config -remote:cscdserver11
Config
MaxEnvelopeSizekb = 150
MaxTimeoutms = 60000
MaxBatchItems = 32000
MaxProviderRequests = 4294967295
Client
NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = false
Auth
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
CredSSP = false
DefaultPorts
HTTP = 5985
HTTPS = 5986
TrustedHosts
Service
RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPerUser = 15
EnumerationTimeoutms = 60000
MaxConnections = 25
MaxPacketRetrievalTimeSeconds = 120
AllowUnencrypted = false
Auth
Basic = false
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5
C:\Users\Administrator.AZALEA>winrm get wmicimv2/Win32_Service?Name=WinRM -r:csc
dserver11
Win32_Service
AcceptPause = false
AcceptStop = true
Caption = Windows Remote Management (WS-Management)
CheckPoint = 0
CreationClassName = Win32_Service
Description = Windows Remote Management (WinRM) service implements the WS-Ma
nagement protocol for remote management. WS-Management is a standard web service
s protocol used for remote software and hardware management. The WinRM service l
istens on the network for WS-Management requests and processes them. The WinRM S
ervice needs to be configured with a listener using winrm.cmd command line tool
or through Group Policy in order for it to listen over the network. The WinRM se
rvice provides access to WMI data and enables event collection. Event collection
and subscription to events require that the service is running. WinRM messages
use HTTP and HTTPS as transports. The WinRM service does not depend on IIS but i
s preconfigured to share a port with IIS on the same machine. The WinRM service
reserves the /wsman URL prefix. To prevent conflicts with IIS, administrators s
hould ensure that any websites hosted on IIS do not use the /wsman URL prefix.
DesktopInteract = false
DisplayName = Windows Remote Management (WS-Management)
ErrorControl = Normal
ExitCode = 0
InstallDate = null
Name = WinRM
PathName = C:\Windows\System32\svchost.exe -k NetworkService
ProcessId = 164
ServiceSpecificExitCode = 0
ServiceType = Share Process
Started = true
StartMode = Auto
StartName = NT AUTHORITY\NetworkService
State = Running
Status = OK
SystemCreationClassName = Win32_ComputerSystem
SystemName = CSCDSERVER11
TagId = 0
WaitHint = 0
Thanks
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 6:13am
These powershell problems are becoming quite common, and because the way it has been implemented (via IIS) is rather new, they're still hard to fix. One more thing you might look at. Make sure in IIS Manager that in the modules for the Default
Web Site, kerbauth and wsman are not listed - they must both show as 'Local' when you look at the powershell VDir, and not 'Inherited' (i.e. inherited modules from the Default Web Site).
You could also try removing/adding it with Remove-PowerShellVirtualDirectory and New-PowerShellVirtualDirectory .Outlook Web Access For PDA , OWA For WAP
www.owa-pda.com
email a@t leederbyshire d.0.t c.0.m
February 8th, 2011 9:11am
Both kerauth and wsman show in the PowerShell virtual directory. There Module Type is "native" and their Entry Type is "local".
Thanks
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 7:16pm
The remove powershell command is not working.
Can you help?
Is there a log or trace command that I can use to track down the problem?
Please help
thanks
February 8th, 2011 7:21pm
Can you post the error for us? If you click the icon in the left hand side of the title bar, then go to Edit, then Select All, then press Enter, you have copied the contents of the powershell cmd window to your clipboard. You can then paste
the error here for us.Outlook Web Access For PDA , OWA For WAP
www.owa-pda.com
email a@t leederbyshire d.0.t c.0.m
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2011 8:52am
Here you go:
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> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #57:
Want to know what permissions an Active Directory user account has on a specific mailbox? Use:
Get-Mailbox <Mailbox to Check> | Get-MailboxPermission -User <Active Directory User>
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: cscdserver11.azalea.local
VERBOSE: Connecting to cscdserver11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process
the request. The following error occured while using Kerberos authentication: The network path was not found.
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 us
e 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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
[PS] C:\Users\Administrator.AZALEA\Desktop>Remove-PowerShellVirtualDirectory
The term 'Remove-PowerShellVirtualDirectory' is not recognized as the name of a cmdlet, function, script file, or opera
ble program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:34
+ Remove-PowerShellVirtualDirectory <<<<
+ CategoryInfo : ObjectNotFound: (Remove-PowerShellVirtualDirectory:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[PS] C:\Users\Administrator.AZALEA\Desktop>
Thanks
February 9th, 2011 7:49pm
I guess that since the PS VDir isn't working properly, this is rendering it incapable of running many of the commands. I don't have anything else to suggest, I'm afraid. You've read this blog, of course, but note that Steve Bryant (the author
of the tool) is inviting feedback from people who are unable to solve PS problems with it. He has provided an email address, so I think it's safe to assume he would not object to being contacted directly. Or, you could add a comment to the blog,
and hope for the best.Outlook Web Access For PDA , OWA For WAP
www.owa-pda.com
email a@t leederbyshire d.0.t c.0.m
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 8:30am
Thank you very much for your help.
Doese anyone at from the Exchange 2010 support group help here?
Thanks
February 10th, 2011 7:08pm
Sometimes, but since MS offer paid support, free help isn't always guaranteed.Outlook Web Access For PDA , OWA For WAP
www.owa-pda.com
email a@t leederbyshire d.0.t c.0.m
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2011 6:11am
I still haven't gotten EMC 2010 to work yet. I put things aside for a while becuase I became so frustrated. I'm trying it again. I have the EMT tool however, I'm not sure what to do next. I've expanded the zip file and have the following:
EMTConnectFunctions.ps1.rename
EMTErrorHandler.PS1.rename
EMTshooter.ps1.rename
EMTshooter.strings.psd1.rename
I didn't see any documentation in the zip file.
What Next?
April 8th, 2011 5:18am
I've never tried it, but the instructions are here:
http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx
In a nutshell, I'd say it was:
1. Remove the .rename part of each file name.
2. Open a PS window (your Exchange Management Shell).
3. Navigate with CD to the folder you put the files in.
4. Run the EMTShooter by typing EMTShooter.ps1 into the command line.
5. Look in the Event Viewer for any results.Outlook Web Access For PDA , OWA For WAP
www.owa-pda.com
email a@t leederbyshire d.0.t c.0.m
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2011 9:46am
I'm still working on my EMC 2010 SP issue. I've run EMCShooter and I'm getting the following results.
[PS] D:\Louis Share\EMTShooter>.\EMTshooter
Welcome to the Exchange Management Troubleshooter!
We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.
Exception setting "BufferSize": "Cannot set the buffer size because the size specified is too large or too small.
Parameter name: value
Actual value was 120,300."
At D:\Louis Share\EMTShooter\EMTshooter.ps1:30 char:13
+ $pswindow. <<<< buffersize = $newsize
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
Checking IIS Service...
Checking the Exchange Install Path variable...
Checking the Powershell Virtual Directory...
Checking the Powershell vdir SSL setting...
Checking the Powershell vdir path setting...
Checking HTTP Port 80...
Checking HTTP Port 80 Host Name...
Testing for errors...
VERBOSE: Connecting to CSCDSERVER11.azalea.local
[cscdserver11.azalea.local] Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found.
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.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed
Exception setting "BufferSize": "Cannot set the buffer size because the size specified is too large or too small.
Parameter name: value
Actual value was 120,300."
At D:\Louis Share\EMTShooter\EMTConnectFunctions.ps1:191 char:14
+ $pswindow. <<<< buffersize = $newsize
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
The Exchange Management Troubleshooter successfully completed connecting to:
CSCDSERVER11.azalea.local
Failed to connect to any Exchange Server in the current site.
Exception setting "BufferSize": "Cannot set the buffer size because the size specified is too large or too small.
Parameter name: value
Actual value was 120,300."
At D:\Louis Share\EMTShooter\EMTErrorHandler.ps1:229 char:12
+ $pswindow. <<<< buffersize = $newsize
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : PropertyAssignmentException
Problem found:
Looking for error...
After each error is resolved, close this window and re-run the tool to check for additional problems.
[PS] D:\Louis Share\EMTShooter>
I'm really at a lost for what is next. I can't pay for Microsoft support. I was hoping to get help here.
Please someone. I've read everything I could find and still no luck.
April 21st, 2011 7:14pm
I'm still tryingto resolve my issue. Here is what I've found so far, however, I'm not sure what its trying to tell me.
C:\Users\Administrator.AZALEA>winrm get winrm/config/service
Service
RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPerUser = 15
EnumerationTimeoutms = 60000
MaxConnections = 25
MaxPacketRetrievalTimeSeconds = 120
AllowUnencrypted = false
Auth
Basic = false
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
C:\Users\Administrator.AZALEA>winrm enumerate winrm/config/resource
Resource
Capability
Capability
Capability
Capability
Capability
Capability
Resource
Capability
Resource
Capability
Capability
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Capability
Capability
Capability
Resource
Capability
Capability
Capability
Capability
Resource
Capability
C:\Users\Administrator.AZALEA>winrm enumerate winrm/config/resource
Resource
Capability
Capability
Capability
Capability
Capability
Capability
Resource
Capability
Resource
Capability
Capability
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Resource
Capability
Capability
Capability
Capability
Resource
Capability
Capability
Capability
Capability
Resource
Capability
C:\Users\Administrator.AZALEA>winrm enumerate winrm/config/listener
Listener
Address = *
Transport = HTTP
Port = 5985
Hostname
Enabled = true
URLPrefix = wsman
CertificateThumbprint
ListeningOn = 127.0.0.1, 192.168.10.11, ::1, fe80::100:7f:fffe%12, fe80::5efe:192.168.10.11%11, fe80::f935:f98b:f781:f29b%10
C:\Users\Administrator.AZALEA>winrm enumerate winrm/config/plugin
PlugInConfiguration
Resources
Resource
Security
Capability
PlugInConfiguration
InitializationParameters
Param
Resources
Resource
Security
Capability
PlugInConfiguration
InitializationParameters
Param
Param
Param
Resources
Resource
Security
Capability
PlugInConfiguration
Resources
Resource
Security
Capability
PlugInConfiguration
Resources
Resource
Capability
Capability
Capability
Capability
Resource
Capability
Capability
Capability
Capability
Resource
Capability
What else should I be looking at?
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2011 3:46pm
I'm not sure what that means. I get the same values for most of those commands. Interestingly, I get nothing at all displayed for the command
winrm enumerate winrm/config/listener
When I type that here, the cursor just moves to the next line, as if it ignored it completely. Whether or not that's significant, I really don't know. Where did you get the idea to try those commands?Outlook Web Access For PDA , OWA For WAP
www.owa-pda.com
email a@t leederbyshire d.0.t c.0.m
April 26th, 2011 9:23am