exchange2013/2016 Ecp/owa cannot open home event 1310 Net 4.0

This article should actually change position with the previous article, this should be the problem that happened earlier.

When I encountered this problem, I was installing the first Exchange 2016 and Exchange 2010 Hybrid deployment.

At that time, the sex joyful but pits mixed with the Exchange 2016, although through their own error, solve the installation process encountered various problems (early exchange2010 environment is too bad), and finally successfully finished 2016.

When you are ready to open the ECP configuration server, the expected problem arises, and the ECP and OWA cannot be opened directly. Middle Recruit!

650) this.width=650; "height=" 484 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00 /7c/b6/wkiom1bwmttskmn5aagbksbl8-q093.png "border=" 0 "/>

Open log file, full screen warning error

650) this.width=650; "height=" 598 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01 /7c/b6/wkiom1bwmtag-bfraals7enn464531.png "border=" 0 "/>

650) this.width=650; "height=" 404 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02 /7c/b6/wkiom1bwmtnhpuyjaaljog7yaoe635.png "border=" 0 "/>

By carefully reviewing the logs, you find

650) this.width=650; "height=" 613 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02 /7c/b5/wkiol1bwm1odausjaaimkqlbv08409.png "border=" 0 "/>

This is called Sharedwebconfig.config file dropped, look at their two folders, sure enough clientaccess inside of this file dropped.

After querying KB, find a way to foreign devil, so the Exchange installation path under the Httpproxy copy of this file into clientaccess, such as:

650) this.width=650; "height=" "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M02 /7c/b6/wkiom1bwmtzwt10jaakq_o4ruaa597.png "border=" 0 "/>

The problem has been solved by the above operation.

Later find a piece of Microsoft Official note.

You can actually re-generate the Sharedwebconfig.config file automatically from the command line form.

1. First open cmd, locate the Bin folder under the installation directory of Exchange (%exchangeinstallpath%\bin), because we want to use a tool inside called DependentAssemblyGenerator.exe

2. If it is clientaccess the following file is dropped, use the following command

Dependentassemblygenerator.exe-exchangepath "%exchangeinstallpath%\bin"-exchangepath "%ExchangeInstallPath%\ ClientAccess "-configfile"%exchangeinstallpath%\clientaccess\sharedwebconfig.config "

3. If the Httpproxy wash-face file is dropped, use the following command

Dependentassemblygenerator.exe-exchangepath "%exchangeinstallpath%\bin"-exchangepath "%ExchangeInstallPath%\ Frontend\httpproxy "-configfile"%exchangeinstallpath%\frontend\httpproxy\sharedwebconfig.config "

4. CMD will run a lot of commands to rebuild this sharedwebconfig.config

650) this.width=650; "height=" 613 "title=" image "style=" border:0px; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00 /7c/b6/wkiom1bwmt-hzyolaapsojqxre8078.png "border=" 0 "/>

5. Restart IIS, fix the problem.

This article is from the "June Ma Run Space" blog, be sure to keep this source http://horse87.blog.51cto.com/2633686/1746783

exchange2013/2016 Ecp/owa cannot open home event 1310 Net 4.0