sql server notification services: OK - for testing I have the following setup....

The NS databases, distributor, generator, windows service, etc. is all
on my PC - we'll call it Instance1 - the machine can be called
Instance1Machine. I want to install the client tools and register
Instance1 on another machine (without installing a service there -
example at BOL at
http://msdn2.microsoft.com/en-us/library/ms162762.aspx ). That 2nd
machine is going to act as a subscription management interface. The
two machines sit in different domains (which I know may be a problem,
but it's the only machine I could find).

I first added an alias to the Instance1 SQL machine.

So I try this & registration is successful.

nscontrol register -name Instance1 -server Instance1Machine

But then when I view the status I get this:

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 10061
State: 0
Class: 20
Server:
Message: An error has occurred while establishing a connection to the
server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow
remote connections. (provider: TCP Provider, error: 0 - No connection
could be made because the target machine actively refused it.)

I've got remote connections enabled on Instance1Machine SQL box. Why
can't I connect from my subscription machine to the NS instance
machine???

have a look at the registry settings that the registration process
created in local machine/software/microsoft/notifications services

also is the user account you are using valid in both domains?

kate

I'll take a look at the registry tomorrow when I get back.

As far as the user accounts go - I think I'm not quite understanding
what I should be doing. I have a domain account set up in the domain
that my NS instance, databases, distributor, generator, and applicaiton
databases sit (i.e. on my PC). I have that user set with permissions
and in the NSRunService role, and I created the windows service with
that user account.

How does this relate to the subscriber management machine? According
to the BOL how-to on nscontrol (see above), my situation seems to fall
under this example where I wouldn't need to specify
credentials???......

"
B. Registering an instance without creating a Windows service

This example shows how to register an instance named StockInstance in
the following scenarios:

* A subscription management interface or independent event provider
is located on the server, but the server does not run a hosted event
provider, generator, or distributor.

In these scenarios, you must register the instance so that instance
components can locate the databases, but you do not use the -server
argument to create the Windows service.

nscontrol register -name StockInstance -server nsuetest

"

The Subscription Management Application (SMA) must be able to login to
the SQL Server database and have sufficient permissions to manipulate
the subscriber and subscription data. The easiest way to do this is to
use the NSSubscriberAdmin database role that's available in the NS
database.

Since your SMA and database are in different domains, you'll likely
need to use SQL Server security rather than Windows integrated
authentication.

Have a look at this BOL link.
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlntsv9/html/6d944fa4-f8eb-44ab-bd80-7c33ef90c9bc.htm
HTH...

Joe


--
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)

[quoted text, click to view]