Colin is correct. I should also point out that it's dangerous to use the sa
account to connect to the database server. You are granting the service way
roles.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Colin Meek" <cmeek@alias.microsoft.com> wrote in message
news:OO76$EUYFHA.2076@TK2MSFTNGP15.phx.gbl...
> Tarpan --
>
> You must use the InstallXps script (in the NS "Bin" directory) to register
> NS extended stored procedures on the the server instance.
>
> Just to make sure we aren't looking in the wrong places, can you forward
any
> event log errors you are receiving when launching the NS service against
the
> named SQL instance?
>
> - Colin Meek [MSFT]
>
> 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
>
http://www.microsoft.com/info/cpyright.htm. >
> "tarpan" <tarpan@discussions.microsoft.com> wrote in message
> news:D872946A-7865-4D19-BBB5-B50D25E2E870@microsoft.com...
> >I have found something new. NS suppose to add one stored procedure to the
> > master db named "xp_NSPermissions_2_0_3008_0". It does not create it on
> > the
> > named instance for whatever reason. It causes the problem.
> >
> > PS. Once again, as a SQL user I use "sa".
> >
> > "Joe Webb" wrote:
> >
> >> Hi Tarpan -
> >>
> >> When the NS$<InstanceName> service fails to start, the first thing I
> >> check is permissions. Does the account used by the service have
> >> appropriate database permissions to login to SQL Server? Does it have
> >> access to the master, instance, and application databases?
> >>
> >> Here's a thread that may help...
> >>
http://groups-beta.google.com/group/microsoft.public.sqlserver.notificationsvcs/browse_thread/thread/bf64b8b0345f8743/0e50fb3e4600aae2?q=permissions&rnum=4&hl=en#0e50fb3e4600aae2
> >>
> >>
> >>
> >> HTH...
> >>
> >> --
> >> Joe Webb
> >> SQL Server MVP
> >>
> >>
> >> ~~~
> >> 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, 24 May 2005 11:17:02 -0700, tarpan
> >> <tarpan@discussions.microsoft.com> wrote:
> >>
> >> >Hi guys,
> >> >
> >> >I have added one more named instance to my SQL Server and tried to use
> >> >NS on
> >> >it. I can not start the service. The "net use start ...." command
shows
> >> >the
> >> >following message:
> >> >
> >> >Could not start the NS$ELSInstance service on Local Computer.
> >> >The service did not return an error. This could be an internal windows
> >> >error
> >> >or an internal service error.
> >> >If it problem persists, contact your system administrator.
> >> >
> >> >However, the nscontrol command creates the instance, registers and
> >> >enables
> >> >the service just fine. The created databases are available. Everything
> >> >seems
> >> >to be fine, I just can not start the service.
> >> >
> >> >The same appADF works just fine on the default instance of the SQL
> >> >server on
> >> >the same PC. %-)
> >> >
> >> >Who has the ideas?
> >> >
> >> >PS. Win 2000 SP4, SQL 2000
> >> >PPS.This thread is follow-up to the "Problem porting NS Application
from
> >> >SQL
> >> >2000 to SQL 2005" thread.
> >> >
> >> >Thanks
> >>
> >>
>
>