Hi there,
Can you please explain why Jobs are left with "Running" status when they have already finished? This is not happening all the time, but there are days like today, almost all jobs are reporting "Running" when in fact they completed successfully.

Hopefully, I'm not the only one seeing this issue, and you can share some info as to how to correct it.

1. Do you have the Client application running overnight?
2. does it stay in running status if you restart the Client?

---

Didn't think of restarting the client. I typically leave the client open overnight, after restarting it, it shows the correct statuses.

Thank you.

Please try first:

1. disconnect and reconnect
2. restart client

Let us know the result when this happens again.

---

I am seeing the same issue with incorrect status (running).
I do not leave the client open for extended periods of time.
If I disconnect and reconnect from a host with this issue, in many cases it fixes the issue.
Relaunching the VisualCron client does not always fix the issue. Only disconnect and reconnect after launch seems to work.
This is annoying, because I have to check the servers to see if the job is actually still running.
I have connections to 20+ VisualCron servers in my client (8.2.3).

Thanks

I am seeing the same issue with incorrect status (running).
I do not leave the client open for extended periods of time.
If I disconnect and reconnect from a host with this issue, in many cases it fixes the issue.
Relaunching the VisualCron client does not always fix the issue. Only disconnect and reconnect after launch seems to work.
This is annoying, because I have to check the servers to see if the job is actually still running.
I have connections to 20+ VisualCron servers in my client (8.2.3).

Thanks

If you relaunch the Client and it is still running it *should be* running. It is the Client keeping track of this and the tracking is reset if you launch the client again. We would like to know how to reproduce this. Can you, at least temporary, switch to connect to one at a time to see if you still can reproduce it?

---

I believe this is part of a bigger issue.
I have been having issues trying to edit jobs and tasks.
My client has been crashing or stalling when performing an edit.
There are circumstances that are different than normal, in that, I am using the client software through Citrix in AWS Cloud and connecting to other VisualCron VMs in the same cloud area.
The crashes when trying to edit seem to be random, it's not the same server or job each time, it just cannot communicate with the server system and times out eventually or I click on the main window and then get the "wait for program to finish or close".
Anyway, I have tried taking all the systems out of auto launch at start and then connecting manually.
Nothing seems to solve the issue, but if I keep trying to connect and reconnect, it will eventually let me edit.
I'm not sure how you can reproduce this, but can you let me know what logs I should send you?

Here is my client log.

Another note on this issue. I am storing my settings in an alternate location, because I'm running the client through Citrix.
I noticed that I can not change the location of the log or backup folders.
It will change in the client settings, but it still directs the files to the default locations.
I'm finding that if I disconnect and then reconnect, things will work for a while, but eventually it will crash when editing settings or I'll edit the settings and they will not take.
I'm not seeing anything in the logs saying what happened.
I'd really like to get this resolved, because our intent is to operate the client from Citrix going forward.

Thanks

I think these are two different issues - not related.

About logs, are you trying to change Client settings->Folder or Server settings->Folder? Please attach screenshot.

---

I tried to change the top and bottom options and they have no affect.
The client still saves to the default locations.
The settings (middle option) does work.

On the connection timeout issue..
I can see all the jobs and statuses on servers set to auto connect on startup, but I might see an incorrect status or
when the edit or server info request times out I get the not a reference to an object error from the send error to VisualCron dialog.
If I close and relaunch the client, then disconnect a server that I have set to auto connect on start, then reconnect, it seems to work for a while, but eventually I'll get the error again.

I had to downgrade the servers to 8.2.1 in order for the client 8.2.3 to start working correctly.

These are two different cases which should have different threads.

1. ACS - we already have a support case open right? In your case you get a connection problem which we are investigating. It is not related to status but a consequence from that. I would say your case is unique so far. We we are working a a debug version for you.
2. SIJU - this sounds like a progress sync issue. On the Jobs or Tasks you get this - are they running very short time or longer time? Please test this version: http://www.visualcron.co....aspx?g=posts&t=7049 

---