When I try to access my PasswordRecovery.aspx page I get an error. I've also added the Event Warning and the Failure Audit. I've tried deleting the ASPNET user account and recreating it using aspnet_regiis.exe. I still get the same error message. Should I add the ASPNET account to the Administrators group? Currently it is with the Users group.
Login failed for user 'PC325862970629ASPNET'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'PC325862970629ASPNET'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
I installed SQL Server 2005 and Visual Studio 2005 and have discovered that the ASPNET machine account was not added as a user when going into "Computer Management". I obviously need this to run ASP.net apps. I tried going to the Administrators group to add user ASPNET, but the system can't find this user. How can I install the ASPNET account?
I seem to remember that when using VS2003 to create a website which connected to a MSDE database, I needed to explicitly grant access to the database for ASPNET machine account using the following SQL commands from within a .sql script: EXEC sp_grantlogin '<machine>ASPNET'EXEC sp_grantdbaccess '<machine>ASPNET' With VS2005, it sppears that upon creating an .MDF database in the App_Data folder this is no longer necessary. I'd be interested to know why this is so. Does VS2005 automatically do this when the database is created? If anybody could shed some light on this I'd be interested. Thanks,Wayne.
This is the error message "Login failed for user 'SUSHMAASPNET'. " I am Building a Data Form that displays data from a single table- the Customers table in the Northwind sample Database. I have Visual Studio.Net 1.0 and SQL Server 2000. So I feel that I need to add an ASPNET account to my database. Please could someone tell me if this could solve the problem, if so please could you tell me how to Add an ASPNET account to my database? Thank you
VS2005Hi If I run the below code (this simply connects to SQL Server and returns the user name the connection is made under): Dim Connection As New SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings("LocalSqlServer").ToString)
Dim AttCommand As New SqlCommand("SELECT System_USER", Connection)
Connection.Open() Dim AttendanceReader As SqlDataReader = AttCommand.ExecuteReader
AttendanceReader.Read()
Debug.Print(AttendanceReader.Item(0).ToString)I get: MyDomainpootle.flump Which is the account I am running on the dev machine. I expected ASP.Net to run as ASPNET irrespective of the currently logged in account. Am I plain wrong? Do I need to change something in IIS? Do I need to change something in ASP.Net? Any help greatly appreciated Thanks
can anyone give me step by step instructions as to how I would go about correctly granting the aspnet account access to my sql server 2005 database ?? As far as I can see Ive set it up, but im getting execute permissions errors on stored procedures even though Ive gone into properties and permissions and added the aspnet account with execute permissions.
Hi,I changed the login for MSSQLSERVER service for 6.5 box to "Thisaccount" from "system account" and then again changed back to "systemaccount". Now I cann't connect thru Enterprize Manager to my server.All my services r running and I can connect to my database thru anapplication as before. I cannot re-boot the machine as it is inproduction. Any thoughts?Thanks in advance.Subodh
I'm creating one of my first asp.net pages, and it accesses an MS SQL database.It runs fine locally, but if you go to it remotely through a web browser, you get an exception saying that the database login failed for user ASPNET.My brother told me to do the following in SQL Server Managment studio. It seems I don't have that program installed, so I did it from the SQL command prompt.CREATE LOGIN [bigblueASPNET] FROM WINDOWSuse AdventureWorkscreate user [bigblueASPNET](Where "bigblue" is the computer name and "AdventureWorks" is the database my asp.net web page reads from).This only partially fixed the problem - now when you open the page remotely and try to access the DB I get an error message saying that permission to use the SELECT command is denied.I searched on these forums, and found this:http://forums.asp.net/69166/ShowPost.aspxFor future reference, let's call what my brother told me "Method 1" and what the previous poster did as "Method 2."I haven't tried method 2 because I don't know exactly what I am giving ASPNET permission to do. Does method 2 enable ASPNET to do anything to any database? It seems method 1 is more secure, as from the commands I could already tell it only has permission to access AdventureWorks.So, I'd prefer to use method 1. Can anyone tell me what further commands I can use to give ASPNET permission to do specific actions?If I can't figure out method 1 and have to do method 2, how can I undo what I did in method 1?Thanks!
Ran a trace using profiler and found that the CLR is not using the ASPNET windows account to log into SQL 2005, instead using the admin. Some ado.net code does not work properly as a result. Have had to change the connection string to use SQL logins.Spec: Win XP Pro; IIS 5; 2.0.Is this normal? Where security and permissions are concerned, what changes, if any, are there from SQL 2000?
set up asp .net user account on sql server 2005Question:
I've read the instructions in this article: http://www.netomatix.com/Development/aspnetuserpermissions.aspxBut do not know how to do this:You can grant 'Network Service' or 'ASPNET' user accounts permissions to connect to database.Please provide example on how to do this, thanks!
Can't connect to local server instance MSSQLSERVER in SQL Server Management Studio (SQL2005 sp2/Vista).
SQL Server Configuration Manager reports SQL Server2005 services: SQL Server (MSSQLSERVER) Running. This would indicate the name of the SQL server is "MSSQLSERVER" correct? I chose "default" instance during the install and that is the name it gave itself.
I tried connecting to the server using the following for the Server Name: MSSQLSERVER and .MSSQLSERVER neither works.
The only thing that works for my installation is just plain "." (no quotes) and nothing else. Can this be correct because I can't find any reference to this. Thanks.
Doing webforms in ASP.NET and i have a connection string in the webconfig that connects to a locally created SQL Server user account.
This is fine however when i try to connect to a domain account created by the IT administrator for me, it wont work.
The User name and password he supplied are correct as i logged into my PC (Win 2000) using it to test it. However when i try to connect to this remote network domain account by changing my connection string it fails... anyone any ideas, or am i missing a subtlety of ASP.NET and SQL connectionstrings?
Heres the connection string that works... ConnectionString = value="Server=MY-SERVER;Network Library=DBMSSOCN;Initial Catalog=MYDATABASE2;User ID=MrLocalUser;Password=password;"
Heres the connection string that fails... ConnectionString = value="Server=MY-SERVER;Network Library=DBMSSOCN;Initial Catalog=MYDATABASE2;User ID=DOMAINMrDomainUser;Password=password;"
We have a SQL database on a non standard instance. If I open SQL server manager and connect to that database using integrated Windows Authentication I can basically do whatever I want with that database.However, if I try to connect to that database remotely (or even from the sql server) using a test connection UDL it only works if I use Windows integrated security. If I specify my account details specifically (or any other account which has access) it doesn't want to connect.
I`m trying to connect to the Analysis Services (AS 2000 Enterprise Edition SP4 on Windows Server 2003 EE, respository is in Access DB) throught Analysis Manager over HTTPS(HTTP) connection. I dont want to use domain account.
I need to specify USER_ID and PASSWORD to the Analysis Manager, but in registration of new server is only IP address or HTTP adress (for http://server) - but it doesn´t work - it says Unauthorized. But I`ve tried to use Anonymous account and it doesn`t work (client wan`t able to make connection)... I would like to use Basic Authentification.... Thise account is member of OLAP_Administrators... but the problem is where should I put USER_ID and PASSWORD???
It works perfect in Excel 2003.... MSOLAP.asp work fine in IE...
During install of SQL Server 2005, we can of course use a domain account or the built-in system account for running the services. I lean toward domain for obvious reaons but would like to know a +/- to each option and why I'd choose one over the other and what consequences or limitations one may encounter if I choose one over the other.
every 1 hour my server's computer is restarting ! when the windows finish restarting i open the Event viewer and see that what coused it is the error :
"Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database." Event 107 source : "Report Server Windows Service (MSSQLSERVER)"
I am running SQL Reporting Services and SQL Server 2005 on a Windows 2003 server. The configuration has been unchanged for approx. 3 weeks. Suddenly today, reports being accessed via an ASP.NET 2.0 application (on Windows 2003 Server with IIS 6) using a SOAP call to the reportserver became inaccessable. End users received the following error:
Message: An error occurred during rendering of the report. ---> An error occurred during rendering of the report. ---> An error occurred during rendering of the report. ---> An error occurred during rendering of the report. ---> Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack Trace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at IFA.CAP.SQLReportingService.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds) in C:ApplicationsIFACAPWeb ReferencesSQLReportingServiceReference.vb:line 1319 at IFA.CAP.BusinessObjects.Reports.Certificate(Int32 certificateID, Boolean isDraft, Boolean isCertified) in C:ApplicationsIFACAPBusinessObjectsIFA.CAP.BusinessObjects.Report.vb:line 551 at IFA.CAP.CertificateDetail.PrintCertificate(Object sender, EventArgs e) in C:ApplicationsIFACAPMainCertificateDetail.aspx.vb:line 2287
Subsequently, the following error is logged on the Report Server/Database server:
Report Server (MSSQLSERVER) cannot connect to the report server database.
I was able to temporarily correct the problem by performing as iisrest on the Report Server/Database server. However, the same problem occured again a couple hours later. I am relatively new to SQL Reporting Services so any help would be appreciated.
I have been running a script in SQL Server 2000 as sa also as a Active Directory user who has administrator rights (I tested both approaches SQL Server then Windows Authentication) in Query Analyser which grants execute rights to the stored procedures within the database instance and Query Analyser does not give any errors when I run the script. I have made sure that each transaction has a go after it. I then return to Enterprise Manager, check the rights (I apply them to roles so that when we create another SQL Server user we just grant him/her rights to the role) and discover that the role has not been granted the rights. I seems to be occurring only with 2 of the procedures. Is there a known bug that might be causing this?
I have several DTS jobs that runs well as a job with my nt login account for the SQL agent service startup account, but if I use the System account they fail with this error. " Error opening datafile: Access is denied. Error source: Microsoft Data Transformation Services Flat File Rowset Provider"
The data has change access to the System account under the NT security.
Basically a dts package has been setup that pulls in data from another companies server, this data requires to be on-demand i.e individual users can pull in updates of the data when they require it.
I am using xp_cmdshell and dtsrun to pull in the data. This obviouly works fine for me as i am a member of sysadmin.
Books online quotes " SQL Server Agent proxy accounts allow SQL Server users who do not belong to the sysadmin fixed server role to execute xp_cmdshell"
So i went to the SQL Server Agent Properties 'Job System' tab and unchecked 'Non-sysadmin job step proxy account' and entered a proxy account.
The proxy account has been setup as a Windows user with local administrator privilages and even a member of the sysadmin server role - just in case.
Now when i log onto the db with my test account - a non-sysadmin - and attempt to run the stored proc to import the data i recieved the message 'EXECUTE permission denied on object 'xp_cmdshell', database 'master', owner 'dbo' '
hmm... so basically i have either misunderstood BoL or there is something not quite right in my setup.
I have search the net for a few days now and yet i can find no solution.
Hi there,BOL notes that in order for replication agents to run properly, theSQLServerAgent must run as a domain account which has privledges to loginto the other machines involved in replication (under "SecurityConsiderations" and elsewhere). This makes sense; however, I waswondering if there were any repercussions to using duplicate localaccounts to establish replication where a domain was not available.Anotherwords, create a local windows account "johndoe" on both machines(with the same password), grant that account access to SQL Server onboth machines, and then have SQL Server Agent run as "johndoe" on bothmachines. I do not feel this is an ideal solution but I havecircumstances under which I may not have a domain available; mypreliminary tests seem to work.Also, are there any similar considerations regarding the MSSQLSERVERservice, or can I always leave that as local system?Dave
I have a situation that I have discovered in our QA database that I need to resolve. When I looked at the Activity Monitor for our server, I discovered that a process is running under a domain user account for one of our .Net applications. The problem is that that domain user account has not been created as a SQL login account on the server. I am trying to figure out how someone can log in to the database server with a domain user account that has not been added to SQL Server as a login account.
Does anyone have any insight on this? I don't like the idea of someone being able to create domain account that can access the database without me granting them specific access.
On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
In SQL Server Configuration Manager, expand Services, and then click SQL Server (MSSQLSERVER).There is no MSSQLSERVER to click!!!!!!!!
The Microsoft SQL Server icon is showing on my task bar but with a white (blank) circle "stamped" over the bottom right of the icon.
To me it seems that the implication is that somehow the server is not being recognized as (local)etSDK.
Resting the mouse arrow on the Server icon displays: unknown - \ - MSSQLServer
Needless to say something is quite wrong and I cannot open nor create ANY DATA while on WebMatrix.
If I right-click on the server icon and select "Start" I get the following error: "Invalid handle" which apparently is error number 6.
Previously, after many try-outs I managed to at least put the server icon on the task bar by making use of a setup.ini file that reads as shown below (and then typing from the MSDE sub directory while in MSDOS "setup.exe").
I am seeing a strange scenario in performance monitor that i am hoping someone could help shed some light on. I have a 8 processor box running only sql configured to utilize all processors. When watching the sqlservr process it seems to max out at times of high traffic. Does this not use all processors? Any know problems with this service maxing out?
MSSQLSERVER won't restart. I can't uninstall SS7, either, because it says I have MSSEARCH running, which Task Manager can't kill (access denied, even to me the administrator). Tried changing the registry keys for MSSQL to MSSQL_old and then the install goes forward but fails at the end because some of the TEMPDB files cannot be activated. This trick worked on my Win98SE once, for the same problem. I ignorantly deleted IE4 from the server's C:drive because I needed more room to reinstall. I tried reinstalling the SS7 "components" (no apparent problem, except it detects that I have now installed IE5.5)(IE5.5 automatically installs to C:Program FilesMicrosoft or thereabouts, not C: where IE4 was, by the way). I was up to SP2 on SS7, and SP6 on NT4. The name of the server hasn't changed, but the name of the c:drive is new. Why would a new install care? I ran scandisk inbetween reboots as a caution, but the install always fails. Should I be choosing the default "allow 5 connections" rather than "5 per computer licenses"? TIA, Jeb
I installed SQL server 2005 on a win2003 server box.
When I open the Connect to Server dialog box, I choose server type: Database Engine. There is no Servername listed, so I put in the name of the PC.
I get a long error message when I try to connect:
Cannot connect to PCName.... ...error: 40 - Could not open a connection to SQL Server)...
When I try to go into the Surface area Configuration, I get this message: "No sql server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)"
I am logged in as Administrator in the PC, so did I do something seriously wrong with the installation?
In the services window, I can not fine MSSQLserver (not sure if this is relevant).
Help! I just took over for a new company and after logging in to one of the servers I tried to click on the Symantec Backup Exec on the desktop. It failed and said that none of the services are started, looking in my services I can not get any of the services related to sql to start. In the bottom right hand corner in the system tray I have a red dot on the sql server and it is stopped. All the event logs say that: During redoing of a logged operation in database 'master', an error occurred at log record ID (199:200:5). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
I installed a copy of SQL server 2005 on a Win 2003 machine. I connected remotely from another machine and started Sql Server Configuration manager. The MSSQLServer is stopped. So, I click to start and it failed. The error it gave me was that it time out. I am new to SQL 2005 and I thought the next step after installing was to configure. Can anyone help me please.
Hi When I am trying to connect to MS Sql Server 2000 through Asp.net using C# , I am getting the error : “ Login Failed for HTASPNET �. Although I have added permission for this account to access the database . I would be very grateful to you if you could kindly explain to me what is the problem. Thank You.
I have a statment that checks fine in query analyser but fails in my webmatrix asp net page. I wonder if it's being too picky?Dim queryString As String =SELECT distinct [CSULOG5].[status] , [CSULOG5].[lmca_nbr] FROM [CSULOG5] works butDim queryString As String = SELECT distinct [CSULOG5].[status] + [CSULOG5].[lmca_nbr] FROM [CSULOG5] does not
I have a ABC service on a server1 that is dependent on MSSQLSERVER service running on server2. Does anyone know how to setup the service ABC on server1 to have a dependancy on MSSQLSERVER running on server2?