Exchange 2010 fails after an attempt to install Sharepoint 2010 in the same server box....
-
Saturday, May 12, 2012 4:38 PM
Hello all. After an attempt to install Sharepoint on the same server as my active Exchange server 2010 my email server stopped.
The symptoms are:
1) in powershell I am getting this error: 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 re
turned by a HTTP server that does not support the WS-Management protocol.- similar error in EM Console
2) EWS seems to be missing in IIS 7
Troubleshooting:
1) uninstalled IIS
2) uninstalled/reinstalled WINRM IIS Ext (twice)
3) modified the ApplicationHost.config (in theGlobal module) to include:
<add name="WSMan" image="%windir%\system32\wsmsvc.dll" />
<add name="exppw" image="C:\Program Files\Microsoft\Exchange server\v14\ClientAccess\Owa\auth\exppw.dll" />
<add name="kerbauth" image="C:\Program Files\\Microsoft\Exchange server\v14\bin\kerbauth.dll" />If need be I will re-install Exchange but I need to know if this is the only way as I have live data. I have taken a copy of the database.
Any help right now would be appreciated...thanks SAS
All Replies
-
Saturday, May 12, 2012 3:42 PM
Hello all. After an attempt to install Sharepoint on the same server as my active Exchange server 2010 my email server stopped.
The symptoms are:
1) in powershell I am getting this error: 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 re
turned by a HTTP server that does not support the WS-Management protocol.- similar error in EM Console
2) EWS seems to be missing in IIS 7
Troubleshooting:
1) uninstalled IIS
2) uninstalled/reinstalled WINRM IIS Ext (twice)
3) modified the ApplicationHost.config (in theGlobal module) to include:
<add name="WSMan" image="%windir%\system32\wsmsvc.dll" />
<add name="exppw" image="C:\Program Files\Microsoft\Exchange server\v14\ClientAccess\Owa\auth\exppw.dll" />
<add name="kerbauth" image="C:\Program Files\\Microsoft\Exchange server\v14\bin\kerbauth.dll" />If need be I will re-install Exchange but I need to know if this is the only way as I have live data. I have taken a copy of the database.
Any help right now would be appreciated...thanks SAS
- Merged by Simon_WuMicrosoft Contingent Staff, Moderator Monday, May 14, 2012 3:28 AM dup
-
Saturday, May 12, 2012 4:39 PMModerator
Sharepoint will take over IIS on an Exchange server as you have seen.
See:
-
Saturday, May 12, 2012 4:46 PM
Thanks....hindsight is always 20/20...now that the deed is done is there a good way to go back or am I pooched?
thanks
-
Saturday, May 12, 2012 4:47 PMThanks....any suggestions on a resolution?
-
Saturday, May 12, 2012 4:53 PMModerator
Well, if you cant recover following the suggestions in that link, you may have to reinstall.
Are the stores mounted and up? Can you build another Exchange Server and move mailboxes to it?
-
Saturday, May 12, 2012 5:11 PM
The stores are up and running but I do not have another box to move the mailboxes to.....if I reinstall will I lose visbility to my old mailboxes? Or do they just get deleted?
Never tried this before and want to ensure there is a way to recover without undo damage to live data..thanks
-
Saturday, May 12, 2012 5:12 PMThanks...I'll do that....cheers
-
Saturday, May 12, 2012 5:20 PM
Hi,
First you need to fix the WinRM Error you are getting, so see the first thread in this forum about that.
You mentioned that EWS is missing...can you see all other virtualdirectores, for example Powershell?When WinRM has been solved, see Reset Client Access Virtual Directories
If you can't reset the virtual directores, it might be a good idea to reinstall the CAS Role.
Martina Miskovic
- Proposed As Answer by Fiona_LiaoMicrosoft Contingent Staff, Moderator Monday, May 14, 2012 7:29 AM
- Unproposed As Answer by Fiona_LiaoMicrosoft Contingent Staff, Moderator Monday, May 14, 2012 7:30 AM
-
Saturday, May 12, 2012 5:23 PMModerator
Well, get an Exhange aware backup before going further of course. Do no further damage
You can use the /recoverserver option , then restore from backup or mount the store out right if the store is in a clean shutdown state.
I would reinstall the entire server if you went this route - clean including the O/S
- Proposed As Answer by Fiona_LiaoMicrosoft Contingent Staff, Moderator Monday, May 14, 2012 7:30 AM
-
Saturday, May 12, 2012 5:59 PM
Thanks...I did the EMTShooter and it did find an error that is corrected but still I am getting errors in Powershell. As a result I cannot get into the EM Console to do any further troubleshooting.
Powershell is there as well as the other virtual directories. Seems that only EWS is missing.
I can try to uninstall/reinstall the CAS server and also uninstall/reinstall the IIS server. Is this a preference? Also which order is best....thanks
-
Saturday, May 12, 2012 6:01 PM
So copying the database from one volume to another would do nothing for me? I can reinstall the OS and then do a recovery if I could be assured that the database could be reatteched.....any thoughts on this?
Thanks
-
Saturday, May 12, 2012 6:04 PMModerator
If you use recoverserver , yes, then the database can be re-attached. But before going that route, exhaust all the possibilities including the ones Martina is pointing out.
Moving the database from one volume to another wont help here.
-
Saturday, May 12, 2012 6:14 PM
Thanks but no kuck with Martina's solution....the EMT Shooter didn't do much and I am still getting the original error. So do I need to re-load the OS and then do the recoverserver? In that case the original database would be removed, correct? Or can I uninstall the Exchange server without reinstalling the OS?
I can also reinstall CAS to see if this works.....let me know...thanks
-
Saturday, May 12, 2012 6:15 PM
Are you able to run any Exchange cmdlets if you load the snapin in Windows Powershell, like get-powershellvirtualdirectory ?
- Start Windows PowerShell (run as Administrator)
- Run --> Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
You didn't mention what WINRm error you get now after running EMTShooter..
Martina Miskovic
-
Saturday, May 12, 2012 6:27 PM
below are the results of the Exchange cmdlet. I will get the error for the EMTShooter..thanks
[PS] C:\Windows\system32>Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
[PS] C:\Windows\system32>get-powershellvirtualdirectoryName Server
---- ------
PowerShell (Default Web Site) EMAIL-SRV2 -
Saturday, May 12, 2012 6:35 PM
Now I am getting an error with EMTShooter......can it get any worser......
[PS] C:\Windows\system32>d:\emtshooter\emtshooter
File d:\emtshooter\EMTshooter.ps1 cannot be loaded. The contents of file d:\emtshooter\EMTshooter.ps1 may have been tam
pered because the hash of the file does not match the hash stored in the digital signature. The script will not execute
on the system. Please see "get-help about_signing" for more details..
At line:1 char:25
+ d:\emtshooter\emtshooter <<<<
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException -
Saturday, May 12, 2012 6:41 PMOk, never seen that error.
Can you please confirm that you have fixed the port bindings in IIS.
This is how it should looks like:
Aslo, are you able to run New-WebServicesVirtualDirectory in Windows Powershell with the loaded exchange cmlets?Martina Miskovic
-
Saturday, May 12, 2012 7:00 PM
I have the following:
net.tcp
net.pipe
net.msmg
msmq.formatname
http 80 *
https 443 *
The only options I have for http and https are * and the internal IP address 192.168.2.x
The results of the cmdlet are:
[PS] C:\Windows\system32>New-WebServicesVirtualDirectory
Name Server InternalUrl
---- ------ -----------
EWS (default site) EMAIL-SRV2 https://email-srv2.kiddieproofers.co...thanks
-
Saturday, May 12, 2012 7:04 PM
The only options I have for http and https are * and the internal IP address 192.168.2.x
Having the local IP Address in the bindings is wrong. Modify that setting and change 192.168.2.x to 127.0.0.1 just as in the picture I posted above.Martina Miskovic
-
Saturday, May 12, 2012 7:53 PM
OK seems to be the same now...
-
Sunday, May 13, 2012 6:08 PM
So I bite the bullet last night and reloaded the OS and did a recoverserver on the Exchange server.Most of it came back but I still have an error below. Any suggestions?
thanks SAS
Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request.
-
Sunday, May 13, 2012 8:13 PMModerator
So I bite the bullet last night and reloaded the OS and did a recoverserver on the Exchange server.Most of it came back but I still have an error below. Any suggestions?
thanks SAS
Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request.
that error should be covered in the EMTShooter tool. I would run it again. -
Monday, May 14, 2012 7:40 AMModerator
Did you reinstall PowerShell and verify the size of "web.config" file? If there is "web.config.old", rename it to the current one and rename the current one to old to have a try.
Hope it is helpful.
Fiona Liao
TechNet Community Support
-
Monday, May 14, 2012 5:55 PM
So I just wanted to say a couple of things:
1) you guys are the best. Thanks for all of your tips and tricks because without it I would not have the issue resolved;
2) the Exchange server is back up and running without any loss of data...wahoo and here is how I did it
a) I did a backup of the system drive and saved the files to another volume
b) did a reload of the OS
c) did a "setup /m:recoverserver"
- it had a couple of errors but I worked through them
d) the powershell and EMC still would not come up (see a couple of posts above)
e) in the meanwhile I had loaded Sharepoint 2010 again and found out that the default website uses Port 80. I re-directed the port to 8080 and restarted Sharepoint.
- I then could open the Powershell and EMC
e) Now I needed to mount the original database files with all of my old data. I did a eseutil /p "mailbox database xxxxxxxxx.edb from the location where the database file was located,
- keep in mind that the EDB file that had all of the original data in it was NOT in the newly recovered mailbox database folder. I located the original database file in the WINDOWS.OLD folder that was created after the reinstall of the OS
- did this a couple of times until it came back clean
f) then I moved all of the temp files from the c:\program files\microsoft\exchange server\v14\mailbox\mailbox database xxxxxxxxxx to a temp directory
- with a blank Transaction Log folder I attempted to mount the original database file and WAHOO it worked
I checked the mail and the calendars and everything was there. Very soon after that the email that was missing started to come through....maybe not all of it but most of it.
Bottom line....backup backup backup and don't install Sharepoint AFTER Exchange.
Thank you again A_D, Martina and Fiona....have a great summer...
- Marked As Answer by Foozie000 Monday, May 14, 2012 6:03 PM
-
Monday, May 14, 2012 6:05 PMThanks for the update Foozie000!
I'm glad to hear that your problem is solved.
A great Summer to you too.Martina Miskovic
.png)
