A new Flexera Community experience is coming on November 25th. Click here for more information.
Hello everyone!
Everything run pretty smooth, the Config.ps1 started to execute, configured a lot of credentials until the following error ocurred:
Executing step Configure FNMP database for operators. C:\Flexera\FlexNet Manager Suite\Support\Config.ps1 : Exception calling "ExecuteNonQuery" with "0" argument(s): "Error 515, Level 16, State 2, Procedure ResetCognosRole, Line 27, Message: Cannot insert the value NULL into column 'GroupID', table 'FNMSCompliance.dbo.RoleRight_MT'; column does not allow nulls. INSERT fails." At line:1 char:1 + .\Config.ps1 ".\Config\FNMS Windows Authentication Config.xml" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Config.ps1], MethodInvocationException + FullyQualifiedErrorId : SqlException,Config.ps1
Any Ideas?
Thanks!!!
‎Mar 18, 2020 04:06 PM
Hi Leonardo,
Interpreting the error message from your PowerShell script:
In FNMS, for configuring the COGNOS Reporting (aka "Flexera Analytics"):
The default installation will create one FNMS role named "Business Reporting Portal Admin" that is configured as described above. This role may be assigned to a single user only.
In FNMS, can you go to 'Admin (cogs) > Accounts > Roles" and make sure your system is configured like this before re-running the PowerShell script, please?
‎Mar 19, 2020 01:43 AM
Hey thanks for the reply.
The problem is that I don´t even have a web ui ready yet as the config.ps1 script is getting this error. Wierd that he is executing everything right and exits in this part. Any other ideas?
Thanks!
‎Mar 19, 2020 03:48 PM
Hi Leonardo,
Ah ...
To work around this problem, I would suggest to:
That should be it ...
‎Mar 19, 2020 05:54 PM
Thanks!
In the end a bunch of other problems started to show up until I´ve noticed that for some wierd reason the SQL Server machine was in the domain but had no trust relationship with it.
For the records, the customer is a huge world service provider which uses Apache Guacamole to access their servers which creates "temporary" administrators in the machine everytime you access it. In the end I rejoined the machine to the domain after erasing everything in the AD and reinstalled SQL Server after that.
So finally, things worked as it should.
Cheers!
‎Mar 21, 2020 05:53 AM