Forum Discussion
KosmosKami
Sep 19, 2023Copper Contributor
Correct path in SharedWebConfig.config for ClientAccess
Hello, community.
After installing the next update, I received a non-working OWA. As you may know, Microsoft recommends that you create the file SharedWebConfig.config in ClientAccess folder again using the utility DependentAssemblyGenerator.exe. But, when command
DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config"
done, I got the next I am getting the following content in the file
<codeBase version="4.2.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\V15\\bin\AntiXssLibrary.dll" />
or
<codeBase version="1.1.5274.28150" href="file:///C:\Program Files\Microsoft\Exchange Server\V15\\bin\AsyncDnsManaged.dll" />
So I have a question. Why does there appear another \ character in the path before \bin?
And when I check the server status with script from PSGallery, one of the items is that the file SharedWEbConfig.config is missing. Could this be related?
- LeonPavesicSilver Contributor
Hi KosmosKami,
the extra \ character in the path before \bin is a typo. The correct path to the SharedWebConfig.config file is:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\SharedWebConfig.config
To fix the path in the SharedWebConfig.config file, you can use a text editor such as Notepad to open the file and remove the extra \ character. Once you have saved the file, you should restart the Exchange services.
Yes, the missing SharedWebConfig.config file is likely related to the non-working OWA. To create the SharedWebConfig.config file again, you can use the following command:
DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config"
Once you have created the SharedWebConfig.config file, you should restart the Exchange services.
Here are the steps to fix the non-working OWA:
- Open a command prompt window as an administrator.
- Navigate to the Exchange installation directory.
- Run the following command:
DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config"
- Restart the Exchange services.
Once you have completed these steps, OWA should be working again.
These are some more reference links for fixing non-working OWA Exchange Server:
- OWA or ECP stops working after you install a security update - Exchange | Microsoft Learn: https://learn.microsoft.com/en-us/exchange/troubleshoot/client-connectivity/owa-stops-working-after-update
- Exchange Server OWA and ECP not working - Jaap Wesselius: https://jaapwesselius.com/2021/12/01/exchange-server-owa-and-ecp-not-working/
- Exchange Server error in '/owa' application - Microsoft Tech Community: https://techcommunity.microsoft.com/t5/exchange/exchange-server-error-in-owa-application/td-p/2546400
- You can't access OWA or ECP after you install Exchange Server 2016 CU6: https://support.microsoft.com/en-au/topic/you-can-t-access-owa-or-ecp-after-you-install-exchange-server-2016-cu6-88b3fe67-5f97-a8a2-8ed8-70034ff15761
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.If the post was useful in other ways, please consider giving it Like.
Kindest regards,
Leon Pavesic
- JaberCopper Contributor
Hi,
I have a Problem with ecp and owa in Exchange and want to create a new sharedwebconfig.config, but Exchange is installed on Drive D!!
That's why I get an error message: Path not found!
What should I do now?Jaber
- KosmosKamiCopper ContributorThank you.
I have a couple more questions. I tried to delete the file and the utility creates it itself with the wrong syntax. It's strange, isn't it? I don't think there's much point in trying it again. I'll try to edit the file in Notepad. And one moment. Need to restart all Exchange services? In the microsoft article it was stated that it is enough to perform iisreset.