July 2007 - Posts

MOM 2005 Backwards Compatibility MP

The MOM 2005 Backwards Compatibility MP is used in Operations Manager 2007 to work with MPs that are converted using the MPConvert utility.

As changes are made to accomidate rules in MOM 2005, the MOM 2005 Backwards Compatibility MP is updated.  So, this means that if an MP is converted from MOM 2005, you need to have the MOM 2005 Backwards Compatibility MP installed.

Microsoft has updated the MOM 2005 Backwards Compatibility MP and released it to the web. 

According to Peter Schmatz:

"MP convert and Back Compat MP (and related MPs) work together, that is we created additional monitortypes in the Back Compat MP and change MPconvert to take advantage of these. The main issues that have been fixed:- 

  • 2-state threshold monitors: These are now converted to a new monitortype that exposes overrides (and allows to seal the converted MP and change the threshold) (5000.1-)         
  • 3-state threshold monitors: Same as above, this time for 3-state (the SMS MP gets re-released using this type) (5000.12)-         
  • Note that in MOM 2005 you could create n-state monitor logic, which we had to handle: The n-state gets still converted to a generic monitortype that doesn’t allow overrides. 

We are catching the common 95% cases for 2-state and 3-state monitors however. Clustered Back Compat discovery: This was not working, and the Exchange 2007 MP did not work: This is a Back Compat MP fix only (no MPConvert issue). (5000.12)

 MOM 2005 Windows service monitoring: It was possible to create a “wildcard” Windows Service monitor in MOM 2005 which did not get converted correctly. (Biztalk MP, ForeFront etc), and we had to a major fix to Back Compat, and MPconvert, including a module change   (5000.12)"

The thing to remember here is, if you use a converted MOM 2005 MP in Ops Mgr 2007, you need to make sure you have the newest MOM 2005 Back Compat MP.

-JFH

Posted Monday, July 16, 2007 2:26 PM by jfhann | with no comments
Filed under:

SQL 2000 Error

While working on a server that was configed from an image, I received the following error when trying to delete a SQL Agent job:

"Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved."

The following KB Article pointed to the issue: http://support.microsoft.com/kb/281642

But, instead of renaming the box back to the original name, I went hunting in the msdb database, in the sysjobs table.  I found the offending job and deleted it.  So that is an option if you don't need to get the original job back.

-JFH

Posted Thursday, July 12, 2007 2:36 PM by jfhann | with no comments
Filed under:

Moved the MOM 2005 DB and the Reindex job Fails

I have to move the MOM 2005 DB to a new server.  One thing I forgot was the issue with the reindex and optimization jobs failing with strange codes.

Listed in the job history is: "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).  The step failed."  That is too generic.

Looking at the Database Maintenance Plan History you get the real issue: "[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'."

Looking that up and you find: http://support.microsoft.com/kb/902388/en-us

I know I have done this before...and I look at the old server, the -S option and the -SupportComputedColumn  was in my Reindex job

-JFH

Posted Thursday, July 12, 2007 8:10 AM by jfhann | with no comments
Filed under: