Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Thursday, March 29, 2012

attach error in sql server express management studio

tried to attach a database in sse-ms, and for some reason the database name is changing to G:\someFolder\some\Folder\db.mdf, even tho i dont have a drive g:,

during "attach as" screens inside sse-ms, , ie attach>add> then select the database the mdf loction is what it is suppose to be ie C:\inetpub\wwwroot\app_data\chp11\wroxunited.mdf but the database name in the same screen shot is G:\someOtherFolderAndPath\wroxunited.mdf and the attach as is also the G:\someOtherFolderAndPath\wroxunited.mdf.

pretty confused, could use a clue, thanks

my data entry error above, the mdf locattion in the sse-ms attach area/screen is C:\inetpub\wwwroot\chp11\app_data\wroxunited.mdf, the rest of the intial post is ok tho,

anyone know if the log file (ldf) is causing this problem, chp11 came in a download form the wrox book site btw.

|||hmm found a work around, ie just deleted that database from within sse-ms, had a backup of the mdf so wasnt to worried, anyway after deleting the mdf that had the G:\WrongPath\db.mdf, i was able to attach the desired database and the mdf location, the database name and the attach as are now all correct, still kinda interested in what caused that but i am now, thanks people, have a lot to learn about sql and permission tho,

Tuesday, March 27, 2012

Attach database SQL 2005

There is an error when i attach the database

"TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

E:\DataBase\Test\MyTest_Data.MDF is not a primary database file. (Microsoft SQL Server, Error: 5171)

"

What I do normally when the log file take much space then i detach the database and delete the log file and attach the database file again. It works in SQL 2000. but generating error in SQL 2005.

Your method of truncating the log file works in SQL2000 but it's not so easy in SQL2005 (like nearly everything in SQL2005 compared to SQL2000). To attach the mdf file after deleting the ldf file, you can use the sp_attach_single_file_db stored procedure. It will build a new log file. I have used it several times when moving DBs to a different server. I did not move the log file but rather rebuilt it on the target server.

However, I suggest changing your setup so that the log file does not grow so big which necessitates manual truncation. There are several ways to do this but let me suggest two:

1. Change the Recovery Model in Database properties in Mgmt Studio to Simple. Then the log file will not grow as transactions occur. The problem with this is that recovery is to the time of the last database backup.

2. If the Recovery Model in Database properties in Mgmt Studio is Full, then transactions remain in the log file until the log file is backed up. That is why it grows so big. Apparently you are not backing it up. A database backup does not truncate the log file. A separate log file backup performs a truncation. We recommend that a maintenance plan be set up to back up the log file at least once daily. This is not the database backup but rather a log file backup. Our standard practice for most of our production DBs is to have the maintenance plan back up the DB at about 11pm each night and back up the log files every 2 hours from 8am to 8pm daily. That way the maximum work that would be potentially lost is 2 hours, which is tolerable in most sites. Believe me, we have used it! Although rare, RAID 5 drives do actually fail.

|||

I guess what u are doing to avoid frequent log full is not the correct way of doing it.

i would suggest

.change the recovery type of database from simple to FULL"

.consider taking frequent Transaction log back ups in between full backups.

otherway..instead of detach the database run the log backup with no_log clause to free up trnsaction log space.

Sunday, March 25, 2012

Attach database

I have a database on a server and want to put it my local laptop that also has sql express. I attached the db, I see it in Management Studio but it does not show up in

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data so my app is not working correctely. How do I get the db to show up in the MSSWL\Data folder. I'm a bit confused.

Attaching a DB to SQL Server does not move the DB file. If you want the DB file to be in a particular directory then you need to move the file to that directory and then attach the DB file to SQL Server.

|||Ok I copied the db to the data folder and then attached it. I can connect but but I get an error "connot find server\instance.|||Then it has nothing to do with the directory of the file. That means that what "MSSWL\Data" is the name of a "named" instance of Sql Server. In that case you will need to configure\modify the application so it can connect to the Sql Server installed on your machine. As it looks now the application is trying to connect to the server from where you got the database file.|||

Need some more info here, when are you getting this error? If you can't find the server, you are not able to connect as you suggest. A few other questions:

What is the name of your instance?
Have you confirmed that it's running in SQL Configuration Manager?
Are you able to connect from the local computer? (i.e. where Sql Express is installed.)

Thanks for the additional informaiton.

Mike

|||

I fugured it out. I put the db and dblog in the data folder and then attached it..it works fine now.

Thanks much

|||

Good to hear it's working.

Mike

Thursday, March 22, 2012

Atlernative to SQL Server Management Studio (i.e. garbage) . Any suggestions?

Folks I have recently had the misfortune of moving to SQL Server Managment Studio as per our upgrade to SQL 2005. There is no doubt that SQL Server Management is a major disappoinment compared to Enterprise manager.

The UI is the biggest disaster I have ever seen. Getting rid of the SQL Query analyzer tool was aTERRIBLE idea. The UI is buggy and unfriendly. It is a major POS. I hope someone in the SQL Dev team is listening / reading this post (hellooooo anybody homeee.....)

Now that I have vented my frustration ...

I wanted to know any atlernatives to the SQL Server Management Studio. There are plenty of 3rd Party tools out there I wanted to find out from this forum which popular 3rd Party tools are most developers using

Thanks for bearing with me.

If all you're after is query analyzer type functionality the free SQL Scripter fromhttp://www.sqlscripter.com/ is worth a look.

|||

There's a bunch of them. Some of them free, some paid. Do a google search and you will find them - SQL Edit, Toad etc.

|||

A colleague found this reference on line yesterday. None of us have tried it out, but it looks reasonable.

http://www.albahari.com/queryexpress.html

|||

That's quite odd actually, I use it every day, and have yet to really stumble across a major issue with it. It's nice having one single app to be able to do all the functionality of the old enterprise manager (Yuck!), query analyzer, and (insert some database project tool that wasn't shipped with 2000). It is however pretty memory hungry, so I feel sorry for those trying to develop on really low end machines.

Really, the only complaint I have with it, is that I wish it's "script to..." functionality for insert/update/delete would default to placing parameters in the placeholders, or even better generate a VB.NET/C# SqlCommand for it (including creating the parameters, with datatypes). Obviously a minor complaint considering that it isn't part of the VB.NET/C# programming tools.

Or perhaps you've overlooked that you can right click any database, choose "New query", and it opens a new tab that acts very similiar to the old query analyzer?

|||

Motley:

That's quite odd actually, I use it every day, and have yet to really stumble across a major issue with it. It's nice having one single app to be able to do all the functionality of the old enterprise manager (Yuck!), query analyzer, and (insert some database project tool that wasn't shipped with 2000). It is however pretty memory hungry, so I feel sorry for those trying to develop on really low end machines.

Really, the only complaint I have with it, is that I wish it's "script to..." functionality for insert/update/delete would default to placing parameters in the placeholders, or even better generate a VB.NET/C# SqlCommand for it (including creating the parameters, with datatypes). Obviously a minor complaint considering that it isn't part of the VB.NET/C# programming tools.

Or perhaps you've overlooked that you can right click any database, choose "New query", and it opens a new tab that acts very similiar to the old query analyzer?

Well after using enterprise manager for a very long time I liked the fact that Query Analyzer open by itself. I realize now that it simply is intergated into the application via tabbed windows. Some how I just do not like that structure of UI design. But that this the least of my issues. In addition to the issue you mentioned there are several other issues.

When I try to open 2 or more db connection in my object explorer items not appear in my summary window. For example if i click on stored procs under programmability it shows me there are x number of items on the top right by the main screen is blank.

Frequently I get invalid errors when trying to browse items in the object explorer (error says invalid index)

When I ask it to remember my password for object explorer or for a new query it does not remember the password the next time

Additionally the UI is poorly designed and does not flow very well from a usability standpoint. (I wish the SQL team would pay more attention to this and not take UI so lightly. UI it is an after thought for developers BUT it is the first impression you make on the user, and that IMO is crucial)

I thought that I was the only person on my team not liking SQL Mgmt studio but 4/5 develpers including our DBA are not at all happy with the product...

|||

Well it seems to me that you are using portions of the studio, that I don't think I've ever used. I don't think I've had the Object Explorer Details window open for more than 2 seconds ever.

As for the UI design, it's probably a matter of taste. The paned view (Objects on left, middle as a work area, right is properties, etc) is used by a number of differing products (Visual Studio, Dreamweaver, Photoshop, etc etc). I'd hardly call it a poorly designed UI, but it's a matter of opinion and what you are trying to accomplish with the tool.

|||

Motley:

Well it seems to me that you are using portions of the studio, that I don't think I've ever used. I don't think I've had the Object Explorer Details window open for more than 2 seconds ever.

As for the UI design, it's probably a matter of taste. The paned view (Objects on left, middle as a work area, right is properties, etc) is used by a number of differing products (Visual Studio, Dreamweaver, Photoshop, etc etc). I'd hardly call it a poorly designed UI, but it's a matter of opinion and what you are trying to accomplish with the tool.

Most of my problems are with SQL Mgmt Studio UI whose is very different from the Visual Studio's UI (I find VS2005 to be quite good actually). I did intially think it was a matter of personal taste but what can I can when 4/5 folks on my team have the same complains.

Believe you me I did not give up on this after a day of working with it. I have been using it for the last 2 months.

Monday, March 19, 2012

Assisted Editor for stored procedures

I have been using SQL server management studio beta to manage my SQL server 2000 and to develop stored procedures. I was very happy with Assisted Editor, but it seems to be missing from final SQL server 2005 products (developer's version) Sad.

In object browser when I right-click on stored procedure and chose modify I used to get Assisted editor (described in http://msdn.microsoft.com/sql/learn/prog/tsql/default.aspx?pull=/library/en-us/dnsql90/html/tsqlqueries.asp). Now I get full Alter procedure statement (like in old Query analyzer) that can be edited and executed but not "real time" edited.

Is there any setting to get my beloved Assisted Editor back or Microsoft decided to get us rid of this user friendly addition?

Thanks and regards, Danko Jevtovic

The assisted editors functionality was cut from SQL Server 2005.

We had a lot of work left to make the feature correctly handle all the scenarios it needed to handle, and we ran out of time to fix it.

Friday, February 24, 2012

ASPNETDB.mdf "...already in use..." Error and Broader Questions

When you create and host an ASP.Net 2.0 site on your local computer and then configure .Net 2.0's drop-in user registration and management system it creates a SQL file named ASPNETDB.mdf with a whole bunch of tables and stored procedures (…as most of you know). If you add your own custom tables to that database file and then try to call those tables you get an error that says that ASPNETDB.mdf is already in use. One way to get around this is to create a separate database in the form of another ".mdf" file and then put all of your own custom tables in it. You avoid the "...already in use..." errors that way but all your user accounts and the primary key structure that identifies them are in the original ASPNETDB.mdf file. This makes it impossible to do primary/foreign key relationships between those tables and those in the new separate database you created. It's kind of a catch-22 situation...unless I'm missing something that relates to releasing the ASPNETDB.mdf file from use whenever it is called so that additional tables and queries against that database file can be made without the "…already in use…" error cropping up. I am wondering if this problem is because the ASPNETDB.mdf file is not a "real" SQL database and as such imposes multiple-connectivity limitations such as those I am seeing. If this is true, migrating to a real SQL database would alleviate this? Finally, from a broader security and scalability standpoint…what are the best practices relating to use of the ASPNETDB.mdf database for all your custom tables? Should an additional database be created for all my application's custom tables (leading to the primary/foreign key problems) or should the additional tables be put into the ASPNETDB.mdf file (with some way of working around the "…already in use…" error)? A long-winded and broad question…thanks in advance for any responses.

MDCragg

The default membership provider already has an open connection to the file, which seems like the reason why you can't make your own connection. Perhaps you could extend this provider to keep its current functionality, but add your own requirements to access the other tables, as well. The default provider is the System.Web.Security.SqlMembershipProvider class. After you create this, set it as the default provider in your web.config.

Sample on how to configure a membership provider in web.config:http://msdn2.microsoft.com/en-us/library/44w5aswa.aspx

|||

That article tells how to merge the membership provider tables and stored procedures into my own database. I will try this to see if it solves the problem. I am at least a little bit doubtful if it will though because it seems like it will just shift the same persistent and exclusive connectivity problem I am having from the current user account database to my own database.

|||

This seems to have worked. I installed SQL Server Management Studio Express. I wasn't able to navigate to the existing custom database that I had created so I copied it to the default directory that SQL Server MSE utilizes. I was able to connect to it there and thus "attach" it to my PC's SQL host. Once that was done I was able to use the aspnet_regsql.exe utility to populate that database with all of .Net's Membership tables, views, stored procedures, etc. I copied the database back to the App_Data folder. I adjusted all the Membership entries in the web.config folder to "point to" the custom database instead of the ASPNETDB.mdf file (which I removed). I did some additional tweaking with things such as connection strings. Then I launched the site and everything seemed to work. I am able to connect to the .Net Membership tables as well as all my own tables...all of which exist in the one custom database file.

So, this is fixed although I don't know what the difference was between the ASPNETDB.mdf file and the custom ".mdf" file that I created. I'm sure there is a setting or two somewhere in the database instance, the connection, or something or other that led to the difficulty.

ASPNETDB migration

I created a website using Visual web developer express edition (including SQL Express). No the user management section of the site (the login/logout database) was created automatically and SQL Server express was installed at my computer under the instance name of SQLExpress. I uploaded it to my web host and he hooked up the ASPNETDB for me. Now the problem is that ASPNETDB has an id password and I was given theMSSQL Server IP. How do I configure my website to accommodate that? Any help will be extremely useful!!!

you need to modify the connection string in web.config

<connectionStrings>
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="server=server ip;database=ASPNETDB;uid=youUsername;pwd=yourpassword"
providerName="System.Data.SqlClient"/>

</connectionStrings>

|||

WOW! Thats it! Thanks a bunch. One more thing. I am also using the same database to display some data(have added some tables into it manually). What should I put in the connection string to make the connection to the database? Also, can I use a MySQL database instead? If yes, what will be the connection string?

Thanks for your help.

|||

if you don't want to use the same name "LocalSqlServer", then you can add another connection with the same connectionString
like:

<add name="yourConnName" connectionString="server=server ip;database=ASPNETDB;uid=youUsername;pwd=yourpassword"
providerName="System.Data.SqlClient"/>

I am not sure if you can use MySQL as a configuration Database, but you can use it for application database.

Honestly, I didn't use it before. to get the exact connection string for MySQL, try to add a coonection from the wizard and see how vs2005 creates it in web.config

aspnetdb connection could not establish but database correctly created.

I installed netframework 2.0 Visual Web developer and MSSQL 2005 express edition with SQL Server management express.

I have got this configuration: 2*256 mb ram Intel Pentium 3.2Ghz Windows XP HUN SP2 latest version.

server name: localhost\SQLEXPRESS
Authentication: Windows Authentication

I run aspnet_regsql.exe and the setup wizard created aspnetdb see here, Microsoft sql server management studio can see the database:
MSSQL server management express & aspnetdb

But! When I run to the asp.net web application administration tool in Provider Configuration and choose
AspNetSqlProvider only 1
then I clickSelect a single provider for all site management data link -> then test

The Tool write this:
Could not establish a connection to the database.
If you have not yet created the SQL Server database, exit the Web SiteAdministration tool, use the aspnet_regsql command-line utility tocreate and configure the database, and then return to this tool to setthe provider.

Hi,

You application does not "know" where your database is. It is trying to find it in App_Data folder of your application. If it is not there you can specify its locaton by using connection string in web.config like this:

<connectionStrings>
<clear/>
<add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
</connectionStrings>

|||

<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<connectionStrings>
<clear/>
<add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient"/>
</connectionStrings>

<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.

Visual Basic options:
Set strict="true" to disallow all data type conversions
where data loss can occur.
Set explicit="true" to force declaration of all variables.
-->
<compilation debug="true" strict="false" explicit="true"/>
<pages>
<namespaces>
<clear/>
<add namespace="System"/>
<add namespace="System.Collections"/>
<add namespace="System.Collections.Specialized"/>
<add namespace="System.Configuration"/>
<add namespace="System.Text"/>
<add namespace="System.Text.RegularExpressions"/>
<add namespace="System.Web"/>
<add namespace="System.Web.Caching"/>
<add namespace="System.Web.SessionState"/>
<add namespace="System.Web.Security"/>
<add namespace="System.Web.Profile"/>
<add namespace="System.Web.UI"/>
<add namespace="System.Web.UI.WebControls"/>
<add namespace="System.Web.UI.WebControls.WebParts"/>
<add namespace="System.Web.UI.HtmlControls"/>
</namespaces>
</pages>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
</system.web>
</configuration>

I paste But doesn't work.Sad modify the text or not? When I run the page createuserwizard

Kiszolgálóhiba t?rtént az alkalmazásban: ?/Website".Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.Leírás: Nem kezelt kivétel k?vetkezett be az aktuális webes kérelem végrehajtása során. A hibára és az azt okozó kódrészletre vonatkozó adatok az alábbi veremkivonatban találhatók.Hiba t?rtént az SQLExpress adatbázisfájl automatikus létrehozásakor:A kapcsolódási karakterlánc az alkalmazás App_Data k?nyvtárában található adatbázishelyet használó helyi SQL Server Express példányt ad meg. A szolgáltató megkísérelte automatikusan létrehozni az alkalmazás szolgáltatási adatbázisát, mert a szolgáltató megállapította, hogy az adatbázis nem létezik. A k?vetkez? konfigurálási k?vetelmények megléte szükséges ahhoz, hogy az alkalmazás szolgáltatási adatbázisának létezése sikeresen ellen?rizhet? legyen, és hogy az alkalmazás szolgáltatási adatbázisa automatikusan létrehozható legyen: 1. Ha még nem létezik az alkalmazás App_Data k?nyvtára, a webkiszolgálói fióknak olvasási és írási hozzáféréssel kell rendelkeznie az alkalmazás k?nyvtárához. Ez azért szükséges, mert a webkiszolgálói fiók automatikusan létre fogja hozni az App_Data k?nyvtárat, ha az még nem létezik. 2. Ha már létezik az alkalmazás App_Data k?nyvtára, a webkiszolgálói fióknak csak az alkalmazás App_Data k?nyvtárához van szüksége olvasási és írási hozzáférésre. Ez azért szükséges, mert a webkiszolgálói fiók megkísérli ellen?rizni, hogy az alkalmazás App_Data k?nyvtárában már létezik-e az SQL Server Express adatbázis. Ha visszavonja a webkiszolgálói fióktól az olvasási engedélyt az App_Data k?nyvtárhoz, a szolgáltató nem fogja tudni helyesen megállapítani, hogy már létezik-e az SQL Server Express adatbázis. Ez hibát okoz, amikor a szolgáltató megpróbálja még egyszer létrehozni a már létez? adatbázis másodpéldányát. Az írási hozzáférés azért szükséges, mert az új adatbázis létrehozásához a webkiszolgálói fiók hitelesít? adatait kell használni. 3. A számítógépen telepítve kell lennie az SQL Server Express programnak. 4. A webkiszolgálói fiók folyamatidentitásának helyi felhasználói profillal kell rendelkeznie. A mind a számítógéphez, mind a tartományi fiókokhoz készített helyi felhasználói profil létrehozásáról az információs fájl tartalmaz további tudnivalókat.Forráshiba:Az aktuális webes kérelem végrehajtása nem kezelt kivételt okozott. A kivétel okára és helyére vonatkozó adatok az alábbi veremkivonatban találhatók.Veremkivonat:[SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735027 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +67[HttpException (0x80004005): Nem lehet csatlakozni az SQL Server adatbázishoz.] System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +122 System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +89 System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +26 System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +388Verzióinformáció: Microsoft .NET-keretrendszer verziója:2.0.50727.42; ASP.NET verziója:2.0.50727.42
|||

I don't understand I try to make an other database in app_data new_item anotherdatabase.mdf and I have got this message:
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
I reinstall Confused everything maybe next time work normal.

|||

Where is located aspnetdb.mdf?

|||

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\here

But I try to put them into the App_Data and doesn't work.
I install Windows Longhorn Beta (server 2008) and sites runingI try the same in my notebook windows XP HUN and workso I don't know what is the problem ,but NOW run everythingSmile and I don't care.

Sunday, February 19, 2012

ASPNET as db owner

Using Management Studio in SS 2005 on XP when I'm adding a user to a
database and I browse for objects (logins) I see MACHINENAME\ASPNET as a
choice and I am allowed to make ASPNET a user.
But in Server2003, MACHINENAME\ASPNET does not show up as a user.
Why? Can't aspnet be a user on server2003?
Regards,
Gary Blakely
Hello
Yes, I think you can't use machine\aspnet in windows 2003. And you may not
need it. aspnet process may run as network-services account, anonymous, or
something another according to your environment. It depends on that the
connection is remote or not, and the existence of active directory.
Why not first check the asp.net process's account executing arbitrary
asp.net file on your server? If you know it, you can grant the account. Or
alternatively you can impersonate the asp.net process first and grant the
impersonated account.
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:ep3vihSMHHA.4928@.TK2MSFTNGP06.phx.gbl...
> Using Management Studio in SS 2005 on XP when I'm adding a user to a
> database and I browse for objects (logins) I see MACHINENAME\ASPNET as a
> choice and I am allowed to make ASPNET a user.
> But in Server2003, MACHINENAME\ASPNET does not show up as a user.
> Why? Can't aspnet be a user on server2003?
> --
> Regards,
> Gary Blakely
>
|||Hi Gary,
I know that you could not see MACHINENAME\ASPNET on your Windows Server
2003.
If I have misunderstood, please let me know.
Per my test, ASPNET is still existed as a user on Windows Server 2003.
Please check if the ASP.NET component had been installed on your computer.
In SQL Server Management Studio, I also can add it as a SQL Server login.
I would like to provide some links here for your reference:
How to configure the process identity for the ASPNET account in ASP.NET 1.1
when you use IIS 5 Isolation mode in IIS 6.0 on Windows Server 2003
http://support.microsoft.com/kb/895967/
Process and request identity in ASP.NET
http://support.microsoft.com/kb/317012/
FIX: ASP.NET does not work with the default ASPNET account on a domain
controller
http://support.microsoft.com/kb/315158
This should be related to IIS. If this issue perstis, it is recommended
that you have a new post at ASP.NET community for wider audience.
Please feel free to let me know if you have any other questions or concerns.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi Gary,
Just check with you to see if you need further assistance on this issue. If
you have any other questions or concerns, please feel free to contact us.
We are always very glad for further assistance.
Have a good day!
Sincerely yours,
Charles Wang
Microsoft Online Community Support

ASPNET as db owner

Using Management Studio in SS 2005 on XP when I'm adding a user to a
database and I browse for objects (logins) I see MACHINENAME\ASPNET as a
choice and I am allowed to make ASPNET a user.
But in Server2003, MACHINENAME\ASPNET does not show up as a user.
Why? Can't aspnet be a user on server2003?
Regards,
Gary BlakelyHello
Yes, I think you can't use machine\aspnet in windows 2003. And you may not
need it. aspnet process may run as network-services account, anonymous, or
something another according to your environment. It depends on that the
connection is remote or not, and the existence of active directory.
Why not first check the asp.net process's account executing arbitrary
asp.net file on your server? If you know it, you can grant the account. Or
alternatively you can impersonate the asp.net process first and grant the
impersonated account.
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:ep3vihSMHHA.4928@.TK2MSFTNGP06.phx.gbl...
> Using Management Studio in SS 2005 on XP when I'm adding a user to a
> database and I browse for objects (logins) I see MACHINENAME\ASPNET as a
> choice and I am allowed to make ASPNET a user.
> But in Server2003, MACHINENAME\ASPNET does not show up as a user.
> Why? Can't aspnet be a user on server2003?
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
I know that you could not see MACHINENAME\ASPNET on your Windows Server
2003.
If I have misunderstood, please let me know.
Per my test, ASPNET is still existed as a user on Windows Server 2003.
Please check if the ASP.NET component had been installed on your computer.
In SQL Server Management Studio, I also can add it as a SQL Server login.
I would like to provide some links here for your reference:
How to configure the process identity for the ASPNET account in ASP.NET 1.1
when you use IIS 5 Isolation mode in IIS 6.0 on Windows Server 2003
http://support.microsoft.com/kb/895967/
Process and request identity in ASP.NET
http://support.microsoft.com/kb/317012/
FIX: ASP.NET does not work with the default ASPNET account on a domain
controller
http://support.microsoft.com/kb/315158
This should be related to IIS. If this issue perstis, it is recommended
that you have a new post at ASP.NET community for wider audience.
Please feel free to let me know if you have any other questions or concerns.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi Gary,
Just check with you to see if you need further assistance on this issue. If
you have any other questions or concerns, please feel free to contact us.
We are always very glad for further assistance.
Have a good day!
Sincerely yours,
Charles Wang
Microsoft Online Community Support

ASPNET as db owner

Using Management Studio in SS 2005 on XP when I'm adding a user to a
database and I browse for objects (logins) I see MACHINENAME\ASPNET as a
choice and I am allowed to make ASPNET a user.
But in Server2003, MACHINENAME\ASPNET does not show up as a user.
Why? Can't aspnet be a user on server2003?
--
Regards,
Gary BlakelyHello
Yes, I think you can't use machine\aspnet in windows 2003. And you may not
need it. aspnet process may run as network-services account, anonymous, or
something another according to your environment. It depends on that the
connection is remote or not, and the existence of active directory.
Why not first check the asp.net process's account executing arbitrary
asp.net file on your server? If you know it, you can grant the account. Or
alternatively you can impersonate the asp.net process first and grant the
impersonated account.
"GaryDean" <GaryDean@.newsgroups.nospam> wrote in message
news:ep3vihSMHHA.4928@.TK2MSFTNGP06.phx.gbl...
> Using Management Studio in SS 2005 on XP when I'm adding a user to a
> database and I browse for objects (logins) I see MACHINENAME\ASPNET as a
> choice and I am allowed to make ASPNET a user.
> But in Server2003, MACHINENAME\ASPNET does not show up as a user.
> Why? Can't aspnet be a user on server2003?
> --
> Regards,
> Gary Blakely
>|||Hi Gary,
I know that you could not see MACHINENAME\ASPNET on your Windows Server
2003.
If I have misunderstood, please let me know.
Per my test, ASPNET is still existed as a user on Windows Server 2003.
Please check if the ASP.NET component had been installed on your computer.
In SQL Server Management Studio, I also can add it as a SQL Server login.
I would like to provide some links here for your reference:
How to configure the process identity for the ASPNET account in ASP.NET 1.1
when you use IIS 5 Isolation mode in IIS 6.0 on Windows Server 2003
http://support.microsoft.com/kb/895967/
Process and request identity in ASP.NET
http://support.microsoft.com/kb/317012/
FIX: ASP.NET does not work with the default ASPNET account on a domain
controller
http://support.microsoft.com/kb/315158
This should be related to IIS. If this issue perstis, it is recommended
that you have a new post at ASP.NET community for wider audience.
Please feel free to let me know if you have any other questions or concerns.
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi Gary,
Just check with you to see if you need further assistance on this issue. If
you have any other questions or concerns, please feel free to contact us.
We are always very glad for further assistance.
Have a good day!
Sincerely yours,
Charles Wang
Microsoft Online Community Support