|
|
|
#1 (permalink) |
|
Messages: n/a
Hébergeur: |
I'm moving an asp.net website application from server2003 to Vista. It runs
fine now on server2003 and accesses Sql Server via a dbo user using NT AUTHORITY \ NETWORK SERVICE. However, Vista, like XP, must use ASPNET as the user. The problem is that on the Vista machine I am not allowed to delete or modify the dbo user. So it seems I am in a catch 22. Is there a way to get rid of this user with the nt authority and replace it with aspnet? thanks, Gary |
|
|
|
#2 (permalink) |
|
Messages: n/a
Hébergeur: |
Hi Gary,
I understand that you would like to know if you can remove the NT AUTHORITY\NETWORK SERVICE user from your SQL Server database and then use the user account ASPNET as the dbo user of your database. If I have misunderstood, please let me know. Yes, sure! You can replace the NT AUTHORITY\NETWORK SERVICE account with your ASPNET account by the following steps: 1. Log on your SQL Server instance with a system administrator; 2. Create the new login ASPNET in SQL Server Management Studio (SSMS). If you are using SQL Server 2000, please use Enterprise Manager (SSEM) to explicitly create the new login under the Security folder. Of course, you can also run the following T-SQL statement to add the login: sp_grantlogin N'ASPNET' Go exec sp_defaultdb N'ASPNET', N'<your database name>' Go 3. In SQL Query Analyzer or SSMS, run the sp_changedbowner to change your database owner from NT AUTHORITY\NETWORK SERVICE to ASPNET. EXEC sp_changedbowner N'ASPNET' Go 4. If there is no other database using the network service account and if you delete the login NT AUTHORITY\NETWORK SERVICE from your SQL Server instance, you can do this in SSMS or SSEM by manually deleting the login under the Security folder or running the following T-SQL statement: EXEC sp_revokelogin N'NT AUTHORITY\NETWORK SERVICE' Go Hope this s. Please feel free to let me know if you have any other questions or concerns. Best regards, Charles Wang Microsoft Online Community Support ================================================== ========= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@microsoft.com. ================================================== ========= Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscripti...ult.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscripti...t/default.aspx. ================================================== ========== This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== ======= |
|
|
|
#3 (permalink) |
|
Messages: n/a
Hébergeur: |
Hi
I am not sure what your issue is, if the user is the owner of the database you can use sp_change_db_owner to change this, in certain situations you may need to change to an intermediate user and you can create a temporary login/user for this oe possible use sa. Although all you may require to do is add the user to the db_owner role, in which case it should be straight forward to add them. If your users are orphaned then use sp_change_users_login, the command sp_change_users_login 'report' will show all orphaned users. John "GaryDean" wrote: > I'm moving an asp.net website application from server2003 to Vista. It runs > fine now on server2003 and accesses Sql Server via a dbo user using NT > AUTHORITY \ NETWORK SERVICE. However, Vista, like XP, must use ASPNET as > the user. The problem is that on the Vista machine I am not allowed to > delete or modify the dbo user. So it seems I am in a catch 22. > > Is there a way to get rid of this user with the nt authority and replace it > with aspnet? > thanks, > Gary > > > |
|
|
|
#4 (permalink) |
|
Messages: n/a
Hébergeur: |
Looking at Charle's reponse it seems I overdid the underscores in
sp_changedbowner!! John "John Bell" wrote: > Hi > > I am not sure what your issue is, if the user is the owner of the database > you can use sp_change_db_owner to change this, in certain situations you may > need to change to an intermediate user and you can create a temporary > login/user for this oe possible use sa. Although all you may require to do is > add the user to the db_owner role, in which case it should be straight > forward to add them. > If your users are orphaned then use sp_change_users_login, the command > sp_change_users_login 'report' will show all orphaned users. > > John > > "GaryDean" wrote: > > > I'm moving an asp.net website application from server2003 to Vista. It runs > > fine now on server2003 and accesses Sql Server via a dbo user using NT > > AUTHORITY \ NETWORK SERVICE. However, Vista, like XP, must use ASPNET as > > the user. The problem is that on the Vista machine I am not allowed to > > delete or modify the dbo user. So it seems I am in a catch 22. > > > > Is there a way to get rid of this user with the nt authority and replace it > > with aspnet? > > thanks, > > Gary > > > > > > |
|
![]() |
| Outils de la discussion | |
|
|