On a production system, 24x7 (v 3.1.0) a few JAL jobs started as normal overnight but did not complete because a dialogue box appeared complaining "There is no disk in the drive, please insert a disk into drive A". These jobs *do not* in anyway interact with drive A. These jobs have worked fine until now and 24x7 has been up for the last 6 weeks.

Now I am finding that I get the same dialogue box when I look at the properties of any job. Do you have any idea why 24x7 suddenly wants to read Drive A all the time?

One (or maybe several) jobs refer to files on your floppy disk. Possible this is done by mistake. Most likely these files are specified in the file trigger of notification action of create file type. Now, someone recently removed that disk and when 24x7 attempts to check or access these files, Windows pops up the
modal "There is no disk in the drive, please insert a disk into drive A" dialog.. The solution is simple - find and fix these jobs.

: On a production system, 24x7 (v 3.1.0) a few JAL jobs started as normal
: overnight but did not complete because a dialogue box appeared complaining
: "There is no disk in the drive, please insert a disk into drive
: A". These jobs *do not* in anyway interact with drive A. These jobs
: have worked fine until now and 24x7 has been up for the last 6 weeks.

: Now I am finding that I get the same dialogue box when I look at the
: properties of any job. Do you have any idea why 24x7 suddenly wants to
: read Drive A all the time?

As I said in my first post, we have no jobs which refer to the A drive. Closing down and restaring 24x7 seems to have resolved this for the time being. However, I have little confidence that it won't return.

: One (or maybe several) jobs refer to files on your floppy disk. Possible this
: is done by mistake. Most likely these files are specified in the file
: trigger of notification action of create file type. Now, someone recently
: removed that disk and when 24x7 attempts to check or access these files,
: Windows pops up the
: modal "There is no disk in the drive, please insert a disk into drive
: A" dialog.. The solution is simple - find and fix these jobs.

You do have jobs or batch files or something else that refer to drive A and that is out of question.

If you didn't change jobs in 24x7 recently check external batch files or programs called from jobs. May be some of them were changed or somehow started to look for drive A. Again, this is the Windows system message that appears when a program attempts to write or read from drive A.

: As I said in my first post, we have no jobs which refer to the A drive.
: Closing down and restaring 24x7 seems to have resolved this for the time
: being. However, I have little confidence that it won't return.

Can you explain why accessing the properties of *any* job would bring up the message? And why this behaviour changed when 24x7 was re-started?

Thanks

: You do have jobs or batch files or something else that refer to drive A and
: that is out of question.

: If you didn't change jobs in 24x7 recently check external batch files or
: programs called from jobs. May be some of them were changed or somehow
: started to look for drive A. Again, this is the Windows system message
: that appears when a program attempts to write or read from drive A.

Please try the following:

1. Run Notepad and open any file from disk A (using File/Open menu)
2. Remove disk A
3. Click File/Open menu. You should get the same message about disk in drive A.

Same thing has happened with jobs or 24x7. Either some job or its dependencies set the current drive to A (or alternatively someone could use File/Open or File/Save As menu in 24x7 or some other file or directory related option to save/open files on disk A). Next time 24x7's attempt to open or find a file that has no path specified leads to the same "Insert disk A" message.

The thing is that it happens on a lower level (this is by Windows design), it always starts searching in the current directory. After restarting 24x7 you are fine again because the current drive/directory does not point to A. Just like in Notepad.

: Can you explain why accessing the properties of *any* job would bring up the
: message? And why this behaviour changed when 24x7 was re-started?

: Thanks