SQL 2012 :: Test Connection Failed Because Of Error In Initializing Provider
May 29, 2015
I am creating my first SSIS package, simple, I read a file, a computation and then write it to an excel.
I am getting the message: "Test connection failed because of an error in initializing provider." The database is NOT remote. My computer is slow though. after about 10 or 15 seconds after clicking the button to test my connection, I get the message and much more. The message asks me if the instance name is correct. I don't know what this would be. This message is on the first task, reading the file (finding the file).
The last sentence of the long message is: "Named pipes provider: Could not open a connection to SQL Server (2).
My question is: Why am I getting this message and what do I need to do to resolve this problem?
Have 6 SQL Server 2012  failover clusters  environments on Windows 2012 R2 standard edition.Have intermittent connectivity issues when using Windows Authentication, with the error "test connection failed because of an error in initializing provider. login timeout expired" . Am checking by using a UDL file and have tried the below.
1) Have made port changes to use static 1433 port. 2) Have enabled shared memory and using Named Pipes and TCP/IP by using cliconfig. 3) Have turned off firewall. 4) Loopback is disabled 5) SQL Browser is running, have changed 'Built in Account setting'  from 'Local Service' to 'Network Service'. but with no effect.
Still I am getting intermittent connectivity issues.
I am using windows 2003 server and i have installed SSAS 2005 and configured http request for AS 2005 with this below url : http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx. I had tried all the possiblities given in this url. But i am getting like "Test connection failed because of error initializing provider. The HTTP Server returned the following error : Not found" when i create udl file. Moreover i have installed MSOLAP 3.0 and OLAP 9.0 provider and MSXML 6.0 Parser.
I have seen several posts on the subject, and have tried various configs. At this point, I am simply trying to connect to SQL Express, that's all.
I have an app. in MS Access that uses SQL Express as a back-end database (this is the simple desktop version of our software). I don't remember having so many issues with just connecting to a small db engine on a single computer..! Just to get it off my chest, there was a post about this subject where someone listed more than 15 items to check... If anyone at Microsoft is reading... connections should not require a 15-item check-list.. People running sql express are not creating a sophisticated database system, probably running it because, they want a free, easy solution, and do not have an IT person, nor are they intersted in reading any 1 of the 15 items... Just trying to connect to the instance of the database that runs on the same computer.... that should not require more than possibly 3 different settings.
My objective at this point, is simply to connect! Nothing else.
My environment settings are:
OS: Win XP Professional MS Access(2003) and SQL Express both installed on the same computer All connection attempts are on the same computer SQL Express is installed in mixed mode SQL Browser running, Network DDE running (if needed) All Network protocols are enabled (tried disabling and enabling each 1 at a time as well) All Client protocols are enabled I tried setting network library to "dbmssocn", and left blank for default (uses namedpipes) I tried using host name, localhost, and IP address for servername (with the SQLEXPRESS of course) Also tried leaving it blank I tried with Integrated security, also tried with the user "sa" and "test" user (both enabled and capable of logging in and accessing the database) I tested the connection from SQL Express Manager, successfully connected in all modes (secure, and with SQL users) to make sure there are no issues with the users or security. Tried turning the SQL browser off (this should not be needed in local mode) Tried using an alias Tried using attach database as a filename And, the firewall is turned off.
Always getting the error "....connection failed because of an error in initializing provider" (whether using namedpipes, or TCP, or shared mem)
Both SQL Express and Access are installed on the computer, that should include the providers...
Please let me know if there is anything left for checking and/or trying... Appreciate your help...
I'm having a problem sending the query set as an email text attachment. Test transmissions from Database mail working fine.
Send simple messages with the sp_send_dbmail sproc works fine as well.
It is only when I try and send a query result that things blow up. The query itself is working fine also, so I'm now down to think there is some esoteric problem with the sproc itself.
Surface config features have database mail on, and SQL Mail off.
Msg 14661, Level 16, State 1, Procedure sp_send_dbmail, Line 476 Query execution failed: Error initializing COM Msg 0, Level 11, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded.
Investigating the sproc itself shows...
Line 476 in the sproc is the beginning of a 'trap' --Raise an error it the query execution fails -- This will only be the case when @append_query_error is set to 0 (false) IF( (@RetErrorMsg IS NOT NULL) AND (@exclude_query_output=0) ) BEGIN RAISERROR(14661, -1, -1, @RetErrorMsg) END
RETURN (@rc) this is the last section of code in the sproc
We have 4 client machine and 1 server machine, that server have all the sql server 2005 database€™s.
A project developed from client1 with Asp.net 2005 now I need to access that project from client2 so I type http://My Ip address/Folder Name/home.aspx in my browser here when the sql connection is open(SqlConnection.Opn()) then I meet this problem
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)
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. I am getting this error and using this connection string Data Source=192.168.0.100;Network Library=DBMSSOCN;Initial Catalog=ENet;User ID=eonline;Password=eonline; What can be solution for this.
Hi, I am working on VS 2005 and using SQL 2005 Express and i am processing excel files and inserting records in data base as i processing starts and almost after processing 600 i got this error provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server. how can i solve that thanx
We just changed the dev environment to sqlagent. From then we were unable to see the reports on the report server because:
An error has occurred during report processing.
Cannot create a connection to data source 'IHRSDataSource'.
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)
this error is cropping up.
To Resolve this issue, we checked the Surface Area Configuration and also checked the Reporting Service Configuration . There seem to be no problem and everything looks ok.
We have 4 client machine and 1 server machine, that server have all the sql server 2005 database€™s.
A project developed from client1 with Asp.net 2005 now I need to access that project from client2 so I type http://My Ip address/Folder Name/home.aspx in my browser here when the sql connection is open(SqlConnection.Opn()) then I meet this problem
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)
I am new to dotnet. I tried connecting to the database MS SQL Server 2000. I gave the code like, the one below, in form load event,
SqlDataReader dr = null;
SqlConnection myConnection = new SqlConnection("Data Source=IP;Initial Catalog=name;User Id=uid;Password=pwd;");
myConnection.Open();
myConnection.Close();
But I could not connect. The error message highlights the line myConnection.Open() and displays the error
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)
It tries connecting to SQL Server 2005. There is no SQL Server 2005 in that system. There is only SQL Server 2000.
I have the aspx code in my local system and the database in another machine.
Could Someone please help me out in solving this problem.
I realised this has been done to death, and so much information out there but I am still in a quandry.
I have had to rebuild my computer.
This is what I did
XP machine using SQL Server 2005 Standard Edition using Windows Authentication NZ6(MSSQLSERVER)
straight default install all the way
unfortunately when ready to run reports from my instance(computer) I received the error as in provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
thought I had it all okayed but obviously something not right
so ended up unistalling then - did the following:
Load SQL Server from disc1 and start install failed on alter Counter Registry key error fixed this from KB article (known error that can happen) restarted Went to Windows Update check IIS is installed - tick is on - IIS - admin tools - make sure asp2 is associated - yes ok Then back to install sql server - there is no instance set up yet Disk 2 and setup .exe
All ok on Reporting Services, Analysis etc.
But once again all seems fine but still getting the error:
connection is all fine in Management Studio - eg I can see tables etc connection is all fine in Business Intelligence - eg I can preview my reports I then can deploy up to - NZ6 open NZ6 eports report is there fine - but just errors
some simple little tick that I have not done!!
I seem to have checked and rechecked everything and obviously doing another re-install does not seem a logical step from here. I will continue to check but if someone jump in and advise please would be great.
I am creating a web site using Visual Studio 2008 & trying to connect to database on SQL Server 2000. My test connection is successful but while debugging the page I am getting this error : " provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server "
Solutions recommended for this were start running the SQL browser instance and enable Namespipes in Sqlserver configuration manager.Did both.. but nothing worked.
I made a Web page, and it works perfect on my local machine, everything is OK, until I uloaded page to the server, it reports this error:
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)
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: 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)
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): 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)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735091 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 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) +1770 System.Web.UI.WebControls.Repeater.GetData() +50 System.Web.UI.WebControls.Repeater.CreateControlHierarchy(Boolean useDataSource) +232 System.Web.UI.WebControls.Repeater.OnDataBinding(EventArgs e) +53 System.Web.UI.WebControls.Repeater.DataBind() +72 System.Web.UI.WebControls.Repeater.EnsureDataBound() +55 System.Web.UI.WebControls.Repeater.OnPreRender(EventArgs e) +12 System.Web.UI.Control.PreRenderRecursiveInternal() +77 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360
I've just posted mywebsite andthis error keep being trhrown as soon as I access the DB I dont understand what is going on and if I dont get it working bu today will delivery date will expire and I will get in trouble... So anyone knows what is going on It says the following: 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) Here is my con string : <add name="ASPNETDBConnectionString" connectionString="Data Source=p3swhsql-v09.shr.secureserver.net;Initial Catalog=myCatalog;User ID=MyID;Password='Mypassword"/> Thanks a lot
i'm going nuts with SQL server notification thing. I have gone throigh this artical which tells how to set user http://www.codeproject.com/KB/database/SqlDependencyPermissions.aspx. This article show how to create new user and setup for sql server notification.But In my case user was alredy existing in database. which is very common senario in most cases. So i did following( check the SQL script below) but then i get this error "A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)" this my sql script use [master]Go -- Ensuring that Service Broker is enabled ALTER DATABASE [DatabaseName] SET ENABLE_BROKERGO -- Switching to our databaseuse [DatabaseName]GO CREATE SCHEMA schemaname AUTHORIZATION usernameGO ALTER USER username WITH DEFAULT_SCHEMA = schemaname GO /* * Creating two new roles. We're not going to set the necessary permissions * on the user-accounts, but we're going to set them on these two new roles. * At the end of this script, we're simply going to make our two users * members of these roles. */EXEC sp_addrole 'sql_dependency_subscriber' EXEC sp_addrole 'sql_dependency_starter' -- Permissions needed for [sql_dependency_starter]GRANT CREATE PROCEDURE to [sql_dependency_starter] GRANT CREATE QUEUE to [sql_dependency_starter]GRANT CREATE SERVICE to [sql_dependency_starter]GRANT REFERENCES on CONTRACT::[http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification] to [sql_dependency_starter] GRANT VIEW DEFINITION TO [sql_dependency_starter] -- Permissions needed for [sql_dependency_subscriber] GRANT SELECT to [sql_dependency_subscriber] GRANT SUBSCRIBE QUERY NOTIFICATIONS TO [sql_dependency_subscriber] GRANT RECEIVE ON QueryNotificationErrorsQueue TO [sql_dependency_subscriber] GRANT REFERENCES on CONTRACT::[http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification] to [sql_dependency_subscriber] -- Making sure that my users are member of the correct role.EXEC sp_addrolemember 'sql_dependency_starter', 'username'EXEC sp_addrolemember 'sql_dependency_subscriber', 'username'
Facts:1. I am using my account on Godaddy trying to connect to my sql server db.2. I can get into my db using user id and password.3. Godaddy's help file shows this for a connection string: connectstr = "Driver={SQL Server};SERVER=" & db_server & ";DATABASE=" &db_name & ";UID=" & db_username & ";PWD=" & db_userpassword4. My connection string: "Server=whsql-v09.prod.mesa1.secureserver.net;uid=dbasolutions;pwd=***;database=DB_87972;" & _ "Trusted_Connection=False providerName=System.Data.SqlClient"{password **** out}5. Get error message 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) I tried to email Godaddy's help desk with this information. There first response: We do not allow remote connections to our sql server database.There second response was to read the help file!Does anybody have any suggestions? Thanks in advance,bswanson
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) (Microsoft SQL Server, Error: 53)
We experience the 40 error when our Asp.net code runs under IIS and uses named pipes to a sql server 2005 named instance.
We've tried all suggestions found on blogs and KB articles such as making sure the named pipes protocol is enabled, making sure the Browser service is started, making sure Allow Remote Connections is enabled, making sure we're not using Asp.Net 2.0 membership providers, and the list goes on and on.
We boiled it down to a simple test scenario. We open a SqlConnection to the sql 2005 box in the code with the intention of binding a datareader to a gridview, but it never gets that far because the connection.Open() fails.
If we run this test application as a virtual directory in IIS and Asp.Net 2.0, the connection.Open() fails.
If we run this test application from Visual Studio .Net using Cassini (PWS), the connection.Open() succeeds and binds to the gridview.
What could be causing the connection to fail under IIS but succeed under Cassini? We've tried setting IIS to run as a domain user and with digest authentication enabled. That made no difference.
I try to connect to a SQL Server 2005 Express Edition via IP address. But anytime the application tries to connect to the database here is th error message I receive:
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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
I have enabled the TCP/IP under SQL Server, Under SQL Server Configuration Area, I have chosen the option Local and remote connection: TCP/IP only I have verified that my firewall allows SQL remote and a Local Connection.
Now I don't know where to look or what I have to fix to continue. I will really appreciate if somebody can help me.
Hi I always get good reply from u all, thank you, I have copied my asp.net website from one server to another. they administrator made necessary modification on IIS manager . and able to see the website on browser. but now i can't loging to system using old password. I tryed to create new password then also it gives error 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) Here I have used asp.net login control and membership class. Do I need to make nay changes in code. I have already modified server name in connection string in web config file. any one can say what is the problem and how to solve this. thanks Pat
Hi , I am struck with one issue.Plz help me out if you have any solution for this one. Details Front End - Visual Studio 2005 Back End -SQL Server 2000 (Remote database) Error i am getting is {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) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at dbcAccess.clsSQL.GetConnect() in C:Documents and SettingskerlsgMy DocumentsVisual Studio 2005ProjectsdbcAccessdbcAccessclsSQL.cs:line 296}
{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)
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
trying to connect to sql server 2005 over the internet. (its a third paty hosting company i'm using)
so i have to connect via tcp/ip using sql server authentication.
my laptop is running vista.
the version of sql server 2005 on my laptopis developer edition with service pack 2.
it worked fine from windows xp and the connection details are valid as it runa fine from .net on the hosting website.
i have added sql serer managemnt studio to the exceptions list in the firewall.
ihave made sure tcpip is enabled in the sql server connection management console.
i have also enabled it in the cliconfg tool
firewall on/off seems to make no difference.
its almost enough to make you turn to oracle and thats saying something considering how long i've been in the microsoft camp...
the error returned is: Login failed for user 'SQL2005_152092_garethbowen'. (.Net SqlClient Data Provider)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
------------------------------ Server Name: 'xxxx',1433 Error Number: 18456 Severity: 14 State: 1 Line Number: 65536
Hi all, I am new in asp.net. In my web.config file, I wrote the connection strings as below and then I got the above error. I already changed SQL server Authentication mode to "SQL server and Windows". Any idea? Thanks in advance. <connectionStrings> <remove name="LocalSqlServer" /> <add name="LocalSqlServer" connectionString="Data Source=xxx;Initial Catalog=mydb;User ID=test;Password=test;Persist Security Info=False;" providerName="System.Data.SqlClient" /> </connectionStrings>
Hello I am receiving the dreaded mail error listed above. I can send out a test E-mail from Enterprise Manager to operators, but I cannot run this Transact query:
I have a web application developed in VS.NET 2005 [using C# as code behind]; and it uses SQL Server 2000 Enterprise edition as backend. The application runs fine, though it gives an error on IRREGULAR intervals on SQL data requests. Error Details: 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)
My problem is this: 1) Why does it show an error of SQL 2005, while I use SQL 2000. SQL 2005 is not even installed on the server, though VS.NET 2005 is installed. 2) The error comes only at irregular intervals. Users are able to login properly otherwise. 3) Application starts working again if we do either of the following: (a) Restart IIS (b) Restart application pool (c) Restart server. 4) Named pipes and TCP/IP are added to the "Network Configuration" of the SQL server 2000. 5) Error does not come on any specific page; or any specific code; or at any specific time. 6) We do not have any background service or any other activity happening on the server; and the server hosts only this application, within a single virtual root.
Any thoughts on why is this happening, and how to resolve this?
