Link to home
Start Free TrialLog in
Avatar of BigBlackMamba
BigBlackMamba

asked on

Unable to connect to SSIS Service - library not registered.

I'm unable to connect to SSIS. The message states "Library not registered".  I've gone into Add/Remove programs and changed my Integrated Services component but with no success.  Is it possible to uninstall SSIS only - I can't find how on the net.

Does anyone know how to resolve this problem?
Avatar of Steve Hogg
Steve Hogg
Flag of United States of America image

Do you have 2000 DTS and 2005 SSIS on the same machine.
Avatar of BigBlackMamba
BigBlackMamba

ASKER

just 2005 ssis - i did download express 2008 but have since removed it.
I think you may be trying to connect in the Object Explorer in SQL Server Management Studio (SSMS). You need to open SSIS as follows: Start Menu, Microsoft SQL Server 2005, SQL Server Buisness Intelligence Development Studio. Then you create a new SSIS Project. In SSMS you are connecting to the Integration Services repository on a server, probably not what you really want to do.
I realisei can do that but i need to be able to import DTSX packages built outside of BIDS and I know I can
do this via the Object Explorer. can i import via the route suggested? i'm new here - should be be posted as a second question?
I've imported many packages using the following intructions given in on-line help:

"Open SQL Server Management Studio and connect to Integration Services.
In Object Explorer, expand the Stored Packages folder.

Expand the subfolders to locate the folder into which you want to import a package.

Right-click the folder, click Import Package. and then do one of the following:

To import from an instance of SQL Server, select the SQL Server option, and then specify the server and select the authentication mode. If you select SQL Server Authentication, provide a user name and a password.

Click the browse button (&), select the package to import, and then click OK.
To import from the file system, select the File system option.
Click the browse button (&), select the package to import, and then click Open.
To import from the SSIS Package Store, select the SSIS Package Store option and specify the server.
Click the browse button (&), select the package to import, and then click OK.

Optionally, update the package name.

To update the protection level of the package, click the browse button (&) and choose a different protection level by using the Package Protection Level dialog box. If the Encrypt sensitive data with password or the Encrypt all data with password option is selected, type and confirm a password.

Click OK to complete the import."

but this requires me to connect to Integated Services. I used to be able to do that but not any more....
Alright, you are further along than I presumed, very sorry. When you get the error, what is the full detail. Can you post the entire error?
obj-expl-is.bmp
no problem and certainly no need to apologise; i appreciate your help. my sql server is TOASTER.

"Cannot connect to TOASTER

Additional Information

  Failed to retreive data for this request. (Microsoft.SqlServer.SmoEnum)

     Connect to SSIS Service on machine "TOASTER" failed:
         Library not registered.

            Connect to SSIS Service on machine "TOASTER" failed:
                Library not registered."
 
 
ASKER CERTIFIED SOLUTION
Avatar of Steve Hogg
Steve Hogg
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
that's what I was afraid you might say - it's only a personal Server although I've written loads of T-SQL programs. Let me work out how to do a backup of my main database (and MASTER, MSDB) and I think I'll go down that route.  

If I can't do a backup, its not the end of the world; the programs are easily reproducible - the main thing is that SSIS works.

thanks for researching this for me.
thanks again for your help.
There are common occasions when dll 's need to be registered. I don't know why this happens, conflicts, installation bugs, etc.. But here is a link to a similar situation. Maybe it would help you. But I sure reccomend a reinstall of all SQL Server.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3999900&SiteID=17 
Have you tried verifying the Service is running?
http://msdn.microsoft.com/en-us/library/ms137789(SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms137731(SQL.90).aspx