After you migrate your database, the Inventory Source may no longer appear in in Snow Management and Configuration Center (SMACC). When you try to add it again, you might see this message:
“The inventory source [SnowInventory] will not be added due to missing columns. Please verify that the database [SnowInventory] is of a valid database type.”
You may also notice that the Data Update Job (DUJ) stays in a running state because no input data is available. This article helps you identify the cause and fix the issue.
IMPORTANT: Always back up the database before making direct SQL changes.
1. Review Flexera support policy
- Flexera Support doesn’t support database migration. If you need guaranteed assistance, contact your account representative to ask about Flexera Professional Services (additional costs may apply).
- If you’re migrating on your own, make sure you meet all prerequisites. See Database migration prerequisites.
2. Reconfigure database connections
After the migration is complete:
- Open Snow Inventory Server Configuration Manager and reconfigure the database connection.
- Open the Snow License Manager Web Configurator and reconfigure its database connection.
- Verify if the Inventory Source is now visible in SMACC.
3. Verify SQL permissions
If the Inventory Source still doesn’t appear:
- Make sure the
LicenseManagerUseraccount has the required SQL permissions. - Follow the instructions in SQL script to check the database permissions for LicenseManagerUser to check the SQL server permissions for
LicenseManagerUserfor required roles and rights. - Correct any missing permissions and try adding the inventory source again.
4. Investigate why the DUJ is hanging
If the DUJ runs continuously after adding the Inventory Source, run these SQL queries against the SnowLicenseManager database:
SELECT * FROM SnowLicenseManager.dbo.tblCIDDataSource;
SELECT * FROM SnowLicenseManager.inv.tblSite;
Look for:
- Any record with CID = 0
- A mismatch between SourceId and CID values
5. Correct any SourceId and CID misalignment
If you find mismatched records:
- Find the correct
SourceIdandCIDvalues intblCIDDataSource. - Identify the incorrect record in
inv.tblSiteusing itsSiteId. - Update the record (back up the database first):
UPDATE SnowLicenseManager.inv.tblSite
SET SourceId = <CorrectSourceId>, CID = <CorrectCID>
WHERE SiteId = <ProblematicSiteId>;
Run the DUJ again to confirm it completes successfully.
Related Articles
Step 10001 in the im-mig1230-migpost.sql inventory database migration script may fail with error: "Violation of PRIMARY KE… 4Number of Views "Incompatible plugin(s) detected" when opening Snow Management and Configuration Center (SMACC) 26Number of Views Database migration may fail during upgrade if SQL Server instance does not have certificates installed to cover all FlexNe… 5Number of Views Known Issue: Database migration may fail if database is restored on to a SQL Server 2017 (or later) instance that does not… 23Number of Views SendSoftwareBundle inventory import step reading from ILMT SQL Server database may fail with error: "The given value of ty… 4Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago