While I was migrating my database server from SQL 2000 to SQL Server 2005 I came across this error as the production and development environment were not quite identical.
Well the first thing to note in this error is non descriptive, preventing information disclosure to unauthenticated clients.
To determine the true reason for the failure, the administrator can look in the server’s error log where a corresponding entry will be written. An example of an entry is:
2006-02-27 00:02:00.34 Logon Error: 18456, Severity: 14, State: 8.
2006-02-27 00:02:00.34 Logon Login failed for user ‘<user name>’. [CLIENT: <ip address>]
A great article with the complete description of this error and states is written by Il-Sung Lee here: http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Happy working with your linked servers.
Helpfull blog.
I have a problem with sql server 2005. I have created a web setup project using custom action to create database at installation time. Every thing is ok. It creates prerequisites (.net farmework 2.0, sqlserver 2005 express, etc.) and database successfully during installation. I have used the connection string
connectionString=”Data Source=.\SQLEXPRESS;Initial Catalog=TrainTrack;Integrated Security=true;” in my custom action which executes database script successfully and install web application as well.
But when i execute my application login page and supplies Login Id and Password, It did not connect to sql server on other machine. It works fine on my development machine fine also.
I check my application connection string in ‘Inetpub\wwwroot\Application\web.config, which is also the same as custom action connection string.
I do not understand, actually what’s problem is? Can I need to use sql server in mixed mode?
Any one please help me.
Thanks