RMA external program test problem
RMA external program test problem
We are currently testing for a process using HostMonitor 4.42 connected to an RMA agent on our remote server (win 2k adv server). When the process test goes bad, another dependent test runs and executes an external program (batch file on server) to stop and start the service.
This has been working great for months now, but i just upgraded to 4.42 and it is no longer working. It is now trying to find the batch file on the local HostMonitor machine and not the remote RMA server. If i try to browse to find the file after i have selected to use the RMA agent all i see is the local files of the HostMonitor PC.
Have you heard of any other problems with this? In summary, the problem is that we cannot execute the batch file on the remote RMA server as it looks for the file only on the local machine.
Thank you for any help you can give us.
This has been working great for months now, but i just upgraded to 4.42 and it is no longer working. It is now trying to find the batch file on the local HostMonitor machine and not the remote RMA server. If i try to browse to find the file after i have selected to use the RMA agent all i see is the local files of the HostMonitor PC.
Have you heard of any other problems with this? In summary, the problem is that we cannot execute the batch file on the remote RMA server as it looks for the file only on the local machine.
Thank you for any help you can give us.
Could you export test settings into text file and send to support@ks-soft.net or publish it here? Use menu File->Export to text fileThanks for the reply. I thought that I was able to browse using the RMA before....guess not. Anyway, when we updated, nothing was changed but the external batch file test no longer worked, even with typing in the path manually.
I don't think its necessary, HostMonitor can work with older versions of RMA.Would I need to update the RMA on the server side as well for this to work properly. The RMA is one to two releases older depending on which servers we are connecting to. Thanks.
Regards
Alex
The error that we receive in host monitor is "RMA: 301 - The directory name is invalid." However, the file is still located in the root C: drive on the server and it is exactly where it was located before the update to this version. The process tests and CPU tests that we are running via the RMA are all working exactly as they had before, it is just the external test that is malfunctioning. Thanks for your continued help.
Clarification
Alex,
The ting that is problematic is that the only thing that has changed in this environment is the fact that we reinstalled host monitor onto the same exact machine. No permissions were changed. We did not change machines, or OS or anything, we installed HostMonitor to the same machine. We did, change the installation drive from c: to d:. Previously, all of the RMA tests were working perfectly, now we can get neither the old preexisting tests nor new tests to function properly.
The ting that is problematic is that the only thing that has changed in this environment is the fact that we reinstalled host monitor onto the same exact machine. No permissions were changed. We did not change machines, or OS or anything, we installed HostMonitor to the same machine. We did, change the installation drive from c: to d:. Previously, all of the RMA tests were working perfectly, now we can get neither the old preexisting tests nor new tests to function properly.
RMA as application no difference
Sorry, that did not help
I was able to reproduce error!!!
But ... may be I am going crazy?
Ok, first I checked code and then I checked it again and again...
But after a while I tried to specify path to the BAT file using some cyrillic letters instead of latin letters. And after that test returns the same error you have!
I changed all letters back to latin but test still return error. I removed BAT file and created new one - test returns error. I stopped RMA service and started it again - test retuns error.
Finally I rebooted system... test still return error!!
However RMA started as application works fine and starts specified BAT file.
Solution? I don't know what we have to do now. Reinstall Windows? Format hard drive?
But ... may be I am going crazy?
Ok, first I checked code and then I checked it again and again...
But after a while I tried to specify path to the BAT file using some cyrillic letters instead of latin letters. And after that test returns the same error you have!
I changed all letters back to latin but test still return error. I removed BAT file and created new one - test returns error. I stopped RMA service and started it again - test retuns error.
Finally I rebooted system... test still return error!!
However RMA started as application works fine and starts specified BAT file.
Solution? I don't know what we have to do now. Reinstall Windows? Format hard drive?