January 20, 2010 at 11:39 am
This issue seems to be intermittent. We have 5 SQL Server 2005 machines. Trust has been established between all. On occasion an SSIS package fails with the error - 'current security context is not trusted.' What else should I be checking, and how do I get these jobs to run?
January 20, 2010 at 1:16 pm
Are the databases on the two different servers owned by the same login?
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 20, 2010 at 1:36 pm
Yes, both databases are owned by 'sa'
January 20, 2010 at 2:14 pm
SSIS using Windows Auth for the connections?
January 20, 2010 at 2:18 pm
It looks to be an issue with cross database chaining..to fix it you will need to run the script below on both databases:
ALTER DATABASE db SET DB_CHAINING ON
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 20, 2010 at 2:26 pm
Nicholas - yes SSIS is using WinAuth for connections
The_SQL_DBA - ran the script on both DBs and no change in error.
January 20, 2010 at 8:43 pm
Check the windows system and application event logs for errors as regards AD/LDAP.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply