Thank you, that was it. On Thu, Dec 18, 2014 at 3:18 PM, Jonathan Raper <[email protected]> wrote: > > I have. > > > > Go into this directory on both servers: > > > > C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp > > > > Look for the numbered folders 15.0.xxx.yy > > > > Compare the contents of each on the non-working server to the working > server. I’m betting you’ve got some missing files in the folders on the > non-working server. There is also a PS script that can fix that for you, > possibly, but start with the numbered folders first. > > > > > > Thanks, > > > > *Jonathan L Raper, A+, MCSA, MCSE, FCC Licensed Technician, VCA-DCV, > VCA-Cloud * > > Senior Solutions Engineer > > [image: cid:[email protected]]* Corporation* > > 336.232.5244 Cisco Single Number Reach > > 7025 Albert Pick Road, Suite 302, Greensboro, NC 27409 > > www.*NWN*IT.com <http://www.NWNIT.com> > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Lemmiksoo > *Sent:* Thursday, December 18, 2014 4:11 PM > *To:* [email protected] > *Subject:* [Exchange] ECP issue after installing Exchange 2013 CU6 > > > > I installed Exchange 2013 CU6 on my two CAS/Mailbox servers last night. > ECP works on one but not the other. You get the login page enter your ID & > password and page errors out. > > In event log see warning message about ASP.NET 4.030319.0 event 3008 > configuration error. > > Any one seen this before. > > > -- > > T. Todd Lemmiksoo > > ------------------------------ > Note: This message and any attachments is intended solely for the use of > the individual or entity to which it is addressed and may contain > information that is non-public, proprietary, legally privileged, > confidential, and/or exempt from disclosure. If you are not the intended > recipient, you are hereby notified that any use, dissemination, > distribution, or copying of this communication is strictly prohibited. If > you have received this communication in error, please notify the original > sender immediately by telephone or return email and destroy or delete this > message along with any attachments immediately. >
-- T. Todd Lemmiksoo
