On Fri, 26 Jan 2007 10:29:05 -0800, Todd C wrote:

> I am new to NS 2005 and going through some samples from Shyam Pather's book.
>
> I can create a NS instance, and register and enable it. But I am having
> trouble getting the service to start.
>
> I am working on an XP machine, connected to a domain. I had the domain admin
> guys create an account that will be used as the startup account for the new
> NS service. I have added that account to my local group
> "SLQServer2005NotificationServicesUser$<machine name>.
>
> But the service does not start. It errors out with Error 1359.
>
> If I add the service account as a member of my local Administrators group,
> it starts OK (I know, not the best practice but just learning on a local
> machine for now). So I deduce that the service account does not have
> sufficient permissions.
>
> What other permissions does it need? What other groups should it be a member
> of?
>
> Thanks in advance.

On Mon, 29 Jan 2007 05:45:01 -0800, Todd C wrote:

> Joe:
>
> Thanks for the tip, but my service account is already a member of the
> NSRunService role in the NS Instance database.
>
> I saw a post similar to this and the suggestion was to uninstall and
> reinstall NS. Not sure that would help seeing how I have proved that it is
> based on the service account not having sufficient permissions unless it is a
> member of the local Administrators group.
>
> How about this: the samples in the book sometimes use a File system delivery
> channel. Is it possible that if the Service Account does NOT have permissions
> on the directory referenced in the <Delivery Channels> section of the ICF
> that it won't be able to start? Therefore, should I grant the Service Account
> appropriate file permissions?
>
> Thanks

On Thu, 01 Feb 2007 08:15:01 -0800, Todd C wrote:

> Joe:
>
> Wow! That was a very freshman DBA mistake on my part: Failed to create the
> LOGIN, and only created the DB user.
>
> One would think ...
>
> That if a database USER is not valid without a login, that before SQL Server
> would allow you to create a USER for a database, it would first check to make
> sure that the LOGIN existed. (Funny how a product like SQL Server, that can
> get heavy into REFERENTIAL INTEGRTITY between data rows, does NOT ENFORCE
> that same concept when it applies to logins and users!)
>
> Thanks.
>
> Todd

"Todd C" <ToddC@discussions.microsoft.com> wrote in message
news:AC608CEE-E921-4000-BA1A-6DF4C89C4886@microsoft.com...
> Joe:
>
> Wow! That was a very freshman DBA mistake on my part: Failed to create the
> LOGIN, and only created the DB user.
>
> One would think ...
>
> That if a database USER is not valid without a login, that before SQL
> Server
> would allow you to create a USER for a database, it would first check to
> make
> sure that the LOGIN existed. (Funny how a product like SQL Server, that
> can
> get heavy into REFERENTIAL INTEGRTITY between data rows, does NOT ENFORCE
> that same concept when it applies to logins and users!)
>
> Thanks.
>
> Todd