Planet Replay

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

I have WiRNS set to start as a service and to not always run from the service perspective. I've set the 'Load WiRNSMON' at Windows startup selected and Show Splash Screen at startup not selected.

Everytime I do an update or make any changes it starts back up from the command line. How do I stop this and go back to a service always?

Note: I must admit that at one time I selected the Show Splash Screen and then unselected it once this started occuring...

I've also checked registry settings and they appear correct to me...
any help would be appreciated...

hdonzis · Posted: Mon May 14, 2012 8:32 am Post subject:

Glenn posted here that he changed WiRNSMon to work that way. However, I didn't think that it would attempt to start WiRNS running unless it was already running, so it only should have started WiRNS back up as an application if it was running when you do an update. In addition, he posted that it would only start it in application mode if the WiRNS service was not installed or was disabled, but I assume you have it in manual mode if you are running it when you want to...

You might want to contact Glenn about your situation...

Henry
_________________
Here's my Poop

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

Thanks Henry. I thought I had saw something in the past, but couldn't locate it (and I'm normally the to say search first...).

That's just it, I do have it running as a service and it's enabled. It only starts as a service with boot up. Subsequent starts from the taskbar icon only run from the command line. If I start it from the services menu, then it runs as a service...
I'll do some more checking on this on my box...

hdonzis · Posted: Mon May 14, 2012 11:58 am Post subject:

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

Maybe I'm not explaining it correctly, but that's what I don't get either.
If I right mouse click on the icon in the taskbar to either restart or to check for updates, when it restarts it starts from the command line...

hdonzis · Posted: Mon May 14, 2012 1:24 pm Post subject:

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

Yes, Running WiRNS 3.

I seem to recall that I had a different service icon, but it didn't really align with the active process, so I switched it out as recommended in a different thread....

hdonzis · Posted: Tue May 15, 2012 9:13 am Post subject:

I looked briefly at the code, and didn't see anything that should make it function as you are experiencing. If it is running as a service and it stops and restarts it, it should restart it as a service. The fact that others aren't complaining about it not restarting as a service makes me wonder if there's something strange with your particular setup. Hopefully Glenn can get involved...

Can you look at the properties of WiRNSMon.exe and post what version it is?

Henry
_________________
Here's my Poop

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

It's not the biggest deal, but just a minor irritant, so I appreciate your help with this.
My WiRNSMon Version 3.0.4338.30078

hdonzis · My WiRNSMon Version 3.0.4338.30078

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

Glenn contacted me and to discuss and we are investigating this.
Once it is resolved, I will update this for any others that may have this issue. IIRC this started when I updated to the new WiRNS Mon from the old one (3.0.4246.300) a while back. I just finally got some time and decided to look into it
Fred

fbreshears · Posted: Wed May 16, 2012 6:06 am Post subject:

I'm also seeing this behavior on one of three machines. It started after I had started WiRNS as an application to troubleshoot a problem. If I start WiRNS from the WiRNS Monitor, it starts as an application. I can start it as a service from the WiRNS directory.
_________________
Frank

hdonzis · Posted: Wed May 16, 2012 8:23 am Post subject:

sgniwder · Replay user Joined: 23 May 2004 Posts: 96

Yes, we discovered that my issue was that my machine had somehow had the WiRNS service named WiRNS.exe. I renamed the service and it is working correctly now. Glenn indicated that a new WiRNSmon may come out in the future to address this. I know some people are leery about renaming in the registry, but I can share that I used the link below and renamed it after I had exported out a copy of it.

I then rebooted the computer and it worked correctly.
Thanks to both Henry and Glenn!

http://thomaskrehbiel.com/post/1733-how_to_rename_a_windows_service

hdonzis · Posted: Wed May 16, 2012 6:18 pm Post subject:

Looks like Glenn posted an update for WiRNSMon, so it should be unnecessary to edit the WiRNS service name...

Frank, I'd still like to know what you find out about your WiRNS service...

Henry
_________________
Here's my Poop

fbreshears · Posted: Wed May 16, 2012 6:29 pm Post subject:

hdonzis · Posted: Wed May 16, 2012 9:10 pm Post subject:

threasoner · Replay fan Joined: 08 Jul 2011 Posts: 45

I am also having an issue with this. I'm running WiRNS_Main.dll 3.0 build 4520 revision 28855, and I refreshed all components this afternoon (5/17). WiRNSMon is running from the registry at startup, but there is also a service for WiRNS set to automatic.

When I check for updates or refresh all, I get a message box stating that the WiRNSMon service is already running, and when I dismiss it the tray icon disappears. At the end of the restart, I get a cmd window:

Glenn1963 · Posted: Fri May 18, 2012 9:58 am Post subject:

With WiRNSMon not running, go to your WiRNS folder and run UpdateMon.bat

That should complete the WiRNSMon update.
_________________
G

"I did absolutely nothing, and it was everything that I thought it could be."

threasoner · Replay fan Joined: 08 Jul 2011 Posts: 45

Thanks, Glenn.
_________________
Poops

hdonzis · Posted: Sun May 20, 2012 12:20 pm Post subject:

Glenn posted an update which should take care of upgrading WiRNSMon on systems which don't have the taskkill command...

Henry
_________________
Here's my Poop