Importing SSIS Package fails with Invalid characters

Question

Post reply

Importing SSIS Package fails with Invalid characters

Leo.Miller

SSChampion

Points: 13051
More actions
August 30, 2011 at 2:37 pm

#247352

I've recently installed SQL Server 2008R2 with SP2 and SSIS. When we try import SSIS packages from SQL 2005 we get the following error: "Object name "䎹녞숋㤧 " is not valid. Name must contain only alphanumeric characters or underscores "_".
Nothing unusual about the install, collation of SQL is Latin1_General_CI_AS.
Package is going to the File System, Package name is Package1 and protection level is "Keep protection level of the original package"
Has anyone seen anything like this. Any help would be appreciated.
Cheers
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.

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

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

Satya(SQLMaster) SSC Eights! Points: 872 More actions · Answer 1

Are you trying to import SSIS package from the file source or SQL Server?

If its from SQL server then check the collation settings.

Is this first time you attempted to import SSIS package from that SQL2005 instance?

-Satya SK Jayanty
SQL Server MVP (Follow me @sqlmaster)
Author of SQL Server 2008 R2 Administration CookBook
SQL Server Knowledge Sharing network

fornewbug SSC Journeyman Points: 88 More actions · Answer 2

Hi,

I'm getting similar error while trying to import a package from a file system to integration services. This error is coming for any package i try to import. Please help!

Thanks!

fornewbug SSC Journeyman Points: 88 More actions · Answer 3

We are using SQL server 2008 R2 isntance and i'm trying to import the package from local drives.

alex69ander69 SSC Enthusiast Points: 134 More actions · Answer 4

I had the same problem for the first time today.

I solved by saving a copy of the file as and then select Packagestorage my sqlserver and presto.

Hope it works for you too.

embooo SSC Rookie Points: 47 More actions · Answer 5

i know this post is old, but i just faced the same problem

i think you guys are using "sa" user and it does not have privilege on the folder holding the package, try to log in to SQL with windows authentication , and try to import the package then.

worked for me, hope it will work for you.

andrew.wilson 51581 SSC Enthusiast Points: 180 More actions · Answer 6

I had this problem with two packages, and tried everything I could think of, changing the package name, changing the source file name in BIDS, and other stuff. In the end I restarted SQL Management Studio and tried again and the error had gone.