Description

Applies to LDMS 8.7, 8.8, 9.0

After deleting a node from the LDMS Console and refreshing the node pops back up into the list.

Console.exe.log:

3/7/2008 10:03:56 AM : Critical Exception: System.Runtime.InteropServices.SEHException: External component has thrown an exception.

at IDALLib.IDALRecordsetClass.DeleteDevices(String conStr, Object& pvtDevices)

Or:

Database.ExecuteDataTable: System.Data.OleDb.OleDbException: Invalid object name 'AlertRulesetDeployment'.

Key Words: Unable to Delete Nodes, Can not Delete Nodes, Cannot Delete Nodes, Unable to Delete Devices, Can not Delete Devices, Cannot Delete Devices.

Cause

A database table is being referenced in the delete query that no longer exists. The list of tables is created from the METAOBJATTRRELATIONS table.

Or the delete operation fails to delete dependant data prior to deleting parent data.

Resolution

For LDMS 9.0 Only, apply patch DB-4196790. Reboot is required!

If the problem still exists or for 8.8 or prior versions see below.

1) Stop all the LANDesk & Intel services

2) Backup the LANDesk DB

3) For SQL Databases

delete from METAOBJATTRRELATIONS where tablename in (select distinct tablename from METAOBJATTRRELATIONS where tablename not in(select table_name from information_schema.tables))

4) For Oracle Databases

These commands should be run by an Oracle DBA. First you must compare the meta data with the actual data, replace the word 'LANDESK' with the correct user.

select upper(tablename) from METAOBJATTRRELATIONS 
 minus 
 select table_name from all_tables where owner = 'LANDESK';

This will return the result you will use with the next statement to delete the bad reference. DO NOT DELETE VIEWS, only delete the incorrectly referenced table which is generally ALERTRULESETDEPLOYMENT.

Run the next command to remove the invalid table reference.

Replace the  with the result tablename (not views) returned in the first query.

delete from METAOBJATTRRELATIONS where upper(tablename) = '

Run DBRepair.exe Then CoreDBUtil.exe

-DBRepair

4) Download the Correct version of DB Repair from: Community Doc DOC-2297

http://community.landesk.com/support/docs/DOC-2297

5) Copy the file to ...\LANDesk\ManagementSuite.

6) Stop the LANDesk Inventory Server Service.

7) Run DBRepair (DO NOT Run from a share (ldmain))

8) Click on each item except for anything under "Custom Data" and click the clean button.

9) Close DBRepair.

-CoreDBUtil

10) Run CoreDBUtil.exe from ...\LANDesk\ManagementSuite\

11) Click the Build Components button (This compares the database to the file Datamart.xml and makes repairs. It usually takes 5-15 minutes. DO NOT Stop the process!!!)

12) When the Build Components process finishes A Message will appear that says.

13) Close CoreDBUtil.

14) Start the LANDesk Inventory Server Service.

15) Start the LANDesk & Intel services that had been stopped in step 1 or alternatively reboot the core server.

DBRepair can be found here:

http://community.landesk.com/support/docs/DOC-2297

NOTE: An issue has been resolved with the upgrade from 8.7 SP5 to 8.8 with the following SQL Query:

Update metaobjattrrelations set tablename = 'UNMODELEDDATA' WHERE TABLENAME = 'ALERTRULESETDEPLOYMENT'

Article on how to install Microsoft SQL Management Studio Express and Run a query:

http://community.landesk.com/support/docs/DOC-5764