microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: Problem debugging in Visual Studio 2005 and SQL Server 2005

Subject: Re: Problem debugging in Visual Studio 2005 and SQL Server 2005
From: "David"
Date: 31 Aug 2006 13:54:43 -0700
Newsgroups: microsoft.public.sqlserver.notificationsvcs
After reading this link
http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=82&threadid=48372&enterthread=y,
I re-installed SQL Server 2005 in its entirety and the problem cleared
itself up. Not elegant, but it did solve the problem.
I suspect that somewhere in the combination of VS 2005 installs, etc.
The client tools got out of sync with the server.
I don't know.



InvalidLastName wrote:
> Any update on this?
>
> I was able to debug the SQLNS application in VS.NET 2005 with "-a" switch. 
> But I got same error when I ran the application -a switch after deployed it 
> to our testing server ( I was trying to identify why the service won't start 
> after applying sp1 and no error logged in the event log, see my other post 
> for details )
>
> ILN
>
> "David" <[email protected]> wrote in message 
> news:[email protected]
> > Is an explanation available for why one might get the following error
> > when starting an instance using the command line:
> >
> > nsservice InstanceName -a
> >
> > Microsoft SQL Server Notification Services service executable 9.0.242.0
> > c Microsoft Corp. All rights reserved.
> >
> > Running NS$MyInstance as an application.  Press RETURN to quit...
> >
> > Error: 99:
> > The Notification Services instance encountered an error in one of its
> > components and must stop.
> > Instance Name: MyInstance
> > Problem Description: UpdatePendingStatus can only be called during the
> > handling of Start, Stop, Pause and Continue commands.
> > Instance: MyInstance
> > Component: Service
> > ComponentDetails: ServiceName: NS$MyInstance
> > Thread: 1
> >
> > The instance otherwise runs fine when invoked from SCM.
> >
> ------=_NextPart_000_0045_01C6BEF1.9AA44350
> Content-Type: text/html; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Google-AttachSize: 2417
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
> <META content="MSHTML 6.00.3790.1830" name=GENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY>
> <DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2>Any update on
> this?</FONT></DIV>
> <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
> <DIV><FONT face=Arial size=2>I was able to debug the SQLNS application in 
> VS.NET
> 2005 with "-a" switch. But I got same error when I ran the application -a 
> switch
> after deployed it to our testing server ( I was trying to identify why the
> service won't start after applying sp1 and no error logged in the event log, 
> see
> my other post for details )</FONT></DIV>
> <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
> <DIV><FONT face=Arial size=2>ILN</FONT></DIV>
> <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
> <DIV><FONT face=Arial size=2>"David" &lt;</FONT><A
> href="mailto:[email protected]";><FONT face=Arial
> size=2>[email protected]</FONT></A><FONT face=Arial size=2>&gt; wrote in
> message </FONT><A
> href="news:[email protected]";><FONT
> face=Arial
> size=2>news:[email protected]</FONT></A><FONT
> face=Arial size=2>...</FONT></DIV><FONT face=Arial size=2>&gt; Is an 
> explanation
> available for why one might get the following error<BR>&gt; when starting an
> instance using the command line:<BR>&gt; <BR>&gt; nsservice InstanceName
> -a<BR>&gt; <BR>&gt; Microsoft SQL Server Notification Services service
> executable 9.0.242.0<BR>&gt; c Microsoft Corp. All rights reserved.<BR>&gt;
> <BR>&gt; Running NS$MyInstance as an application.&nbsp; Press RETURN to
> quit...<BR>&gt; <BR>&gt; Error: 99:<BR>&gt; The Notification Services instance
> encountered an error in one of its<BR>&gt; components and must stop.<BR>&gt;
> Instance Name: MyInstance<BR>&gt; Problem Description: UpdatePendingStatus can
> only be called during the<BR>&gt; handling of Start, Stop, Pause and Continue
> commands.<BR>&gt; Instance: MyInstance<BR>&gt; Component: Service<BR>&gt;
> ComponentDetails: ServiceName: NS$MyInstance<BR>&gt; Thread: 1<BR>&gt; 
> <BR>&gt;
> The instance otherwise runs fine when invoked from
> SCM.<BR>&gt;</FONT></BODY></HTML>
> 
> ------=_NextPart_000_0045_01C6BEF1.9AA44350--


<Prev in Thread] Current Thread [Next in Thread>
  • Re: Problem debugging in Visual Studio 2005 and SQL Server 2005, David <=