jakecornejo We had a similar problem, where our asset DB was corrupted by the NPM asset discovery. We raised a call to Solarwinds support (Case # 606976), who after some trials and tribulations, gave us the following SQL to delete all assets from Web Help Desk and reset the asset_id to 0.
This is of course destructive and will delete all assets and break all associated purchase orders and assets within existing tickets.
I would strongly advise on a backup of the database, or at least the tables mentioned, possibly even raise it as a call to SolarWinds Support for their assistance....
You need to access the database (in our example PostgreSQL) and here's the PostgreSQL:
--Clean up Asset table and references
UPDATE job_ticket SET asset_id=NULL;
UPDATE po_item SET asset_id=NULL;
UPDATE asset SET po_item_id=NULL, parent_id=NULL;
DELETE FROM asset_custom_field;
DELETE FROM asset_bulk_action_child;
DELETE FROM asset_bulk_action_parent;
DELETE FROM asset_client;
DELETE FROM asset_generic_attachment;
DELETE FROM asset_history;
DELETE FROM asset_reservation_asset;
DELETE FROM job_ticket_asset;
DELETE FROM po_item;
DELETE FROM asset_parent_child; --added to break the child/parent fk problem
DELETE FROM asset;
DELETE FROM computer_identity;
DELETE FROM nodes;
--Reset asset_id count
ALTER SEQUENCE asset_seq RESTART 1;
I hope it helps, it certainly gave us a nice clean sheet to start again with.