Hello,
Can anybody have a suggestion how to solve a problem that appear after upgrading from: SAM 5.2 SP1 to: 5.5 we noticed that we have 22 Unknown Applications:
Regards
Moshe Reish
Please open support ticket and refer this thwack post. We need to look at the log files for more information.
Thank you,
Lukas Belza (SolarWinds development)
Hello Lukas,
I already opened support ticket (Case: 520970), but I didn’t received any appropriate solution for this problem.
Regards,
Information Technology
Motorola Solutions, Inc.
motorolasolutions.com<www.motorolasolutions.com/>
O: +972-3-5684422
M: +972-57-5684422
E: bmr025@motorolasolutions.com<mailto:bmr025@motorolasolutionscom>
Mail address: Motorola Solutions Israel Ltd., 2 Negev St., Airport City - 70199, Israel
Skimming through the case notes it looks like the script was corrupted after the upgrade process. Restoring the original script resolved the issue. Is that an accurate synopsis of the case?
Hello aLTeReGo,
Thank you for your suggestion,
We don't know how to restore to the original scripts because we didn't backup those scripts before the upgrade, but we have created a backup for all SolarWinds DB so the only thing that we can do is to restore all SolarWinds DB & rollback to SAM Version: 5.2 SP1.If you have any suggestion how to restore those corrupted scripts from DB backup i will be glad if you can guide me how to do it.
I would recommend creating a new, temporary virtual machine separate from your production Orion installation. Restore a backup copy of your Orion Database to the same SQL server as the production database, ensuring that you restore it under a different name than your production database. If you have a different SQL server in your environment it may be easier/safer to restore the database there instead. If your database is under 10GB you might instead consider bringing up a temporary SQL Express instance.
Once the database is restored. Download and install a SAM 6.0 evaluation from SolarWinds.com. Install it on the new clean/fresh VM using the "Advanced" installation option. When prompted to create a new database or use an existing, choose "Existing". You will then be prompted to enter the SQL server instance name and database name where your Orion database was restored.
Once you're up and running on your restored database, you will be able to access the script files.
