"The nscontrol register command must be run locally. You cannot
use NSControl to register the instance.
I support PASS, the Professional Association for SQL Server.
<tarpan@discussions.microsoft.com> wrote:
>nscontrol Crashes if I start it from remote location.
>
>"Notification Services Command Prompt" shows
>CMD.EXE was started with '\\jadm\c\Program Files\Microsoft SQL
>Server\90\Notific
>ationServices' as the current directory path. UNC paths
>are not supported. Defaulting to Windows directory.
>'C:\Program' is not recognized as an internal or external command,
>operable program or batch file.
>
>
>
>"Joe Webb" wrote:
>
>> On the server that will host your subscription management application,
>> you need to register the instance using something like:
>>
>> nscontrol register -name instanceName -server databaseServer
>>
>> where instanceName is the name of the instance and databaseServer is
>> the name of the server that hosts the instance database.
>>
>> If you omit the -server parameter, NSControl defaults to the local
>> server name.
>>
>> How did you register your instance on the IIS box?
>>
>> HTH...
>>
>>
>> --
>> Joe Webb
>> SQL Server MVP
>>
http://www.sqlns.com >>
>>
>> ~~~
>> Get up to speed quickly with SQLNS
>>
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 >>
>> I support PASS, the Professional Association for SQL Server.
>> (
www.sqlpass.org)
>>
>>
>>
>>
>> On Tue, 17 Jan 2006 13:56:04 -0800, tarpan
>> <tarpan@discussions.microsoft.com> wrote:
>>
>> >Hi,
>> >
>> >It suppose to be real simple, but I can not find out how to do it. I have a
>> >SQL server and Web server on 2 separate PCs. When I create NSInstance object
>> >
>> >NS_Instance = New
>> >Microsoft.SqlServer.NotificationServices.NSInstance(NS_InstanceName)
>> >
>> > .Net tries to access NS right on the Web server.
>> >
>> >How to point it to the another PC?
>> >
>> >
>> >
>> >Thanks
>> >
>> >Oleksiy
>> >