Re: How to connect to an SQL Server 2000 Personal Edition Database



You've got to give the aspnet worker process the permission to the database, add a new login from your Windows Account(ASPNET for Win XP or Net work Service for Win2k3). Otherwise you've to run impersonnation or use sql authentication.

regards
erymuzuan mustapa
keps wrote:
Hi,

I have created a web service that needs to access data in an SQL Server 2000 Personal Edition database. However, when I create a SqlCoonection object in C# and tries to connect using the path \(local) , it gives an error messga estating that the Server can not be found or have in adequate permissions to perform the operation.
I think I have a problem getting the right path. Does anyone know how to go about this.
A prompt reply will be highly appreciated.


Thanks.

Kapila
.



Relevant Pages

  • Re: Complete Neophyte Question(s)
    ... I have a user named james on a database. ... WITH GRANT is one of the more esotheric features in SQL Server in my ... Or does that depend on the permission? ... CREATE USER erik ...
    (microsoft.public.sqlserver.security)
  • RE: security problems with AD and SQL Server 2000
    ... I believe it is SQL server permission ... >The System developers group is placed into each users section of the ... >database for permitting database access to each database. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Alter Many Stored Procedures
    ... Books Online for SQL Server SP3 at ... >> What permission do I need to setup for a developer in order to change ... >> stored procedures in ABC database? ... Developer windows group is added to ...
    (microsoft.public.sqlserver.security)
  • Re: ASP page and SQL server error
    ... It's not the account, it's the priveleges that the account has with regards ... SQL Server permissions are very granular. ... while the user has permission to USE the database (in a general ...
    (microsoft.public.frontpage.programming)
  • Re: Read-only Reports User
    ... >> open each database and go to the Reports user's Permission ... > event entirely dedicated to SQL Server, ...
    (microsoft.public.sqlserver.security)