SSIS 2008 in Failover Clustering 2008
Hi,We know the disadvantages by configuring the SSIS in a clustred environment, but yet this is the way we do it.In SQL Server 2005 and Windows 2003 Server it works fine with the MS guide in Configuring SSIS in a Cluster. But for SQL 2008 and Windows 2008 Failover Cluster is seems to me, that the guide has just been pasted from the 2005 guide. It doesnt fit in many of the steps to perform. I found this guide http://msdn.microsoft.com/en-us/library/ms345193.aspx and it should apply to Failover 2008 but as mentioned it does not. I have tried to follow the guide as far as I could and the tried to "think up" the steps thats doenst match.1. I install SSIS on both nodes.2. I make a cluster group called SSIS and add a clustered disk3. I create a resource of the type: SQL Server Integration Services 10.0 and calls the service name: MsDtsServer1004. I make a registry replication entry: SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS\ServiceConfigFile5. I place the file: MsDtsSrvr.ini on my SSIS disk and modify the file with the path to the MsDtsSrvr.ini file and the name of the instance to run with6. I modify the regkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS\ServiceConfigFile to have the path to the file.Then I start the service at it comes online. I connect to the integrations service and no errors. But I can not expand the Stored packages and that indicates an error to me.Anyone ?
March 8th, 2010 5:35pm

Kristian,Do you save your packages on a file system or in SQL?- If you're saving them on the filesystem use a manifest file to register them on your SSIS server. (Use DtUtil.exe)- If you're saving them in SQL you may want to check your msdb database.See:http://blog.hoegaerden.be/2010/01/10/list-all-ssis-packages-deployed-on-your-integration-server/Regards,Ivo
Free Windows Admin Tool Kit Click here and download it now
March 8th, 2010 5:44pm

Hey IvoWell it's a bit tricky. I'm working in a function where we install and prepare servers and SQL servers for our DBA guys. So I really don't know anything about how they use it. I just know that it is not a correct installation, when I can't expand the Stored packages. Normally there would be a File System and a MSDB folder when expanding Stored packages. But there is not. Therefor I guess that the installation has failed somehow. And the guide for Failover Cluster 2008 and SSIS is not usefull because the steps are different from 2005, which the guide from MS is for.
March 9th, 2010 12:00pm

Hey Kristian,I think your installation wend well. A new installation does not automaticly restores your SISS package from a other instance.So i think you have to check the other old instance and check where the packages where saved and import them in your new clustered instance.Regards,Ivo
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2010 12:14pm

Hi Ivo,What is the error message? Did you also check the MsDtsSrvr.ini.xml file to make sure that the servername was specified correctly?<?xml version="1.0" encoding="utf-8"?><DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> <TopLevelFolders> <Folder xsi:type="SqlServerFolder"> <Name>MSDB</Name> <ServerName>.</ServerName> </Folder> <Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>..\Packages</StorePath> </Folder> </TopLevelFolders></DtsServiceConfiguration>By default the ServerName here is '.' for local server, but since you are in a cluster, you need to specify your SQL Server virtual instance name here.Best regards,Charles WangPlease remember to mark the replies as answers if they help and unmark them if they provide no help
March 9th, 2010 12:27pm

Hey Ivo I'll try to have the DBA guys to perform that task Charles: My ini file looks like this: (our domain is x'ed out in the following) <?xml version="1.0" encoding="utf-8" ?> - <DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> - <TopLevelFolders> - <Folder xsi:type="SqlServerFolder"> <Name>MSDB</Name> <ServerName>PD0200.xxx.xxx.dk\pdsql0200</ServerName> </Folder> - <Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>s:\Packages</StorePath> </Folder> </TopLevelFolders> </DtsServiceConfiguration>
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2010 12:54pm

Kristian,If you query the MSDB database on msdb.dbo.sysssispackagefolders what do you see?Regards,Ivo
March 9th, 2010 2:24pm

folderid parentfolderid foldername 8877FE4B-A938-4A51-84B9-C5BDAD74B0AD 00000000-0000-0000-0000-000000000000 Data Collector 39163C42-602B-42C9-B4F7-1843614F9625 8877FE4B-A938-4A51-84B9-C5BDAD74B0AD Generated 00000000-0000-0000-0000-000000000000 NULL 08AA12D5-8F98-4DAB-A4FC-980B150A5DC8 00000000-0000-0000-0000-000000000000 Maintenance Plans
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 10:07am

Kristian,You have not answered my question:what is the error message?Beiseds please check if there is any error message in Windows application event logs. Please remember to mark the replies as answers if they help and unmark them if they provide no help
March 10th, 2010 2:28pm

Kristian,I just read the article you posted before, http://msdn.microsoft.com/en-us/library/ms345193.aspx, and find the following description:=========================================The Integration Services service cannot delegate credentials. Therefore, you cannot use Management Studio to manage packages stored in the msdb database when the following conditions are true: The Integration Services service and SQL Server are running on separate servers or virtual servers. The client that is running SQL Server Management Studio is a third computer. The client can connect to the virtual server on which the Integration Services service is running. However, that computer cannot delegate the user's credentials to the virtual server on which SQL Server is running. This is known as a double-hop scenario.========================================This looks like a product limitation.Please remember to mark the replies as answers if they help and unmark them if they provide no help
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2010 4:06pm

Kristian - Did you ever get your MSDB to show up? I'm running into the exact same situation.
March 23rd, 2011 7:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics