CAS not working with Outlook after OS upgrade

%3CLINGO-SUB%20id%3D%22lingo-sub-1096609%22%20slang%3D%22en-US%22%3ECAS%20not%20working%20with%20Outlook%20after%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096609%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20on-prem%20Exchange%202010%20SP3%20environment.%20It%20consists%20of%202x%20Client%20Access%20Servers%20(CAS01%2BCAS02)%20and%202x%20Mailbox%20servers%20(MB01%2BMB02).%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20CAS%20are%20running%20a%20Windows%20software%20NLB%20and%20the%20MB-servers%20are%20running%20a%20DAG%2C%20with%20CAS01%20being%20the%20witness%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3%20of%20the%20servers%20are%20running%20Windows%20Server%202008%20R2%20while%20the%20last%20one%20(CAS01)%20earlier%20today%20was%20upgraded%20to%20Server%202012%20R2%20through%20an%20in-place%20upgrade%20due%20to%20the%20pending%20end-of-life%20of%20Server%202008(R2).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20that%20both%20Exchange%20and%20OS%20versions%20are%20way%20behind%2C%20hence%20the%20upgrade%20%3A)%3C%2Fimg%3E%20a%20full%20migration%20to%20another%20Exchange%20environment%20is%20planned%20within%20the%20next%204-6%20months%2C%20which%20is%20why%20we%20are%20only%20upgrading%20the%20server%20OS'es.%20Exchange%202010%20goes%20EOL%20in%20October%202020%2C%20but%20the%20current%20setup%20should%20be%20decomissioned%20by%20then.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20the%20problem%3A%3C%2FP%3E%3CP%3EAs%20stated%2C%26nbsp%3BCAS01%20was%20upgraded%20to%20Server%202012%20R2%20and%20the%20upgrade%20went%20as%20planned%20with%20no%20errors.%3CBR%20%2F%3EHowever%2C%20after%20the%20upgrade%20CAS01%20no%20longer%20works%20with%20Outlook.%20OWA%20and%20ActiveSync%20works%20fine%2C%20but%20not%20Outlook.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAll%20services%20are%20running%2C%20network%20connectivity%20is%20fine%20(obviously%2C%20since%20OWA%20and%20AS%20work)%20and%20everything%20else%20looks%20normal%20on%20the%20server.%3C%2FP%3E%3CP%3EWhen%20trying%20to%20start%20Outlook%20on%20a%20client%20machine%20I%20get%20the%20following%20error%3A%3CBR%20%2F%3E%22Cannot%20start%20Microsoft%20Outlook.%20Cannot%20open%20the%20Outlook%20window.%20The%20set%20of%20folders%20cannot%20be%20opned.%20The%20attempt%20to%20log%20on%20to%20Microsoft%20Exchange%20has%20failed.%22%20(attached%20screenshot).%3CBR%20%2F%3EWhen%20getting%20this%20error%2C%20I%20have%20disabled%20the%20non-upgraded%20CAS02%20in%20the%20NLB%20to%20ensure%20that%20CAS01%20gets%20the%20requests.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWhen%20I%20disable%20CAS01%20in%20the%20NLB%20and%20enable%20CAS02%2C%20Outlook%20works%20as%20normal.%3C%2FP%3E%3CP%3EThe%20plan%20is%20to%20upgrade%20the%20remaining%203%20servers%20to%202012%20R2%20as%20well%2C%20but%20this%20will%20of%20course%20wait%20until%20any%20and%20all%20problems%20are%20sorted.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20by%20no%20means%20an%20Exchange%20guru%2C%20so%20I%20am%20running%20out%20of%20ideas%20on%20why%20this%20isnt%20working.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAny%20advice%20is%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%20%26amp%3B%20thanks%20in%20advance%3CBR%20%2F%3EAnders%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1096609%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1101208%22%20slang%3D%22en-US%22%3ERe%3A%20CAS%20not%20working%20with%20Outlook%20after%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1101208%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%3A%20the%20reason%20was%20very%20simple.%20OS%20upgrade%20is%20not%20supported%20on%20Exchange%20servers%2C%20end%20of%20story.%3C%2FP%3E%3CP%3EThe%20solution%20would%20be%20to%20create%20new%20servers%20and%20migrate%20the%20environment.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

 

We have an on-prem Exchange 2010 SP3 environment. It consists of 2x Client Access Servers (CAS01+CAS02) and 2x Mailbox servers (MB01+MB02).


The CAS are running a Windows software NLB and the MB-servers are running a DAG, with CAS01 being the witness server.

 

3 of the servers are running Windows Server 2008 R2 while the last one (CAS01) earlier today was upgraded to Server 2012 R2 through an in-place upgrade due to the pending end-of-life of Server 2008(R2).

 

I know that both Exchange and OS versions are way behind, hence the upgrade :) a full migration to another Exchange environment is planned within the next 4-6 months, which is why we are only upgrading the server OS'es. Exchange 2010 goes EOL in October 2020, but the current setup should be decomissioned by then.

 

 

Now, the problem:

As stated, CAS01 was upgraded to Server 2012 R2 and the upgrade went as planned with no errors.
However, after the upgrade CAS01 no longer works with Outlook. OWA and ActiveSync works fine, but not Outlook.


All services are running, network connectivity is fine (obviously, since OWA and AS work) and everything else looks normal on the server.

When trying to start Outlook on a client machine I get the following error:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opned. The attempt to log on to Microsoft Exchange has failed." (attached screenshot).
When getting this error, I have disabled the non-upgraded CAS02 in the NLB to ensure that CAS01 gets the requests.


When I disable CAS01 in the NLB and enable CAS02, Outlook works as normal.

The plan is to upgrade the remaining 3 servers to 2012 R2 as well, but this will of course wait until any and all problems are sorted.

 

I am by no means an Exchange guru, so I am running out of ideas on why this isnt working.


Any advice is greatly appreciated.

 

Best regards & thanks in advance
Anders

1 Reply
Highlighted

Update: the reason was very simple. OS upgrade is not supported on Exchange servers, end of story.

The solution would be to create new servers and migrate the environment.