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.
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#?
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.