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.
| Author |
Topic |
|
rlaubert
Yak Posting Veteran
96 Posts |
 Posted - 2008-09-16 : 14:16:35
|
| I was wondering if you might be able to help. I have about 18 jobs currently set up on our clustered SQL 2005 Enterprise environment. They all used to work prior to the upgrade to Enterprise from SQL Server 2005 Standard. Since the upgrade 5 SSIS created jobs no longer run on DB2 when it is active. The same jobs run fine on DB1 when it is active. Currently we fail over every night (don't ask :) )so the jobs run every other night (db1 online). The jobs are the same since they are part of the clustered SQL. The accounts are the same, security is the same, server configurations and SQL configurations are the same.I get an error message that states:Executed as user: 'Domain'\'Account'. ...ion 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:30:00 AM Error: 2008-09-16 01:30:01.20 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Property" 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-09-16 01:30:01.20 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Property" 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 Progress: 2008-09-16 01:30:01.43 Source: AutoEscalation Login The Web Service task ... The package execution fa... The step failed.The 'Account' in use, is a domain account, currently with sysadmin rights in SQL and members of SQLService, ServiceAccounts, and Domain Users Groups. SQLService is a member of the Local Admin Group on both servers.Given all the above, the assumption is that there is a configuration issue with DB2 that is different from DB1 since it works on one server but not the other. I have tried to verify every aspect but apparently I am missing something. I have verified file locations, server configurations, SQL configuration, security configuration. I currently do not have the soruce code for the SSIS, but am trying to track it down. I did review the article at http://support.microsoft.com/kb/918760 and it does not seem to apply if for no other reason than the jobs do run on DB1 and almost all files and databases are shared on the cluster.Any help would be appreciated.Raymond LaubertMCSE, MCDBA, MCITP:Administration, MCT |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-16 : 14:32:25
|
| Is SSIS installed properly in 2nd node? I think the issue is "Protection Level" of those packages. We use 'Rely on server storage". |
 |
|
|
rlaubert
Yak Posting Veteran
96 Posts |
Posted - 2008-09-19 : 16:02:43
|
| Actually, the problem was that SP2 was not applied to the second server. For some reason it was missed when applied. Found it when I started comparing versions to see what was different.Raymond LaubertMCSE, MCDBA, MCITP:Administration, MCT |
|
|
|
|
|
|
|
|
Some jobs fail after failover...