IT for you

Error [80004005-501-4B9-560 or 80070057-501-80070057-560]: Synchronizing Forms Folder

myit4u — Fri, 09 Jul 2010 13:23:53 +0000

15:46:29 Synchronizing Forms
15:46:29 Downloading from server ‘Exch2010_MBX’
15:46:29 Error synchronizing folder
15:46:29 [80004005-501-4B9-560]
15:46:29 The client operation failed.
15:46:29 Microsoft Exchange Information Store
15:46:29 For more information on this failure, click the URL below:
15:46:29 http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560

I encountered this error when doing an Exchange 2k3 to 2k10 migration for a customer. After having to turn on “Use Exchange Cached Mode” to work around this (http://support.microsoft.com/?kbid=2009942) issue all our outlook clients started having problems with synchronizing the forms folder. Thanks to some colleagues I can report this is an issue by design and should hopefully be solved in Exchange 2010 RollUp 5. Official Microsoft comment below.

Hi,

Yes, similar issue but different error occurs in Outlook 2003. The issue has been aware by our product team and it is scheduled to be addressed in Exchange 2010 server RU5.

That’s all for now!

The certificate status could not be determined because the revocation check failed

myit4u — Tue, 29 Jun 2010 16:36:52 +0000

Hi everyone! Long time since I posted something worthwhile. Today I received the message below on an Exchange 2010 box after importing a certificate from a local enterprise CA.

Apparently this is related to the following KB (http://support.microsoft.com/kb/979694). Not for us as we didn’t use a third party certificate! Apparently this problem was associated with the enterprise CA settings involving the Certificate Revocation List distribution point. To solve we adjusted some settings as you can see in the images below.

Which should be adjusted to:

Apparently exchange doesn’t like to contact it’s CDP when using LDAP. The LDAP query also did not return any certificate when opening it through CertUtil.

The store driver couldn’t deliver the public folder replication message ” … (Public Folder Database@domain)” because the following error occurred: Cannot open mailbox ..

myit4u — Sun, 06 Jun 2010 13:03:13 +0000

The store driver couldn’t deliver the public folder replication message “Status Request (PUBDB01@testlab.local)” because the following error occurred: Cannot open mailbox ..

Fancy error, yes? It comes in two other forms as well.

The store driver couldn’t deliver the public folder replication message “Status (PUBDB01@testlab.local)” because the following error occurred: Cannot open mailbox ..

The store driver couldn’t deliver the public folder replication message “Hierarchy (PUBDB01@testlab.local)” because the following error occurred: Cannot open mailbox ..

As you can see, all three are related to eachother and public folder replication.

I encountered this error in a test environment of one DC + GC and two Exchange 2010 CAS, HUB, MBX servers. Because I’m still in the progress of understanding some concepts of Exchange server I started playing with some Public Folders. Anyway… Long story made short! I started some “googling” and soon found out that I should check my Message Tracking Log. I did that and found the following:

432 4.3.2 STOREDRV.Deliver; retryable mailbox access denied failure

Apparently this error involves the “Microsoft Exchange Transport” service! Simply setting that service’s logon to “Local System” solved this error.

Like I said.. Story made short, because that took 4 hours of my life! Hope it helps!

LaunchDLL: Could not load DLL drmv2clt.dll

myit4u — Wed, 17 Mar 2010 09:38:08 +0000

A colleague of mine experienced this strange issue the other when trying to sysprep a Windows Server 2008.

Funny error isn’t it? After some troubleshooting we found that the problem was somehow related to Media and Network sharing services. Guess what?! Those aren’t shown in on a Windows Server 2008! Our workaround was to install the Desktop Experience feature on the server. Obviously this server won’t be used in a production environment, but just in case you experience this in a test environment where the Desktop Experience isn’t all that much of a problem.