Problem
You are unable to see all inventory for mobile devices inside the core console. You may see blocked inventory in Configure Software Services. Queries you create to return mobile inventory may return no results as the scanner data has not database tables to populate the mobility data being sent from the scanner. This is not an issue for customers who upgraded from earlier versions of mobility but is an issue for those who have a clean install of LDMO.
Symptoms
You will see these errors when trying to do an inventory sync:
Log Name: Application
Source: LANDesk Inventory Server
Date: 12/3/2013 8:36:43 AM
Event ID: 4100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXX
Description:
Database exception: 0d73.02f67e67d30fec1.scn, LDInv.dll
-2147467259
Unspecified error
Computer.Mobile Android Program.Application Name is an unmodeled one-to-many relationship. This is not supported., Thread ID: 5316.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LANDesk Inventory Server" />
<EventID Qualifiers="0">4100</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-12-03T15:36:43.000000000Z" />
<EventRecordID>626607</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
<Data>0d73.02f67e67d30fec1.scn, LDInv.dll
-2147467259
Unspecified error
Computer.Mobile Android Program.Application Name is an unmodeled one-to-many relationship. This is not supported., Thread ID: 5316</Data>
</EventData>
</Event>
Your LDMS database will be missing the following tables:
O_MobileProfileConfigInfo
O_MobileAndroidAccount
O_MobileAndroidAdmin
O_MobileAndroidPolicy
O_MobileAndroidPermission
O_MobileAndroidProgram
O_MobileIosProfileRestrict
O_MobileIosGlobalRestrict
O_MobileIosProfileContent
O_MobileIosProvProfile
O_MobileIosProfile
O_MobileIosPolicy
O_MobileIosCert
O_MobileIosProgram
O_MobilePhone
O_MobileIosDevice
O_MobileIdentity
Solution
You will need run CoreDBUtil.exe to add a missing datamartLMM.xml file on your core. This datamartLMM.xml file is attached to this article.
To do this you will need to save the datamartLMM.xml to a location on your core and open a command prompt window, and run the following command;
ManagementSuite\CoreDBUtil.exe /xml=[Path to datamartLMM.xml]\datamartLMM.xml
This will create the missing tables and then you should be able to sync all inventory and attributes to your core.