Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 SSIS Stand Alone

Author  Topic 

NeilG
Aged Yak Warrior

530 Posts

Posted - 2008-10-30 : 13:05:17
Hi Guys,

Thought it would be quicker and easier to ask you clever guys this one, the situation is as follows

Three Window servers
Two Sql Server Default instances on two of the servers
Intecration Services installed on the last server

or explanation sake SERVERONE and SERVERTWO are the two SQL instances
and SERVERSSIS is integration service server

We have created a SSIS package which has been Placed in the SSIS package default location which basically transfers data from one table in SERVERONE over to SERVERTWO

When we are trying to invoke the job from a SQL agent Job created on SERVERONE we are getting a error

"DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-10-30 16:14:30.18 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-10-30 16:14:30.65 Code: 0xC0202009

I have googled and there doesn't seem to be any answers to this problem, does anyone know if this is possible or should we just go for buying an extra license and installing sql server on the third server and just control it all from there

It's only really arose due to budgets

Any help will be apprciatiated please

**************************
Check Check and double check it's the safest way

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2008-10-30 : 13:24:47
what was security setting you gave while exporting the package to SERVERSSIS server?
Go to Top of Page

NeilG
Aged Yak Warrior

530 Posts

Posted - 2008-10-31 : 08:01:48
I have designed the package on the ssis server using bisdev and we can get the package to run by using the sql server agent that invokes the job windows domain account and making that account a dbo in the two databases and then setting the package security to run as EncryptSensitiveWithUserKey and it will run.

However this obviously creates a security problem having that account as a dbo on all the databases that a job will be require for.
Go to Top of Page

NeilG
Aged Yak Warrior

530 Posts

Posted - 2008-10-31 : 10:08:12
0
Go to Top of Page
   

- Advertisement -