IBM License Metric Tool (ILMT)

 View Only

 Getting error messages after migrating ILMT

C Powers's profile image
C Powers posted Thu May 29, 2025 03:26 PM

Support -

We have migrated the ILMT application (9.2.36.1) from Windows 2012 to Windows 2022 and migrated the database from SQL 2014 to SQL 2022 using the migration steps.

We are seeing the below error messages during the data import:

 "Language for connection changed!"

"The database that you added is not a valid Bigfix database"

Application AI-generated content may be incorrect.

With regards to "Language for connection changed!" error message, we see the following:

  • On the old SQL server 2014, the Default language is assigned as “English”.
  • On the new SQL server 2022 server, the Default language is assigned as “English - us_english".

Per the Vendor docs..."Ensure that the MS SQL Server user has the default language set to "English" (not a variety of English)."

However, when the database admin looks on SQL 2022 there is no default language option of just "English"

Please advise next steps for resolution on how to select "English" (only) as the default language in SQL 2022?

Also, asking if this is related and causing the issue with the second encountered error message: The database that you added is not a valid Bigfix database"??

Thank you

Oktawian Powązka's profile image
Oktawian Powązka posted Fri May 30, 2025 04:40 AM

Hi,


With regards to "Language for connection changed!" message.
As you can see it's not an ERROR...it's just informative message which always shows up if Debug logging is being used.


As to "The database that you added is not a valid Bigfix database" issue,
Have you also migrated the Bigfix database ?
If so, has anything (like host/authentication) changed ?
To move forward please open up 'Management: Data Sources' panel and re-Save the existing Bigfix Data Source.
In case of any connection/database consistency related issues the corresponding error will be placed in tema log.

"The database that you added is not a valid Bigfix database" shows up when DBINFO table in can't be located.

C Powers's profile image
C Powers posted Fri May 30, 2025 08:33 AM

Oktawian - 

Wanted to provide an update...

Somehow the database schema was incorrectly changed for the account making the connection.

Once properly set, it resolved the issue and connection and data imports were successful.

Thanks for you assistance on this.

Oktawian Powązka's profile image
Oktawian Powązka posted Fri May 30, 2025 12:48 PM

In recent versions there is a dedicated message addressing user's default schema problem :
A user's default schema must be set to 'dbo'. Currently, it is set to database schema xxx

Related Content