Skip to main content

bug with synthetic transactions (exchange 2007 native mp)

Computer bug

Image by Hil via Flickr

if you’re using the native exchange 2007 mp with clustered mailbox servers, you may have noticed that your synthetic transaction executions are timing out.

you should be able to recognize the alerts.  they look something like this:

Some of the MAPI connectivity transactions failed. Detailed information:

Target: System mailbox for XYZ

Error: The transaction did not complete in the alotted time (20 seconds).

 

here is an explanation from microsoft:

“In the core OpsMgr code, there is a “cluster override” that disables all workflows for objects that are contained by a cluster virtual server, unless the workflows are running on the Active Node.  When we create the relationship between the Synthetic Transaction object and the Cluster Virtual Node for the Mailbox Server, the CAS Server is now subject to the "cluster override" even though it isn't a member of the cluster, because now the Synthetic Transaction hosted on the CAS server is contained by the Cluster virtual server.”

 

the workaround is to disable the discovery that builds this relationship.  when you do this, be cognizant that the maintenance mode model changes.  the discovery mentioned above that requires disabling is:

name: rms target relationship discovery
target: root management server

 

this is the net effect of disabling this discovery:

  1. Mailbox Server is put into Maintenance Mode and taken offline
  2. The CAS Synthetic Transactions that target that Mailbox Server will not be put in MM and will continue to run
  3. The transactions will fail and will go into a critical state

 

oh well!  at least your synthetic transactions will run.  by the way, since this is a bug, it’s being worked on.  :)

Comments

  1. Nice post! We still experience this bug on weekly base. Have any ideas how to resolve this so far?

    Cheers mate

    ReplyDelete
  2. my understanding is that it was corrected in the latest mp.

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m