A missing stored procedure like this suggests that the earlier step to configure your databases wasn't done successfully, or maybe the name of the wrong database was entered for the compliance database name somewhere. Check that the stored procedure dbo.ComplianceOperatorCreateOperatorWithTenantPermission exists in your compliance database - if not, review the logs from when you set up the database to check for errors.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
Building on steven_donovan1's point, it looks like you do have support access. To file a ticket, sign in to community, click "Get Support" in the top navigation and select "Open New Case"
If you appreciate my efforts, please give me a kudo Accept as solution to help others find it faster.
cd drive-and-path\FlexNet Manager Suite\Support .\InstallFNMS.ps1 $FnmpInstallerMsi $AnswerFile $FNMSConfigFile
-> Executing step Configure FNMP database for operators. C:\Temp\FlexNet Manager Suite\Support\Config.ps1 : Exception calling "ExecuteNonQuery" with "0" argument(s): "Could not find stored procedure 'dbo.ComplianceOperatorCreateOperatorWithTenantPermission'. . This could mean the database is incomplete.
A missing stored procedure like this suggests that the earlier step to configure your databases wasn't done successfully, or maybe the name of the wrong database was entered for the compliance database name somewhere. Check that the stored procedure dbo.ComplianceOperatorCreateOperatorWithTenantPermission exists in your compliance database - if not, review the logs from when you set up the database to check for errors.
(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
Build completed , i would say be careful which account is used during the build. i would recommend using the service account through out the build. The documentation refers to an admin account that needs permission that have not been granted ( probably user error) which cause the build to fail.
