Highlighted
Intrepid explorer

Re: Error ComplianceMigration - FNMS 2019 R2 + SQL Server 2017 - Flexera Signed Security Certificate for SQL Server 2017

Jump to solution

Hi Dennis,

For you next migration project: You could try to temporarily turn off CLR strict security on SQL Server 2017 and then re-enable it after your FNMS Database migration scripts have completed?

EXEC sp_configure 'show advanced options', 1
RECONFIGURE;
EXEC sp_configure 'clr strict security', 0;
RECONFIGURE;

0 Kudos
Highlighted
Active participant

Re: Error ComplianceMigration - FNMS 2019 R2 + SQL Server 2017 - Flexera Signed Security Certificate for SQL Server 2017

Jump to solution

Query from @erwinlindemann didn't help me, but running this query helped me:

ALTER DATABASE [FNMSCompliance] SET TRUSTWORTHY ON
GO
USE [FNMSCompliance]
GO
EXEC sp_changedbowner 'sa'
GO

 

Source:  https://support.microsoft.com/sk-sk/help/918040/you-may-receive-an-error-message-when-you-try-to-run...