October 4, 2007 at 8:27 am
We have a user who is running a group of three DTS packages from a batch scheduler using dtsrun. Two of the packages run ok. The third is getting the following output:
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1
DTSRun OnStart: DTSStep_DTSOlapProcess.Task_1
DTSRun OnError: DTSStep_DTSOlapProcess.Task_1, Error = -2146828236 (800A0034)
Error string: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 700
Error Detail Records:
Error: -2146828236 (800A0034); Provider Error: 0 (0)
Error string: You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts80.hlp
Help context: 700
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Bad file name or number
Error source: DTSOlapProcess
Help file:
Help context: 1000052
DTSRun OnFinish: DTSStep_DTSOlapProcess.Task_1
DTSRun: Package execution complete.
Completed at 04-Oct-07 06:02
I have checked and there is not another computer with the same name on our network. I have checked in the package and the connection task is correct and the same as the other two packages. I am open to any other suggestions.
October 7, 2007 at 9:02 pm
What is in the package? This is definitely some type of network error. Are you sure you're checking the names referenced in the package? You might try saving it out as a Structured Storage file and checking all connections.
October 8, 2007 at 7:25 am
And - just for giggles - what's the name it's trying to connect to in the OLAP step?
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 8, 2007 at 7:55 am
As I said, there are three packages executing as a group. Each package contains a connection task, one or more stored procedure tasks to update data in a SQL Server database, and an OLAP task to update the cube with the new data. In the two packages that are working, the connection task has an existing connect called 'SQL Server', the data source is 'Microsoft OLE DB Provider for SQL Server'. In the package that is not working, the connection task's existing connection and the data source are both 'Microsoft OLE DB Provider for SQL Server'. This is the only difference I can fine between the packages.
I did save the failing package as a Structured Storage file (.dts), but how do you read the package without using the designer? If I open it in another app, I just see garbage.
Steve Jones - Editor (10/7/2007)
What is in the package? This is definitely some type of network error. Are you sure you're checking the names referenced in the package? You might try saving it out as a Structured Storage file and checking all connections.
October 8, 2007 at 8:02 am
I'd really check the values in the Structured Storage file. There were issues in the past where something wouldn't show up in the designer, but still existed in the VB file, like an extra connection.
Does the third one fail every time you run it? Even if you manually run it or just when it's in a batch job?
How are the connections configured? IP, Windows name?
Can't really think of what would cause this except a duplicate name. Are all three packages configured for the same servers?
October 8, 2007 at 8:08 am
How do I read a Structured Storage file?
The third package only fails if it is run as a batch job.
Since we have the same packages on test and prod, we created an alias on both servers to simplify the migration process.
As I stated in my previous response, all the packages are configured identically, except for the existing connection name.
Steve Jones - Editor (10/8/2007)
I'd really check the values in the Structured Storage file. There were issues in the past where something wouldn't show up in the designer, but still existed in the VB file, like an extra connection.Does the third one fail every time you run it? Even if you manually run it or just when it's in a batch job?
How are the connections configured? IP, Windows name?
Can't really think of what would cause this except a duplicate name. Are all three packages configured for the same servers?
October 8, 2007 at 8:21 am
You can open the Structured Storage file in Notepad Or Visual Studio. It's just text, VB code. Look through it and you should figure it out.
However, if it only fails when run as a batch job, I'd be sure that you're running the correct file. Prod and not against dev. I'd also check rights on the person running the batch job. Does it fail for everyone?
October 8, 2007 at 2:43 pm
We do not have Visual Studio available. When I open the Structured Storage file in Notepad, I only see garbage. I have tried saving the file as both a .dts and a .txt, but it is unreadable in either format.
Steve Jones - Editor (10/8/2007)
You can open the Structured Storage file in Notepad Or Visual Studio. It's just text, VB code. Look through it and you should figure it out.However, if it only fails when run as a batch job, I'd be sure that you're running the correct file. Prod and not against dev. I'd also check rights on the person running the batch job. Does it fail for everyone?
October 8, 2007 at 3:02 pm
Sorry, being an ID-10-T here today. Or for sure today, possibly other days as well 🙂
Save as a VB file (.bas). You should be able to open in notepad and see something like this:
'****************************************************************
'Microsoft SQL Server 2000
'Visual Basic file generated for DTS Package
'File Name: c:\test.bas
'Package Name: New Package
'Package Description:
'Generated Date: 10/8/2007
'Generated Time: 3:00:41 PM
'****************************************************************
October 8, 2007 at 3:30 pm
That worked. Thanks.
Steve Jones - Editor (10/8/2007)
Sorry, being an ID-10-T here today. Or for sure today, possibly other days as well 🙂Save as a VB file (.bas). You should be able to open in notepad and see something like this:
'****************************************************************
'Microsoft SQL Server 2000
'Visual Basic file generated for DTS Package
'File Name: c:\test.bas
'Package Name: New Package
'Package Description:
'Generated Date: 10/8/2007
'Generated Time: 3:00:41 PM
'****************************************************************
July 21, 2008 at 4:00 pm
Did you ever find a resolution?
We are having a similar problem.
January 24, 2012 at 7:11 am
I just received it. I'm thinking that it is a double hop problem (rights to read or write to that server share).
*******************
What I lack in youth, I make up for in immaturity!
February 17, 2012 at 5:45 am
Each package contains a connection task, one or more stored procedure tasks to update data in a SQL Server database, and an OLAP task to update the cube with the new data
February 17, 2012 at 5:49 am
Okay, the problem for me was:
One of the servers had a firewall that it shouldn't have had.
One of the linked servers had a path that was too long.
I didn't resolve it but the DBA did (I'm a developer).
Have a great day.
Bill
*******************
What I lack in youth, I make up for in immaturity!
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply