Do you have C-drive? It might be trying to write a log to the c-drive, and if you don't have one, it gives you an error. If that's the problem, the work around is this:
Open a command prompt window and type “subst c: <some valid path>”. This will trick Windows into thinking you have a C drive.
Thanks for the reply.
Yes, I do have a C: drive. I believe it's possible that the InstallShield is trying to write to a place where it doesn't have the rights to do so. Hence my question: What log file and where?
I appreciate the quick reply though...
If you installed in the default location, it would write the files to the Program Files\SolarWinds\Orion directory.
and created an empty .txt file called OrionApplicationMonitorLog.txt (just guessing that this was the log file the installer was trying to create and write to) and that didn't work either.
I believe it's a permissions issue, but my brain doesn't know where else to look. I was hoping someone who intimately knew what the App Monitor Installation program was trying to do could help me.
the install log file goes to the APPDATA directory for the current user (by default this is C:\Documents and Settings\<user>\Application Data\Solarwinds). Make sure you have access to that directory.
Thanks for the reply....
I believe we fixed it. We decided to rerun the Orion executable (after first backing up our database). Rerunning that, we choose "repair" and let that run. "Repair" suggested we run a hotfix* so we did that. Then we reran the Application Monitor installation and it worked!
Who knows what went wrong, but at this point we don't care. We had problems installing Orion due to a Group Security Policy. After moving the server into another group Orion finished installing. Most likely, beginning the install under one policy then finishing it under another causes some "confusion" inside the server.
----------
*Our original installation of Orion was Eval 8.5.1. It never suggested a hotfix update.The "repair" installation of Orion was also Eval 8.5.1. It suggests you run the update.The update we ran was to update 8.5 to 8.5.1. We ran it anyway.This whole process seemed odd but the end result is good so, instead of trying to figure it out, we move forward!
Thanks!