SAP reconciliation failure

[SRicky]

Dear all

When tried to click current license position under SAP>License Position but error occurred. having error mentioned inline

A Problem Occurred SAP>License Position: {LandscapeName} FlexNet Manager Platform detected a problem and could not complete your request.  Error SAP license position calculation failed with error message An error has occurred during SAP license position calculation: OLE DB provider 'STREAM' for linked server '(null)' returned invalid data for column '[!BulkInsert].Consumed'

Please suggest 

[JohnSorensenDK · Accepted solution]

@SRicky 

Although you didn't include the complete error message I did a quick search based on the error and found that something like this can happen in situations where one of the metrics in the divider of a formula is 0, e.g. Metric(5001)/Metric(5001)*2000 which fails if Metric(5001) is '0'

If you find something like that you can replace the formula with If(Metric(5001)>0, Metric(5001)/Metric(5001)*2000, 0)

Thanks,

[vikasvijayan]

We have a similar problem with the following error. Where do we find the metric which is causing. This is since the upgrade from FNMS 2015 to FNMS 2020 R2

FlexNet Manager Platform detected a problem and could not complete your request.

[ERROR 2021-10-19 07:08:35,606 34655ms Global ] Unhandled exception
System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.Data.SqlClient.SqlException (0x80131904): Divide by zero error encountered.
at Flexera.Portal.Web.Controls.PortalPage.DataBind(Boolean p_RaiseOnDataBinding)
at Flexera.Portal.Web.Controls.PortalPage.OnPreRender(EventArgs p_EventArgs)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
ClientConnectionId:e67e4f84-edfb-45cf-824a-fafccd58d369
Error Number:8134,State:1,Class:16

[JohnSorensenDK]

@vikasvijayan 

I think that you got your issue resolved through a support case.

Therefore this response is merely to close the loop and update the community about the fact that Microsoft SQL Server 2019 introduced some new features that may cause symptoms like you've seen. Please refer the SQL Server 2019 specific section in to https://docs.flexera.com/FlexNetManagerSuite2021R1/EN/SysReq/index.html#FNMS_sys_req/RN_sys_req_prereq.html for further details on how to avoid running into these.

Thanks,