Package Configuration Wizard hangs using VS2013 and SQL2014

Question

Package Configuration Wizard hangs using VS2013 and SQL2014

carpay

SSC Veteran

Points: 241
More actions
January 17, 2015 at 3:57 am

#314569

hi, I'm having trouble to use the Package Configuration Wizard. The first time using is OK (that is I can configure-save-run it as a was used to in VS2008 / SQL2008R2). But when I want to edit the configuration it hangs. It is doing something because the scrollbars are updated. After waiting for half an hour I killed the process. I tried it over and over with XML or SQL storage. I even tried it on a fresh new server with only SQL2014 and SSDT on it. The OS on both boxes is 2012R2.
Anyone having the same issue's? Workarounds?
Using a home-cooked variable reading and writing with SQL Task and/or Script Task would be a workaround for me. But I hesitate; the Package Configuration Wizard is a core component of SSIS. It should work!
thanks for any help

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246686 More actions · Answer 1

carpay (1/17/2015)
hi, I'm having trouble to use the Package Configuration Wizard. The first time using is OK (that is I can configure-save-run it as a was used to in VS2008 / SQL2008R2). But when I want to edit the configuration it hangs. It is doing something because the scrollbars are updated. After waiting for half an hour I killed the process. I tried it over and over with XML or SQL storage. I even tried it on a fresh new server with only SQL2014 and SSDT on it. The OS on both boxes is 2012R2.
Anyone having the same issue's? Workarounds?
Using a home-cooked variable reading and writing with SQL Task and/or Script Task would be a workaround for me. But I hesitate; the Package Configuration Wizard is a core component of SSIS. It should work!
thanks for any help

As you're up to date with your SQL technology, can I assume that you're using the project deployment model?

If so, your config could be handled straight out of SSISDB using project/package connections and parameters. Have you deliberately chosen not to do this for some reason?

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

lcarpay SSC Veteran Points: 271 More actions · Answer 2

Thanks Phil. I'm trying to move my packages "as is" from SQL2008R2 to SQL2014. I will dive into the project deployment model. It is new to me.

As for my question, I am just wondering if others experience any problems with the package configuration wizard in Visual Studio 2013 / SSDT BI 2014

cheers, leon

abc SSC Rookie Points: 33 More actions · Answer 3

Hi, I have the exact same issue. Package Configuration Wizard Not responding. I've got a indirect SQL config for a DB connection and then I use that connection to pull values for various variables.

I'm using Visual Studio Professional 2012 11.0.61033.00 Update 4. Integration Services designer is version 11.0.3436.0

I tried the same package on VS 2010 and it works fine when I edit the package configuration.

I tried different variables, different dbs, removed all components for the package and still it hangs.

I've left it for 3 hours and eventually the wizard comes back - but obviously 3hrs to edit a package config value is unacceptable.

lcarpay SSC Veteran Points: 271 More actions · Answer 4

hi Tom, I have a work-around using BI Express from Pragmatic Works. No problems there.

I was also using indirect configuration (the Metadata connection in the XML and all of the variables in the SQL-table in the MetadataDB).

cheers, Leon

huishi.ca SSChasing Mays Points: 600 More actions · Answer 5

hi all :
Best solution I found is to update configuration table directly

For example: you've added a new user variable called DummyVariable (Int32, initial value is 9999) into the existing pkg and want to use pkg configuration to make it dynamic (we use sql server table to store), If using the GUI, depending on your luck, sometimes, the GUI will hang while sometimes it won't . If it does end up hanging, the best solution is to update Configurations table directly

insert [SSISConfig].[dbo].[SSIS Configurations]
( [ConfigurationFilter]
     ,[ConfiguredValue]
     ,[PackagePath]
     ,[ConfiguredValueType])
     Values
    (
    N'DummyFile2',
    N'9999',
    N'\Package.Variables[User::DummyVariable].Properties[Value]',
    N'Int32'

    )

Of course, it comes with some manual process. However, if you got stuck with pkg deployment mode or still using SSIS pre 2012, this is your best bet.

Cheers

Hui