M2M Warning. Please Read ASAP

This morning approximately 75% of my users were no longer able to open M2M without an error. The error says “Omsg is not found” and this typically indicates a VBA issue.

The problem appears to be related to a set of updates issued yesterday and is only affecting those machines which have Office 2007 installed. I am running Windows XP and M2M Version 5.6.

I will follow up with details after I have thoroughly tested everything, but I wanted to give a heads up to any of my readers in case they run into the same problem.

6 comments to M2M Warning. Please Read ASAP

  • scott

    Good to know. Fortunatly we only have a couple of people on 2007 and most don’t use automatic updates.

    What is the M2M CR#?

  • roleki

    Good to know; is this limited to local installs, or is it affecting TS installs as well?

  • I am loathe to admit it, but the problem was ours, not the update or M2M. I’ll follow up with a detailed explanation soon.

  • Alex

    So, what is the ultimate resolution to this issue?


  • Wow, this is a blast from the past. To the best of my recollection, the problem was the way we installed M2M. We created an automated script to install M2M silently. It included the installation of VBA as well. VBA installation is a convoluted process. I cannot remember every detail, but there are steps where you move this file to that directory and then activate it there. It must be activated locally. However, we accidentally “activated” it on a remote share. Well, that works fine until someone decommissions that remote share server. This happened and my VBA installations went nuts. Hope that helps.

  • Alex

    Thanks for the response David! I will follow your recommendation and see if it helps.

Leave a Reply




You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>