STT Support,
I'm having a problem installing your 24x7 Scheduler v3.4.18 upgrade.
It continues to generate an error message indicating an
access denied problem with the logcat.dll. This .dll
and the entire '24x7 Automation 3' folder has full rights for the
account that I'm using to run the upgrade. I've tried disabling the
24x7 service account then restarting the server to no avail. Any ideas
on this one? Thanks

Rick Close
State of Calif
Franchise Tax Board
eMail: rick.close@ftb.ca.gov

logcat.dll is used by the Windows Event Viewer application to display log records written by 24x7. Please close all applications including 24x7 and the Event Viewer before running the install.

: STT Support,
: I'm having a problem installing your 24x7 Scheduler v3.4.18 upgrade.
: It continues to generate an error message indicating an
: access denied problem with the logcat.dll. This .dll
: and the entire '24x7 Automation 3' folder has full rights for the
: account that I'm using to run the upgrade. I've tried disabling the
: 24x7 service account then restarting the server to no avail. Any ideas
: on this one? Thanks

: Rick Close
: State of Calif
: Franchise Tax Board
: eMail: rick.close@ftb.ca.gov

I just reattempted to install the upgrade after shutting
down ALL running applications. Again I was unsuccessful.
On this machine 24x7 runs as a service which I stopped
prior to running the upgrade. Last week I disabled the
service, then rebooted the box and got the same result
when running the upgrade. It continues to generate the same
error message that indicts logcat.dll. The message states:
"An error occured while trying to replace an existing file:
DeleteFile failed, code 5. Access is denied."
Question: Do you have an email address so I can include
attachments in our correspondence?

Rick,

This error seems to be very obvious. Some of the applications are reading or monitoring NT event logs and this causes locks on logcat.dll (it is simply in use). You need to stop these applications first. Hope this helps.

By the way, it is good to have logcat.dll file updated, but it is not that critical. This DLL will not affect 24x7 Scheduler because the scheduler does not use it. The DLL is used by applications that read event logs to properly display 24x7 event log messages.

: I just reattempted to install the upgrade after shutting
: down ALL running applications. Again I was unsuccessful.
: On this machine 24x7 runs as a service which I stopped
: prior to running the upgrade. Last week I disabled the
: service, then rebooted the box and got the same result
: when running the upgrade. It continues to generate the same
: error message that indicts logcat.dll. The message states: "An error
: occured while trying to replace an existing file: DeleteFile failed, code
: 5. Access is denied."
: Question: Do you have an email address so I can include
: attachments in our correspondence?

There is nothing 'obvious' that is preventing this
upgrade from successfully running. I've ensured that
all apps and potential conflicting processes are shut
down prior to running the upgrade - all to no avail.

I ran the upgrade and 'Ignored' the logcat.dll error
message only to fail next on the logmsg.dll file. At
this point I aborted the install routine.

If the upgrade cannot/will not install is it possible
to: 1) Save the current configuration, 2) Remove the
current version of 24x7, and then 3) Install the full
v3.4.18 version. That would be my last resort.

You won't be able to uninstall it for the same reason.

If you don't see any applications using event logs locally check if these logs are opened or monitored remotely from other computers. For example NT Event Viewer application can be used to open/view logs on other network computers.

: There is nothing 'obvious' that is preventing this
: upgrade from successfully running. I've ensured that
: all apps and potential conflicting processes are shut
: down prior to running the upgrade - all to no avail.

: I ran the upgrade and 'Ignored' the logcat.dll error
: message only to fail next on the logmsg.dll file. At
: this point I aborted the install routine.

: If the upgrade cannot/will not install is it possible
: to: 1) Save the current configuration, 2) Remove the
: current version of 24x7, and then 3) Install the full
: v3.4.18 version. That would be my last resort.

I took a closer look at remote devices accessing the
Event Log and did not see anything unusual. I'll
attempt the re-install early tomorrow when there are
no users connected to this server.

Just for kicks I tried to install the upgrade ignoring
on the logcat.dll and logmsg.dll error messages. Next
popped up the snmp.dll error message - looks like this
failure doesn't just apply to the NT Event Log.

This install of 24x7 runs as a service. Whenever I attempt
the upgrade I always stop the service. Is this the correct
thing to do for the 24x7 upgrade? Thanks.

Did you mean 24x7snmp.dll? To upgrade this DLL you need to stop
SNMP service if it is running. This service could use 24x7snmp.dll.

And yes, you definitely need to stop 24x7 service before running the upgrade.

: I took a closer look at remote devices accessing the
: Event Log and did not see anything unusual. I'll
: attempt the re-install early tomorrow when there are
: no users connected to this server.

: Just for kicks I tried to install the upgrade ignoring
: on the logcat.dll and logmsg.dll error messages. Next
: popped up the snmp.dll error message - looks like this
: failure doesn't just apply to the NT Event Log.

: This install of 24x7 runs as a service. Whenever I attempt
: the upgrade I always stop the service. Is this the correct
: thing to do for the 24x7 upgrade? Thanks.