SQL Protocols : Troubleshoot Connectivity Iss...

来源：百度文库编辑：神马文学网时间：2024/07/03 10:10:45

Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Please visithttp://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx for troubleshooting connection problems when SNAC(SQL Native Client) connect to SQL Server 2005.
Part II – Connection Fail when MDAC connects to SQL Server 2005
Use osql.exe to simulate the connection string in your application and quick troubleshoot if your application uses ODBC provider and use Query Analyzer (isqlw.exe) in SQL Server 2000 for OLEDB provider. Usually, they are located under %SYSTEMDRIVE%\Program Files\Microsoft SQL Server\80\tools\binn.
How to distinguish your application is using MDAC client or SNAC client:
1) From connection string, especially follow blue part:
- MDAC ODBC -
DRIVER= {SQL Server}; SERVER=xx; Trusted_connection=yes; Connect Timeout=30
- MDAC OLEDB –
Provider= SQLOLEDB; Data Source=xx; Integrated Security=SSPI;Connect Timeout=30
- SNAC ODBC –
DRIVER= {SQL Native Client}; SERVER=xx; Trusted_connection=yes; Connect Timeout=30
- SNAC OLEDB –
Provider=SQLNCLI; Data Source=xx; Integrated Security=SSPI; Connect Timeout=30
2) From error message:
Osql /Sxxx /E ß “xxx” is an unknown server
Result of using MDAC client:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
Or
[DBNETLIB]Specified SQL server not found.
Result of using SNAC client:
Named Pipes Provider: Could not open a connection to SQL Server [53]
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.
Basic connection string: osql(sqlcmd) /S[prefix] /E
osql(sqlcmd) /S[prefix]\ /E
Before start troubleshooting, another important thing is to identify MDAC version on your client box.
Step 1: Browse to the following Microsoft Web Site to know about MDAC release version.
http://support.microsoft.com/default.aspx?scid=kb;en-us;231943
Step 2: Browse to the following Microsoft Web Site to download the tool that help you check the MDAC version on your client box.
http://support.microsoft.com/default.aspx?scid=kb;en-us;301202
However, MDAC does not provide so many visible error messages like SNAC, which makes it more difficult to troubleshoot connection problems when using MDAC connect against Yukon. Most likely, any of the follow three errors you would see in any case. Therefore, I will give tips for troubleshooting not based on the messages, but, on various Protocols Setting in SQL Server 2005.
Message 1:
[DBNETLIB]SQL Server does not exist or access denied.
Message 2:
[DBNETLIB]Specified SQL server not found.
Message 3:
[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.
Before further troubleshooting, you need to know what is the current protocol setting on the server box, and make sure server is running and sqlbrowser service is running, two ways to check.
1) Go to SSCM( SQL Server Configuration Manager ), click “protocols for ”, you can see the status of each protocol that server support.
2) Look at server ERRORLOG file.
- Key words indicates server shared memory is enabled -
“Server local connection provider is ready to accept connection on [\\.\pipe\SQLLocal\MSSQLSERVER]” or [ \\.\pipe\SQLLocal\]
- Key words indicates server named pipe is enabled -
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$\sql\query ] or [ \\.\pipe\sql\query ]
Note: you may also see these key words even when only shared memory is enabled. To make sure server remote named pipe is enabled, you need to do one more thing, test connection through named pipe. “osql /S\\\pipe\sql\query /E” or
“osql /S\\\pipe\MSSQL$\sql\query /E” only when the connection succeeds that means server is listening on name pipe.
- Key words indicates server TCP/IP is enabled –
Server is listening on [‘any‘ ] or
[ ].
First one is when enabling server “ListenonAllIPs”, and second one is when server listening on individual IP. To further verify, you can test whether sql server is listening on the exact port using "netstat -ano| findstr ".
Thereby, the following troubleshooting tips would be based on which protocol was enabled. When you came across connection failure, please first identify what is the current protocol configuration on your server box.
Note: only when I explicitly point out named instance, otherwise, all cases apply to both default instance and named instance. And, normally, there are three parts in “Server” or “DataSource” field in the connection string. []\[], in the server part, it could be any of those:
“.” “(local)” “localhost” “127.0.0.1” FQDN(Server Fully Qualified Domain Name)
Assumption: Follow situation are mainly cover MDAC 2.8/2.81/2.82 client connects against Yukon RTM on Windows 2000/Windows 2003/Windwos XP.
Case 1 – Only shared memory was enabled:
Go through follow reason list:
1) You might specify “tcp:” in your connection string, however, TCP was disabled, to resolve this, remove the prefix.
2) You might specify ”np:” in your connection string, plus, specify localhost or FQDN or “127.0.0.1” or in the server part in Server or DataSource field in your connection string, to resolve this, either enable name pipe or specify as Server part.
3) You might specify localhost or FQDN or “127.0.0.1” or , to resolve this specify as Server part.
4) You might specify “lpc:” in your connection string, plus, specify localhost or FQDN or “127.0.0.1” or in the server part in Server or DataSource field in your connection string, to resolve this, specify instead as Server part.
5) You might first, use OLEDB provider; secondly, connect to local default instance through "." or "(local)", to resolve this, replace the server part as .
Case 2 – Shared Memory and TCP/IP was enabled, but Named Pipe was disabled.
Go through follow reason list:
1) You might specify ”np:” in your connection string, plus, specify localhost or FQDN or “127.0.0.1” or in the server part in Server or DataSource field in your connection string, to resolve this, either enable name pipe or specify as Server part.
2) You might specify “lpc:” in your connection string, plus, specify in the server part in Server or DataSource field in your connection string. To resolve this, replace to .
Case 3 - Shared Memory and Named Pipe was enabled, but TCP/IP was disabled.
Go through follow reason list:
1) You might specify “tcp:” in your connection string, however, TCP was disabled, to resolve this, remove the prefix.
2) You might first, use OLEDB provider; secondly, connect to local default instance through "." or "(local)", to resolve this, replace the server part as .
Case 4 – Only Named Pipe was enabled.
Go through follow reason list:
1) You might specify “tcp:” in your connection string, however, TCP was disabled, to resolve this, remove the prefix.
2) You might first, use OLEDB provider; secondly, connect to local default instance through "." or "(local)", to resolve this, replace the server part as .
Case 5 – Only TCP was enabled.
Go through follow reason list:
1) You might specify “np:” prefix in your connection string, Named Pipe was disabled. To resolve this, remove the prefix.
Case 6 – Only Shared Memory was disabled.
Case 7 – All protocols are enabled.
All connection in Case 6 and Case 7 should succeeds unless some special cases.
Special Cases:
Case 1: localhost
Windows 2000 and Windows XP do not recognize “localhost” as a representative of local machine in pipe name. In another word, you can not connect to default instance through explicit pipe\\localhost\pipe\sql\query( eg, you connection string like "Data Source =\\localhost\pipe\sql\query; Integrated Security = SSPI" or "osql /S\\localhost\pipe\sql\query /E") on Win2k and WinXP when remote name pipe was enabled.
Case 2: Connect to local named instance
If you can not identify cause for connection fail when use MDAC connecting to local named instance, there are two other possible reasons:
1) Your application was running under an account that has no permission to the registry entry where MDAC client reads (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\\MSSQLServer).
2) SQL Browser service was not enabled or running.
Case 3: Remote Connection
Whenever remote connection fail and you saw any of above error messages, you should first check whether remote named pipe or tcp was enabled or sqlbrowser service was enabled and running. Please see “SQL Server 2005 Connectivity Issue TroubleShoot –Part I” for more detail info.
Case 4: Blank
If you use ODBC driver and leave the server part as blank when connecting to local default instance, connection would fail. Please explicitly specify server name whenever make connection. The error message when connection fail usually is “[Microsoft][ODBC SQL Server Driver]Neither DSN nor SERVER keyword supplied ”.
Case 5: "." or "(local)"
To emphasize this, if you use MDAC OLEDB, you can not connect to local default instance through "." or "(local)" whenever TCP was disabled on the Server. To resolve this, please use instead.
Summary:
When you discover any connection fail through MDAC client to SQL Server 2005, please first make sure server is accessible and SQL instance is running; secondly, identify which protocol is enabled; finally, go through above scenarios to track the root cause.
Ming Lu SQL Server Protocols
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights
Published Saturday, October 29, 2005 11:37 PM bySQL Protocols

Comment Notification
Send me email alerts for new comments to this post
Subscribe to this post‘s comments usingRSS
Comments
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I am using MDAC OLEDB connection where shared memory is the only enabled protocol.
I am just wondering why "(local)" and "localhost" do not work but does? Is there any more information on this? This seems very counter intuitive to me. Is this a problem in Windows 2000 and XP?
Monday, November 28, 2005 11:01 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Eric
MDAC OLEDB uses TCP protocol when you connect through (local) and localhost and in your case, your TCP/IP was disabled, you can verify this by enabling TCP/IP. However, if you specify , it connects through shared memory.
Appreciate your comments.
Monday, November 28, 2005 11:32 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I am trying to connect to a remote SQL Server 2005 Standard edition server with TCP from a Virtual Machine running XP/VS2005. When I try to add a connection in VS, I get the server name in the database server dropdown list but I get the following error when testing the connection:
"An error has occurred while establishing a connection to the server. When connectiong 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, errror:0-A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
On the Sql Server server:
I have the SQLBrowser service running and it is active.
I have the remote connection enabled using TCP/IP only
Connection string I am using from VS2005:
Data Source=W-MODINEDEV;Integrated Security=True;Network Library=dbmssocn
I am at a loss, any help would be appreciated. When I am on the server, making connections works fine, it is just remotely that I have issue. --Allen
Thursday, December 01, 2005 9:57 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Allen:
In my another post:http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
I point out the exact case you faced.
Please search Message 11 in the post and follow the resolution.
This is because connection blocked by firewall. To resolve this, take follow steps:
1)Enable SqlBrowser, see the info in Message 4. Plus, add sqlbrowser.exe into Firewall exception list: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List
2)Add Tcp port to Firewall exception list. (eg, Name-1433:TCP, Value-1433:TCP:*:Enabled:Tcp 1433).
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\GloballyOpenPorts\List
For more detailed operation, seehttp://support.microsoft.com/default.aspx?scid=kb;en-us;287932
If you have further question, please let me know.
Thanks for your comments.
Ming.
Thursday, December 01, 2005 8:42 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Ming:
Thanks for the reply. I would not think this is the problem because I should not be going through the firewall to make a connection to the SQL Server machine, we are both on the same domain and both behind the firewall. Why would I need to do anything with the firewall? Thanks, Allen
Monday, December 05, 2005 8:47 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Allen
Please follow the below step to identify your problem:
1) Make sure SQL Server is listening on the right TCP port. You can check errorlog, and search key words:Server is listening on [‘any‘ ] or
[ ]. Then "netstat -ano |findstr " to see which process is listening on this port.
2)From your client machine, "telnet " see whether succeeds.
3)Please check whether the windows firewall is on your server. Eg, if your server is XP, then Go to Control Panel -> select "Network and Internet Connection" -> "Windows Firewall", please turn off it if it is on and then try your connection again, if works that means your original connection failure is because the windows firewall on your server blocks any out packet if the application was not added into the exceptionlist since you were making remote connection. I believe the *firewall* that you mentioned is not the same as the windows firewall.
Thanks!
Ming.
Wednesday, December 07, 2005 1:11 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
The Ming Dynasty Rules, you the man, thanks much, and yes, I was thinking "real firewall" versus "windows fiewall" and thought you were crazy, but off course it was me that was foolish.
Wednesday, December 07, 2005 3:09 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,
Where I can find part III of this series?
Tuesday, December 20, 2005 12:39 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Here it is
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
Thanks for your comments!
Ming.
Wednesday, December 21, 2005 11:22 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Out of all my forum/net searching on this topic, yours by far is the most indepth and well-presented. Good job!
After going through your steps, my problem hasn‘t gone away. On my development machine, I‘m using SQL Server 2005 and the sqloledb provider via C++. This is my connection string:
string ConnectionString2 = "Provider=‘sqloledb‘;Data Source=‘localhost‘;Initial Catalog=‘master‘;Integrated Security=‘SSPI‘;";
and it works just fine on that machine.
I‘ve installed SQL Server 2005 Express on two separate machines and it fails in the connnection->Open() call with the standard error: "[DBNETLIB][ConnectionOpen(Connect()).]SQL Swerver does not exist or access denied."
I can connect to the sqlcmd just fine. TCP, Shared, NP are all enabled. The browser is started. The OLEDB provider is correctly pointing to MS‘s file. The port (1314) is reporting in the App event log and Netstat as listening.
I tried changing to machine name, but it didn‘t help. I did notice in the TCP/IP properties of the Server config mgr that even though TCPIP was enabled, looking at the specific IP address showed that they were active, but disabled. After enabling port there it still didn‘t help.
Any clues?
Friday, January 27, 2006 3:50 PM byShawn
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
On a hunch, I changed my provider from MDAC to Native Client with the string:
"Provider=‘SQLNCLI‘;Data Source=‘localhost‘;Initial Catalog=‘master‘;Integrated Security=‘SSPI‘;"
This gave me a more helpful error:
"[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]."
I didn‘t even know I was using Named Pipes, I thought it would‘ve been defaulting to TCP/IP. Going back to your other article as reference and stepping through the debugging process for named pipes, I couldn‘t connect with \\.\pipe\sql\query, but I could connect with \\.\pipe\MSSQL$SQLEXPRESS\sql\query.
That seems to have done it, my app works both on the development and test machines.
Thanks for the tips!
Friday, January 27, 2006 4:37 PM byShawn
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Shawn
Glad to hear you solve the problem. Basically, SQLEXPRESS is installed as a named instance and with TCP and Named Pipe are disabled by default.
For local connection: You need to change your connection string to:
Provider=‘SQLNCLI‘;Data Source=localhost\SQLEXPRESS;Initial Catalog=‘master‘;Integrated Security=‘SSPI‘
For remote connection, remember enable tcp or named pipe.
Here is useful info for SqlExpress
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
Thanks for your comments!
Ming.
Friday, January 27, 2006 5:41 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I try to connect to SQL Server 2005 using ADO:
(1)connect to a named instance(mynamedinstance),using SQL Native Client as the driver.
CString strConn =_T("Provider=SQLNCLI;Data Source=mypcname\\mynamedinstance;Initial Catalog=mydb;User Id=myuser;Password=mypw;");
_ConnectionPtr conn("ADODB.Connection");
_bstr_t bstrConn(strConn);
if( FAILED(conn->Open(bstrConn, _T(""), _T(""), 0)) )
{...}
Connect successfully!
(2)connect to the default instance, using SQL Native Client as the driver, but use DSN in the connection string.
CString strConn =_T("Provider=SQLNCLI;DSN=myDSN;Uid=myuser;Pwd=mypw;");
...
...
Connect successfuly!
(3)Conncet to a named instance(mynamedinstance), using SQL Native Client as the driver, using DSN in the connection string.
CString strConn =_T("Provider=SQLNCLI;DSN=myDSN;Uid=myuser;Pwd=mypw;");
...
...
Connect error!!!
Why (3) failed? Please help me.
Monday, February 20, 2006 5:40 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Provider SQLNCLI does not recognize DSN. So, in the second case, the DSN=myDSN is ignored and, possibly, connection successfully connect to local default instance. In the third case, the DSN=myDSN is ignored as well and connection cannot be established for named instance.
So the short answer is “Do not use DSN when using SQLNCLI provider”.
Wednesday, February 22, 2006 8:42 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Ming,
I‘m getting the error message: "SQL Server does not exist or access denied." I‘ve followed the instructions here as closely as possible. I‘m trying to access from a client with MDAC 2.8 SP1 on Windows XP SP2. I checked with netstat -ano on the server, and it‘s listening on the right IP address and right port. I can connect to an SQL 2000 server just fine.
One possibility is that I installed Windows Server 2003 and SQL 2005 on a new machine and then changed the name of the server.
Any advice would be greatly appreciated.
Thanks,
George C
Sunday, March 05, 2006 9:42 PM byGeorgeC
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, George
Were you trying to connect remotely to SQL Server 2005? Is it default or named instance? Is it SQL Express 2005? How do you make connection?
The MDAC error is very general, if you can provide the above info, we can help you identify the problem quickly.
Thanks for your comments!
Ming.
Tuesday, March 07, 2006 2:56 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,
I‘m having a problem with a .NET 2 command-line app which accesses a SQL 2000 cluster.
If I run it on a Windows 2003 Server SP1 box, it runs fine.
If I run it on a Windows 2000 Server SP4 box, it reports that it can‘t access the SQL database despite the fact that I can create a DSN on that same box pointing to the db which runs fine and run the .NET 1.1 version of the same app from that box without a glitch. I‘ve run cliconfg.exe and enabled TCP and named pipes but with no avail.
The connection string looks like this. Server=xx;Integrated Security=SSPI;Initial Catalog=name
Any ideas? Does Win2k work differently for .NEt 2.0 than .NET 1.1 somehow?
Cheers, Dan
Tuesday, March 28, 2006 9:23 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Is the SQL Server named instance or default instance? If it is named instance, you need to enable sql browser service eventthough the client is on the same box of the server. Otherwise, please post the entire exception stack trace of your .Net2.0 app of connection failure.
Tuesday, March 28, 2006 2:09 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
It‘s the name referring to the virtual IP address for a SQL cluster. But its just the default instance on that cluster: CLUSTERDB rather than CLUSTERDB\INSTANCE. That said, do you mean turn on the sqlbrowser on the client or the cluster? Apologies for being dumb, but how do i do either? The Win2k machine has no client tools installed - is part of cliconfg.exe? - and how do ou switch sqlbrowser on for a cluster? - do ou need to switch it on on both machines?
The full error messages I get are as follows - the first is if I try and use named pipes, the second if i use tcp.
-----
Named pipes error message
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 System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
-----
TCP error message
System.Data.SqlClient.SqlException: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject
stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean
encrypt, Boolean trustServerCert, Boolean& marsCapable)
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 System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
Wednesday, March 29, 2006 5:32 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I have a client with 64 bit 2003 server running SQL 2005.
Also has 32 bit XP sp2 client machines that connect fine to the server with OLEDB. When attempting to connect with DMO from the machines with the same credentials and IP, I get
error number: 55555
error source: Microsoft SQL-DMO (ODBC SQLState: 42000)
error description: [Microsoft][ODBC SQL Server Driver][SQL Server]To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).
If I try the same code locally on the server it connects fine.
The client has installed the DMO backwards compatibility patch on both client and server.
I am at wit‘s end. All protocals on the server are enabled. SQL Browser is enabled on the server. Windows firewall is not enabled on the server.
Monday, April 10, 2006 11:41 AM byDave W.
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Dave
This is not connectivity issue, please post your question to SQL DMO/SMO Forum:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=88&SiteID=1
Thanks!
Ming.
Tuesday, April 11, 2006 2:02 AM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Ouyaaaaah!
I solved it! I spent two day by reading many many forums and blogs. Finally I found this stupid error...it must be two backslashes between MachineName and InstanceName in connection string in my application - "\\".
Everything was enabled, every service ran well but symptoms were identical
So if someone has the same little problem.....
Tuesday, April 25, 2006 12:57 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
i just test for adding an exception in firewall. Only add sqlbrowser.exe in exception. it‘s fine. No need to add port 1433 anymore. thank you.
Wednesday, May 31, 2006 3:41 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
try to register your sql server on the active directory.
go to the sql server instance name and then right click go to properties and an active directory tab is there click on add and then ok.
try to connect now.
I hope it connects
Monday, June 19, 2006 5:37 AM byPRANAV GARG
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,
Can you provide your connection string? The error you saw could caused by various reason:
1) Is your Yukon default instance?
2) What protocol enabled in your Yukon instance?
3) How you make connection? "localhost/127.0.0.1//" which one you specified as server?
4) Could you run cliconfg.exe and see what protocol order you specify?
5) Which OS were you running your client APP? WIN2K3?
Thanks!
Ming.
Friday, July 07, 2006 12:49 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,
I can‘t create a DSN using SQL Server to connect to SQL Server 2005, but I can connect successfully using SQL Native Client. My Shared Memory, Named Pipes, & TCP/IP are enabled. My firewall is disabled.
I upgraded SQL Server 2K to 2005 so I have some users who have an DSN using FileMaker SQL Server Driver. I am trying to re-establish that connection but I get:
[ODBC SQL Server Driver] Client unable to establish connection.
[ODBC SQL Server Driver] Unable to load communication module. Driver has not been correct.
I was thinking if I can establish a connection using SQL Server drivers then I can figure out my FileMaker SQL Server Driver issue. The error I‘m getting using SQL Server is:
[TCP/IP Sockets]ConnectionOpen(Invalid Instance())
[TCP/IP Sockets]Invalid connection.
Please help.
Thanks
SU
Friday, July 07, 2006 6:15 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Su
From the error message, it looks like that your connection string is not correct, could you provide it to us? Double check following things:
1) Is your SQL 2k5 a default instance or named instance? if named instance, you need add in your connection string, like \
2) What is the SKU of your SQL 2k5? Express? Were you making local or remote connection? What OS are you using?
Thanks!
Ming.
Friday, July 07, 2006 6:51 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi Ming,
I figured out the SQL Server DSN issue. My "Dynamically determined port" was checked with port number 1433 on "Client Configuration", but my TCP Dynamic Ports on SQL 2K5 was 1157.
Now I still have that Filemaker SQL Server Driver issue. I tried connecting using a named instance "DPMMSSQL\MSSQL" and I‘m getting [Named Pipes]Specifed SQL server not found. When I use the static IP, I get [ODBC SQL Server Driver] Unable to load communication module. Driver has not been correct.
Could it be that Filemaker SQL server Driver does not support SQL 2K5?
My OS is 64 bit Win2K3 server. All clients are using XP Pro. SQL server 2k5 is 64 bit version 9.00.2047.00.
Thank you so much Ming!
Su
Sunday, July 09, 2006 8:15 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, su
Glad to hear you address the issue.
I am not sure whether your SQL2k5 is a named instance? And you connect through" DPMMSSQL\MSSQL", is the "DPMMSSQL" the remote machine name? Is the "MSSQL" the instance name of SQL2K5? Can you provide more specifically about your connection string? Means how you make connection?
Can you telnet to your remote server? eg: if your sql server was listening on tcp port 1157, can you run "telnet 1157" on your client machine?
Can you try "osql /S\ /E" from client machine? what was the error?
What sql protocols enabled on your server?
To identify your problem quickly, could you help to answer following question and provide it to us?
http://blogs.msdn.com/sql_protocols/archive/2006/04/21/581035.aspx
Good Luck!
Ming.
Monday, July 10, 2006 10:26 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi Ming,
I‘ve called the vendor of that ODBC drive and they don‘t support 2K5.
My new question is can I backup a DB from 2K5 and restore it on SQL server 2000?
Thanks
Su
Wednesday, July 12, 2006 11:44 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Su
You can post your question to sql database engine forum, there are a lot of experts who can quickly help you:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1
Good Luck!
Ming.
Thursday, July 13, 2006 11:58 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
hi,
i am having connectivity issues with sql 2000. i have a cgi script that has been accessing this database for production operations and suddenly, it started to return this error
Cannot connect: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation. (SQL-08001)
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (PreLoginHandshake()). (SQL-01000)(DBD: db_login/SQLConnect err=-1)
i have tried everything but restarting the sql server as this server is constanly in use. is there a way to solve this problem? i hav tried using sql ping and i can greac the server, but sqlping also gives the followinh error
Connection error: [DBNETLIB][ConnectionOpen (PreLoginHandshake())
timely response will be grately appreciated
Sunday, July 23, 2006 5:21 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,Gabby
The error you saw is quit common and it can be mapped to many cases. In most cases, the error happens because the server closes the connection for some reason when client is expecting data from the server.
1) Can you described more about you app? Does the error happen during a long running query? Is the error consistent or intermittent?
2) Which OS your sql server installed? WIN2K3 SP1? Here is a blog that bound to OS specific issue:
http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx
Also, could you check your Server ERRORLOG, what protocls enabled on your server? and whether there is any error info that may give clue? If you were running long query, please open server trace file and watch which operation caused server close connection.
Good Luck!
Ming.
Sunday, July 23, 2006 11:52 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
thanks a lot Ming,
i actually found out that it was one of the network admins that turned on firewall filtering on the Gateway router. this was actually filtering out MSSQL connections
Thanks a lot for your response
Monday, July 24, 2006 4:28 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi Ming,
I have SQL Server 2005 Express installed on a windows server 2003 standard endition. I have configured the firewall according to specs above where I added program exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility.
Here is the strange part: I am able to connect to the Sql Server remotely via Sql Server Management Studio Express, but I am unable to connect to the Sql Server by registering it in Sql Server Enterprise Edition...Is it possible to register the Instance through Enterprise Manager?
Thanks,
Greg
Thursday, July 27, 2006 1:17 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
hi,
I am trying to deploy an analysis server cube on a remote server on my LAN. The remote server has firewall off. From the Business development studio I can connect to the remote machine and create data source and data source view. However, when I try to deploy the cube I get the folowing error:
A connection cannot be made to redirector. Ensure that ‘SQL Browser‘ service is running.
I have ensures that the SQL Browser is running. What could be the problem and its solution?
thanks in advance,
PKJ
Wednesday, August 02, 2006 3:24 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
PKJ,
Please take a look at the Windows event log on the machine where you have Analysis Server and SQL Browser running to see if there is any error and warning events generated by SQL Browser. If there are, please post a sample of them to help us troubleshoot what the problem may be.
BTW, I would recommend that you continue to have the Windows Firewall on, but put the SQL Server process (sqlservr.exe) and SQL Browser process (sqlbrowser.exe) in the exception list.
Jimmy
Wednesday, August 02, 2006 1:09 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Very many thanks for a good work. Nice and useful. Like it!
Sunday, August 27, 2006 6:00 AM byJeorge Lukasing
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,
I am trying to deploy a DTSX package to 32-bit SQL Server 2005 in a 64-bit machine from my installer.
I am getting the following error in the SaveToSQLServer method:
The SaveToSQLServer method has encountered OLE DB Error code 0x80004005 (Communication Link Failure). The SQL statement that was issued has failed.
However I am not facing this problem when I try to deploy the DTSX package to a 32-bit SQL Server 2005 in a 32-bit machine.
Can anyone tell me why this happens and how this could be solved?
Thanks,
Sandhya
Wednesday, September 06, 2006 8:33 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi,
I have been running backup on a database(with size more than 20 GB), here I was not able to connect mssql server 2005 thro‘ management studio.
Event log says the following error
Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: 4%. System Idle: 16%.
However I icreased the worker thread value from 128 to 300, but still problem exists.
After the backup was completed every thing was fine.
Any suggestions would be appreciated.
Thanks
deena
Saturday, November 11, 2006 6:52 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I have just installed SQL SErver 2005,
when i start server management studio, it asks for server registration.
i have downloaded adventureworks x86 from the website. but now i don;t know how to register.
please provide some feedback as i am new toit.
Thursday, November 16, 2006 7:22 AM byDeepak sethi
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Deepak
Find the answer from Books Online installed w/ SQL Server 2k5.
Good Luck!
Ming
Sunday, November 19, 2006 2:00 AM bySQL Protocols
# SQL Server 2005 Remote Connectivity Issue TroubleShoot
With shipping SQL Server 2005, we heard from customer feedback about suffering make successful remote
Thursday, November 23, 2006 6:23 PM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Is there a space for Service Broker connectivity issues ? (... connection forcibly closed ...)
Thursday, December 07, 2006 9:53 AM byALZDBA
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I am have setup SQL Server 2005 Express on Windows XP Pro SP2 machine. I enabled SQL Server and SQL Server Browser services, configured the firewall. I migrated Access 2002 databases (in linked tables mode) to this SQL server from workstations running XP Pro SP2. All went perfectly well, as planned. The problem is that, we have two W2k Pro machines, and I can not connect these machines to the SQL at all. I can ping the machine running SQL, but can‘t connect to the SQLEXPRESS.
Friday, January 19, 2007 12:13 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Sanjay
Try this blog and follow the best practice:
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
Good Luck!
MIng.
Monday, January 22, 2007 1:02 AM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I unable to connect to sql from windows 2003 server were as I can able to connect from windows xp
Connection failed:
SQLState: ‘01000‘
SQL Server Error: 53
[Microsoft][odbc sql server driver][dbnetlib]connectionopen(connect())
connection failed:
SQLState: ‘08001‘
SQL Server Error: 17
Monday, January 22, 2007 5:10 AM byVijay Anand
# SQL 2000 client (Eng) to SQL 2005 Server(Korean)
Hi Guys,
I have a unique problem, i am having SQL Server 2000 client (English Version)running in my machine and i have a SQL Server 2005 (Korean Version). When i try to establish a connection in my enterprise manager i am not able to connect, but the same is getting connected when i try in SQL Query Analyzer.
Can someone help me in resolving the issue.
Thanks
Praveen
Monday, January 22, 2007 11:47 PM by
# help me
Thank you!
http://symy.jp/?Ct_220745,Thank">http://symy.jp/?Ct_220745,Thank you!
http://symy.jp/?Ct_220745
Wednesday, January 24, 2007 8:39 AM byPreved
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Praveen
Please provide your connection string and the error message you came accross.
If you face further problem, please provide more detail info by following:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1
Thanks!
Ming.
Monday, January 29, 2007 1:31 AM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Vijay
Can you provide more detail info by follow up below questions?
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1
Thanks!
Ming.
Monday, January 29, 2007 1:34 AM bySQL Protocols
# SQL Server 2005 Connectivity Issue Troubleshoot - Part I
This post provides some tips to troubleshoot Sql Server connection problems based on various displayed
Monday, January 29, 2007 1:43 AM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Help am doing C# and whenever i call store procedure a message come up that i can‘t open or login.
string connstring = "Data Source =.\\SQLEXPRESS; Initial Catalog=testDatabase; User Instance=True; Integrated Security = True";
SqlConnection connection = new SqlConnection(connstring);
// SqlConnection Connection = new SqlConnection("Data Source=.\\SQLEXPRESS;AttachDbFilename=|DataDirectory|\testDatabase.mdf;Integrated Security=True;User Instance=True");
SqlCommand cmd = new SqlCommand();
SqlDataReader reader;
cmd.CommandText = "StoredProcedure1";
cmd.CommandType = CommandType.StoredProcedure;
cmd.Connection = connection;
// cmd.ExecuteNonQuery();
// connection.Open();
connection.Open();
reader = cmd.ExecuteReader();
// Data is accessible through the DataReader object here.
connection.Close();
where am i going wrong? HELP!!!!!!!!!
Friday, February 02, 2007 5:13 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I am not able to figure out how to use sql express 2005 in client server environment.
I have installed the completed SQLEXpress and Advnaced Sql Express on both machines, enabled all protocols but still not able to connect from client to server.
I also tried SQLEXpress and Advnaced Sql Express on one machine and only Sql NAtive Client on client machine but no success.
What settings needed on server machine and what on client machine?
Can you please help?
Tuesday, February 06, 2007 2:43 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Ming,
First of all, thank you for this great resource.
We have a strange case with some customers. We are connecting to a local SQL 2005 Express named instance. We are supplying the local server and instance name using "127.0.0.1\TOCTTARGPPC05". Also note we are using Windows Authentication. When we try to connect to the instance using the IP for the local machine we get the error:
[DBNETLIB][ConnectionOpen (Connect()).]Specified SQL Server not found. (6)
We have shared memory, named pipes and tcp protocols enabled. In our troubleshooting we tried using sqlcmd to connect to the database. When we used "127.0.0.1\TOCTTARGPPC05" the connection failed, but when using ".\TOCTTARGPPC05" the connection was established immediately. From our research we noticed that this can occur if the SQL Browser service is not running and in fact we could reproduce this issue on our own machines. However, on the customers machine the SQL Browser service is running and they are still not able to connect using "127.0.0.1\TOCTTARGPPC05". We are currently stumped. Do you have any suggestions?
Thanks,
Shane
Tuesday, February 13, 2007 1:41 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Shane
Assume your local sqlexpress has np and tcp enabled, and it is listening on a tcp port and named pipe from ERRORLOG.
Can you try:
1) "sqlcmd /Snp:127.0.0.1\TOCTTARGPPC05", what is the error message you got?
2) "sqlcmd /Stcp:127.0.0.1\TOCTTARGPPC05", what is the error message you got?
3) Repeat step 1) and 2) by replace server to
a. "\TOCTTARGPPCO5"
b. "localhost\TOCTTARGPPCO5"
c. "\TOCTTARGPPCO5"
Would all of these work?
Is this problem only occur when you were trying "127.0.0.1"?
What OS when repro? WIN2K3? Do you have ipv6 enabled on the box?
Thanks!
Ming.
Wednesday, February 14, 2007 12:21 AM bySQL Protocols
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
I want to know why in Case 2 that SQL Browser service is required when it is dealing with local instance:
Case 2: Connect to local named instance
If you can not identify cause for connection fail when use MDAC connecting to local named instance, there are two other possible reasons:
1) Your application was running under an account that has no permission to the registry entry where MDAC client reads (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\\MSSQLServer).
2) SQL Browser service was not enabled or running.
Saturday, March 03, 2007 3:46 PM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
i am using the following connection string in my desktop application.it works fine with SQL Enterprise edition but when i use it with SQLExpress edition it does not work.
kindly help me how to fix this problem
Provider=sqloledb;Data Source=;Initial
Catalog=HTMS;User Id=HC;Password=123;
Monday, April 02, 2007 6:45 AM bykhalid
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, khalid
Please take a look the blog for best practice of connecting to sqlexpress.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
Good Luck!
Ming
Monday, April 02, 2007 3:04 PM bySQL Protocols
# how to differentiate MS SQL SERVER 2005 named instance and default instance
i need to differentiate MS SQL SERVER 2005 named instance and default instance
Thursday, April 12, 2007 8:48 AM by
# how to differentiate MS SQL SERVER 2005 named instance and default instance
i need to differentiate MS SQL SERVER 2005 named instance and default instance through c# code..
This is needed to attach the data base with server. that is i have to know whether i have to give (local) or (local)\SQLEXPRESS at the time attaching the data base.
Thursday, April 12, 2007 8:52 AM by
# Why SQL Client cannot connect SQL Server 2005 but OLEDB have no problem to connect SQL 2005
Hello,
I have some problem here...
When I use Server Explorer on Microsoft Visual Studio .NET 2005, I can‘t connect the SQL Server 2005 with Data Source : Microsoft SQL Server (SqlClient) but when I use Microsoft SQL Server (OLE DB) its work, its also happening when I make a connection test using udl file.
why this problem happening?
Thank for your help. Thank You
Monday, April 16, 2007 6:18 AM by
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Hi, Chandra
Please check out the blog according to the error message that you saw from sql client.
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
Good Luck!
Ming.
Tuesday, April 17, 2007 12:59 PM bySQL Protocols
# Handling and troubleshooting memory issues in a SQL Server 2005 instance
We had a major issue on one of the SQL Server instance with the memory and getting following error message
Wednesday, June 20, 2007 5:02 AM bySQL Server Performance and Tuning - (SSQA)
# re: Troubleshoot Connectivity Issue in SQL Server 2005 - Part II
Database access error. Reason [Microsoft][SQL Native Client]Communication link failure.
Webi report server log
(.\infostore.cpp:265): trace message: CInfoStore::Query: SELECT SI_SERVER_NAME,SI_CLUSTER_NAME,SI_SERVER_IS_ALIVE,SI_SERVER_IOR,SI_SYSTEM_INFO FROM CI_SYSTEMOBJS WHERE (SI_PARENTID = 16 AND SI_SERVER_KIND = ‘aps‘) OR SI_ID = 4
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: UNV_Manager:originalReportFilePath:frs://Input/a_068/001/000/324/test_universe.unw
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: UNV_Manager:tempFileName:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: FSFactoryListener_impl::GetNewServiceHelper: Asking for filestore from server Input:Input.alg1101rh2boa01..
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_Manager:attachHelper: 0.015
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1644). (false : TraceLog: **ASSERT:UNV_CacheManager:copy Universe file failed... [UNV_CacheManager.cpp;210]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_CacheManager:UNWCacheManager::DownloadFile: 0.031
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:The universe cache manager failed to download file.. [UNV_Manager.cpp;1758]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [ENTER] UNV_CacheManager:UNWCacheManager::DownloadFile
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [ENTER] UNV_Manager:attachHelper
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: UNV_Manager:originalReportFilePath:frs://Input/a_068/001/000/324/test_universe.unw
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: UNV_Manager:tempFileName:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_Manager:attachHelper: 0
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1644). (false : TraceLog: **ASSERT:UNV_CacheManager:copy Universe file failed... [UNV_CacheManager.cpp;210]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_CacheManager:UNWCacheManager::DownloadFile: 0.016
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:The universe cache manager failed to download file.. [UNV_Manager.cpp;1758]).
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:Failed at : -2147206823 [UNV_Manager.cpp;1986]).
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:UNV_Manager:HRESULT : -2147206823 [UNV_Manager.cpp;1986]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_Manager:ImportUniverseFromCE: 0.062
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_Manager:GetUniverseFromCache: 0.062
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] UNV_Manager:LoadUniverseHeader: 0.062
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [ENTER] QT_LocalServer:SetErrorMessage
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: QT_LocalServer:An error occurred, the corresponding message will be set in the TLS
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: QT_LocalServer:Error Code:506
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ctResourceBundle:Message bundle loaded::qtserver_error_en_
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:[Cdztools Error Trace:BEGIN]
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:PREFIX:ERR
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:COMPONENT:WIS
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:ERRORCODE:506
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:ERRORTYPE:USER
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:MESSAGE:Could not download the universe test_universe from the CMS for the following reason: . See your Business Objects administrator for further information. (Error: WIS 00506)
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:BORESULT:89
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:MODULENAME:QTServer
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:FILENAME:QTLocalServer.cpp
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:LINEPOSITION:1770
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:DPNAME:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:DPLONGNAME:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:DPID:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:COMMANDNAME:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:COMMANDID:
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ct_cdz_error_context:[Cdztools Error Trace:END]
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ctResourceBundle:Message bundle released::qtserver_error_en_
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: ctResourceBundle:Message bundle released::qtserver_error_en_
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] QT_LocalServer:SetErrorMessage: 0
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] QT_LocalServer:GetUniverseParameters: 0.062
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:C3_cdbQTServer:m_pQT->GetUniverseParameters : -2147206823 [kc3qtds.cpp;3911]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] C3_cdbQTServer:LoadUniverseConnection: 0.062
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:C3_cdbQTServer:LoadUniverseConnection failed [kc3qtds.cpp;5389]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] C3_cdbQTServer:_LoadDictionary: 0.062
[Wed Jun 20 08:04:08 2007] 4920 6528 assert failure: (.\TraceLog.cpp:1646). (false : TraceLog: **ERROR:C3_cdbQTServer:m_pServer->_LoadDictionary(*m_pDict); failed : -2147467259 [kc3qtds.cpp;2801]).
[Wed Jun 20 08:04:08 2007] 4920 6528 trace message: TraceLog: [EXIT] C3_cdbQTServer:tbQTDS_CreateObjects: 0.062
Input FRS log
Timestamp ProcessID ThreadID Message
[Wed Jun 20 07:58:06 2007] 7072 7896 (.\nsclient.cpp:2037): trace message: Name server communication failed. Reconnect...
[Wed Jun 20 07:58:06 2007] 7072 7896 (.\nsclient.cpp:224): trace message: NSCLIENT: Do connection to alg1101rh2boa01.connectprod.connect.bt.com. Last successful connection to ALG1101RH2BOA01.CONNECTPROD.CONNECT.BT.COM
[Wed Jun 20 07:58:06 2007] 7072 7896 (.\oscafactorymgr.cpp:1318): trace message: DONT CALL DONT CALL DONT CALL DONT CALL
[Wed Jun 20 07:58:07 2007] 7072 7896 trace message: SIWarning: ResolveSocket failed!
[Wed Jun 20 07:58:07 2007] 7072 7896 trace message: CNSClientManager::DoConnectToAps(): failed to retrieve aps factory handle from aps alg1101rh2boa01.connectprod.connect.bt.com.
[Wed Jun 20 07:58:07 2007] 7072 7896 (.\oscafactorymgr.cpp:1318): trace message: DONT CALL DONT CALL DONT CALL DONT CALL
[Wed Jun 20 07:58:08 2007] 7072 7896 trace message: SIWarning: ResolveSocket failed!
[Wed Jun 20 07:58:08 2007] 7072 7896 trace message: CNSClientManager::DoConnectToAps(): failed to retrieve aps factory handle from aps alg1101rh2boa01.connectprod.connect.bt.com:6401.
[Wed Jun 20 07:58:08 2007] 7072 7896 trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com from m_ActiveMembers and adding to m_InactiveMembers
[Wed Jun 20 07:58:08 2007] 7072 7896 trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com:6401 from m_ActiveMembers and adding to m_InactiveMembers
[Wed Jun 20 07:58:08 2007] 7072 7896 trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com from m_ActiveMembers and adding to m_InactiveMembers
[Wed Jun 20 07:58:08 2007] 7072 7896 trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS alg1101rh2boa01.connectprod.connect.bt.com:6401 from m_ActiveMembers and adding to m_InactiveMembers
[Wed Jun 20 07:58:08 2007] 7072 7896 (.\nsclient.cpp:237): trace message: NSCLIENT: no valid APS available to connect to
[Wed Jun 20 07:58:08 2007] 7072 7896 (.\nsclient.cpp:2069): trace message: Failed to connect to name server: Transport error: unable to retrieve the CMS factory. (44)
[Wed Jun 20 07:58:52 2007] 7072 5016 trace message: FileResourceMgr::cleanup: Going thru maps of readers and writers
Wednesday, June 20, 2007 9:53 AM by
# Glorf IT - Bedenkliches aus dem IT-Alltag » SQL-Server-2005: immer mit Named-Pipes
PingBack fromhttp://www.glorf.it/blog/2007/06/25/sql-server/sql-server-2005-immer-mit-named-pipes
Monday, June 25, 2007 2:54 PM byGlorf IT - Bedenkliches aus dem IT-Alltag » SQL-Server-2005: immer mit Named-Pipes

SQL Protocols : Troubleshoot Connectivity Iss... Troubleshoot ActiveSync: More | Smartphone an... Troubleshoot ActiveSync: Port 990 | Smartphon... SQL A comparison of Web services transaction protocols A comparison of Web services transaction protocols Home Wireless Video and Audio Connectivity Salmon Lab Protocols: Porcine Brain Tubulin P... Build a groundhog snare by Allen Easterly Iss... Client to Server Secure SMTP Connectivity in Exchange Server 2007 SQL 基础-SQL 简介 SQL语法,SQL语句大全,SQL基础 SQL語句集錦 SQL优化 sql 触发器 SQL code SQL code SQL命令 sql补充 SQL 通配符 sql 注入 SQL基础省市sql SQL集锦