Im developing a ASP.NET website. Recently we were required to move the databse from localhost to another server. I'm able to connect to the other server database from SQL 2005 management studio with windows authentication. However when I try to do it in ASP.NET it says error: login failed for domain/server$. I have declared the connection string in web.config file.
View 7 Repliesam working on asp application which basically is an interface to the report server. I am currently unable to determine the source of the problem so it may have nothing to do with reporting services.
View 4 Replies View RelatedI am working on asp application which basically is an interface to the report server. I am currently unable to determine the source of the problem so it may have nothing to do with reporting services.
View 11 Replies View RelatedFor some reason , the report server is trying to login as <domainname><machine name> - its supposed to be <domain><user name> or ASPNET or Network Service Authority - I have no clue why it is pickin gup machine name. Any ideas and how to fix?
View 3 Replies View RelatedFolks,
I have read the posts concerning login failures for the ASPNET user. I have a slightly different problem, as you can see from the title of this post.
My environment is a private domain that has two machines:
1) Windows 2000 server on which SQL Server is running. Let's call it FOO_SERVER.
2) Windows XP Professional on which I am running my IIS and .NET development environment. Let's call it FOO_WORK.
3) Let's call the domain, FOO_DOMAIN.
The user, ASPNET, is not a domain user, but a local user, so I do not know how to establish it as a valid login for SQL Server. But this is beside the point, anyway, as the error I am getting has nothing to do with the ASPNET user. It appears that a different username is being used to access SQL Server.
My connection string is:
"server=FOO_SERVER;database=pubs;Trusted_Connection=yes"
The error I receive is:
"Login failed for user FOO_DOMAINFOO_WORK$"
I am using the default settings in machine.config. Specifically <processModel> userName="machine" password="AutoGenerate" </processModel>
Thanks in advance for any suggestions.
-Joel
In an attempt to improve security for our web server/db server setup, we have a SQL Server 2005 server set for Windows authentication only and a web server (both behind a firewall together on a single local domain).
The web server is using IIS7, and the default NetworkService account to run the ASP.NET processes.
I've given the NT AUTHORITYNETWORK SERVICE account access to the database in question.
The SQL authentication fails, but the account failing is NOT the NetworkService account, but the <DOMAIN><COMPUTER>$ account.
Note that if I use identity impersonation with a specific domain account, I can get the app to work. However, I do NOT want to use impersonation, I want the default NetworkService account to work.
Does anyone know why IIS, which is supposed to be using NetworkService, is instead using the <DOMAIN><COMPUTER>$ account to connect to SQL, which is then failing?
JK
(Cross post from newsgroup)
Attempting to implement Windows authentication between trusted domains. . .
I have a domain trust set up between two domains connected via persistent vpn:
hi,
so i have a new box and I'm trying to get my websites and SQL Server 2005 Standard Edition working on it, but the pages give me the following error when I try to load them:
"Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user 'xxx'"
Everything seems exactly the same settings and user-wise from my old box to my new one, but nevertheless everything I've tried gives me the same error.
I've tried creating new users in SQL Server and giving them appropriate permissions to my database. I've even tried just using the built in 'sa' account. Nothing seems to change the error, except when I give it the incorrect password then it just says 'login failed'
This leads me to believe that i'm successfully logging into the SQL Server, but it doesn't want to give me access to the database I'm requesting access too. But "apparently" the account i'm using should have access to the database. If nothing else the 'sa' account should, but that didn't work either.
I'm stumped. Any ideas?
Hi all,
Have just tried my sql server 2005 connected asp classic website on II7 for the first time and have gotten some errors.
First off I have unchecked show friendly errors in IE and have enabled ASP to send error messages to the browser.
My error I get is when I execute a basic .asp page:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "mydatabasename" requested by the login. The login failed.
/index.asp, line 10 which is dbConnect.Open cstring
from this peice of code:
sub dbOpen()
set dbConnect = Server.CreateObject("ADODB.Connection")
cstring = "DSN=mysqldsn; Trusted Connection=yes"
dbConnect.Open cstring
end sub
I have gone into ODBC and have setup both a user dsn and file dsn that equals mysqldsn and points to my database (I know you only need to set up one DSN but I'm not sure which)
I also notice under mywebsite home panel there is a connection string option. Do I do anything with that?
Definatley a lot more to it than XP's II6!
Any help or advice would be greatly appreciated.
i'm using the Enterpirse library logger to write logs into a database.
When choosing connection string i choose the database i want in the "connection properties" dialog box and
push 'Test connection' button.
everything goes well.
then i open the SQL Server Management studio express and connect to the databse to check some things,
from that point on , when i push the 'Test Connection' button in the Enterprise library i get the error:
"cannot open user default database. Login failed. login failed for user My'server/MyuserName'"
even when i close the sql server manager , it is still stuck - the connection test doesn't work anymore....
it only work when i restart the computer.
why ?
We have a SQL 2000 Active/Passive cluster running on Windows 2000. On one node, everything logs in fine (second node is powered off). I can use local authentication fine in OSQL (-E) and even see my connection in SQLEM current activity as [DomainUser] for the NT account which I am logged in as. Then I bring the second node online and initiate a failover. SQL Server starts but Cluster Admin cannot connect and starts throwing this Anonymous Logon error. I open a command prompt and try the same OSQL (-E) local login and sure enough it is also giving the Anonymous Logon connection user. I do not understand why the failover to a second node is causing the Trusted Connection Local authentication to switch to Anonymous instead of the [DomainUser] which I am using. Any help is appreciated. John.
View 1 Replies View RelatedWe recently upgraded to SQL 2005 from SQL 2000. We have most of our issues ironed out however about every 1 minute there is a message in the Application Event log and the SQL log that states:
EVENT ID 18456 Login Failed for the users DOMAIN/ACCOUNT [CLIENT: <local machine>]
This is a state 16 message which I thought meant that the account does not have access to the default database. The account is actually the account that the SQL services run under.
Any ideas? We can't seem to figure this one out. We actually upgraded to 2005 from 2000 and had an error appear after every reboot that prevented the SQL Agent from running(This application has failed to start because GAPI32.dll was not found. Re-installing the application may fix this problem.) We did a full uninstall of SQL and reinstalled fresh and restored the databases from .bak files and that is when the EVENT ID 18546 started occuring every minute.
We don't have any SQL heavy hitters here so please be detailed with any possible solutions. That you very much for any help you can provide!
David
Hi,
I have a script component. What it does, it queries the a table using a connectionstring assigned to it in the Connection Managers Editor (which is an ado.net adapter). this works fine when i'm using a windows login in the ado.net connection manager. But when i changed my connection to use SQL server login, I encounter this error:
OnError,,,Add new records to Dim_T_Status (Case),,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
OnError,,,LOAD AND UPDATE OCEAN Dimension Tables,,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
OnError,,,LoadOCEANDimensions,,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
How to go about this?
cherriesh
All the logins with sysadmin role are locked out in one of the SQL server. Also in that instance Logon trigger is implemented which allows only certain users with Windows Authentication to logon.
This server is converted into single user mode by using command prompt. Now we are attempting to connect to SQLServer using command sqlcmd -S FTCPU3239 (since we do not have any other login) and create a new login with sysadmin role but are refused due to logon trigger. it says Login failed for login 'DomainNameUserName' due to trigger execution.
Many a times see the below error in SQL Error log.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]
Is this something to do here?
Note: If I run the below statement I know that the SQL Error log entry will go off, but wanted to know the real significance of this error?
CREATE LOGIN [NT AUTHORITYANONYMOUS LOGON] FROM WINDOWS
Hello everyone,
Since last so many days i am seeing that someone is trying to login to sql server through login name sa.but that login is failed.and this is occuring constantly.
Earlier i had same login failed message for another ip address.i have blocked that ip address through access-list in firewall.but now i am seeing the same message for another ip address.
(1).how can i permenently remove this message from Event log.
(2).What is the impact of this on sql server performance.is sql server performance degraded by this kind of contineous attack?
here i am attaching that report from event viewer log file.
2/26/2007 1:48:18 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:13 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:13 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:03 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:58 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:58 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:56 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:56 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:55 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:55 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:51 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:51 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:46 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:46 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
Needs your help to resolve this issue.
Thanks,
Bharat
Hi when i try and open a database in sql server management studio i get the error "Cannot open user default database. Login failed. Login failed for user 'DOMAINUser'. (.Net SqlClient Data Provider)", what can i do to rectify this, i have googled around and still havent found no answers.
View 4 Replies View RelatedHi,
Im getting this error when attempting to retrieve data from an sql database.
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: Cannot open database requested in login 'projectAllocations'. Login fails. Login failed for user 'sa'.
Source Error:
Line 13: objConn = New SqlConnection( "Server=LAB303-066NETSDK; Database=projectAllocations; User ID=sa;Password=mypassword")
Line 14: objCmd = New SqlCommand("SELECT * FROM project_descriptions", objConn)
Line 15: objConn.Open()
Line 16: objRdr = objCmd.ExecuteReader()
Line 17: While objRdr.Read()
Source File: C:finalyearproject2sample.aspx Line: 15
Please Help!! Im a beginner to this, so if anyone knows the answer, take baby steps when explaining. Thanks
Been looking through the forums for a solution to this problem.I already tried granting access through statements such as:exec sp_grantloginaccess N1'machineNameASPNET'But they don't seem to work.. i vaguely remember seeing somewhere a DOS command line statement that grants access to the ASPNET_WP and that fixed my problem before on another computer.. but this is a new computer and i forgot to write down the command.Can anyone help explain and propose a solution to my problem. Many thanxs.
View 9 Replies View RelatedI am using the MSDE to connect to my ASP.NET application. I get this error after clicking the login button of my login page. Anyone know why this would happen?
Thanks for any help,
Cannot open database requested in login 'DataSQL'. Login fails. Login failed for user 'serverASPNET'.
Hey Microsoft: this affects development that will eventually sell a lot of seats on SharePoint Server 2007. If you guys and gals can't straighten out this mess, you can't expect custom solutions with custom web parts. So pay attention for your own good. Yes, SPS 2007 is what this is all about. I've created simpe web parts and deployed them, same VS 2005, but I need local development and debugging for more complex stuff. I'm really disappointed that you have no solution for this problem.
I've seen other posts on this, but the result seems to be the same: if you fix it, it's by accident, not by design.
1. I created a blank ASP.NET web site
2. I added a web part manager
3. I added a web part zone
I get the error described above. I have no idea why SQL Server settings are so screwed up.
I've tried all the stuff in the other posts - security settings, command line installation, etc. None of those worked.
The default template(s) don't copy anything into App_Data, nor create an empty folder. I don't know why that is. I have other web sites working just fine, but they use remote SQL databases, or local ones I created, and didn't need profile management (no forms authentication, no web parts, no web zones).
I've also started out with a local database, using SQL Authentication, later moving it to a remote server, and never had any problems. The SQL Server developer edition and Express seem to work just fine. I can also debug stored procs when the .mdf is in App_Data. So the problem isn't one of connectivity.
What would cause the default screw-up? This would seem to point from all directions to a problem with Visual Studio (2005)? The installation is defalt - perhaps some extras included (copy local), but nothing unusual. AJAX for ASP.net is installed, but not used in the above "default web site" trial. Likewise Syncfusion's tools, which work fine on other developer workstations at this same location, all of which are from the same image (purchased at the same time & imaged). That web parts work on other boxes, running all the same management tools (anti-virus, remote sys admin/sms etc.) makes none of those suspect.
I think Microsoft needs to have a clean problem solution and publish it. SP1 certainly doesn't fix it. What's worse is the stupid, lame error message. "I can't open the default database". Well, what did you try? What do you think the default is? What settings are you using? Why is there no debugging information other than the usual worthless trace information showing it's all deep within the ProviderBase and SqlClient namespace code? How is that supposed to be helpful?
If anyone has anything solid, not guesses, I'd like to know.
I am getting the error:
Cannot open database "aspnetdb" requested by the login. The login failed.
When I browse to my ASP.NET 3.5 LINQ web application on the IIS 6.0 server on Server 2003.
I imagine this is because while I granted SQL Server 2005 login and permissions to my database that the application stores its data in, I did NOT grant any rights to the service account the IIS Application Pool uses for its identity to the aspnetdb database on SQL Server which is where all my roles information is stored at.
My question is what are the MINIMUM permissions needed for this database so it can perform its roles related functions?
I'm using Windows Authentications with the SQL Role provider for authorization.
Thank you.
EDIT: I think I only need to open the aspnetdb database and add my login to the aspnet_Roles_FullAccess role. Is that correct?
I Guys
I am trying to create an application that writes data to a SQL database (studio express).
The application works fine but as soon as I open the table with the SQL server management studio express the application does not work any more displaying the following message:
€śCannot open user default database. Login failed. Login failed for user€¦€?
If I siwtch off and on the computer the problem disappear till the table will be open with the database management studio express!!!!!
How can I solve this annoying problem?
Cheers
I recently formatted my pc, everything is set but one thing, the sql server db.
I can't remember how I set the permission for my local machine for the db.
Error: Login Faile for <machineName>ASPNET
How do I add the user to access the db?
Thanks all,
Zath
For the life of me I've had nothing but trouble using SQL Server Express. My latest problem sprung up out of nowhere, I all of a sudden begin getting the following error, when I know my app was working last time I ran it: "Cannot open user default database. Login failed.Login failed for user 'PINCHCPUBrad'."I get this error in an auto-generated file App_Code.1voqxxpd.18.cs. What kills me is, I can connect to the database through Server Explorer and SQL Management Studio, but for some reason my application cannot. I really don't understand how logging-in works with SQL Server Express as I've never even set up a login. When I look at my database properties in Server Explorer is shows Owner as the exact entity my application says it can't find: 'PINCHCPUBrad'. The database I'm trying to connect is in my App/Data folder and my Connection String says: "LocalSqlServer" connectionString="Data Source=.SQLExpress;Integrated Security=True;User Instance=False;AttachDBFilename=|DataDirectory|aspnetdb.mdf" providerName="System.Data.SqlClient"/> I honestly don't get why attaching to and maintaining a simple database is unbelievable difficult and unpredictable, but I constantly get screwey errors like this that pop up out of nowhere.
View 2 Replies View RelatedI wrote a code to check and validate the username and password against the database and redirect the user based on the user flag as follows:
Dim MyConnection As SqlConnection
Try
If Page.IsValid Then
Dim strUsername As String = txtUsername.Text
Dim strPassword As String = txtPassword.Text
Dim DS As DataSet
Dim MyCommand As SqlDataAdapter
Dim SelectCommand As String = "select userid, flag from employees where username = @login and password = @password"
MyConnection = New SqlConnection("Data Source=localhost;Integrated Security=SSPI;" & _
"Initial Catalog=rfd;")
MyCommand = New SqlDataAdapter(SelectCommand, MyConnection)
MyCommand.SelectCommand.Parameters.Add(New SqlParameter("@login", SqlDbType.Char, 10))
MyCommand.SelectCommand.Parameters("@login").Value = strUsername
MyCommand.SelectCommand.Parameters.Add(New SqlParameter("@password", SqlDbType.Char, 10))
MyCommand.SelectCommand.Parameters("@password").Value = strPassword
DS = New DataSet
MyCommand.Fill(DS)
'MyConnection.Close()
If DS.Tables(0).Rows.Count = 1 Then
Dim flag As String = DS.Tables(0).Rows(0)("flag")
Dim id As Integer = DS.Tables(0).Rows(0)("userid")
Session.Add("flag", flag)
If flag = "u" Then
Session.Add("userid", id)
Session.Add("Page", "user")
Response.Redirect("user_index.aspx")
ElseIf flag = "pl" Then
Session.Add("userid", id)
Session.Add("Page", "pl_index")
Response.Redirect("PL_index.aspx")
End If
Else
msg1.Style("color") = "red"
msg1.Text = "Username or Password incorrect: Please Try again"
End If
End If
Finally
Session.Timeout = 10
MyConnection.Close()
End Try
End Sub
However, when I run it, it points as the line " MyCommand.Fill(DS)" and said Server Error - Login failed for user/aspnet. Where should look and what should I ckeck? Please help me !
Level: beginner!
What is wrong?
Login failed for user 'DEBBY-76GXHEASPNET'.
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 'DEBBY-76GXHEASPNET'.
Source Error:
Line 90:
Line 91: If Not Page.IsPostBack Then
Line 92: Da_leerlingen.Fill(Ds_leerlingen1)
Line 93: Dg_leerlingen.DataBind()
Line 94:
Source File: c:inetpubwwwrootWebApplication3WebForm1.aspx.vb Line: 92
Stack Trace:
[SqlException: Login failed for user 'DEBBY-76GXHEASPNET'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +472
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +38
WebApplication3.WebForm1.Page_Load(Object sender, EventArgs e) in c:inetpubwwwrootWebApplication3WebForm1.aspx.vb:92
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731
Thanks
Hi all,For testing purposes I created a local database using SQL Server 2000. I want to connect to this database using following code:mySqlConnection = New SqlConnection("server=(local)SQLExpress;Integrated Security=SSPI;database=TestDbInge;UID=IVANSARK;PWD=test") mySqlCommand = New SqlCommand("SELECT Voornaam FROM Personen", mySqlConnection) mySqlConnection.Open() I'm getting the message below: System.Data.SqlClient.SqlException: Cannot open database "TestDbInge" requested by the login. The login failed. Login failed for user 'IVANSARKASPNET'. It's the same when I don't add the userid and password part to the connectionstring.
What am I doing wrong?? And where does "IVANSARKASPNET" come from? Shouldn't I be anonymous? Please help.Regards, Inge
I am using Crystal Reports, VB.net, SQL Server 2000sp3, MDAC 8.0, and Windows XP. When I try to make a connection from a Crystal Report to SQL Server via an ODBC connection, I get the following message:
Details: 28000:[Microsoft][SQL Server Driver][SQL Server]Login failed for user domain/username
In the odbc, I specify SQL Server authentication and provide a username and password but these are being ignored. Why is Windows authentication being used in place of the SQL Server authentication that I specify in my odbc?
Thanks in advance,
Matt
I have been using SQL Server 2012 developer edition for quite a while without problems. But now when I try to connect I get this error:
Cannot open user default database. Login failed.
Login failed for user 'D8700Ken'. (Microsoft SQL Server, Error: 4064)
I suspect that I caused this problem myself but I don't know how to recover from it. Here is what I did:
1: Used SSDT in Visual Studio to change the set default database from 'master' to 'DTNSQL' (My first SSDT experiment!)
2: Used SQLSMS to rename the 'DTNSQL' database to 'DTNSQL01'.
3: Logged out of SQL Server - then tried to log back in.
I have read that the solution to this problem is to "login using another Login."
I don't seem to have "another Login". How to find an existing Login or create a new Login.
Hi I have asp.net2 app using SQLExpress which works fine in VS2005.
When I compile it and try to run it from IIS on the same machine using the same
sql server database with:
connectionstring="server=.SQLEXPRESS;Database=abc.mdf;Trusted_Connection=yes"/>
I get the following error.
Cannot open database abc.mdf requested by login. The login failed. Login failed for user 'machinenameASPNET'
Any help much appreciated
Thanks
David
Cannot open database "QuoteSystem" requested by the login. The login failed.Login failed for user 'NT AUTHORITYNETWORK SERVICE'.
Last time I recieved this error I had to add ASPNet, NTAuthority, and myWebSiteUsers USERS under the database properties-->permissions setting for the specific database I am trying to access with the website but this database(QuoteSystem) does not lists any of these objects so I can add them. Does anybody know what I have to do to fix this?
I am using SQL Server 2005.
Please, can anyone tell me why I am getting the undermentioned error message when I develop my application as an IIS Site in Visual Web Developer 2005 Express ? I have already developed and successfully tested it as a 'FileSystem Web Site' .I am using SQLSErver Express 2005 edition and have which I have installed along with the Northwind database as per the download instructions. My IIS software is version 5.1 which I have checked and it is configured to allow Integrated Windows Authentication. the relevant code is (1) web.config file connection strings
<connectionStrings>
<add name="NorthwindConnectionString"
connectionString="Data Source=.sqlexpress;Initial Catalog=Northwind;Integrated Security=True"
providerName="System.Data.SqlClient"/>
</connectionStrings>(2) the grid view control and sqldatasource
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False" DataKeyNames="CategoryID"
DataSourceID="SqlDataSource1">
<Columns>
<asp:BoundField DataField="CategoryID" HeaderText="CategoryID" InsertVisible="False"
ReadOnly="True" SortExpression="CategoryID" />
<asp:BoundField DataField="CategoryName" HeaderText="CategoryName" SortExpression="CategoryName" />
<asp:BoundField DataField="Description" HeaderText="Description" SortExpression="Description" />
</Columns>
</asp:GridView>
<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:NorthwindConnectionString %>"
SelectCommand="SELECT [CategoryID], [CategoryName], [Description] FROM [Categories]">
</asp:SqlDataSource>This is the full error message and details:
Server Error in '/sqlservertest' Application.
Cannot open database "Northwind" requested by the login. The login failed.Login failed for user 'JERRY-3C9615BAAASPNET'. 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: Cannot open database "Northwind" requested by the login. The login failed.Login failed for user 'JERRY-3C9615BAAASPNET'.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:
[SqlException (0x80131904): Cannot open database "Northwind" requested by the login. The login failed.
Login failed for user 'JERRY-3C9615BAAASPNET'.]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +684883
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +207
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1751
System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +32
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +601
System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +159
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +346
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +445
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +304
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +85
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +137
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +83
System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1837
System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +17
System.Web.UI.WebControls.DataBoundControl.PerformSelect() +129
System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +70
System.Web.UI.WebControls.GridView.DataBind() +4
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +69
System.Web.UI.Control.EnsureChildControls() +87
System.Web.UI.Control.PreRenderRecursiveInternal() +41
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1787
Version Information: Microsoft .NET Framework Version:2.0.50215.312; ASP.NET Version:2.0.50215.312