Hi, I am seeing the same symptoms as Greig, who posted the message "Problem With Upgrade to 3.3.0" on June 10. In short, when I right-click on a job, the Debug and Run-Now options are disabled. The Validate button in the editor does nothing. I upgraded my workstation from 3.2.4, but after reading the other thread, did an uninstall and full re-install. We did a full uninstall/reinstall on a server that was running 3.2.4 and it now exhibits the same behaviour.

There is only one 24x7srv.dll on each machine, file version 3.0.0.7, product version 3.3.0.1. There is only one netapi32.dll on my machine, v5.0.2195.2808, dated 5/4/2001 2:05:02pm.

Any other suggestions/thoughts?

The upgrade package 3.3.0 fails to update couple of dlls. There is a more recent upgrade available 3.3.1 see link below. Please try it. You don't need to uninstal things, just run the upgrade. Keep us posted if that upgrade doesn't help.

http://www.softtreetech.com/download/247upg.exe

: Hi, I am seeing the same symptoms as Greig, who posted the message
: "Problem With Upgrade to 3.3.0" on June 10. In short, when I
: right-click on a job, the Debug and Run-Now options are disabled. The
: Validate button in the editor does nothing. I upgraded my workstation from
: 3.2.4, but after reading the other thread, did an uninstall and full
: re-install. We did a full uninstall/reinstall on a server that was running
: 3.2.4 and it now exhibits the same behaviour.

: There is only one 24x7srv.dll on each machine, file version 3.0.0.7, product
: version 3.3.0.1. There is only one netapi32.dll on my machine,
: v5.0.2195.2808, dated 5/4/2001 2:05:02pm.

: Any other suggestions/thoughts?

: The upgrade package 3.3.0 fails to update couple of dlls. There is a more
: recent upgrade available 3.3.1 see link below. Please try it. You don't
: need to uninstal things, just run the upgrade. Keep us posted if that
: upgrade doesn't help.

: http://www.softtreetech.com/download/247upg.exe

The upgrade to 3.3.1 failed with a message referencing 24x7u2.lib. It says "an error occured while trying to copy a file: The source file is corrupted."

I'm running Windows 2000 (5.00.2195) SP2.

Please check the downloaded file size it should be 4.85 MB (5,086,803 bytes)

: The upgrade to 3.3.1 failed with a message referencing 24x7u2.lib. It says
: "an error occured while trying to copy a file: The source file is
: corrupted."

: I'm running Windows 2000 (5.00.2195) SP2.

: Please check the downloaded file size it should be 4.85 MB (5,086,803 bytes)
I have verified that the file size is correct. I tried the upgrade again and got the same error. I used the "retry" option but it fails consistently. I did make sure that the 24x7 service is stopped. I can't help but feel I've missed something obvious!

I just grabbed the file from the web server and made succesfull install (used W2K SP2 same as yours).

Try deleting the destination file manually and then re-running the upgrade.
If that doesn't help try restarting the computer.

: The upgrade to 3.3.1 failed with a message referencing 24x7u2.lib. It says
: "an error occured while trying to copy a file: The source file is
: corrupted."

: I'm running Windows 2000 (5.00.2195) SP2.

Please check my message one level above

: I have verified that the file size is correct. I tried the upgrade again and
: got the same error. I used the "retry" option but it fails
: consistently. I did make sure that the 24x7 service is stopped. I can't
: help but feel I've missed something obvious!

: I have verified that the file size is correct. I tried the upgrade again and
: got the same error. I used the "retry" option but it fails
: consistently. I did make sure that the 24x7 service is stopped. I can't
: help but feel I've missed something obvious!
One other thought. I completely removed (or so I thought) 24x7, rebooted, then reinstalled V3.2.4. I still have the problem. I tried installing the 3.3.1 upgrade and again got the "corrupted source file" error. I clicked ignore and the installation completed. However I still have the problem. There must be a DLL "stuck" somewhere?

: Please check my message one level above
I re-downloaded the 3.3.1 upgrade .exe to my desktop and was able to install it without error (before I had downloaded it to a network drive and was running the install from there).

However, I still see the "Run Now" and "Debug Script" job menu options as disabled if 24x7 is running as a service. If the service is stopped, they appear as enabled. The "Validate Script" button in the editor now works regardles of whether the service is running.

Am I remembering this incorrectly from the previous version? I should be able to "Run Now" and "Debug" while the service is running, right? Thanks for all you help and the quick responses.

Ah...

I thought you had the same issue as the one you referenced in your original message.

When the service is running you can only use the GUI portion to modify jobs and view logs. You cannot run jobs from this GUI because they can affect the service processing. This is not new in 3.3, it was "always" there.

By the way, when you start the GUI you should get a warning message telling you that the timer will be disabled in this 24x7 instance (meaning that the scheduling engine and the job engine will be turned off) but you can still use the GUI to modify jobs. To run or debug jobs manually use the 24x7 Remote Control instead. In order to use the 24x7 Remote Control need to run the 24x7 Scheduler in the distributed server mode (see Tools/Options/Network menu.)

: I re-downloaded the 3.3.1 upgrade .exe to my desktop and was able to install
: it without error (before I had downloaded it to a network drive and was
: running the install from there).

: However, I still see the "Run Now" and "Debug Script" job
: menu options as disabled if 24x7 is running as a service. If the service
: is stopped, they appear as enabled. The "Validate Script" button
: in the editor now works regardles of whether the service is running.

: Am I remembering this incorrectly from the previous version? I should be able
: to "Run Now" and "Debug" while the service is running,
: right? Thanks for all you help and the quick responses.

You're right - sorry for the confusion. I did have a problem initially, but after applying the "new" upgrade I guess I was looking for a problem that didn't exist. Yes, I do get the warning message about the timer when starting the GUI when the service is running. Looks like all is well. Thanks for your patience and quick responses.

: Ah...

: I thought you had the same issue as the one you referenced in your original
: message.

: When the service is running you can only use the GUI portion to modify jobs
: and view logs. You cannot run jobs from this GUI because they can affect
: the service processing. This is not new in 3.3, it was "always"
: there.

: By the way, when you start the GUI you should get a warning message telling
: you that the timer will be disabled in this 24x7 instance (meaning that
: the scheduling engine and the job engine will be turned off) but you can
: still use the GUI to modify jobs. To run or debug jobs manually use the
: 24x7 Remote Control instead. In order to use the 24x7 Remote Control need
: to run the 24x7 Scheduler in the distributed server mode (see
: Tools/Options/Network menu.)