benharel
asked on
Microsoft Exchange Initialization failed - cannot connect?
When trying to start the Exchange Management Console I get a Initialization failed.
I removed the port 80 iis site that can conflict with it. I ran the winrm config. I made sure the services are running. I checked the firewall and made sure the exceptions exist.
any ideas?
The following error occurred while attempting to connect to the specified exchange server 'removed for security':
The attempt to connect to (removed for security/powershell) using the Kerberos authentication failed: connecting to the remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting the request. Consulting the logs and documentation for WS-Management service running on the destination, most commonly IIS or WinRM. IUf the destination is WinRM service, running the following command on the destination analyze the configure the WinRM service: 'winrm quickconfig;.
I removed the port 80 iis site that can conflict with it. I ran the winrm config. I made sure the services are running. I checked the firewall and made sure the exceptions exist.
any ideas?
check the powershell vdir
ensure require ssl is not enabled
ensure require ssl is not enabled
A much better document:
Troubleshooting Exchange 2010 Management Tools startup issues
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
Troubleshooting Exchange 2010 Management Tools startup issues
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
ASKER
How do i check the powershell vdir? Where do i find it?
iis manager, expand default web site
ASKER
SSL seems to be off
follow the article e_aravind provided
ASKER
No luck so fare, i check iis in regards to the procedure the link e_avarind told me to follow.
did not work.
in ssl settings its off, site isnt using https so how could it be on?
did not work.
in ssl settings its off, site isnt using https so how could it be on?
ASKER
Ok now i get a new error
The WinRM client sent a request to an http server and got a response saying the requested HTTP url was no available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
The WinRM client sent a request to an http server and got a response saying the requested HTTP url was no available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
ASKER
ALSO I DID try to fix that using e_aravind method, it didnt work everything was correct
ASKER
I now tried doing a reinstall of SP1 because that is when problems occured. I get this error now
Error:
The following error was generated when "$error.Clear();
$vdirName = "PowerShell (Default Web Site)";
$InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
$vdir = get-PowerShellVirtualDirec tory -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $vdirName };
if ($vdir -eq $null)
{
$vdirName = "PowerShell";
new-PowerShellVirtualDirec tory $vdirName -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$fals e -WindowsAuthentication:$fa lse -RequireSSL:$false;
}
else
{
update-PowerShellVirtualDi rectoryVer sion -DomainController $RoleDomainController;
Set-PowerShellVirtualDirec tory $vdirName -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -WindowsAuthentication:$fa lse -RequireSSL:$false;
}
" was run: "A failure occurred while trying to update metabase properties.".
Error:
The following error was generated when "$error.Clear();
$vdirName = "PowerShell (Default Web Site)";
$InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
$vdir = get-PowerShellVirtualDirec
if ($vdir -eq $null)
{
$vdirName = "PowerShell";
new-PowerShellVirtualDirec
}
else
{
update-PowerShellVirtualDi
Set-PowerShellVirtualDirec
}
" was run: "A failure occurred while trying to update metabase properties.".
post the results from
Get-PowerShellVirtualDirec tory | fl
Get-PowerShellVirtualDirec
ASKER
where do i get that?>
lol - that was a good mistake on my part
one sec
one sec
open adsiedit
browse to the following
configuration - services - microsoft exchange - ex org name - administrative gorups - exchange administrative group... - servers - servername - protocols
- http
view the properties of Powershell
check all and pay attention to
msExchInternalHostName
attempt to browse to that value
browse to the following
configuration - services - microsoft exchange - ex org name - administrative gorups - exchange administrative group... - servers - servername - protocols
- http
view the properties of Powershell
check all and pay attention to
msExchInternalHostName
attempt to browse to that value
ASKER
my tree does not look like what you describe,
I have my Domain -> bultin, clients, ciomputers, domain controllers etc etc
what your describing is nothinglike what i see in adsiedit.msc
I have my Domain -> bultin, clients, ciomputers, domain controllers etc etc
what your describing is nothinglike what i see in adsiedit.msc
ASKER
i can see the config tree, i only see domain tree
ASKER
i am using server 2008 not 2003 btw
right click on adsiedit and select connect to
change from default to config
change from default to config
yep, 2010 requires 2008
ASKER
Ok now were getting somewhere,
I got http://myservername.domainname.com/powershell
I removed the server info from privicy reasons.
When i go to that link however i get a HTTP Error 403.4 which means the page is secured with SSL.
however my ssl is off do i dont understand?
I got http://myservername.domainname.com/powershell
I removed the server info from privicy reasons.
When i go to that link however i get a HTTP Error 403.4 which means the page is secured with SSL.
however my ssl is off do i dont understand?
ASKER
Also in my webiste IIS wwwroot\ folder there is no powershell folder
excellent now we are getting somewhere
enable ssl and disable it
enable ssl and disable it
ASKER
my default web site does not have any of the virtual folders its suppose to in IIS!
is there anyway to recreate them?
is there anyway to recreate them?
you're looking at the CAS server
this is going to take more effort :(
this is going to take more effort :(
ASKER
What does CAS stand for? What do you suggest to do? Is reinstalled exchange repopulate the default website? wwwroot?
The exchange server is part of the domain controllers, there are 4 domain controllers at this time.
The exchange is on its own VM
The exchange server is part of the domain controllers, there are 4 domain controllers at this time.
The exchange is on its own VM
ASKER
I still cannot get into the Exchange management console or shell, i get the error that requested HTTP url was not available.
client access server
the recreation is done thru powershell which is not available
need a minute
the recreation is done thru powershell which is not available
need a minute
ASKER
No problem. thank you
ASKER
Here is error i get in power shell.
again server name and domain were removed.
again server name and domain were removed.
VERBOSE: Connecting to servername.domain.com
[servername.domain.com] 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 return
ed by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubl
eshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to servername.domain.com
[servername.domain.com] 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 return
ed by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubl
eshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to servername.domain.com
[servername.domain.com] 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 return
ed by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubl
eshooting 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.:
can you post an image of your default web site expanded
ASKER
Sure, do you have aim or something would be much easier to solve over live chat and then post the solution here so others can see.
defayultsite.gif
defayultsite.gif
wow! (sorry, but that is shocking)
right-click on default web site and select add application
Alias = PowerShell
Application pool = MSExchangePowerShellAppPoo l
physical path = C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Po werShell
connect as = application user
right-click on default web site and select add application
Alias = PowerShell
Application pool = MSExchangePowerShellAppPoo
physical path = C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Po
connect as = application user
once we have the powershell vdir working you should be able to create the others thru powershell
ASKER
lol thank you but your gonna love this new error.
I now get
The WinRm, client cannot process the request. It cannot determine the content type of the http response from the destination computer. The content type is absent or invalid.
When i go to the powershell link I get the code below!
I now get
The WinRm, client cannot process the request. It cannot determine the content type of the http response from the destination computer. The content type is absent or invalid.
When i go to the powershell link I get the code below!
Server Error in '/PowerShell' Application.
--------------------------------------------------------------------------------
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Source Error:
Line 40: <compilation debug="true">
Line 41: <assemblies>
Line 42: <add assembly="Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Line 43: <add assembly="Microsoft.Exchange.Configuration.CertificateAuth, Version=14.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Line 44: <add assembly="Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Source File: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell\web.config Line: 42
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.5018; ASP.NET Version:2.0.50727.5014
verify this file is present
C:\Program Files\Microsoft\Exchange Server\V14\bin\Microsoft.E xchange.Co nfiguratio n.Redirect ionModule. dll
C:\Program Files\Microsoft\Exchange Server\V14\bin\Microsoft.E
Add the ExchangeInstallPath variable to the Environment variables in System Properties, and check the path of the PowerShell Virtual Directory in IIS
1.Open System Properties, and then click Environment variables.
2.In the System variables area, verify that the ExchangeInstallPath variable exists and that the value for the variable is C:\Program Files\Microsoft\Exchange Server\V14\. Add the variable if it does not exist.
3.Start IIS.
4.Expand Default Web Site, and then click PowerShell.
5.In the Actions pane, click Basic Settings.
6.In the Edit Application dialog box, verify that the path in the Physical path box is as follows: C:\Program Files\Microsoft\Exchange Server\v14\ClientAccess\Po wershell.
7.Click OK.
1.Open System Properties, and then click Environment variables.
2.In the System variables area, verify that the ExchangeInstallPath variable exists and that the value for the variable is C:\Program Files\Microsoft\Exchange Server\V14\. Add the variable if it does not exist.
3.Start IIS.
4.Expand Default Web Site, and then click PowerShell.
5.In the Actions pane, click Basic Settings.
6.In the Edit Application dialog box, verify that the path in the Physical path box is as follows: C:\Program Files\Microsoft\Exchange Server\v14\ClientAccess\Po
7.Click OK.
ASKER
The file is Present
steps 1 and 2 are the critical the rest should be good with the creation we did
ASKER
I followed the steps you provided. all the information was already present and correct. I did not have to add or change anything
What do you suggest?
What do you suggest?
ASKER
Just for background this all happened after installed Exchange SP1
was the install successful?
is basic mail functionality working (outlook works)?
i'm trying to determine the best way to recover from this. i don't know if anyone else has encountered this
is basic mail functionality working (outlook works)?
i'm trying to determine the best way to recover from this. i don't know if anyone else has encountered this
is this the only exchange 2010 server you have?
ASKER
The install was not successful the first time because it did not meet all the prequites. This was fixed with i installed the missing hotfitxs, so the install itself did finish correctly yes. This exchange server is a project being developed for a migration i am preforming from Novll groupwise to Exchange. (150+ users)
There is no email hosted in it or active accounts at this time(though the domain already has all the users created in it etc). Right now i am trying to get it working so i can begin setting it up for the migration.
Would you suggest a uninstall and reinstall? and if so would the existing data in exchange be removed?
I do not know of the mail functionality works because this not a live server. What is the best way to get this thing working?
There is no email hosted in it or active accounts at this time(though the domain already has all the users created in it etc). Right now i am trying to get it working so i can begin setting it up for the migration.
Would you suggest a uninstall and reinstall? and if so would the existing data in exchange be removed?
I do not know of the mail functionality works because this not a live server. What is the best way to get this thing working?
i would remove the cas server role and attempt to reinstall
ASKER
This is just nuts! I went ahead to run the Exchange uninstall procedure from the Add and Remove. It launchs the exchange server 2010 sp1 upgrade, not the uninstall.
.......................... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... ..........
..........................
run thru it
ASKER
When i try to click next from introduction I get the foloowing error
some controls arent vaild.
-ExSetup cannot be called directly to preform upgrades. Please use setup.com.
some controls arent vaild.
-ExSetup cannot be called directly to preform upgrades. Please use setup.com.
locate the installation files
run
setup /mode:uninstall /roles:ca
run
setup /mode:uninstall /roles:ca
ASKER
Its running the setup right now, we will most lilkely have to complete this monday.
i should be online
ASKER
Good morning i hope you had a good weekend and are still with me? Here is the error log I get during uninstall. I hope i entered the command the correct method. I was unable to create a shourtcut for the setup.com so i ran the command though cmd.exe, view code below to see what i mean.
Thank again so much for your assistance.
Thank again so much for your assistance.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator.mydomainname>cd desktop
C:\Users\Administrator.mydomainname\Desktop>cd sp1
C:\Users\Administrator.mydomainname\Desktop\sp1>setup /mode:uninstall /roles"ca
</rolesca> isn't a valid command-line option. To list the available
command-line parameters, type Setup /?
C:\Users\Administrator.mydomainname\Desktop\sp1>setup /mode:uninstall /roles:ca
Welcome to Microsoft Exchange Server 2010 Unattended Setup
Preparing Exchange Setup
The following server roles will be upgraded
Languages
Hub Transport Role
Client Access Role
Unified Messaging Role
Mailbox Role
Management Tools
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Language Pack Checks COMPLETED
Hub Transport Role Checks COMPLETED
Setup cannot detect an SMTP or Send connector with an address space of '*'. Mai
l flow to the Internet may not work properly.
Client Access Role Checks COMPLETED
Unified Messaging Role Checks COMPLETED
Mailbox Role Checks COMPLETED
Configuring Microsoft Exchange Server
Language Files COMPLETED
Restoring Services COMPLETED
Languages COMPLETED
Hub Transport Server Role COMPLETED
Client Access Server Role FAILED
The following error was generated when "$error.Clear();
$CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe
;
$imagePath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess
\Owa\auth\exppw.dll");
Start-SetupProcess -Name "$CommandAppCmd" -args "install module /name:
exppw /image:`"$imagePath`" /add:false" -IgnoreExitCode @(183);
Start-SetupProcess -Name "$CommandAppCmd" -args "add module /name:expp
w /app.name:`"Default Web Site/owa`"" -IgnoreExitCode @(183);
" was run: "Process execution failed with exit code 50.".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Exchange Server setup encountered an error.
C:\Users\Administrator.mydomainname\Desktop\sp1>
can you post the exchange setup log?
ASKER
[REQUIRED] A reboot from a previous installation is pending. Please restart the system and rerun setup.
when was the last time this server was rebooted
when was the last time this server was rebooted
ASKER
today, let me do it again
ASKER
Do it again and rtun the command again?
ASKER
Restart running though setup.com /mode:uninstall /roles:ca
right now
right now
yes, then post the results of the log from the latest run
ASKER
Results for 20th, should be two attempts mixed in, one after restart.
EXCHANGELOG.txt
EXCHANGELOG.txt
ASKER
btw during cmd.exe
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator.DOMAINNAME>cd..
C:\Users>cd..
C:\>cd shared
C:\Shared>cd sp1
C:\Shared\sp1>setup.com /mode:uninstall /roles:ca
Welcome to Microsoft Exchange Server 2010 Unattended Setup
Preparing Exchange Setup
The following server roles will be upgraded
Languages
Hub Transport Role
Client Access Role
Unified Messaging Role
Mailbox Role
Management Tools
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Language Pack Checks COMPLETED
Hub Transport Role Checks COMPLETED
Setup cannot detect an SMTP or Send connector with an address space of '*'. Mai
l flow to the Internet may not work properly.
Client Access Role Checks COMPLETED
Unified Messaging Role Checks COMPLETED
Mailbox Role Checks COMPLETED
Configuring Microsoft Exchange Server
Language Files COMPLETED
Restoring Services COMPLETED
Languages COMPLETED
Hub Transport Server Role COMPLETED
Client Access Server Role FAILED
The following error was generated when "$error.Clear();
$CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe
;
$imagePath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess
\Owa\auth\exppw.dll");
Start-SetupProcess -Name "$CommandAppCmd" -args "install module /name:
exppw /image:`"$imagePath`" /add:false" -IgnoreExitCode @(183);
Start-SetupProcess -Name "$CommandAppCmd" -args "add module /name:expp
w /app.name:`"Default Web Site/owa`"" -IgnoreExitCode @(183);
" was run: "Process execution failed with exit code 50.".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Exchange Server setup encountered an error.
looking for vdirs that don't exist
try running
setup /m:recoverserver
try running
setup /m:recoverserver
ASKER
Ok Update, the Exchange management console, and shell work! they pull the data and everything. After i ran recoverserver!! However i still got a error of failure during the recoverserver maneuverer.
I have included below the code form cmdline and Log of event.
It failed on client access server role, but i do repeat the shell console and management console for exchange work!
I have included below the code form cmdline and Log of event.
It failed on client access server role, but i do repeat the shell console and management console for exchange work!
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator.domainname>cd..
C:\Users>cd..
C:\>cd shared
C:\Shared>cd sp1
C:\Shared\sp1>setup /m:recoverserver
Welcome to Microsoft Exchange Server 2010 Unattended Setup
Preparing Exchange Setup
Copying Setup Files COMPLETED
The following server roles will be upgraded
Languages
Hub Transport Role
Client Access Role
Unified Messaging Role
Mailbox Role
Management Tools
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Language Pack Checks COMPLETED
Hub Transport Role Checks COMPLETED
Setup cannot detect an SMTP or Send connector with an address space of '*'. Mai
l flow to the Internet may not work properly.
Client Access Role Checks COMPLETED
Unified Messaging Role Checks COMPLETED
Mailbox Role Checks COMPLETED
Configuring Microsoft Exchange Server
Language Files COMPLETED
Restoring Services COMPLETED
Languages COMPLETED
Hub Transport Server Role COMPLETED
Client Access Server Role FAILED
The following error was generated when "$error.Clear();
$CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe
;
$imagePath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess
\Owa\auth\exppw.dll");
Start-SetupProcess -Name "$CommandAppCmd" -args "install module /name:
exppw /image:`"$imagePath`" /add:false" -IgnoreExitCode @(183);
Start-SetupProcess -Name "$CommandAppCmd" -args "add module /name:expp
w /app.name:`"Default Web Site/owa`"" -IgnoreExitCode @(183);
" was run: "Process execution failed with exit code 50.".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
Exchange Server setup encountered an error.
C:\Shared\sp1>
lastexchangelogo.txt
ASKER
going to have to recreate all the apps and virtual directory's on the default website you said as well? and the command is run from exchange shell?
check iis manager for the vdirs
if they are not there, yes i can provide a list
if they are not there, yes i can provide a list
ASKER
Nothing there but powershell
New-OwaVirtualDirectory
New-OabVirtualDirectory
New-WebServicesVirtualDire ctory
New-AutodiscoverVirtualDir ectory
New-ActiveSyncVirtualDirec tory
New-EcpVirtualDirectory
you'll also want to uninstall rpc proxy and reinstall
this will require you to re-enable outlook anywhere as well
New-OabVirtualDirectory
New-WebServicesVirtualDire
New-AutodiscoverVirtualDir
New-ActiveSyncVirtualDirec
New-EcpVirtualDirectory
you'll also want to uninstall rpc proxy and reinstall
this will require you to re-enable outlook anywhere as well
ASKER
Do you know what the recovery parameter would be for these objects? To Run recovery on them?
For example
New-OwaVirtualDirectory /recover (just example)
For example
New-OwaVirtualDirectory /recover (just example)
New-OwaVirtualDirectory -WebSiteName "Default Web Site"
ASKER
Any of those commands i attempt to do i get stuck with The Virtual Directory already exists under "the server name"
When i look in IIS they are not there. When I i try the repair command says it already exists in AD but not in IIS. when i try Remove-OawVirutalDirectory for example it requests me to supply values for the following parameters identity:
Before we go any further i would like to thank you deeply for your assistance you have been amazing If i could award you a million points i would. Thank you
When i look in IIS they are not there. When I i try the repair command says it already exists in AD but not in IIS. when i try Remove-OawVirutalDirectory
Before we go any further i would like to thank you deeply for your assistance you have been amazing If i could award you a million points i would. Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is wonderful thank you so very much. You are a Genius.
Were done now i think...
Its been fun!
Were done now i think...
Its been fun!
excellent news.
ASKER
This man is a godsend. Thank you your help. you have been extremely patient helpful and a gentlemen.
WinRM Resolution Steps