SSIS SQL Server 2012 - Salt Attribute Missing in project manifest

1,012 views
Skip to first unread message

sutt...@plu.edu

unread,
Oct 22, 2013, 6:04:33 PM10/22/13
to coz...@googlegroups.com
I'm receiving an error 'Salt' attribute for ServerPassword is missing in the project manifest when attempting run any package that uses a Salesforce Destination or Source using CozyRoc.  I'm using project level security (encrypt sensitive with password).  This is set at the project level and at package level within VS.
 
I've tried removing the connection and creating a brand new one updating each of the packages to use the new one and I still receive the error. It seems to only affect my cozyroc connection.
 
I'm trying to avoid creating package level connections because that would require me to maintain it 50 times.  (Using 1.6.4 of SSISPlus)
 
Lennie Sutton

Ivan Peev

unread,
Oct 22, 2013, 7:45:17 PM10/22/13
to coz...@googlegroups.com, sutt...@plu.edu
Hi Lennie,

I believe this is a bug in SQL 2012. Check here.

William Beasley

unread,
Sep 24, 2014, 1:46:41 PM9/24/14
to coz...@googlegroups.com, sutt...@plu.edu
I am running into the same error.  I am trying to use project connections to simplify the connection process with multiple packages.  I am also using encrypt sensitice with password option.  My local machine is on SP1 and has the error.  But I also have on server that does not have SP1 applied with the error.  Did the service pack or the hotfix address your issue?  I have downloaded the hotfix but apparently doesn't apply if you have SP1.  But a posting (MS Connect Bug) on the problem made it seem like the problem exists in SP2 but wanted to check with the CozyRoc folks on their perspective.

William Beasley

unread,
Sep 24, 2014, 1:44:45 PM9/24/14
to coz...@googlegroups.com, sutt...@plu.edu
I am running into the same error.  I am trying to use project connections to simplify the connection process with multiple packages.  I am also using encrypt sensitice with password option.  My local machine is on SP1 and has the error.  But I also have on server that does not have SP1 applied with the error.  Did the service pack or the hotfix address your issue?  I have downloaded the hotfix but apparently doesn't apply if you have SP1.  But a posting (MS Connect Bug) on the problem made it seem like the problem exists in SP2 but wanted to check with the CozyRoc folks on their perspective.

On Tuesday, October 22, 2013 5:04:33 PM UTC-5, sutt...@plu.edu wrote:

Ivan Peev

unread,
Sep 24, 2014, 6:05:30 PM9/24/14
to coz...@googlegroups.com, sutt...@plu.edu
Hi William,

I would recommend you contact MS for further information. There is nothing we can do about this issue. It is a bug in SSIS.

sutt...@plu.edu

unread,
Sep 25, 2014, 1:30:29 PM9/25/14
to coz...@googlegroups.com, sutt...@plu.edu
Hi, All,

I was able to work around the issue by doing the following:

1.       Choose “Do Not Save Sensitive Information,” at the project and package levels. 

2.       Instead, submit the credentials at runtime through the new Project Parameters feature in SQL Server 2012.

We’ve been running SSIS with CozyRoc that way for nearly a year now and it has been without any issues. 

 

  You just select your project connection in the Connection Manager at the bottom of your package screen, right click and choose Parameterize.  You can do the connection string and then do one for the password.  These can then be entered when you schedule the job.  This should complete avoid the SALT error when that username and password are saved directly in the connection manager.

 

   On the other hand, it may have been fixed since CU 6.

 

   Here is the current list of SP1 CUs for 2012 that have been released. 

   

http://support.microsoft.com/kb/2772858

 

Looks like the last one released was CU 12 on September 15, 2014.  I haven't tried going back to what I had, as I really like the parameter option better anyway so it will be kept separate from the package.


HTH, Lennie

William Beasley

unread,
Oct 2, 2014, 5:21:41 PM10/2/14
to coz...@googlegroups.com, sutt...@plu.edu
Thanks for recommending Project Parameters.  They were great.   
I like the idea of protecting sensitive data but not at the expense of making the process unusable in a multi-developer scenario.

Plus in this integration scenario its really not that big a deal if its protected or not.

Thanks again.

--
You received this message because you are subscribed to a topic in the Google Groups "COZYROC" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cozyroc/VN0m6qihKWc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cozyroc+u...@googlegroups.com.
To post to this group, send email to coz...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cozyroc/a8a91030-a37d-4fc8-a330-0820a85f227c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages