Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS Config Wizard failing on SQL Server config


SSIS Config Wizard failing on SQL Server config

Author
Message
Angela Henry
Angela Henry
SSC-Enthusiastic
SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)SSC-Enthusiastic (148 reputation)

Group: General Forum Members
Points: 148 Visits: 285
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
sqlgirlatty
sqlgirlatty
Valued Member
Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)Valued Member (63 reputation)

Group: General Forum Members
Points: 63 Visits: 224
Did you ever get a resolution for this? I'm having the same issue on the same platform (Windows 7, Visual Studio 2008).
Paul Hernández
Paul Hernández
SSC-Enthusiastic
SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)

Group: General Forum Members
Points: 173 Visits: 654
Hi sqlgirlatty,

have you solved this problem?

Thanks in advance.

Paul Hernández
Daniel Bowlin
Daniel Bowlin
SSCrazy
SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)

Group: General Forum Members
Points: 2954 Visits: 2629
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
Paul Hernández
Paul Hernández
SSC-Enthusiastic
SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)SSC-Enthusiastic (173 reputation)

Group: General Forum Members
Points: 173 Visits: 654
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search