Applications Systems
Error while executing script- Invalid object name 'APM_ComponentStatus_Hourly' for SolarWinds Platform 2023.3 and below
This article will walkthrough how to resolve the following error: Orion Database FAILED Database configuration failed: • Error while executing script- Invalid object name 'APM_ComponentStatus_Hourly'.
First published date
Last published date
Overview
When running the configuration wizard, the following error may occur:
Error while executing script- Invalid object name 'APM_ComponentStatus_Hourly'.
Product section
Cause
Resolution
To resolve this issue, please upgrade to SolarWinds Platform 2023.4 and above. If upgrade is not possible, perform the steps below to workaround the issue:
Please note that these queries contain the GO command that is incompatible with Orion Database Manager and will not work.
Instead, Microsoft SQL Studio Manager will need to be used.
APM_ComponentStatus_Hourly
|
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, damages for loss of business profits, business -- interruption, loss of business information, or other pecuniary loss) arising -- out of the use of or inability to use the scripts or documentation. |
APM_ComponentStatus_Daily
|
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, damages for loss of business profits, business -- interruption, loss of business information, or other pecuniary loss) arising -- out of the use of or inability to use the scripts or documentation. |