I want to mirror some database to another server (without witness server)
I have 2 machines, where Microsoft SqL '05 Developer Edition SP1 installed.
Two machines working in domain network, one of them is a server, secondmachine enters into domain with username and password.
I can ping each machine by the ip adress and by the networks name, like a.machine.com, b.machine.com
TCP/IP is enabled in Server Configuration.
What I DO:
1. Create full backup of my database on server A
2. Create full backup of transaction logs on server A
3. Restore my database and transaction logs from backup WITH NO RESTORE on server B
4. On machine A: I open tasks -> mirroring properties dialog (configuring mirroring) and go to configure security dialog.
5. I use standart properties (port, endpoint name, ecryption)
6. On page "Mirror Server Instanse" i click "Browse for more" and type there server B adrress (b.machine.com). Click connect.
7. Server configuring was sucsessful
8. Server network addresses were:
Principal : TCP://a.machine.com:5022
Mirror : TCP://b.machine.com:5022
9. I click Start Mirroring but system gives me error:
Error 1418, The Server network address can not be reached or does not exists.
I open logs on machine b (mirror server):
Message
Database Mirroring login attempt by user 'NT AUTHORITYAnonymous login.' failed with error:
'Connection handshake failed. The login 'NT AUTHORITYAnonymous login' does not have CONNECT permission on the endpoint.
State 84.'. [CLIENT: 172.168.0.130]
and this message before:
The database 'mybase' is marked RESTORING and is in a state that does not allow recovery to be run.
When I configured database mirroring, i choose "Windows Authentication", Why 'NT AUTHORITYAnonymous login.' ...??
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.
I just upgraded to Vista and can not run the website anymore. Getting: Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. error I added that user to all databases as db_owner, but that did not help..
I am receiving the above error when using a workstation to connect to my webfiles.
I am using windows authentication (whcih I have selected as my only option on the IIS). Impersonate is set to true in the webconfig file, with authentication set to Windows.
My connection string is: SQLConnection1 = "initial catalog=SIMS;data source=spacesql;integrated security=SSPI"
It runs no problem when I use the localhost. It allows me to use other aspx pages that do not connect to the SQL server. It only gives me this error when I am using a page that tries to connect to the SQL server.
The SQL files reside on a separate server to the IIS and I would like it to remain this way.
I get the following error message when I select a report:
An error has occurred during report processing.
Cannot create a connection to data source 'PSS5'.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.
My Data source is set to Windows Integrated Security when I get this error message. If I change my data source to be "Credential supplied by the user running the report", the report generates fine. I am running SQL 2005 SP2. I have SQL reporting services installed on different server than my database services. Both servers are W2K3 R2 x64.
My IIS website and virtual directories are set up for Integrated Windows Authentication. My IIS application pool is set up to use an AD service account. I have followed the step/procedures outlined at: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx
I'm trying to connect to a Sql Server 2005 database from my local development machine, which is running IIS 5.1 (Windows XP Pro). The web application is not using impersonation and has anonymous access enabled. In my system's machine.config file, I've set the processModel section to look like:
This has been working fine for us connecting to SQL Server 2000 databases (running on Windows 2003). When we connect, I access Sql 2000 databases under the context of "OurDomainMyMachineName$". However, we've recently installed Sql Server 2005 on a new Windows 2003 server & when I connect to that server, I receive the error:
System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITYANONYMOUS LOGON'
when trying to call the SqlConnection.Open() method. Our connection string is very basic:
Data Source=sql-dev2; Initial Catalog=TestDatabase; Integrated Security=True; Application Name=PrototypeWebservice;
In the Sql Server logins, we've granted the computer account "OurDomainMyMachineName$" db_owner access to every database (in both Sql Server 2000 & 2005).
I am able to connect to the Sql Server 2005 databases if I change my section in machine.config to <processModel userName="OurDominamyPersonalAccount" password="myPersonalPwd"/>, or if I move the application to an IIS6 server & set the application pool identity to NETWORK SERVICE, but we'd like to continue accessing our Sql Server 2005 databases (from our development machines running IIS5.1) as we currently access our Sql Server 2000 databases; under the context of "OurDomainMyMachineName$".
Would anyone have any ideas why this would be happening or how to resolve? Thanks in advance.
I have two machines that i want to use for merge replication :
Laptop ( Publisher + Distributor )
VPS90 ( Subscriber )
Both connected via the internet
NO DOMAIN
Need to implement merge replication ,after initializing the snapshot I get the following error on both machines :
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. [CLIENT: 192.168.1.1]
I created a new user "Repuser" (admin)with the same password on both machines and configured the Agent proccess to run under that account ,now i get this error : Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.1]
Please note that :
· Mixed mode authentication IS ENABLED ON BOTH MACHINES · BOTH MACHINES CAN PING AND ACCESS EACH OTHER ,BOTH COMPLEETELY VISIBLE. · CONFIGURED ALIASES ON BOTH MACHINES. · Both configured to use Sa account . * I have NO DOMAIN
what does this mean?
It simply means that the SQL Server Agent process account is the one that€™s being authenticated to connect to the other machine and NOT the Sa account ,WHY?
I have searched all the forums on this issue and tried the other options but nothing seems to work. I have an IIS server using asp.net to connect to a SQL database on a separate server which also happens to be a domain controller(i.e. no local accounts). I have tried changing the connection string, web.config, etc. but I still can't get connected. I believe the issue is with the SQL security but I'm not sure.
<!-- DYNAMIC DEBUG COMPILATION Set compilation debug="true" to enable ASPX debugging. Otherwise, setting this value to false will improve runtime performance of this application. Set compilation debug="true" to insert debugging symbols (.pdb information) into the compiled page. Because this creates a larger file that executes more slowly, you should set this value to true only when debugging and to false at all other times. For more information, refer to the documentation about debugging ASP.NET files. --> <compilation defaultLanguage="c#" debug="true" />
<!-- CUSTOM ERROR MESSAGES Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable. Add <error> tags for each of the errors you want to handle.
"On" Always display custom (friendly) messages. "Off" Always display detailed ASP.NET error information. "RemoteOnly" Display custom (friendly) messages only to users not running on the local Web server. This setting is recommended for security purposes, so that you do not display application detail information to remote clients. --> <customErrors mode="Off" />
<!-- AUTHENTICATION This section sets the authentication policies of the application. Possible modes are "Windows", "Forms", "Passport" and "None"
"None" No authentication is performed. "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to its settings for the application. Anonymous access must be disabled in IIS. "Forms" You provide a custom form (Web page) for users to enter their credentials, and then you authenticate them in your application. A user credential token is stored in a cookie. "Passport" Authentication is performed via a centralized authentication service provided by Microsoft that offers a single logon and core profile services for member sites. --> <authentication mode="Windows" />
<!-- AUTHORIZATION This section sets the authorization policies of the application. You can allow or deny access to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous (unauthenticated) users. -->
<authorization> <allow users="*" /> <!-- Allow all users --> <!-- <allow users="[comma separated list of users]" roles="[comma separated list of roles]"/> <deny users="[comma separated list of users]" roles="[comma separated list of roles]"/> --> </authorization>
<!-- APPLICATION-LEVEL TRACE LOGGING Application-level tracing enables trace log output for every page within an application. Set trace enabled="true" to enable application trace logging. If pageOutput="true", the trace information will be displayed at the bottom of each page. Otherwise, you can view the application trace log by browsing the "trace.axd" page from your web application root. --> <trace enabled="true" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="false" />
<!-- SESSION STATE SETTINGS By default ASP.NET uses cookies to identify which requests belong to a particular session. If cookies are not available, a session can be tracked by adding a session identifier to the URL. To disable cookies, set sessionState cookieless="true". --> <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20" />
<!-- GLOBALIZATION This section sets the globalization settings of the application. --> <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
<!-- ADDED BY YURI --> <identity impersonate="true" />
I get this error when trying to alter a stored procedure that has an insert statement referencing a new linked server I created:
INSERT INTO [servername].databasename.dbo.DirectReport ...
Msg 18456, Level 14, State 1, Procedure Get_Direct_Pay_Move_Data, Line 17 Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.
I added Administrators and my logon to the permissions of my linked server but still get this error when it tries to save my stored proc...the one which has that insert.
This is further to my previous post, which has had over thirty viewing but as yet no replies. Is there really no solution to this problem?
I have now given up trying to use the wizard to get mirroring running, as although I'm not entirely sure, some stuff I've read implies that the wizard only works using Windows authentication. Maybe someone can confirm this. Either way, the wizard doesn't work for me (see my previous post).
So instead of using the wizard I've now tried to set up mirroring manually using SQL statements. Following are the steps I've taken. I've tried to replicated exactly what it says in the online documentation. At the end of the post are the SQL statements issued.
1. Enable encrypted outbound connections on the primary server 2. Enable encrypted outbound connections on the mirror server 3. Enable encrypted outbound connections on the witness server 4. Enable encrypted inbound connections on the primary server 5. Enable encrypted inbound connections on the mirror server 6. Enable encrypted inbound connections on the witness server 7. Set mirror's partner to the primary 8. Set primary's partner the mirror (EXPLOSION)
There might be more stuff to do after this, but here is where it breaks down. Again, the error is the same as before when using the wizard:
Msg 1418, Level 16, State 1, Line 1 The server network address "TCP://10.152.58.243:7024" can not be reached or does not exist. Check the network address name and reissue the command.
Which is **INCORRECT** or at least highly unhelpful because: i) netstat -abn shows the sql server process listening on port 7024; no other processes are listening on this port ii) I can telnet to port 7024 on this machine and issue the 16 keystrokes
Please, someone help, I am crying tears of despair. SQL below.
Cheers,
Mike
/* The following is a complete list of the SQL statements issued. Please assume they are issued on the relevant master databases. */
/* -------- 1. ENABLE OUTBOUND CONNECTIONS ON THE PRIMARY -------- */
DROP ENDPOINT Mirroring GO DROP CERTIFICATE BILL_PRIMARY_CERT GO DROP MASTER KEY GO
CREATE MASTER KEY ENCRYPTION BY PASSWORD = '**************' -- real password used GO
CREATE CERTIFICATE BILL_PRIMARY_CERT WITH SUBJECT = 'BILL_PRIMARY_CERT for database mirroring', START_DATE = '01/01/2006', EXPIRY_DATE = '01/01/2099' GO
CREATE ENDPOINT Mirroring STATE = STARTED AS TCP ( LISTENER_PORT=7024 , LISTENER_IP = ALL ) FOR DATABASE_MIRRORING ( AUTHENTICATION = CERTIFICATE BILL_PRIMARY_CERT , ENCRYPTION = REQUIRED ALGORITHM AES , ROLE = ALL ) GO
BACKUP CERTIFICATE BILL_PRIMARY_CERT TO FILE = 'C:certificatesBILL_PRIMARY_CERT.cer' GO
-- then copy certificate to other two machines
/* -------- 2. ENABLE OUTBOUND CONNECTIONS ON THE MIRROR -------- */
DROP ENDPOINT Mirroring GO DROP CERTIFICATE BILL_SECONDARY_CERT GO DROP MASTER KEY GO
CREATE MASTER KEY ENCRYPTION BY PASSWORD = '**************' -- real password used GO
CREATE CERTIFICATE BILL_SECONDARY_CERT WITH SUBJECT = 'BILL_SECONDARY_CERT for database mirroring', START_DATE = '01/01/2006', EXPIRY_DATE = '01/01/2099' GO
CREATE ENDPOINT Mirroring STATE = STARTED AS TCP ( LISTENER_PORT=7024 , LISTENER_IP = ALL ) FOR DATABASE_MIRRORING ( AUTHENTICATION = CERTIFICATE BILL_SECONDARY_CERT , ENCRYPTION = REQUIRED ALGORITHM AES , ROLE = ALL ) GO
BACKUP CERTIFICATE BILL_SECONDARY_CERT TO FILE = 'C:certificatesBILL_SECONDARY_CERT.cer' GO
-- then copy certificate to other two machines
/* -------- 3. ENABLE OUTBOUND CONNECTIONS ON THE WINTESS -------- */
DROP ENDPOINT Mirroring GO DROP CERTIFICATE BILL_WITNESS_CERT GO DROP MASTER KEY GO
CREATE MASTER KEY ENCRYPTION BY PASSWORD = '**************' -- real password used GO
CREATE CERTIFICATE BILL_WITNESS_CERT WITH SUBJECT = 'BILL_WITNESS_CERT for database mirroring', START_DATE = '01/01/2006', EXPIRY_DATE = '01/01/2099' GO
CREATE ENDPOINT Mirroring STATE = STARTED AS TCP ( LISTENER_PORT=7024 , LISTENER_IP = ALL ) FOR DATABASE_MIRRORING ( AUTHENTICATION = CERTIFICATE BILL_WITNESS_CERT , ENCRYPTION = REQUIRED ALGORITHM AES , ROLE = ALL ) GO
BACKUP CERTIFICATE BILL_WITNESS_CERT TO FILE = 'C:certificatesBILL_WITNESS_CERT.cer' GO
-- then copy certificate to other two machines
/* -------- 4. ENABLE INBOUND CONNECTIONS ON THE PRIMARY -------- */
/* enable inbound from the mirror */
DROP CERTIFICATE BILL_SECONDARY_CERT GO DROP USER MIRROR_SECONDARY_USER GO DROP LOGIN MIRROR_SECONDARY_LOGIN GO
CREATE LOGIN MIRROR_SECONDARY_LOGIN WITH PASSWORD = '****************' -- real password used GO
CREATE USER MIRROR_SECONDARY_USER FOR LOGIN MIRROR_SECONDARY_LOGIN GO
CREATE CERTIFICATE BILL_SECONDARY_CERT AUTHORIZATION MIRROR_SECONDARY_USER FROM FILE = 'c:certificatesBILL_SECONDARY_CERT.cer' GO
GRANT CONNECT ON ENDPOINT::Mirroring TO MIRROR_SECONDARY_LOGIN GO
/* enable inbound from the witness */
DROP CERTIFICATE BILL_WITNESS_CERT GO DROP USER MIRROR_WITNESS_USER GO DROP LOGIN MIRROR_WITNESS_LOGIN GO
CREATE LOGIN MIRROR_WITNESS_LOGIN WITH PASSWORD = '****************' -- real password used GO
CREATE USER MIRROR_WITNESS_USER FOR LOGIN MIRROR_WITNESS_LOGIN GO
CREATE CERTIFICATE BILL_WITNESS_CERT AUTHORIZATION MIRROR_WITNESS_USER FROM FILE = 'c:certificatesBILL_WITNESS_CERT.cer' GO
GRANT CONNECT ON ENDPOINT::Mirroring TO MIRROR_WITNESS_LOGIN GO
/* -------- 5. ENABLE INBOUND CONNECTIONS ON THE MIRROR -------- */
/* enable inbound from the primary */
DROP CERTIFICATE BILL_PRIMARY_CERT GO DROP USER MIRROR_PRIMARY_USER GO DROP LOGIN MIRROR_PRIMARY_LOGIN GO
CREATE LOGIN MIRROR_PRIMARY_LOGIN WITH PASSWORD = '****************' -- real password used GO
CREATE USER MIRROR_PRIMARY_USER FOR LOGIN MIRROR_PRIMARY_LOGIN GO
CREATE CERTIFICATE BILL_PRIMARY_CERT AUTHORIZATION MIRROR_PRIMARY_USER FROM FILE = 'c:certificatesBILL_PRIMARY_CERT.cer' GO
GRANT CONNECT ON ENDPOINT::Mirroring TO MIRROR_PRIMARY_LOGIN GO
/* enable inbound from the witness */
DROP CERTIFICATE BILL_WITNESS_CERT GO DROP USER MIRROR_WITNESS_USER GO DROP LOGIN MIRROR_WITNESS_LOGIN GO
CREATE LOGIN MIRROR_WITNESS_LOGIN WITH PASSWORD = '****************' -- real password used GO
CREATE USER MIRROR_WITNESS_USER FOR LOGIN MIRROR_WITNESS_LOGIN GO
CREATE CERTIFICATE BILL_WITNESS_CERT AUTHORIZATION MIRROR_WITNESS_USER FROM FILE = 'c:certificatesBILL_WITNESS_CERT.cer' GO
GRANT CONNECT ON ENDPOINT::Mirroring TO MIRROR_WITNESS_LOGIN GO
/* -------- 6. ENABLE INBOUND CONNECTIONS ON THE WITNESS -------- */
/* enable inbound from the mirror */
DROP CERTIFICATE BILL_SECONDARY_CERT GO DROP USER MIRROR_SECONDARY_USER GO DROP LOGIN MIRROR_SECONDARY_LOGIN GO
CREATE LOGIN MIRROR_SECONDARY_LOGIN WITH PASSWORD = '****************' -- real password used GO
CREATE USER MIRROR_SECONDARY_USER FOR LOGIN MIRROR_SECONDARY_LOGIN GO
CREATE CERTIFICATE BILL_SECONDARY_CERT AUTHORIZATION MIRROR_SECONDARY_USER FROM FILE = 'c:certificatesBILL_SECONDARY_CERT.cer' GO
GRANT CONNECT ON ENDPOINT::Mirroring TO MIRROR_SECONDARY_LOGIN GO
/* enable inbound from the primary */
DROP CERTIFICATE BILL_PRIMARY_CERT GO DROP USER MIRROR_PRIMARY_USER GO DROP LOGIN MIRROR_PRIMARY_LOGIN GO
CREATE LOGIN MIRROR_PRIMARY_LOGIN WITH PASSWORD = '****************' -- real password used GO
CREATE USER MIRROR_PRIMARY_USER FOR LOGIN MIRROR_PRIMARY_LOGIN GO
CREATE CERTIFICATE BILL_PRIMARY_CERT AUTHORIZATION MIRROR_PRIMARY_USER FROM FILE = 'c:certificatesBILL_PRIMARY_CERT.cer' GO
GRANT CONNECT ON ENDPOINT::Mirroring TO MIRROR_PRIMARY_LOGIN GO
/* -------- 7. SET MIRROR'S PARTNER TO THE PRIMARY SERVER -------- */
ALTER DATABASE failover_test SET PARTNER OFF GO
ALTER DATABASE failover_test SET PARTNER = 'TCP://10.152.58.242:7024'; GO
/* -------- 8. SET PRIMARY'S PARTNER TO THE MIRROR SERVER -------- */
ALTER DATABASE failover_test SET PARTNER OFF GO
ALTER DATABASE failover_test SET PARTNER = 'TCP://10.152.58.243:7024'; GO
/* Response: Msg 1418, Level 16, State 1, Line 1 The server network address "TCP://10.152.58.243:7024" can not be reached or does not exist. Check the network address name and reissue the command. */
I am trying to do mirroring using SQL Server Ent. 2005 SP1 on two machines. I was able to create end points on both the machines at the port no.s 5091 and 5092 respectively. I have all the security setting settings for both the users. I am getting error no. 1418 while starting mirroring sessions. Can anybody tell me how to troubleshoot this error?
I am trying to mirror the databse with a witness server.
I have sql server 2005 with SP1 or both my mirror and principle and sql express on my witness.
The problem is when I click start mirroring, I get the following error
The server network address"TCP://serveraddress:7026" can not be reached or does not exist. Check the network address name and that the ports for the local and remote epoints are operational.
(Microsoft SQL server, error:1418)
I have pinged the address it works fine . The telnet comes up with a blank screen.
When I look at the the server log file viewer, I get the following message
An error occured while receiving data: 10054 (An existing connection was forcibly closed by the remote host)
Can I know is it possible that if the database servers' collation in both principal and mirror server might unable to get the mirroring? Because one of database collation is Latin1_General_CI_AS while another server (mirror) is SQL_Latin1_General_CP1_CI_AS. I did several type of troubleshooting but still unable to solve the Error 1418. All the ports are stated as started, able to use telnet to connect to the server's port but still unable to get a connection for the database mirroring. I do really need help on it. Thx for the assistance and kindness.
Hi everyone, I am a newbie on setting up database mirroring and right now I am facing the connection problem during mirroring which is Error 1418 which kinda common problem. I just view through all the threads regarding this problems and BOL also. However, I just based on all the guide to setting it up and the result are still the same.
I did tried on both instance names in my server for mirroring and displayed the same results as well. When I type this t-sql on mirror server :
ALTER DATABASE AdventureWorks SET PARTNER = 'TCP://TSUYOSHI:5022' -- which is the principal server
It shows connection ok to me. However, when I type this t-sql on the principal server :
ALTER DATABASE AdventureWorks SET PARTNER = 'TCP://HAN:5023' -- which is the Mirror server
It shows connection ok to me. However, when I type this t-sql on the principal server :
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://HAN:5023" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
I just wondering that why mirror can get a connection to principal but principal can't? Is that any extra configuration especially security settings that needed to be set within the database (MS sql server 2005) ?
I hope I am able to get any assistance from anyone at here and will appreciate on it. Thanx. Anyway, sorry for the inconvenience
I'm new to DB Mirroring, and I am trying to get it going in a test enviroment between two SQL 2005 Dev Servers. I have followed documentation that I have found but cannot get past a 1418 error when establishing a connection between the servers initially. Does anyone know of any good step by step guides that I could look at, in case I have missed something stupid.
II use the mirroring wizard to config all these three servers(windows authorization is used), the error logs in primary server and mirror server are showed as below a) On primary server: Error: 1474, Severity: 16, State: 1 Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://mymirror.mydomain:5022' b) On mirror server: Database Mirroring login attempt by user 'NT AUTHORITYANONYMOUS LOGON.' failed with error: 'Connection handshake failed. The login 'NT AUTHORITYANONYMOUS LOGON' does not have CONNECT permission on the endpoint. State 84.'.
It states I do NOT have permission on this endpoint, but actually, I grant the permission to the endpoint on both primary and mirror server using command GRANT CONNECT ON ENDPOINT::Mirroring TO [mydomainmyuser]; Also, I followed the article http://msdn2.microsoft.com/en-us/library/ms189127.aspx ,no firewall issue, the endpoint is created and started by checking sys.database_mirroring_endpoints Hope someone can help me resolve this issue... Thank you very much..
I need help. The security principal is the correct DomainUser, but the error message says I am not authenticated. So here is my error Message: Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Me.User.Identity.Name=CompanyDomainRyan; System.Security.Principal.WindowsIdentity.GetCurrent=CompanyDomainRyan; HttpContext.Current.User.Identity.Name=CompanyRyan Generated by: Dim secPrinc As System.Security.Principal.WindowsIdentity = System.Security.Principal.WindowsIdentity.GetCurrent Me.lblError.Text = ex.Message & vbCrLf & vbCrLf & "Me.User.Identity.Name=" & Me.User.Identity.Name & "; System.Security.Principal.WindowsIdentity.GetCurrent=" & secPrinc.Name & "; HttpContext.Current.User.Identity.Name=" & HttpContext.Current.User.Identity.Name Here is the Connection String: Private ConnString As String = "Server=10.144.162.111;Database=DNS;Trusted_Connection=True"
IIS has 4 websites hosted on it. The parent level allows anonymous with windows auth off, but the website level has anonymous off with widnows auth and digest. In IIS, is there a problem with having the parent level anonymous and website level windows auth?
Hi, 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()
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:
After upgrading a SQL 7.0 WINNT 4.0 SP5 box to Windows 2000 SP1, SQL 2000 configuration I am getting the following error when some users try to connect to the server using Enterprise Manager;
"A connection could not be established to 'SERVERNAME'. Reason: Login failed for user 'NT AUTHORITYANONYMOUS LOGON'"
After doing some troubleshooting, I have found that this only occurs when I have the services started with a domain service account (this account is part of the domain admin global group and is a System Administrator in SQL as well) and it does not occur when the services are started with the System Account. Additionally, it also appears that this only occurs for some users and not all. However, these same users that are having problems on this server, can connect to other Database Servers using the "same" configuration.
Has anyone seen this. I have searched TechNet and found nothing that applies directly to this error. Any help that could be provided would be greatly appreciated.
I read a lot of artical but didn;t find a solutio to this problem.
I have Windows 2003 SP1 install Reporting services 2005
I have other Windows 2003 SP1 server with SQL 2005 database.
I set kerberos delegetion control on the server in the AD
I also run the command
cscript adsutil.vbs set w3svc/1/root/NTAuthenticationProviders "Negotiate,NTLM"
on reporting services server but still getting this error message.
Any help ????
w3wp!processing!7!8/30/2006-00:00:01:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'MyDB'., ; Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'MyDB'. ---> System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.
i tried to set up mirroring having only principal and mirror. mirroring endpoints were easily created for both servers. when i try to add the partner name it responds with Msg 1418, Level 16, State 1, Line 1The server network address "TCP://machine1.domain.com:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. On the log of machine1 i see, Database Mirroring login attempt by user 'NT AUTHORITYANONYMOUS LOGON.' failed with error: 'Connection handshake failed. The login 'NT AUTHORITYANONYMOUS LOGON' does not have CONNECT permission on the endpoint. State 84.'.
i am a sysadmin on both SQL Servers and have connect permission on both end points. Both the endpoints are in started state and listening to all IP's Both services are as 'Local System' As per what was mentioned in the above post to add a 'domain/machine$' user did not help. Tried using setspn.exe to add a new SPN MSSQLsvc/<HOST>:<MIRRORINGPORT> did not work. an ERROR comes 'not enough privileges' setup shows the following SPN only on both HOST/Machine name HOST/Machine name.Domin.com MSSQLSvc/Machine name.Domin.com:1433 SMTPSVC/Machine name SMTPSVC/machine name.Domain.com
I have set up 3 servers - Primary, Mirror and Witness. When I run the database mirroring wizard all my endpoints are configured, but when i start the mirroring service i get a 1418 error - in the logs in says -
Database Mirroring login attempt by user 'NT AUTHORITYANONYMOUS LOGON.' failed with error: 'Connection handshake failed. The login 'NT AUTHORITYANONYMOUS LOGON' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 10.20.1.5]
I have looked through the BOL and can't find anything helpful. - I'm pretty new to SQL server, so any help is very much appreciated!
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.
I 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'.
I have a stored proc that attempts to execute xp_cmdshell using a login other than 'sa'. The permissions have been given to the login to execute xp_cmdshell and the stored procedure executes perfectly within the query analyzer in EM. However, when attempting to execute the same stored proc in ISQL_W under a login with permissions for everything as dbo (other than Master) I get error 1326 for LogonUser on line 359. This is with the "xp_cmdshell - Use SQLExecutiveCmdExec Account for Non SAs" disabled (as described as a "workaround" on the technet). Microsoft acknowledged this as being a 'bug' to 'fix' and put a 'fix' in Service Pack 5a. The server that is experiencing this problem is running service pack 5. Is there any difference between the service packs and if so, will installing service pack 5a help me? And if not, what can be done to alleviate this problem?
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.
I am trying to create a linked server between 2 SQL Server 2005 boxes. When I create the linked server I specify a login for the connection. The strange part is that I get the following error when it goes to test the connection:
The test connection to the linked server failed Login failed for user 'Domainuser'. (Microsoft SQL Server, Error: 18456)
I can use the SQL mangement studio to conenct to the database using this same login. The login has all the server roles assigned to it also.
Can anyone shed some light as to what may be the problem?
I have created a site using a login through the Asp.net Admin Website Tool. Through numerous tries of trying to get this to work, I am now receiving the following error "Login failed for user 'app1_lakeshore'." Can anyone help? Here is my werbconfig file: <?xml version="1.0"?> <!-- 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 WindowsMicrosoft.NetFrameworkv2.xConfig --> <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> <appSettings> <add key="/LMCIntranet" /> </appSettings> <connectionStrings> <remove name="LocalSqlServer"/> <add name="LocalSqlServer" connectionString="Data Source=sqldev2.aurora.org;Initial Catalog=Lakeshore;Persist Security Info=True;User ID=app1_lakeshore" 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. -->
<authentication mode="Forms" /> <customErrors mode="Off"/> <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. --> <!-- 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>
