Introduction - Exchange 2010 Post Patch CAS Array Errors

Hello Fellow System Engineers...



I Hope this blog will help with those hard to find answers...


Every once in awhile google fails you....
It is my mission to save your kiester from staying up all night, losing data and damaging your forehead from the dreaded face-plant keyboard smash... we all hate that don't we...


This is a collection of the most annoying and difficult problems I have faced, (or will be facing!?) during my IT consultant tenure...

 You name it, I've probably blundered my way through it...


I hope this blog saves you from some of the long nights I had to endure..








Post Exchange Service Pack Upgrade - CAS Server Connectivity Issues


 I ran into this wonderful issue last night... turned a 2 hour quick Exchange 2010 SP1 to SP3 upgrade into a 4 hour nightmare.. well ok it wasn't so bad.. but it still annoying that microsoft always goofs up exchange updates..

After applying the sp3 patch to both servers in the CAS array we decided to stop and start testing access before moving on to the DAG. Everything APPEARED to check out.... but of course the last test, outlook anywhere, decided to take a dump.

 FACE-SMASH PREVENTION TIP: All the folder settings in IIS are reset during a patch upgrade, (so take screenshots or write down the SSL settings, authentication settings, and the redirect settings of ALL the subfolders in IIS)


I double-checked all the IIS settings again just to be sure I did not forget anything... everything checked out..

 I went into the Application Log to see if any errors were popping up... and it was full with the below error..

*********************************************************************************


Event code: 3008 
Event message: A configuration error has occurred. 
Event time: 12/11/2014 12:25:20 AM 
Event time (UTC): 12/11/2014 5:25:20 AM 
Event ID: c9c5ccec4c0446cd81ee2ea9ce3d9cd8 
Event sequence: 1 
Event occurrence: 1 
Event detail code: 0 

Application information: 
    Application domain: /LM/W3SVC/1/ROOT/Rpc-53-130627491203872611 
    Trust level: Full 
    Application Virtual Path: /Rpc 
    Application Path: C:\Windows\System32\RpcProxy\ 
    Machine name: BigDickMagee 

Process information: 
    Process ID: 5784 
    Process name: w3wp.exe 
    Account name: IIS APPPOOL\DefaultAppPool 

Exception information: 
    Exception type: ConfigurationErrorsException 
    Exception message: Could not load file or assembly 'Microsoft.Exchange.RpcClientAccess.Coexistence, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. 

Request information: 
    Request URL: https://Igot.abig.wanger:443/rpc/rpcproxy.dll?wang.wang.local:6001 
    Request path: /rpc/rpcproxy.dll 
    User host address: 741.109.146.876 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: IIS APPPOOL\DefaultAppPool 

Thread information: 
    Thread ID: 1 
    Thread account name: IIS APPPOOL\DefaultAppPool 
    Is impersonating: False 
    Stack trace:    at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
   at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement)
   at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList)
   at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext)
   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)


Custom event details: 

 ********************************************************************************************************

 What kind of BS is this?  Well let me tell you what happened...  The darn web.config file, located at 

 C:\windows\system32\rpcproxy\ 

 Did not update properly... and had incomplete paths.. Let me show you what i mean...

Post Patch RPC Web.Config file:                       

 ********************************************************************************************************
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Exchange.RpcClientAccess.Coexistence" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <codeBase version="14.0.0.0" href="file:///%ExchangeInstallDir%bin\Microsoft.Exchange.RpcClientAccess.Coexistence.dll" />
      </dependentAssembly>

      <dependentAssembly>
********************************************************************************************************



Pre Patch RPC Web.Config file:                      

 ********************************************************************************************************
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Exchange.RpcClientAccess.Coexistence" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <codeBase version="14.0.0.0" href="file:///C:\Program Files\Microsoft\Exchange Server\V14\bin\Microsoft.Exchange.RpcClientAccess.Coexistence.dll" />

      </dependentAssembly>

 ********************************************************************************************************


The "new" and "improved" web.config file uses some sort of variable that 
IIS NO LIKEY...  
Either do a find and replace inserting the correct full path OR restore the file from the backup you took before performing the upgrade.  You backed up everything beforehand right???

 After that is done run an IISRESET at an elevated command prompt.. you should not see those ASP errors anymore... Outlook Anywhere works in all its glory...


Hope this saved you at least a few hours and a phone call to "FRANK" from Mumbai... 

Comments

Post a Comment

Popular posts from this blog

"WE COULDN’T COMPLETE THE UPDATES. UNDOING CHANGES" HYPER V 2012 R2 ERROR

Image
Microsoft strikes again... another thoughtfully laid out patch that set my project back close to 16 hours. I am sure you are here because you are desperately trying to figure out why the first few VM's you have tried to build and patch on your 2012 R2 Hyper-V cluster are all stuck.   I would assume you see this wonderful message, and its been HOURS, maybe DAYS and there is no movement.  You probably have even built a new VM and started over thinking it was some sort of weird fluke.. or perhaps there is an issue with your shared storage.. Well no, you did nothing wrong.  The issue is that you chose to use Hyper-V Gen 2 and there is a patch [ KB2920189] t hat does not play well with Gen 2 VMs and SECURE BOOT . So to get around this problem, Power off the VM, its never going to finish.  Go into boot settings and then disable Secure Boot. Now power back on the VM, you will see the same error message, but this time it will go through.  It wi...
Read more

Hyperflex 3.0(1e) Nested VCenter Install Bug

I recently had to deploy a hyperflex cluster for a client, which was for a DR site.  The cluster was going to use an nested VCenter, meaning VCenter is within the hyperflex cluster itself.  There is some official documentation from Cisco on this, and it seems pretty straight forward. https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/TechNotes/Nested_vcenter_on_hyperflex.html#reference_8EF12C954D6049E285F924713804F9B6 However I ran into a few issues... First during the installer, I received an error """ INTERNAL_ERROR: something went wrong in executing scripts " I found the following Cisco Bug article: CSCvk07339 https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvk07339/?rfs=iqvred I didn't have the option of using a temporary external vcenter, this was a remote DR site with only the hyperflex hosts and networking equipment available.  Instead I put a fake vcenter cluster name, as mentioned as one of the...
Read more