• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1128
  • Last Modified:

Exchange 2010 SP1 -> SP2 upgrade issues

Hello Exchange experts,

We’re having a bit of an issue:

At the company I work for, we’ve decided to upgrade our Exchange 2010 DAG cluster from service pack 1 to service pack 2 due to a series of strange issues we are having. This upgrade process itself has caused some issues that we’re trying to solve.

The DAG consists of two (CAS & Hub Transport) servers and 2 MailDB servers running on Windows Server 2008 r2.

We started by upgrading the first of our two CAS servers, which caused a few issues, first we had problems with http -> https redirection, because the default website was changed to require ssl.

After this was solved, people were unable to log onto the OWA, which was solved by changing requireSSL in the following line in web.config to false.
<httpCookies httpOnlyCookies="false" requireSSL="false" domain=""/>

After applying this fix, our users were able to log on, and view their email, but when they try certain things  they encounter an error, which says the following  “An unexpected error occurred and your request couldn't be handled.”.

This happens when:

1)      They try to create a new email, or reply to an existing email, and the fields “To:” or “CC:” are activated. That means there is no problem writing text, but the To field cannot be validated, and the mail cannot be sent.
If I press OK to hide the error, I can fill out the “To:” field, but when I then try to send the email the following pops up:
“You need to choose a recipient before this message can be sent.” And underneath that the same error reappears: “An unexpected error occurred and your request couldn't be handled.”.

2)      Accessing Deleted emails causes the error to show up as soon as I enter the Deleted Emails folder. If I click OK, the error shows up every time I change to a different email.

3)      Similarly for Sent items.

4)      Curiously, NOT for the Inbox. I can browse those mails fine.

So the situation right now is that we have one SP2 CAS server that doesn’t work fully, and one SP1 CAS server that works fine, and we’re reluctant to upgrade the other one until the first one is fully functional.

We use a load balancer to switch between them, and have currently disabled the SP2 CAS server in the loadbalancer.
0
JetTime
Asked:
JetTime
  • 5
  • 4
2 Solutions
 
Meir RivkinFull stack Software EngineerCommented:
did u try install the Update Rollup 3 for Exchange Server 2010 (SP2)?
that might fix your issues:
Update Rollup 3 for Exchange Server 2010 Service Pack 2
0
 
JetTimeAuthor Commented:
We've installed Update Rollup 5 v2, which did not solve the issue unfortunately.
0
 
Meir RivkinFull stack Software EngineerCommented:
do you see something on the event viewer?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
JetTimeAuthor Commented:
Under MSExchange CmdletLogs:

Cmdlet failed. Cmdlet Get-AddressBookPolicy, parameters {Identity=e80b230a-dbcf-4738-a9aa-dd392657af78}.

This only occurred once however.

In contrast, we have a lot of failed authentications in the Windows security auditing event log, but they do not coincide with the errors I encounter, so it does not trigger a log event when I log in, try to write an email and the error shows up - I think its unrelated.
0
 
Meir RivkinFull stack Software EngineerCommented:
are you using http redirect on iis?
0
 
JetTimeAuthor Commented:
I've resolved the issue - There was a Redirection loop, so that webmail.oursite.dk redirected to webmail.oursite.dk/owa. However, this redirection was also in place on the /owa site. Disabling it there stopped the issue.
0
 
Meir RivkinFull stack Software EngineerCommented:
thanks for the points.
0
 
JetTimeAuthor Commented:
Thank you for assisting - You came up with the correct solution before I posted that I had found it, even if by less than a minute, so it only seems fair you should be awarded for your assistance :)
0
 
JetTimeAuthor Commented:
Browsed google further for similar problems and encountered others who had the same issue due to a redirection loop from http to https, and from standard website to /owa.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now