Running into Public Folders problems after migration? Read this first…
After migrating your Exchange Public Folders from Exchange 2003 to Exchange 2007 / 2010 chances are you will start experiencing some problems.
These issues might show up under different symptoms however they all have one common solution.
Changing password using Exchange 2010 OWA fails
There have been lately quite a few buzz around the fact that changing password through Exchange 2010 OWA is failing with the following error even though user is not logged on with the light version of Outlook Web App
This feature isn't supported in the light version of Outlook Web App.
This feature isn't supported if Outlook Web App is set to maximize the blind or low vision experience.
This error is due typically because the operating system on which you are running your Exchange 2010 CAS has been cloned, virtual image template etc..., but not prepared with sysprep before installing Exchange on it.
OCS 2007 R2 Clients cannot connect to Lync Server due to authentication Service incompatibility
After migrating to Lync 2010 server some of my client users where not able to log in using OCS 2007 R2 clients due an incompatibility in the Authentication Service version.
I have checked the OCS 2007 R2 client logs, by browsing to %userprofile%\tracing\Communicator-uccapi-0.uccapilog and noticed the following error
010/08/2010|11:51:55.781 E0C:14A8 INFO :: SIP/2.0 401 Unauthorized
Cannot move mailboxes: INSUFF_ACCESS_RIGHTS error
When moving mailboxes from Exchange 2003 to Exchange 2007 or Exchaneg 2010 either from Exchange Management Console or Powershell using the move-mailbox or new-moverequest cmdlets the move operation might fail with the following error.
Active Directory operation failed on server.domain.com. This error is not retriable. Additional information:
Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], ADOperationException
+ FullyQualifiedErrorId : 6C39B6E8,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
At first sight it looks like the user initiating the move mailbox doesn't have enough rights to perform this operation, however that user can move other mailboxes just fine.
Here is how to solve the issue
Solved: Setup Exchange 2007 SP1 CCR passive node fails
When installing Exchange 2007 SP1 in Cluster Continuous Replication (CCR) configuration. The setup of the passive node fails with the following error:
"This is not a passive node. A clustered mailbox server represented by the cluster resource group [clustername] was found on this node."
I've found out that the reason for the problem is that upon finishing the Exchange Cluster installation on the active node the setup will ask you for a restart. Restarting the machine will cause the Windows cluster to failover to the passive node to be and thus causing the Exchange installation to fail on that node.
To solve this problem make sure to move back the cluster resources to the active node and re-run the Exchange 2007 SP1 installation on passive node.
This solution was tested on Microsoft Windows 2008 and Microsoft Exchange 2007 SP1
Give me 2 minutes and I'll save you hours of Exchange troubleshooting !
Disclaimer: Guys if you happen to be suffering from "Event ID: 494" syndrom on your Microsoft Exchange Server do not attempt anything before reading this article, I might save you a lot of time.
It is always frustrating to me to receive a calls from customers telling me that their exchange database is refusing to mount and that they have tried everything, even restored from their last backup but nothing seems to work! Oh if only they'd call earlier
Symptoms: Typically a storage group will fail to mount and an error will be logged in the Application Log with an event id of 494. The error is the following
