Sorry for the repost... thought it better to put in a message of its own...

We have installed SSIS in a cluster.

We have a test package setup, however when we go into the properties for the package, go into Steps and on the General tab, under Server: we enter the Server Name, the package fails, but when we enter the IP address the package runs...

We need to have the server name and not the IP address, any ideas as to what the problem might be?

From http://www.developmentnow.com/g/99_0...clustering.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

See if this helps any:
http://weblogs.sqlteam.com/geoffh/ar...-Question.aspx

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Chris" <nospam (AT) developmentnow (DOT) com> wrote

Here's an update,

In the setup for the job that ran the package, under the Step properties, on the General tab we had SSIS Package Store as the Package Source and under Package, point to the package we wanted under the MSDB folder. When we executed the job, the job was failing with the message 'Could not load the package'. Was getting very frustrating!

We changed the Package Source to be SQL Server and pointed the Package directly to MSDB, the package ran succesfully. It's an acceptable work around.

I can't determine what the benefit of using the SSIS Package Store is when all it seems to be is a pointer area for either the File System or the SQL Server.

From http://www.developmentnow.com/g/99_2...IP-address.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com