My system config is VISTA Ultimate, Visual Studio 2005 SP1, SQL SEVER 2005 SP2. Using 2005 SQL Server Management Studio I am unable to create a servername/aspnet login account.
I right click logins and get the new login form; key ASPNET Login Name; select Windows Authentication; click search; I get the Select User or Group form; under object type I select all three; location I select my server name; if I enter SERVERNAME/ASPNET and click Check Names I get an error; if I click Advanced and Find Now; ASPNET is not listed in Name(RDN) list.
I tried aspnet_sql.exe -E -A all; that did not work.
Where can I find information on creating an ASPNET Login after experiencing the above problems?
hi, I am very new to asp.net..I am creating a webform which connects to sqlserver and display table contents to a grid control.When i run this form,i get error message as follows Login failed for user 'SERVERNAME/ASPNET'. I have read in one page of this forum that we should create aspnet user in sqlserver..i tried to create user,i can see 2 user Guest and public...I don't know what to do ? If someone replies my question,i would appreciate..I have struggling with this for the past 1 week..i couldn't find a solution. My code is as follows: Dim MyConnection As SqlClient.SqlConnection Dim MyCommand As SqlClient.SqlDataAdapter Response.Write("hello world") MyConnection = New SqlClient.SqlConnection("server=Localhost;Integrated Security=SSPI;uid=sa;password=;database=sample") MyCommand = New SqlClient.SqlDataAdapter("select * from emp", MyConnection) Dim ds = New DataSet MyCommand.Fill(ds, "emp") Response.Write("data set has been created") DataGrid1.DataSource = ds.Tables("emp").DefaultView DataGrid1.DataBind() thanks kar
Hi all, Iam getting this error System.Data.SqlClient.SqlException: Cannot open database "XYZ" requested by the login. The login failed.Login failed for user 'xyz-abcASPNET'. when trying to open the page.... http://localhost:1807/projectname/WebFormName.aspx as http://localhost/projectname/WebFormName.aspx Couldnt figure out the solution.Please help Soujanya
I thought I would post how I got remote t-sql debugging working in my environment. Hope it might help someone. I have two domains, DomainA and DomainB. DomainB has a one way external trust to DomainA. Dev Vista machine running VS 2005 is in DomainA logged in as user DomainAauser. SQL 2005 running on test Windows Server 2003 DC machine in DomainB under user DomainBuser. When trying to 'step into stored procedure' in VS, whether my data connection used windows authentication or sql server authentication, I would get the 'Unable to start T-SQL degbuggin...'. I could debug t-sql when I logged into the domain controller (console or rdp) and running VS on the server. I changed the SQL Server service to run under the DomainAauser account and I can now remote t-sql debug using both window authentication and sql server authentication. Hope this may help anyone that might run into this.
Hello,I am getting following error when I tried to connect to the database. Login failed for user 'SHALINIASPNET' I am new to this and don't know how to fix it. I am running SQL Server Desktop engine 2000. I could connect through Server Explorer window, but not through ADO.NETHere's my connection string: sConnectionString = "Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyStore;Data Source=SHALINI;Workstation ID=SHALINI" I have IIS and SQL Server running on the same machine.Please please help me.Thanks in Advance
Hi all, I am new to ASP .NET and now I have been messing two days with the connection thing. I use the Visual Studio 2003 provided drag and drop SqlDataAdapter and SqlConnection to connect to the SQL 2000 server, developer edition (configured with the Windows authentication mode), but whenever I tried I always got a "Login failed for user mymachine/ASPNET" error. Can anyone help me with this? I have also tried, as somebody did, adding one line "<identity imperonate="true"/> to the Web.config file, but had the same kind of error. Do I have do make some change to my SQL server? Thanks a lot! Charlize
I hope anyone can help me with this. I am having problems connecting to the aspnet database. It all started when I noticed that I could not log in to my webapplication anymore under debug mode, although I was able to log in when remotely accessing the website. I got the error message that the machineaspnet user did not have access to the database: "Login failed for user 'GM-FEDORSASPNET' "This was highly peculiar and rather annoying so I tried several things to straighten this out, but it only made things worse!I read that this had to with permissions of the database in question, al though I could not understand why permissions suddenly had changed. I tried to change the rights by attaching it to Management Studio Express and defining an aspnet login, but that failed because a login under that name was not accepted. I tried to make a copy of aspnet.mdf, delete the original and rename the copy to aspnet.mdf. When that didn't work, I then deleted the aspnet.mdf, counting on it that it would be regenerated automatically, but alas. I located the aspnet_regsql.exe tool to regenerate the database, but got the following error message: System.Web.HttpException: Unable to connect to SQL Server database. ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)What can I do?
How do I add login user ASPNET to my SQL 2000 Desktop Engine Server?. I can not find the "Server Manager" in the Start - Programs. Is there any other way to get around adding ASPNET login to the SQL server so I can test my VB program. I got the error: Login failed for user 'com_nameASPNET'.
Respected Members, I have a question, when our aspx page is trying to access the SQL Server 2000 database than before this do we have to creaete a user with the name of ASPNET in SQL Server 2000, or without creating this paticular user(its the default user of ASP.NET account) our aspx pages can also access the SQL Server 2000,I have already SQL Server 2000 running in "SQL Server Authentication Mode" so while creating the user do I have to create it in "Windows Authentication" or "SQL Server Authentication", can you provide some link where I could find complete steps for craeting the ASPNET user or if some one can tell all the steps in details here.
I have a question, when our aspx page is trying to access the SQL Server 2000 database than before this do we have to creaete a user with the name of ASPNET in SQL Server 2000, or without creating this paticular user(its the default user of ASP.NET account) our aspx pages can also access the SQL Server 2000,I have already SQL Server 2000 running in "SQL Server Authentication Mode" so while creating the user do I have to create it in "Windows Authentication" or "SQL Server Authentication", can you provide some link where I could find complete steps for craeting the ASPNET user or if some one can tell all the steps in details here.
I receive this error message occasionally in my ETL - usually when trying to pull data from our source system:
An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in login response". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: Timeout error . ". There is a setting in the connections manager, under the ALL tab, Initialization, Connect Timeout. It is set to zero, which would be the default. It appears (by looking at the timestamps in my error log) that the default is 15 seconds. If I change this to a higher value (60 seconds or so) should this fix the error?
On my VWD 2005 Express, I have installed 2 SQL Server 2005 Express databases in the App_Data folder.I kind of remember these 2 databases were installed from Wrox web site or a zip file. Now we still useSQL Server 2000 databases for our ASP.net applications. I have downloaded the SQL Server 2005 Express.These 2 databases in the App_Data folder seem to work fine although I can not see them from theManagement Studio Express. My question is: How do I 'manually' create a new SQL Server 2005 database into the App_Data folder? TIA,Jeffrey
I've searched all over the web trying to find a goddamn fix for this problem and no one has it right or they have the commands misspelled (!!!), so in spite of all those idiots, in spite of the makers of the Web Matrix guided tour for not pointing out this problem, and in spite of Microsoft who has not posted a solution themselves, here it goes:
* !! Change MYCOMPUTER below to the appropriate name of your computer !! * Open a command prompt * Type: C: * Type: cd "C:Program FilesMicrosoft SQL Server80ToolsBinn" (or the exact location of the file "osql.exe" if different) * Copy/paste the following commands
Hi I created my DB in SQL 2005 Express in VS IDE. I have my app in IIS. When I try to use the DB (e.g. try to login a user in the app) it gives me the following error: Cannot open database "cvRepository" requested by the login. The login failed.Login failed for user 'MyPCASPNET'. My guess was that I had to give permissions to ASPNET user so I did in SQL Server Management. Still not working! Checked my Connection string and I think it's fine... connectionString="Data Source=.SQLEXPRESS;Database=cvRepository;Integrated Security=True;User Instance=True" Still not working! Can anyone explain me what's wrong and to solve this?!
I have explicitly used Exec SP_dropserver and Exec SP_Addsserver SP's to drop and add a SQL server.
After that i restarted the sql server service. After that, when i used the query
select @@servername, it is returning NULL. But, when I used Select Serverproprty('servername'), it is returning me the correct servername. Can i know as why this behavior is exhibited for the same property of finding servername?
I just installed a SQL Server 2005 Express SP2 instance on a server with an existing SQL Server 2000 SP3 installation. (I need SQL Server 2005's INSERT from an EXEC capability). It's working great now except for one thing: I can't link any other SQL servers! I've already successfully added and queried a linked Oracle server, but attempting to add a linked SQL server gives me the following error, no matter which SQL provider I try to use:
Code Snippet "The linked server has been created but failed a connection test. Do you want to keep the linked server?" Additional information: --> An exception occured while executing a Transact-SQL statement or batch (Microsoft.SqlServer.Express.ConnectionInfo) --> Cannot create an instance of OLE DB provider "SQLNCLI" for linked server "SERVERNAME". (Microsoft SQL Server, Error: 7302)
The technical details reveal the error source as "sp_testlinkedserver".
I've scoured the net and premier support for advice on this problem, but the little I found wasn't helpful. I've tried reinstalling the SQL Native Client, but it didn't help. I've tried uninstalling SQL Server 2005 Express completely (including management studio and native client), rebooting, and reinstalling everything, with no luck. The server (obviously) does not have a firewall enabled. I've tried stopping the SQL 2000 Server installed on the system, no help. If I create a test .UDL file on the system, pointing to any of the SQL servers I'm trying to link, clicking the "Test Connection" button returns successful. I'm also able to connect to and query the servers directly from the SQL 2005 Express Management Studio. I just can't add them as linked servers.
The server is running Windows 2003 SP1, SQL Server 2000 SP3, and SQL Server 2005 Express SP2 (the default "SQLExpress" named instance). I've tried setting up SQL 2005 Express to run under the network service account and under a domain account used by the other SQL 2000 servers.
From other SQL 2000 servers, I can connect and link to the SQL Server 2005 Express instance successfully. I can also successfully add linked SQL servers in SQL Server 2000 instance installed on the same server. Only adding linked SQL servers in 2005 Express seems to be broken.
Anyone have any other suggestions? I'm totally baffled. Thank you so much for any helpful advice.
Hello all, I have Membership Authentication services in my application, connecting to a remote SQL Express DB, using a saved username and password (saved in Web.Config connectionStrings).Everything works fine with Membership: i created pages to "sign up" and "log in"... and usernames are stored in the DB with no problems, users are able to register and login with no problems. However, i'm trying to use LINQ to access non-asp-services tables from the same DB, for example, add record to table "comment": I have addComment() method which uses LINQ's InserComment() and SubmitChanges().I use to get the error "Login failed for user tmpOO" when I try to add a comment, then I played with the settings and now I get nothing - no error, the page is loaded as if everything went fine, and no record is added to DB. I'm using IIS7 and Visual Studio 2008 Pro. These are my settings (i didn't change anything else..... i think): IIS7->Website->Authentication: - Anonymous authentication: enabled - ASP.NET impersonation: enabled - Forms authentication: enabled Web.Config: <identity impersonate="true" /> Regards,Naimi
I am novice to SQL, I have a software which uses SQL as backend. The software is made in such a way that during its installation it runs a stored procedure which deletes all users except SA. Now when I try to login to SQL either via Enterprise Manager or via query analyser it asks for password. When I put the password it gives error "Unable to connect to server. msg:18456, level 16, state 1[microsoft][odbc sql server driver][sql server] login failed for user SA. Someone told me that it is unable to connect to server. But the main thing is that I dont have any client I have only server. What could be the possible reason. 1)Is there anyway of creating a user in SQL in such a situation when there is only one user SA and it is unable to log in SQL server. 2)Or is there anyway of removing SA Password. 3)Or is there anyway (in SQL SERVER) of stopping a particular procedure from getting executed while software installation.
Hi. We are using SQL Server 2005 64-bit on Windows Server 2003 R2 x64Enterprise Edition. I have a really weird problem where I have peopleout there who are placed in the db_owner, db_accessadmin, anddb_securityadmin roles in their database, and yet they are unable toadd new users to their databases, despite the fact that logins existfor these users on the server. The reason is that when attempting toadd a new user in Management Studio, upon using the "Browse" option tolook at the logins, the complete list is not presented to them. Infact, they only see a couple of logins or so (the server has hundredsof logins). Also, if they try to type in the login name directly,they get a "permission denied" error message. Since they cannot addusers to their databases, they have to call me and have me do it forthem.I created a test, non-privileged, SQL-authenticated login to testthings for my own sake, and when logged in under the test account, Isaw the same behavior. I had db_owner role for a single testdatabase, and when I went to add users, the only server logins thatwere displayed were my own (the test login in this case) and that ofsa. Further, when I queried the master.sys.syslogins view, I saw thesame thing, it only came back with the rows for myself and sa.It appears that this is clearly a security problem, but I'm not sureat what level to look. We never had this problem with SQL Server 2000or earlier. Does anyone have any idea what I can do to allow mydb_owners to see all the server logins, and therefore be able to addusers to their databases as they see fit? I really do NOT want toassign them to server-level security roles, for obvious reasons.Thanks,SkyGringo
I am running into a problem loggin into SQLsrver 7.0 using 'sa' account but works fine admin account(NT acct)
I have installed sqlsrvr 7.0 on win2k - server standard edition. Installed SQLserver using NT domain account. I have created a username 'sa' with admin previleges. When I try to login with sa, login fails in the enterprise manager. ?
I tried to re-install the server7.0 using local account, again unable to login with 'sa' account in the enterprise manager
Appreciate if you could shed some lights on this issue
Using SQL Server 2005 under XP Professional. I am attempting to log into the Server Management Studio as "UserX". I had previously been using Server Management while logged in as admin. I now get this error message when attempting to connect to the database server: **********************************************************************TITLE: Connect to Server------------------------------Cannot connect to [**NAME OF SERVER**].------------------------------ADDITIONAL INFORMATION:Login failed for user '[**NAME OF SERVER**].UserX. (Microsoft SQL Server, Error: 18456)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476------------------------------BUTTONS:OK------------------------------ ******************************* Microsoft help doesn't have a specific help for that particular error message. Any hints as to what is going wrong?
I keep getting this following error when trying to set-up an updateable subscription on SQL 2005 (latest service packs). Server is set for mixed mode auth. At the final stage of the new subscription wizard I get: Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication. (New Subscription Wizard) The user is not associated with a trusted SQL Server connection Login failed for user ''. The user is not associated with a trusted SQL Server connection Error Number: 18456, Severity: 14, State: 1,Line Number: 1
Can anyone recommend a possible way of debugging this? Is it some issue with RPC security?
I have a SQL 2k5 ent. 64 bit on Windows 2003 Ent x64 edition.
The sql server was running fine under localsystem account. Recently I changed the service account to a local user (part of users group in windows) and implemented permissions according to KB article 283811. (have imlpemented the same on many other sql servers without issue).
However, the SQL services are not starting up and I am seeing the following errors in the errorlog.
2007-07-25 12:36:55.90 spid11s Server name is 'HBCARPROD'. This is an informational message only. No user action is required.
2007-07-25 12:36:55.90 spid13s Starting up database 'model'.
2007-07-25 12:36:55.90 Server Error: 17182, Severity: 16, State: 1.
2007-07-25 12:36:55.90 Server TDSSNIClient initialization failed with error 0x5, status code 0x51.
2007-07-25 12:36:55.90 Server Error: 17182, Severity: 16, State: 1.
2007-07-25 12:36:55.90 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.
2007-07-25 12:36:55.90 Server Error: 17826, Severity: 18, State: 3.
2007-07-25 12:36:55.90 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-07-25 12:36:55.90 Server Error: 17120, Severity: 16, State: 1.
2007-07-25 12:36:55.90 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I have gone through the http://blogs.msdn.com/sql_protocols but everything mentioned here seems to be there. I understand this is some permission issue. Just not able to find it out. Can anybody help?
Client of mine has a major problem with the Error 17832 (accompanied by 1608) on MS SQL Server 6.5 running on NT 4.0 SP3. SQL Server has 100 per-seat licenses.
Application, running on the client computers, establishes several connections (I know...) to the SQL Server on as-needed basis. The errors started to come up when application has executed on 40+ workstations. When the "saturation level" is reached, no connection to the SQL server could be established (even for Enterprise Manager, running on the same NT box!)
Any suggestions? Licenses, network, client configuration, SQL Server configuration... Your suggestions sent to email@example.com will be appreciated.
Even though it does not cause any problems, it really fills up the Error Log, which makes the log take a lot of disk space. From researching this problem, I realize that it has something to do with the network. Could anybody suggest what is it specifically on the network that could be not set up properly?
I am unable to drop the above login. The error is Error:15141 The server principal owns an event notification and cannot be dropped.
I have looked in the table sys.server_event_notifications and there are rows returned that have a server_principal_id of the user I am trying to drop. No events have been created on this server, so I am assuming these notifications are either created by default or are somehow related to Database Mail?
All the event notifications belong to service name "SQL/Notifications/ProcessWMIEventProviderNotification/v1.0" and begin with SQLWEP (i.e. SQLWEP_RECHECK_SUBSCRIPTIONS, SQLWEP_B415ADB8_A604_4057_976F_600002FA5AF6). How can I find out what these are for and how they were created?
What purpose do these event notifications have? Is there some syntax to change the owner of these event notifications so I can successfully drop the login? If the only way is to directly update the system view, is this safe and what repercussions could this have?
I am trying to setup Reporting Services on my local machine. I have installed SQL 2005 Developer Edition on my laptop and when I goto http://localhost/reports/Pages/Folder.aspx I receive the following error:
The report server is not responding. Verify that the report server is running and can be accessed from this computer.
I checked in the Event Viewer and I see some cryptic error by SQLDUMPER: