chimp153
asked on
OWA Already Exists when trying to install CAS role in exchange
Hi there,
I have had a problem with Exchange 2010 SP1 where I cannot install the client access role. Due to a problem with IIS, it was removed and then reinstalled and this has now broken exchange in that I cannot get into EMS or EMC as it comes up with a WinRM error indicating that the URL could not be found.
I can run the exchange setup on the last page where it goes to set everything up it gets about 75% through the process on the Client Access Role and then comes up with the following:
I have checked IIS under the default website and there is no virtual directories under there at all. Only the default documents iistart.htm etc.
Any help would be much appreciated.
Darren
I have had a problem with Exchange 2010 SP1 where I cannot install the client access role. Due to a problem with IIS, it was removed and then reinstalled and this has now broken exchange in that I cannot get into EMS or EMC as it comes up with a WinRM error indicating that the URL could not be found.
I can run the exchange setup on the last page where it goes to set everything up it gets about 75% through the process on the Client Access Role and then comes up with the following:
Log Name: Application
Source: MSExchangeSetup
Date: 6/01/2014 2:32:59 PM
Event ID: 1002
Task Category: Microsoft Exchange Setup
Level: Error
Keywords: Classic
User: N/A
Computer: {myservername}
Description:
Exchange Server component Client Access Role failed.
Error: Error:
The following error was generated when "$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
" was run: "The virtual directory 'owa' already exists under '{myservername}/Default Web Site'.
Parameter name: VirtualDirectoryName".
The virtual directory 'owa' already exists under '{myservername}/Default Web Site'.
Parameter name: VirtualDirectoryNameI have checked IIS under the default website and there is no virtual directories under there at all. Only the default documents iistart.htm etc.
Any help would be much appreciated.
Darren
Gareth Gudger
Anything in the Application Pools?
open the IIS managger and under web service extensions check and make sure asp.net v2.0 is or allowed. Then try again to install CAS role.
If the issue continues, download the asp.net sp2 into local disk and install it again.
If the issue continues, download the asp.net sp2 into local disk and install it again.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for the replies. I used ADSIEDIT and removed the owa, oab relating to the exchange server and started the install again. This got me further, but now I have the following error coming up.
Summary: 3 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:00:08
I have uninstalled/reinsalled the ISAPI Extension for IIS but still i get the same error appear.
Thanks
Darren
Summary: 3 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:00:08
Preparing Setup
Completed
Elapsed Time: 00:00:00
Client Access Role
Failed
Error:
The following error was generated when "$error.Clear();
$InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";
new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://myservername/W3SVC/1/ROOT/owa' on 'CCSBADM01'.".
An error occurred while creating the IIS virtual directory 'IIS://myservername/W3SVC/1/ROOT/owa' on 'CCSBADM01'.
ISAPI extension owaauth.dll in group MSExchangeClientAccess wasn't found and its status can't be changed. Please make sure this ISAPI extension (IIS Web service extension) is still listed in IIS Manager. If it's not, it may need to be added again.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.438.0&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:00:07
Finalizing Setup
CancelledI have uninstalled/reinsalled the ISAPI Extension for IIS but still i get the same error appear.
Thanks
Darren
ASKER
diggisaur, I have three entries in Application Pools in IIS as below:
Classic .NET Appool Started V2.0 Classic ApplicationPoolIdentity 0
DefaultAppPool Started V2.0 Integrated ApplicationPoolIdentity 1
MSExchangeOWACalendarAppPool Started v2.0 Integrated LocalSystem 0ASKER
sameert,
ASP.NET v2.0.50727 is allowed for both Framework64 and Framework and i have registered the dlls with IIS using the aspnet_regiis -i command.
ASP.NET v2.0.50727 is allowed for both Framework64 and Framework and i have registered the dlls with IIS using the aspnet_regiis -i command.
Check if this helps :
http://social.technet.microsoft.com/Forums/exchange/en-US/2f365e9f-b4e1-43ec-8830-a711f14535bd/problem-with-installation-exchange-2010-client-access-role-isapi-extension-owaauthdll?forum=exchangesvrdeploylegacy
Ensure you take the registry key backup before you delete it.
http://social.technet.microsoft.com/Forums/exchange/en-US/2f365e9f-b4e1-43ec-8830-a711f14535bd/problem-with-installation-exchange-2010-client-access-role-isapi-extension-owaauthdll?forum=exchangesvrdeploylegacy
Ensure you take the registry key backup before you delete it.
Any progress?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So everything is working again except for POP3. We only have one client that uses POP3, the rest use RPC over HTTP so I am going to move that client over to the same.
When I telnet into the Server on port 110 and enter the username and password I get an error 21 about the server being unavailable. When I run the Test-PopConnectivity command in EMC I get an error that it couldn't find the Microsoft.Exchange.Complia
As I will not be using this and this is a different problem from the original post I am going to mark this as done.
When I telnet into the Server on port 110 and enter the username and password I get an error 21 about the server being unavailable. When I run the Test-PopConnectivity command in EMC I get an error that it couldn't find the Microsoft.Exchange.Complia
As I will not be using this and this is a different problem from the original post I am going to mark this as done.
ASKER
Thank you everyone for your help.
Glad the issue is fixed.
ASKER
thanks vSolution for your ongoing support. I work in the I.T Department at a school and I may work on exchange once every couple of years so when something goes wrong I sort of have to relearn it a bit as it just seems to hum along most the time so it was good to have someone keeping in touch as I was trying to get it working.