---
title: "Error: Invalid Object name 'LMS_ZACTAR_ActionConfigArchive'"
canonical: "https://servicedesk.maxgeo.com/space/LC/1263796309/Error%3A%20Invalid%20Object%20name%20'LMS_ZACTAR_ActionConfigArchive'"
format: markdown
---
<u>**Problem:**</u>

1. You were issued a script to fix a bug in V1.8.0, however an error was returned reading: Invalid Object name 'LMS_ZACTAR_ActionConfigArchive'.

<u>**Cause:**</u>

1. You are running the script against a database that doesn't have this particular table, which means you are not running the script against a V1.8.0 database.

<u>**Solution:**</u>

1. You need to either: **(a)** run the script against the V1.8.0 database, or **(b)** run the most recent V1.8.0 upgrade against the non-V1.8.0 database.  Remember: If you were not provided a new V1.8.0 install/upgrade with the bug fix, the bug fix isn't included in the upgrade file you have.  You therefore need to email servicedesk.maxgeo.com for the latest upgrade build.

<u>**Additional Info:**</u>

- 'LMS_ZACTAR_ActionConfigArchive' is a table that was created in the V1.8.0 upgrade.  As V1.8.0 made adjustment to Action Configurations, it was prudent to record all changes being made, in the event of error.  The bug fix looks to this table to determine the fixes required, which will be specific to each database.  Therefore the table needs to exist for the bug fix to do it's job.
- V1.8.0 contained enhancements that needed a 'clean up' to ghost records.  However, in some instances, these ghost records were attached to anomalies that interferred with the upgrade.  The bug fix therefore rectified these anomalies while still cleaning up ghost records.  It affected very few clients, however regardless was built into the V1.8.0 upgrader along with a check pre-upgrade for further anomalies to discontinue adverse impact.