• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 212
  • Last Modified:

DTS Creation Error ~ SQL Server 2005 SP2

Hi, I have asked this question a few times and I'm not getting any responses... I can't believe nobody has an aswer for this.  I'm really desperate as I cannot find anything on the web regarding this that I haven't already tried.  I need to fix this problem very soon.

Error Loading Type Library/DLL

I can connect to SSIS just fine... but when I try to create a DTS package... I get that error.  I have registered the DTS.dll but it hasn't helped.

I also don't think my server is 64 bit and the MSDN solution for it seems to be a 64 bit solution.

Please and thanks.
0
Roxanne25
Asked:
Roxanne25
  • 13
  • 8
  • 3
3 Solutions
 
CragCommented:
The result of the following statement should tell you if you have 64-bit or not.
select @@version

I don't know of any other resolution except registering the DLL.
Have you used the sysinternals process monitor to watch the process as it loads?
0
 
Roxanne25Author Commented:
Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)   Mar 23 2007 16:28:52   Copyright (c) 1988-2005 Microsoft Corporation  Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Why does it say Service Pack 1 still when I installed SP2 on the server like 2 days ago?

And what is the sysinternals process monitor?
0
 
Roxanne25Author Commented:
At the bottom of my query window... where it says Query executed successfully... in the next box over it says the server name and then (9.0 SP2) ...

I'm so confused.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ptjcbCommented:
Your Windows Server is SP1, your SQL Server is SP2.

2005 SP2+Q934458            GO      3,054      9.00.3054

FROM http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx
0
 
CragCommented:
The Windows NT 5.2 (Build 3790: Service Pack 1)  piece relates to the Windows version and service pack.
The 9.0 SP2 in the Management Studio is the SQL Server version.
The Process Monitor can be found here:
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

It makes it possible to watch all of the file and registry activity for the system. You will have to filter it down to find the SSIS process that is generating the error.
0
 
ptjcbCommented:
By the way, when you say "create a DTS package" do you mean create an SSIS package, yes?
0
 
Roxanne25Author Commented:
Yes, an SSIS package.  I need to copy a database to a test database and when I do a database copy... it goes through the motions then when I click on run immediately... it has the steps it needs to do to finish the process.  One of the processes is save the package to the server.  This is the line it errors out on and it stops the entire process.  

So, basically my server is successfully patched to 2 but my client is still 1.  Would not having SP2 on my client keep this error present?  

Also, can I use the same install for my client that I used for the server?  I tried running the install on my client and it ran a check to see what instances of SQL I had on my machine and it was asking me to select which ones I wanted to update... it said I had SQLSERVEREXPRESS installed... if I didn't check anything off it wouldn't proceed with the install.

I'm basically a developer that's been forced to become my server admin because our admin left the company and we have no other SQL Server Admins to take his place.  I really appreciate the help.
0
 
Roxanne25Author Commented:
This is the file name of the install package:
SQLServer2005SP2-KB921896-x86-ENU.exe
0
 
ptjcbCommented:
OK - you have one Windows server with SQL Server 2005 Enterprise.
What do you mean by "my client"? You have only sent only one result from the @@version. I assume that you are calling the second computer your client? On the second computer, the SP2 installation found SQLExpress installed.

Did you run SELECT @@VERSION on the SQLExpress computer?

You need to copy a database to a test database. Why not do a backup of the first database, copy the file to the second computer and then do a restore?


0
 
Roxanne25Author Commented:
When I say my client computer... I mean the computer I'm accessing the server with.  
I have management studio installed my PC that is connecting to the server.  I don't actually have a copy of sql server express.

The @@Version I did was from my client computer.  So, that's why I'm asking if I need to install the service pack on my client as well as the server?

I am making a copy of the database to the same server.  I just need to make a test enviornment for my production database.  No matter which way I do it... I still need to fix this DLL error problem.  
0
 
CragCommented:
In the interim you can just use a backup restore to give you the copy you require.
Have you tried to create a SSID package that does something else such as extracts data to a flat file?
0
 
Roxanne25Author Commented:
Yes, any kind of package creates this error.
0
 
Roxanne25Author Commented:
And sorry we didn't answer my other problem... do I need to upgrade my client install with Service Pack 2?  I know when my admin was still here, he did patch my client to service pack 1.  

I'm just not sure cause I thought it was strange it was thinking I had sqlserver express installed and wouldn't install unless I selected those items.
0
 
CragCommented:
I thought so too - having the two systems at the same level is generally a good idea although shouldn't be necessary.
Have you tried to create the package on another client or on the server?
0
 
Roxanne25Author Commented:
Yea, it does the same thing from the other client.  The server doesn't have management studio installed on it... so I can't do it from there. :/
0
 
Roxanne25Author Commented:
I also just discovered that if I go into BI Studio and try to create an integration service project, I get the same error.
0
 
CragCommented:
I think that the only way to identify the cause, without guessing, is to use the ProcessMonitor and fill the DLL that it is objecting to. It might be the DTS.dll and it might not.
0
 
Roxanne25Author Commented:
Hmm....well I have searched my client pc and I searched the server harddrive as well... I cannot find procmon.exe anywhere...  I checked the link that someone provided above and in the "installation" section of the page it said "just run procmon.exe" ... is this something I should already have installed?
0
 
CragCommented:
I supplied the link before:
The Process Monitor can be found here:
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

Unfortunately you need to go to the bottom of the page and download the program before you can execute it.
The virtual execution mode version hasn't been released as yet.

ps. I've no idea why they put the download link at the bottom - took me a while to find it as well.
0
 
Roxanne25Author Commented:
Ok, yea I didn't scroll all the way to the bottom. :)

I got it, installed it... its running...now you're gonna have to help me with it cause I've never used it before.  I need to filter out all the gazillion things it is showing right now and just make it track sql server/bi studio... how do I do dat?

Thanks in advance.
0
 
CragCommented:
you'll need to use a filter and exclude all of the programs that you don't need to monitor and this will take a bit of trial and error until you find the right one. try filtering out all of the stuff that's running without the SSIS piece running and then add it in as you go. Notmuch i can do to help. Once you get rid of the other stuff you're looking for failed messages.
0
 
Roxanne25Author Commented:
I guess what I'm saying is I don't know how to filter it... it wants me to pick from a drop down that says Architecture,  Category, Command line... I dunno what to select and then the next text box has is , is not, less than and then of course I type in what else I want...  I have over 1 billion events in the list ... sigh.
0
 
CragCommented:
You need to identify the process that SSIS is running under and then go in and create a filter than includes just that one process. You can try either Task Manager to identify the process or download Process Explorer from the Microsoft Technet site and use that to find the process.
0
 
Roxanne25Author Commented:
I was not successful in identifying the problem with the process monitor unfortunately.

Oddly enough I just reinstalled for the second time, service pack 2 on my desktop and now its magically working.  I'm going to have my 2 other employees try it on theres and see if its working now as well.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 13
  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now