when i start console or shell i see VERBOSE: Connecting to EXCH-SRV.veditour.local [exch-srv.veditour.local] Connecting to remote server failed with the following error message : WinRM cannot process th e request. The following error occured while using Kerberos authentication: The network path was not found. i can change -auto in shell shortcut to FQDN and it will works correct! in console, after the error, i can type "exch-srv" and it will work, but if i will write FQDN there will be the same error! what else .. IIS error.. in "basic setting" while i press "test setting" on "autodiscover", "powershell" and "owa" virtual directories i got an error "invalid application path" .. while OWA, for example, works good through the IE web browser.. no possibility to unisntall or reinstall EXCH or SP1.. because of unavailability of checkboxes on the roles ... what the differences between FQDN and the short name in my case? and why is it so ?? P.S. Exchange was installed a month ago SP1 on windows 25.02 problems apperas 01.03 with console with our common error and this in log "The following fatal alert was generated: 10. The internal error state is 1203." source schannel, ID 36888 (so there are MANY errors in system log still) reboot helped next day problem appears once more.. reboot didn't help. i installed SP1 on Exchange and rollup 2 on SP1.. and no better.. i have no ideas.. maybe masters can help me ? windows server 2008 R2 SP1 + exchange 2010 SP1 + rollup2 if it will helps.. AFTER i connect to the exchange server [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Test-PowerShellConnectivity CasServer LocalSite Scenario Result Latency(MS) Error --------- --------- -------- ------ ----------- ----- EXCH-SRV Default-Fi... Logon User Success 412.04 [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-ClientAccessServer | ft Name, *internal* Name AutoDiscoverServiceInternalUri ---- ------------------------------ EXCH-SRV https://exch-srv.veditour.local/Autodiscover/Autodiscove... [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts> it may be helpfull please help me!? P.S. Exchange was installed a month ago SP1 on windows 25.02 problems apperas 01.03 with console with our common error and this in log "The following fatal alert was generated: 10. The internal error state is 1203." source schannel, ID 36888 (so there are MANY errors in system log still) reboot helped next day problem appears once more.. reboot didn't help. i installed SP1 on Exchange and rollup 2 on SP1.. and no better..

Hi, It looks like the application pool is corrupt or something is damaged in IIS. Please run the ExBPA which can be found in the following directory: Program Files\Microsoft\Exchange Server\V14\Bin And post the rsults here. Regards, JohanExchange-blog: www.johanveldhuis.nl

Hi Please check your DNS server of your FQDN. Can you ping the server by FQDN? If the record is well, you can run exbpa and post your result.

Oh! thank you guys for attention for my problem! what type of test is intereston on expba ? should i export "all issues" or something else ? P.S. DNS works good i guess! nslookup exch-srv Server: exch.veditour.local Address: 192.168.30.112 Name: exch-srv.veditour.local Address: 192.168.30.101 nslookup exch-srv.veditour.local Server: exch.veditour.local Address: 192.168.30.112 Name: exch-srv.veditour.local Address: 192.168.30.101

healt check http://rapidshare.com/files/451888713/ExBPA.201103101109346357.data.xml we've found new problem, more globaly but i guess associated. when i give "full access rights" to someone's mailbox this mailbox appears in client's outlook BEFORE i add this mailbox in users's outlook. and outlooks closes with error.. log has no usefull information outlook.exe error..in mudule outlook.exe ... if it's not associated - i don't know what to think.

"recipient update service not configured" "site folder server deleted"

Hi Can you post healt check on another side? I can't access http://rapidshare.com/files/451888713/ExBPA.201103101109346357.data.xml (No permission)

Hi, I have looked at the file and it looks like there is/was an Exchange 2003 environment besides the Exchange 2010 can you confirm this? From the log you uploaded I can see it has not been cleaned up completely by following the procedures mentioned in this technet article: http://support.microsoft.com/kb/822931 Besides this cirular logging has been enabled, keep in mind that this will increase the change to recover a database if needed. On the new Exchange 2010 server a component is missing: ASP this component is needed to provide the password change functionality to end users. The current databases are still looking at another Public Folder DB please check the configuration of mailbox database 'Mailbox Database 1142139776' But now for the original problem: You still got issues when connecting via either EMS and EMC because the network path could not be found? What you might try is to recreate the Powershell virtual directory in IIS. This needs to be done by using Powershell: First remove the Powershell Virtual Directory: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 Get-PowerShellVirtualDirectory | Remove-PowerShellVirtualDirectory Remove-PowerShellVirtualDirectory -identity "powershell-vdir Reset IIS by executing IISReset Now create a new Powershell Virtual Directory: New-PowerShellVirtualDirectory Name: PowerShell Again perform an IISReset Disable require SSL: Set-PowerShellVirtualDirectory -identity "powershell-vdir" -RequireSSL:$false Regards, JohanExchange-blog: www.johanveldhuis.nl

first of all o want to thank you for your attention and answer! i am really appreciate! yes! there was i 2007 exchange, but for now it's gone. and i cannot follow actions of your link, by the way i has roughly broken this manual. exchange 2007 was roughly deleted. last step was - deleted something in "adsiedit", bucause i didn't know how to delete in other way. and i don't remember what it was.. so now it sins payment :(br> i didn't think anyone will answer me so i choose the way to uninstall all the update i can. i've started from deleting SP1 for 2008 R2 server.. and ends with all others.. later there was a tons of errors and solutions and now i stuck at the: VERBOSE: Connecting to EXCH-SRV.veditour.local [exch-srv.veditour.local] Connecting to remote server failed with the following error message : WinRM cannot process th e 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.: exch-srv VERBOSE: Connecting to exch-srv [exch-srv] Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP serv er that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help to pic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed [PS] C:\Windows\system32> let's start with this point. i will follow your recommendation, to not to make a wrong turn. let's start ? thank you! P.S. what wrong with this forum? why i must use "br" html tags to make my posts readable ? is it firefox 4.0RC bugs ?

usefull i guess, new exbpa report http://rapidshare.com/files/452039652/ExBPA.201103111651057943.data.xml

Hi, Please check these things: 1. The http binding has been removed from the Default Web Site. A common scenario for this is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by requiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Remote PowerShell requires port 80 to be available on the Default Web Site. If you want to set up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx and follow the directions under the section "For a Configuration in Which SSL is Required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0". 2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue, you need to clear out the Hostname field under the port 80 bindings on the Default Web Site. Mentioned on this blog: http://blogs.technet.com/b/jribeiro/archive/2010/04/05/troubleshooting-exchange-2010-management-tools-startup-issues.aspx Regards, JohanExchange-blog: www.johanveldhuis.nl

i don't use any redirection and i don't think i need it! i'll look at owa later! first of all let the EMS and EMC work! bindings of default web site was http exch-srv.veditour.local 80 * https 443 * http 80 127.0.0.1 http 443 127.0.0.1 i've deleted host name from first binding for now we have VERBOSE: Connecting to EXCH-SRV.veditour.local [exch-srv.veditour.local] Connecting to remote server failed with the following error message : WinRM cannot process th e 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.: exch-srv VERBOSE: Connecting to exch-srv [exch-srv] Connecting to remote server failed with the following error message : The client cannot connect to the desti nation specified in the request. Verify that the service on the destination is running and is accepting requests. Consu lt the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM s ervice: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed [PS] C:\Windows\system32>

so.. what is better ?:) i guess first... but googling say the URL should not be there! [exch-srv] Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP serv er that does not support the WS-Management protocol or Connecting to remote server failed with the following error message : The client cannot connect to the desti nation specified in the request. Verify that the service on the destination is running and is accepting requests. Consu lt the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM s ervice: "winrm quickconfig"

Please run winrm quickconfigExchange-blog: www.johanveldhuis.nl

[PS] C:\Windows\system32>winrm qc WinRM already is set up to receive requests on this machine. WinRM already is set up for remote management on this machine. [PS] C:\Windows\system32>

if NOT fqdn - no connection if nothing - no connection fqdn - got "a response saying the requested HTTP URL was not available" fqdn i guess the only variant we must use ? i've deleted the fisrt 2 bindings. nothing changed. now it's http (empty) 80 127.0.0.1 http (empty) 443 127.0.0.1 we stucked at "got a response saying the requested HTTP URL was not available"! ant it is after i got an error of "network path not found" after i started EMS, and then i type exch0srv anfd got error about response! as we can remember yesterday typing exch-srv works! i guess there is 2 steps! first make it works after typing! second - network path..

Can you try to connect from remote: Start Powershell on your computer $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<FQDN of Exchange 2010 server>/PowerShell/ -Authentication Kerberos Import-PSSession $Session Exchange-blog: www.johanveldhuis.nl

PS C:\Documents and Settings\aerotop> $Session = New-PSSession -ConfigurationNam e Microsoft.Exchange -ConnectionUri http://exch-srv.veditour.local/PowerShell/ - Authentication Kerberos [exch-srv.veditour.local] Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_T roubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:Re moteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId : PSSessionOpenFailed PS C:\Documents and Settings\aerotop>

new feauture of my server :) [PS] C:\Windows\system32>Set-PowerShellVirtualDirectory -identity "powershell-vdir" -RequireSSL:$false Set-PowerShellVirtualDirectory : The operation couldn't be performed because object 'EXCH-SRV.veditour.local\powershell -vdir' couldn't be found on 'exch.veditour.local'. At line:1 char:31 + Set-PowerShellVirtualDirectory <<<< -identity "powershell-vdir" -RequireSSL:$false + CategoryInfo : NotSpecified: (0:Int32) [Set-PowerShellVirtualDirectory], ManagementObjectNotFoundExcept ion + FullyQualifiedErrorId : D6DEE86D,Microsoft.Exchange.Management.SystemConfigurationTasks.SetPowerShellVirtualDire ctory [PS] C:\Windows\system32> exch.veditour.local it is the server on wich i have exchange 2007 installed. now it is the second DC!

somehow i got it works. only "network path now found" is the rest...

while "dcdiag /s /v /s:dc" from exch-srv i see Starting test: SysVolCheck * The File Replication Service SYSVOL ready test The registry lookup failed to determine the state of the SYSVOL. The error returned was 0x35 "The network path was not found.". Check the FRS event log to see if the SYSVOL has successfully been shared. ......................... DC failed test SysVolCheck