Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Config Wizard failing on SQL Server config Expand / Collapse
Author
Message
Posted Monday, July 18, 2011 10:57 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 16, 2013 6:50 AM
Points: 139, Visits: 269
We have a SSIS package that has been developed in VS2008. Our company standard is to have package configuration enabled and use both XML and SQL Server Configuration values. The XML configuration points to the configuration server\database and then all subsequent Configurations are typically SQL Server. We stored connection strings, UNC paths, etc, in the SQL Server configurations.

We have a package that was created about 2 months ago, all configurations were set up in SQL Server using the SSIS Configuration wizard at that time. I recently needed to modify the package and add an additional SQL Server configuration. I used the wizard, just like always, and it came back with:

"Could not Complete Wizard Actions."
"Cannot insert configuration information into the configuration table."
(Microsoft.DataTransformationServices.Wizards)

When I run a profiler trace on the configuration server, I see the error:

"Error: 8152, Severity: 16, State: 13
String or binary data would be truncated"

Simple enough, I'm trying to insert something that's too big for the columns. However, it's not so simple. All the values I'm inserting are less than the respective column lengths. I can even copy the values out of the wizard window and paste them into a query window and insert them manually into the configuration database with success.

Anybody else run into this?

All my other packages (in different solutions) seem to work just fine, however they are in different schemas.

Pertinent Info:
SSIS configuration server: SQL Server 2008 R2, SP1, 64-bit
Visual Studio: 2008, Version 9.0.30729.4462 QFE
My machine: Windows 7 (Virtual), 64-bit
Post #1143547
Posted Thursday, January 31, 2013 12:51 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, April 04, 2014 2:14 PM
Points: 61, Visits: 194
Did you ever get a resolution for this? I'm having the same issue on the same platform (Windows 7, Visual Studio 2008).
Post #1414296
Posted Monday, February 18, 2013 8:00 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 10, 2014 5:48 AM
Points: 107, Visits: 436
Hi sqlgirlatty,

have you solved this problem?

Thanks in advance.


Paul Hernández
http://hernandezpaul.wordpress.com/
https://twitter.com/paul_eng
Post #1421235
Posted Monday, February 18, 2013 8:14 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 14, 2014 2:16 PM
Points: 2,812, Visits: 2,543
I ran into this problem, or at least a problem with the same symptom. The solution was to go back to the connection editor. On the All tab there is a property called "Application Name" that usually has a really long value that typically starts with SSIS, then your package name, then a GUID then the name of the connection. I usually remove all the stuff in the middle so that all I have left is SSIS.ConnectionName
Post #1421240
Posted Monday, February 18, 2013 9:27 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 10, 2014 5:48 AM
Points: 107, Visits: 436
Thanks Daniel for your quick reply.

In my case the problem was the connection string of the Cozyroc Dynamics CRM Destination. It has a long connection string. The solution was to store only the parameters that I really need and not the whole string, i.e. the Organization Name, Server Host, Server User, etc.

At the end the common symptom is the length of the value to be stored, which must not exceed 255 characters.

Kind Regards


Paul Hernández
http://hernandezpaul.wordpress.com/
https://twitter.com/paul_eng
Post #1421269
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse