February 5, 2003 at 7:36 am
Does anyone know what could be my problem here?
Let me explain….
I have two servers, one in a DMZ and the other on our local network. I have a DTS package running every night form the server on the DMZ. I can verify this by looking in the jobs. Here is the kicker. I can run the DTS package from Enterprise Manager (EM) and the package works just fine. But, every night the “job” fails (job error below). The job is running under the SA account so it has the permissions but fails. I am thinking that it could be something with the firewall between the DMZ and the local network. Some port that is being blocked or something. Does anyone know if “jobs” are using a special port or something? The reason why I am going down this path is that using EM and sitting on the local network I must be acting as some kind of “middle” man and that is why the DTS package is working when I fire it off. But, when the server in the DMZ is doing all the work there is no middle man helping it out. I.e. I can see the server in the DMZ and it can see the server on the local network through me. I know, sounds dumb. But, that is all I can think the problem could be some port being blocked on the firewall. Any help would be so wonderful.
*******************
Start Of Job Error
*******************
DTSRun: Loading...
Error: -2147008507 (80074005);
Provider Error: 0 (0)
Error string: Unspecified error
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 713
Error: -2147467259 (80004005);
Provider Error: 1326 (52E)
Error string: Client unable to establish connection
Error source: Microsoft OLE DB Provider for SQL Server
Help file: Help context: 0
Error: -2147467259 (80004005);
Provider Error: 1326 (52E)
Error string: [DBNMPNTW]ConnectionOpen (CreateFile()).
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0. Process Exit Code 1. The step failed.
*****************
End Of Job Error
*****************
Thanks,
Dane-
February 5, 2003 at 8:22 am
Why don't you run the package on the DMZ server through a job on a server in the local network then.
John Zacharkan
John Zacharkan
February 6, 2003 at 4:14 am
Sounds like your server is trying to connect using Named Pipes. Use Client Network Utility on the server to create alias to other server and make sure network library is set to TCP/IP.
If you run the DTS via EM on your machine then it will use the settings on your machine, could explain why it works.
Far away is close at hand in the images of elsewhere.
Anon.
February 6, 2003 at 12:54 pm
Has the sa password changed recently?
February 6, 2003 at 1:13 pm
Keep in mind when you are running the DTS pacakge from enterprise manager on your workstation, the package is actually executing on your workstation, not on the server.
Make sure the package can run from the server, as this is what is happening when SQL Server Agent kicks it off. You may have to remote console access the server, and / or log in locally on th console and run the package.
This is one of the reasons why DTS can be a nightmare to support in a large environment. When you design and execute a DTS package from your workstation, the code that is written in the background fot the package is designed to work with whatever your machine can support.
This basically means that if you have differing versions of things like MDAC installed on your PC, versus what is on the server, the DTS package basically will fail. If you encrypt the DTS package by adding a password, it minimizes this somewhat, however I have seen issues even with this...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply