leogeeko asked a question.
Hey All!
Did you guys ever faced that error on reconcile before? I am pretty sure I saw them in the Cloud Edition but, of course, Flexera always fix it. I am interested to know how to fix it on the on-premise solution as well. Any clues where to start?
Thanks!
Leo
Hi Leonardo,
I would always start with the log file from the inventory import. It usually gives the specific step in which the error occurred.
From there I would take the SQL code and run it manually from the SQL Server Management Studio. In some cases, when statements consume temp data, prerequisite queries need to be run before the actual statement can be executed.
Ideally, if you start breaking down the statement, you should find the specific line in code and hopefully the responsible data as well.
Sounds to me like it tries to separate data from a string, but the charater for "cutting" cannot be found. Like with DomainName\Username.
Best regards,
Markward
Markward is correct, the couple of times we've seen this is where the query is not able to split out a string.
In addition to what Markward suggested, the other 2 bits of information that would be useful here are:
For number 2, you can find this in the log that Markward suggested.
I can see a couple of older bugs (most recent was fixed in 2017 R2 and that was for the App-V standalone adapter) so the information above will help confirm if it's an issue that has been resolved already in later versions or not.
Hey Guys!
Just to give you a feedback on this, the problem solved when I reviewed the DATABASE configurations and found that the Database was not with compatibility level set to "SQL Server 2014 (120)". After changing this and giving a couple of days, the system worked as intended.
Cheers!
Hi,
I had the error in a test FNMS 2020 R2 VM and solved it by installing the latest SQL Server 2019 cumulative update (11) as mentioned here: https://community.flexera.com/s/FlexNet-Manager-Knowledge-Base/SQL-Server-2019-Needs-Cumulative-Update-Package-5-or-later-for169557
Best regards,
Markward
Hey Guys!
Just to give you a feedback on this, the problem solved when I reviewed the DATABASE configurations and found that the Database was not with compatibility level set to "SQL Server 2014 (120)". After changing this and giving a couple of days, the system worked as intended.Cheers!