Error using /SET

I have a data importing .dtsx file that I would like to point towards another server on occasion. I tried:

DTEXEC /FILE "fubar.dtsx" /SET "\Package.Connections[ConnectionManagerName].Properties[ConnectionString];Data Source=NEWSVR;Initial Catalog=Fubar;Provider=SQLNCLI;Integrated Security=SSPI;Auto Translate=False;" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

but I keep getting the error:

Argument ""\Package.Connections[ConnectionManagerName].Properties[ConnectionString];Data Source=NEWSVR;Initial Catalog=Fubar;Provider=SQLNCLI;Integrated Security=SSPI;Auto Translate=False;"" for option "set" is not valid.

Staring at the XML within the .dtsx file gave me no insight other than I suspect the "ConnectionManagerName" is the problem. How do I figure out the magic incantation? It's definitely not as trivial as using '-S NEWSVR' on SQLCMD!
You need to put double quotes around the connection string, first of all.

You also might want to try using the /CONN switch instead. Search this forum for examples.

Error saving package to msdb (IA64 - April CTP)

When attempting to save a copy of my .dtsx package (from BI Dev Studio), I get the following error. Any one have any ideas? - note: This is an IA64 machine running W2k3 Server (SP1). If I select * from msdb.dbo.sysdtspackages90 I get no rows.

Thanks!
=============================================

The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.). The SQL statement issued has failed.
(Microsoft Visual Studio)

-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.ExistsOnSqlServer(String packagePath, String serverName, String serverUserName, String serverPassword)
at Microsoft.DataTransformationServices.Controls.PackageLocationControl.SavePackage(Package package)
at Microsoft.DataTransformationServices.Design.Controls.PackageSaveCopyForm.PackageSaveCopyForm_FormClosing(Object sender, FormClosingEventArgs e)

=============================================

The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.). The SQL statement issued has failed.

-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.ExistsOnSQLServer(String bstrPackagePath, String bstrServerName, String bstrServerUserName, String bstrServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.ExistsOnSqlServer(String packagePath, String serverName, String serverUserName, String serverPassword)

Additional Info: I've been checking the public newsgroups and this error appears with SQL2000, too. Most proposed solutions relate to certificates being installed. I've checked the various places (xyz\certificates\personal) where the problem certificates might be and have found none, so uninstalling these certificates is not a solution.

Any other ideas? Any would be appreciated!

Thanks!|||I just blogged about this:
http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/09/15772.aspx
Basically, with earlier CTP releases you have two options, supply a self signed cert to the server or upgrade to the June CTP.
Thanks,
K