K
krakdcorn
Guest
Not to rule anything out here - this is a phenomenon that occurred a few minutes ago.
There are several packages handled through an ispac project in our repository. After upgrading from the SSDT 2012 to SSDT 2015 (which is compatible with VS2017). I see three system errors in the RestartManager EventID 10006:
In the security section, I see Audit Failure Event5061 Cryptographic Operation
As a rule, our systems are enclosed and we cannot use passwords - only certificates, the package is set to a default of DontSaveSensitive. I suspect that given the cryptographic error the package reloads on a crash with EncryptSensitiveWithKey. I don't believe the behavior is desired for my situation during a crash.
Result of the above errors :: Integration Services was disabled and required a reinstall (sort of) to re-enable it.
How can the server be set to default back to DontSaveSensitive if there is a crash and the project restarts?
Continue reading...
There are several packages handled through an ispac project in our repository. After upgrading from the SSDT 2012 to SSDT 2015 (which is compatible with VS2017). I see three system errors in the RestartManager EventID 10006:
- SSIS Debug Host could not be shut down
- Microsoft Visual Studio 2017 could not be shut down
- PerfWatson2.exe could not be shut down
In the security section, I see Audit Failure Event5061 Cryptographic Operation
As a rule, our systems are enclosed and we cannot use passwords - only certificates, the package is set to a default of DontSaveSensitive. I suspect that given the cryptographic error the package reloads on a crash with EncryptSensitiveWithKey. I don't believe the behavior is desired for my situation during a crash.
Result of the above errors :: Integration Services was disabled and required a reinstall (sort of) to re-enable it.
How can the server be set to default back to DontSaveSensitive if there is a crash and the project restarts?
Continue reading...