
I have a server ABCD that uses control-m to run a vb .exe file once a week.
What the VB .exe does: this exe file looks at the database server ABCD is connected to, it then looks at a table for .jpg information, and then moves certain .jpg files to another server called XYZ.
When control-m runs the job it starts and completes sucessfully. I can also see the application running on server ABCD and then I see it completing sucessfully.
HOWEVER, the vb app is not actually performing the move of the .jpg files to server XYZ. The job completes sucessfully but no new .jpg files appear on server XYZ.
Now, when i run the vb app manually from the specified folder that control-m uses, the VB app actually works and the .jpg files get moved to XYZ.
I originally thought this was a user issue because I am signed onto server ABCD as "JANE" and the control-m job is using user "BOB" to run the vb .exe. I tested this theory out though and when the control-m uses "JANE" to run the vb app, it looks like it runs and completes sucessfully but still no jpg's get written to server XYZ.
So in short, the jpgs from this VB app get written to server XYZ if i run the app manually on the server and not through control m.
Comments? Things to try? Thanks.
Things I would check are:
Does CONTROL-M actually correctly log on as JANE?
You could run a test job for this; tasktype Command, command line: whoami
If that checks out; does the VB exe have any error handling in it? It sounds like it doesn't...
The commands that copy the .jpg file are probably returning errors, but if the VB exe doesn't catch these you have no way of knowing what's going wrong.
If it's an exe you developed, make sure you catch any exceptions and negative return codes from those copy commands.
--Michiel
what you use to copy files to another server ? ssh, ftp, mapped drives ? what about authentication ?
Ok I have some new information. I put error handling in the code and found that when control m runs the batch script which kicks off the application, i get Error 75 in Visual Basic which means "Path/File Access Error".
However, when I run the batch script manually, I do not get this error at all.
I am logged in as user JANE and control m is running the batch script from user JANE as well.
What would cause this file access error when control m runs the job?