Description:

This document describes how to resolve "Database Exception" errors found in a core servers Event Viewer.  Event ID 4100 and sourced from the "Landesk Inventory Server".

Database exception: EXAMPLE.scn, LDInv.dll

-2147467259

Data provider or other service returned an E_FAIL status.

Error committing on table :   DATA PROVIDER OR OTHER SERVICE RETURNED AN E_FAIL STATUS.

     Increased column size might be necessary, Thread ID:

Cause:

Inventory scans sent to the core server contain attributes whose values exceed the amount of characters allowed in database schema of the attributes associated column.

Resolution:

In order to resolve these error we must increase the column size(VARCHAR) for the effected attributes. This must be adjusted in the core servers database schema configuration file (Datamart.xml) otherwise your changes may be overwritten by "CoreDBUtil.exe"

Updating database schema

The database schema is configured in DataMart.xml. After modifying this configuration you can apply the changes to the database using CoreDBUtil.exe . Both "Datamart.xml" and "CoreDBUtil.exe" can be found in the core servers installation directory. (Program Files\LANDesk\ManagementSuite)

Modifying the Database Schema Configuration:

1. Open "Datamart.xml" in notepad or your preferred text editor
2. Modify the "Varchar" value of all the effected columns to "Varchar(MAX)"

   • Effected Tables/Columns

     Tables	Columns	Modifications
     BiosSettings	CurrentSetting
     BiosSettings	PossibleValues
     EnvironSettings	Name
     EnvironSettings	ValueString
     PeripheralAdapters	Type
     Printer	Version
     Services	Path
     Services	Description
     Video	DriverName

3. Save Datamart.xml
4. Apply Configuration changes to the Database
   

Apply Configuration Changes

1. Stop the "LANDesk Inventory Server" service.
2. Navigate to Program Files\LANDesk\ManagementSuite
3. Launch CoreDBUtil.exeas administrator
4. Click "Build Components"
5. Click OK when complete
6. Restart the "LANDesk Inventory Server" service
7. Confirm resolution by reprocessing scans

Manually Updating the Database Table Schema

If a database is hosted in an SQL Cluster or if "CoreDBUtil.exe" fails to commit the changes for any reason you will need to update the effected tables in your LDMS Database manually using SQL Management Studio.

1. Allow saving changes to the DB tables.
   • Navigate to "Tools > Options > Designers" and Uncheck "Prevent saving changes that require table re-creation"
2. To increase this value, run the following in a new SQL query:

alter tableBiosSettingsalter column CurrentSettingnvarchar(max);

alter tableBiosSettingsalter column PossibleValuesnvarchar(max);

alter table environsettingsalter column namenvarchar(max);

alter table environsettingsalter column valuestringnvarchar(max);

alter tableperipheraladaptersalter columntypenvarchar(max);

alter tableprinteralter columnversionnvarchar(max);

alter tableservices alter column path nvarchar(max);

alter tableservices alter column description nvarchar(max);

alter tablevideoalter column drivernamenvarchar(max);

Confirm resolution by reprocessing scans

Confirm Resolution

To validate that the changes were applied as expected you can "re-process" your failed scans

1. Navigate to Program Files\LANDesk\ManagementSuite\ldscan\ErrorScan Your
2. Move all files that have been modified within the last 24 hours to Program Files\LANDesk\ManagementSuite\ldscan\ the

• It is common for scans to become out of sync after recovering from errors. If your scans return to "ErrorScan" you should review the Event Viewer to validate the cause.

• Out of Sync Scans are moved to "ErrorScan" and log as Warnings in the Event Viewer