It can take several minutes to update an instance. This is not a great
experience. The reason is known (it has to do with some lower-level code
used by NS), and bugs have been filed.
Let it run for several minutes. It should complete. (It has every time for
When using SQL Server Managment Studio, I often multitask and don't realize
that a secondary window has popped up that requires me to click OK. I
thought I should mention that.
Diane Larsen [MSFT]
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
"Vince Sefcik" <[email protected]> wrote in message
> I have an application that has run under NS 2.0 for over a year. I
> it many times using "nscontrol update" without a problem. I recently
> converted the application to NS 2005 ande SQL Server 2005. After making
> necessary changes (e.g., change Notify function to Insert Into), I was
> to run "nscontrol create" and built the instance and application
> added a subscriber and subscription and it ran fine.
> I then needed to update the application using "nscontrol update" and
> nscontrol never completes. Regardless of whether I run nscontrol as a
> command-line or via Management Studio, the same happens: I get the message
> "Examining instance : ...", CPU cycles at 15%-40% (used by sqlservr.exe)
> the process never ends. If I kill the process, re-enable all components
> restart the Windows instance service, it works fine (with the
> prior to running "nscontrol update"). If I recreate the databases using
> "nscontrol delete" and "nscontrol create", everthing works OK. But,
> "nscontrol update" never gets past the "Examining instance" step.
> I'm using SQL Server 2005 Developer edition.
> Any suggestions on how to track down why "nscontrol update" never gets
> "Examining instance.."?