|
Hi, One of upload job is failing with following error message... Failed to connecto to the data server Inner Error ------------------> Row #: 0 Source: "Microsoft SQL Server Native Client 10.0" Description: "Login timeout expired" Help File: "(null)" Help Context: 0 GUID: {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}. Row #: 1 Source: "Microsoft SQL Server Native Client 10.0" Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online." Help File: "(null)" Help Context: 0 GUID: {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}. Row#: 2 Source: "Microsoft SQL Server Native Client 10.0" Instance: "" Procedure: "" Line#: 0 Error Number: 2 Error State: 1 Error Severity: 16 Error Message: "Named Pipes Provider: Could not open a connection to SQL Server [2]. " Help File: "(null)", Help context: 0 GUID: {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Process Exit Code 1. The step failed. can you please let me know what is the reason? how can I resolve it? The job is running with correct authentication. regards.
(comments are locked)
|
|
Have you checked the connection protocol settings on the systems? It appears your Client is attempting Named Pipes but the Server isn't enabled for that. And since the error doesn't talk about TCP/IP your Client may not be configured for that. The Client and SQL Server require a common protocol to communicate over. Here you mean SQL server is not enabled for Named Pipes? where are you referring the same under properties?
Jun 21 '11 at 07:57 AM
pits
Check SQL Server Configuration Manger.
Jun 21 '11 at 08:05 AM
Blackhawk-17
(comments are locked)
|
|
@Grant Fritchey is 100% correct. This is a connectivity issue. It it where authentication or something else it would specify in the message. Grant list out a lot of possible areas to look into. The only other things I can think of to check would be firewall. If the job is trying to upload data to a remote server a firewall may be preventing you from reaching the server. You might try setting up an ODBC connection just to validate your connectivity. Is this a job on the same server, a new instance of SQL, or something that has been working and just started failing. Please provide as much detail as you can.
(comments are locked)
|
|
Have you followed the detail of the error message where it says
Is this a newly installed SQL instance? Other than that, all the things @Grant Fritchey says are what you need to explore Congrats on the 25K.
Jun 21 '11 at 04:32 AM
Tim
(comments are locked)
|
|
It could be a lot of things. It could be that the server is offline. It could be that the process doesn't have the correct permissions. It could be a typo so you're attempting to connect to the wrong server. It could be that you're running it through SQL Agent and the SQL Agent process doesn't have permission. It could be that the protocol you're using to connect isn't enabled on that server. It could be that the server doesn't allow remote connections, as the error message says. It's a straight connectivity issue. Address it that way. Investigate everything that could prevent the connection from going through. Congrats on the 28K.
Jun 21 '11 at 04:32 AM
Tim
Thanks. 30 is the big number now.
Jun 21 '11 at 06:00 AM
Grant Fritchey ♦♦
the job type is cmdexec where the command is some code...how I can understand that what that code does or what are the steps in the code?how can I read that code...i.e from where its picking file ...where it is uploading...ect?
Jun 21 '11 at 08:01 AM
pits
You have to be able to read the code. I can't help you there. No way to know what it's doing without looking at it. Also, what/who is calling the code? That's probably where the problem is.
Jun 21 '11 at 08:04 AM
Grant Fritchey ♦♦
(comments are locked)
|
