| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: UD Windows Agent Support [Read Only]
Thread: Can only run agent as screensaver |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I had to shutdown my computer because of hardware upgrade (DVD-ROM) and after booting the computer there was no way of getting the agent icon to the taskbar, I can only run it as a screensaver which, of course, makes my agent lose an awful lot of valuable idle time.
I only get the "Another instance already running" whatever I try. Is there a way to return to the original situation, what and where should I change in the configuration? |
||
|
|
depriens
Senior Cruncher The Netherlands Joined: Jul 29, 2005 Post Count: 350 Status: Offline Project Badges: 
|
I am getting the message "Another instance already running" sometimes when I use our VPN client to access our server from my house.
----------------------------------------When I return to work, there will be no icon in the taskbar anymore. But when I run taskmgr (Crtl-alt-del --> taskmanager) The WCG appears as normal in the process-list and it at full throttle! So everything is normal, except for the icon in the bottom. So try to find out if WCG is still running (in your taskmanager). If so and you want it to see in the taskbar, end the process and restart it normally.   |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This is a problem that Lewis Carroll knows about. See http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=4726#36901 for his solution. (I think it takes a mad logician to understand this one!
 ) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What seemed to help was rebooting the machine and letting it do whatever it wanted to do and log in after a couple of minutes or so. After being patient I got the beast working. Too hasty logging in seemed to upset the process.
I have used Windows for 19 years now, written Windows programs since 1990 (still writing them, sigh) and still lost under certain circumstances... |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
mkniskanen --
The problem will continue to be a problem for you. Check out the link that mycrofth provided to the earlier discussion on this. Until I applied that fix, I could not depend on seeing the icon in the system tray. It is an easy fix and will not upset anything on your system. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
mkniskanen -- The problem will continue to be a problem for you. Check out the link that mycrofth provided to the earlier discussion on this. Until I applied that fix, I could not depend on seeing the icon in the system tray. It is an easy fix and will not upset anything on your system. Ok, I'll do that before my next reboot - that will probably occur within a few months as I tend to have a typical uptime of 100 days or so. Now it is visible and everything is under control. As the writer of the "Systray Icons Missing" article proposed it may simply be a matter of loading order or readiness of the taskbar service to accept input. For me a patient reboot (log in only after the disk activity has stopped) helped and and thus it _may_ be that when there is not much other initialization activity going on the systray gets bit more quickly ready to accept input. Anyhow, thanks for your link, I'll do what's necessary before my next boot. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
mkniskanen --
I agree that it looks a lot like a timing issue as well. I seem to remember a "slow" login helping sometimes back when I was having the problem. |
||
|
|
|