http://blogs.msdn.com/rslaten/archive/tags/MOM+2005/default.aspxTags: MOM 2005en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/rslaten/archive/2007/11/08/mom-2005-mcf-throws-an-exception-when-updatealerts-is-called.aspxThu, 08 Nov 2007 19:00:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:5989673rslaten0http://blogs.msdn.com/rslaten/comments/5989673.aspxhttp://blogs.msdn.com/rslaten/commentrss.aspx?PostID=5989673http://blogs.msdn.com/rslaten/rsscomments.aspx?PostID=5989673<P>After calling UpdateAlerts() an exception is returned: "Value does not fall within the expected range". DBGView will show the following output: </P> <P><SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: Arial">[4680] [E] 04680.01796, (cdasmomconnectorframework.cpp::2114) Could not decode unknown vartype 36 ! <BR></SPAN><SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: Arial">[4680] [E] 04680.01796, (cdasmomconnectorframework.cpp::2045) Could not decode unknown vartype 36 ! <BR></SPAN><SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: Arial">[4680] [E] 04680.01796, (cdasmomconnectorframework.cpp::1991) Could not determine ADO type or typeLength for [0][0] Param Name is @AlertId and VARTYPE is 36 [hr=0x80070057]! <BR></SPAN><SPAN style="FONT-SIZE: 7pt; FONT-FAMILY: Arial">[4680] [E] 04680.01796, (cdasmomconnectorframework.cpp::1342) AppendParamsFromSafeArray() failed for AlertHistory # 0 [hr=0x80070057] ! </SPAN></P> <P>This error occurred for a customer after compiling their custom application in Visual Studio 2005. This did not happen when it was compiled with Visual Studio 2003. It turns out that the MCF isn't designed to work with the .NET 2.0 runtime. The solution here is to compile the application in VS 2003 or us MSBee (<A href="http://www.codeplex.com/MSBee" mce_href="http://www.codeplex.com/MSBee">http://www.codeplex.com/MSBee</A>) to force the use of the .NET 1.1 runtime.</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=5989673" width="1" height="1">MOM 2005http://blogs.msdn.com/rslaten/archive/2007/09/19/mom2005-timeoffirstevent-and-timeoflastevent-are-set-to-12-30-1899.aspxWed, 19 Sep 2007 21:06:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:4999541rslaten0http://blogs.msdn.com/rslaten/comments/4999541.aspxhttp://blogs.msdn.com/rslaten/commentrss.aspx?PostID=4999541http://blogs.msdn.com/rslaten/rsscomments.aspx?PostID=4999541I recently had a customer ask me why the TimeOfFirstEvent and TimeOfLastEvent fields in an alert get set to 12/30/1899 when their custom application, which uses the MOM Connector Framework (MCF), uses UpdateAlerts() to set the resolution state of an alert.&nbsp; I did some research and found that SQL Profiler actually shows this old date being passed to the MCF_DoAddPendingAlertUpdate stored procedure.&nbsp; After doing a code review and review of the SDK I noticed that this will occur if you don't specifically&nbsp;set a value&nbsp;for TimeOfFirstEvent and TimeOfLastEvent and/or you don't flip the boolean bit on TimeOfLastEventUseExisting and TimeOfFirstEventUseExisting.<img src="http://blogs.msdn.com/aggbug.aspx?PostID=4999541" width="1" height="1">MOM 2005