Utility: STBKeepAlive - scheduled commands for USB-UIRT

[something fishy]

I'm hugely grateful for all developers that post material on this board so I'm reluctant to post "feature requests" for risk of seeming cheeky.

But yes please, if it were possible to poll NeilM's webserver to avoid rebooting the STB during an active recording session this would help me enormously

Thanks
Eric

[shadeblue.com]

Originally Posted by something fishy

I'm hugely grateful for all developers that post material on this board so I'm reluctant to post "feature requests" for risk of seeming cheeky.

But yes please, if it were possible to poll NeilM's webserver to avoid rebooting the STB during an active recording session this would help me enormously

Thanks
Eric

Hi Eric, I don't mind adding it if it will help people :-) I am in the middle of another SageTV plugin project right now, but as soon as I wrap that one up, I can revisit this one.

Thanks,
shadeBlue

[lpott6]

shadeblue,

Sorry I haven't been back sooner, been very busy.

I finally had time to do some testing and found that the service cannot seem to find the USB-uirt when it starts up, but in console mode it finds it and successfully sends commands. I am attaching the log file.

2008-11-25 21:13:53,586 [4] DEBUG STBKeepAlive.Service [(null)] - START SERVICE
2008-11-25 21:13:53,836 [4] INFO  STBKeepAlive.Service [(null)] - STBKeepAlive version: 1.0.2.0
2008-11-25 21:13:54,102 [4] INFO  Quartz.Core.SchedulerSignalerImpl [(null)] - Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
2008-11-25 21:13:54,102 [4] INFO  Quartz.Core.QuartzScheduler [(null)] - Quartz Scheduler v.1.0.0.2 created.
2008-11-25 21:13:54,102 [4] INFO  Quartz.Simpl.RAMJobStore [(null)] - RAMJobStore initialized.
2008-11-25 21:13:54,102 [4] INFO  Quartz.Impl.StdSchedulerFactory [(null)] - Quartz scheduler 'STBKeepAliveQuartzScheduler' initialized
2008-11-25 21:13:54,102 [4] INFO  Quartz.Impl.StdSchedulerFactory [(null)] - Quartz scheduler version: 1.0.0.2
2008-11-25 21:13:54,289 [4] FATAL STBKeepAlive.Service [(null)] - STBKeepAlive encountered a fatal exception in 'STBKeepAlive::Program::Main()'
System.ApplicationException: Unable to connect to USB-UIRT device! Please ensure device is connected to the computer
   at UsbUirt.Controller.OpenDriver()
   at UsbUirt.Controller..ctor()
   at STBKeepAlive.Service.StartService()
2008-11-25 21:13:54,461 [4] DEBUG STBKeepAlive.Service [(null)] - STOPPING SERVICE
2008-11-25 21:13:54,477 [4] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED shutting down.
2008-11-25 21:13:54,477 [4] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED paused.
2008-11-25 21:13:54,477 [4] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED Shutdown complete.
2008-11-25 21:13:54,477 [4] DEBUG STBKeepAlive.Service [(null)] - STOPPED SERVICE
2008-11-25 21:13:54,555 [STBKeepAliveQuartzScheduler_Worker-1] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:13:54,555 [STBKeepAliveQuartzScheduler_Worker-2] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:13:54,555 [STBKeepAliveQuartzScheduler_Worker-4] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:13:54,555 [STBKeepAliveQuartzScheduler_Worker-3] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:13:54,555 [STBKeepAliveQuartzScheduler_Worker-5] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down

Stop Service

2008-11-25 21:15:34,352 [4] DEBUG STBKeepAlive.Service [(null)] - STOPPING SERVICE
2008-11-25 21:15:34,383 [4] ERROR STBKeepAlive.Service [(null)] - Quartz.SchedulerException: The Scheduler has been Shutdown.
   at Quartz.Core.QuartzScheduler.ValidateState()
   at Quartz.Core.QuartzScheduler.GetJobNames(SchedulingContext ctxt, String groupName)
   at Quartz.Impl.StdScheduler.GetJobNames(String groupName)
   at STBKeepAlive.Service.StopService()
Quartz.SchedulerException: The Scheduler has been Shutdown.
   at Quartz.Core.QuartzScheduler.ValidateState()
   at Quartz.Core.QuartzScheduler.GetJobNames(SchedulingContext ctxt, String groupName)
   at Quartz.Impl.StdScheduler.GetJobNames(String groupName)
   at STBKeepAlive.Service.StopService()

Start Console

2008-11-25 21:16:41,477 [1] DEBUG STBKeepAlive.Service [(null)] - START SERVICE
2008-11-25 21:16:41,492 [1] INFO  STBKeepAlive.Service [(null)] - STBKeepAlive version: 1.0.2.0
2008-11-25 21:16:41,570 [1] INFO  Quartz.Core.SchedulerSignalerImpl [(null)] - Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
2008-11-25 21:16:41,570 [1] INFO  Quartz.Core.QuartzScheduler [(null)] - Quartz Scheduler v.1.0.0.2 created.
2008-11-25 21:16:41,570 [1] INFO  Quartz.Simpl.RAMJobStore [(null)] - RAMJobStore initialized.
2008-11-25 21:16:41,570 [1] INFO  Quartz.Impl.StdSchedulerFactory [(null)] - Quartz scheduler 'STBKeepAliveQuartzScheduler' initialized
2008-11-25 21:16:41,570 [1] INFO  Quartz.Impl.StdSchedulerFactory [(null)] - Quartz scheduler version: 1.0.0.2
2008-11-25 21:16:41,586 [1] INFO  STBKeepAlive.Service [(null)] - USB-UIRT Info: Protocol: Version=257
2008-11-25 21:16:41,617 [1] INFO  STBKeepAlive.Service [(null)] - USB-UIRT Info: Firmware: Version=1289 Date=3/26/2004
2008-11-25 21:16:43,477 [1] INFO  STBKeepAlive.Service [(null)] - LOADED JOB: Uverse STB Wake Up
2008-11-25 21:16:43,508 [1] INFO  STBKeepAlive.IRJob [(null)] - (*) Added Quartz Job: Uverse STB Wake Up
2008-11-25 21:16:43,649 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 20:55 AM] Every day at [8:55 PM]
2008-11-25 21:16:43,664 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 20:56 AM] Every day at [8:56 PM]
2008-11-25 21:16:43,680 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 20:57 AM] Every day at [8:57 PM]
2008-11-25 21:16:43,680 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 20:58 AM] Every day at [8:58 PM]
2008-11-25 21:16:43,695 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 20:59 PM] Every day at [8:59 PM]
2008-11-25 21:16:43,711 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 21:00 PM] Every day at [9:00 PM]
2008-11-25 21:16:43,727 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 21:01 PM] Every day at [9:01 PM]
2008-11-25 21:16:43,742 [1] INFO  STBKeepAlive.IRJob [(null)] - (+) Added trigger: [Daily @ 21:02 PM] Every day at [9:02 PM]
2008-11-25 21:16:43,742 [1] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED started.

Initiated Trigger

2008-11-25 21:16:57,461 [1] INFO  STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STARTED.
2008-11-25 21:16:57,570 [10] INFO  STBKeepAlive.Service [(null)] - EXECUTE CMD: Name=[Button - Select] Delay=[100] RepeatCount=[7]
2008-11-25 21:16:57,586 [10] INFO  STBKeepAlive.Service [(null)] - IR PROCESSING TIMER STOPPED.

Stopped Console

2008-11-25 21:17:02,227 [1] DEBUG STBKeepAlive.Service [(null)] - STOPPING SERVICE
2008-11-25 21:17:02,289 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 20:55 AM,DEFAULT
2008-11-25 21:17:02,320 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 20:56 AM,DEFAULT
2008-11-25 21:17:02,352 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 20:57 AM,DEFAULT
2008-11-25 21:17:02,383 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 20:58 AM,DEFAULT
2008-11-25 21:17:02,399 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 20:59 PM,DEFAULT
2008-11-25 21:17:02,414 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 21:00 PM,DEFAULT
2008-11-25 21:17:02,430 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 21:01 PM,DEFAULT
2008-11-25 21:17:02,430 [1] DEBUG Quartz.Simpl.RAMJobStore [(null)] - RemoveTrigger Uverse STB Wake Up-Daily @ 21:02 PM,DEFAULT
2008-11-25 21:17:02,430 [1] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED shutting down.
2008-11-25 21:17:02,430 [1] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED paused.
2008-11-25 21:17:02,445 [1] INFO  Quartz.Core.QuartzScheduler [(null)] - Scheduler STBKeepAliveQuartzScheduler_$_NON_CLUSTERED Shutdown complete.
2008-11-25 21:17:02,445 [1] DEBUG STBKeepAlive.Service [(null)] - STOPPED SERVICE
2008-11-25 21:17:02,555 [STBKeepAliveQuartzScheduler_Worker-1] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:17:02,555 [STBKeepAliveQuartzScheduler_Worker-2] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:17:02,555 [STBKeepAliveQuartzScheduler_Worker-3] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:17:02,555 [STBKeepAliveQuartzScheduler_Worker-4] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down
2008-11-25 21:17:02,555 [STBKeepAliveQuartzScheduler_Worker-5] DEBUG Quartz.Simpl.SimpleThreadPool [(null)] - WorkerThread is shutting down

Any help you can provide is appreciated.

Larry in Denver

[something fishy]

@shadeblue.com
Cheers
Eric

[shadeblue.com]

lpott6,

I'm not exactly sure why this would fail. One thing you could try is to run the server as the same user account that the SageTV process is running under. Maybe they are both competing for the same resource and singe they are in different user contexts, one one gets the device?

-SB

[lpott6]

Originally Posted by shadeblue.com

lpott6,

I'm not exactly sure why this would fail. One thing you could try is to run the server as the same user account that the SageTV process is running under. Maybe they are both competing for the same resource and singe they are in different user contexts, one one gets the device?

-SB

Thanks for the reply.

I thought of that, but it works in "Control Panel" mode with Sage running. I would think that rules out a contention problem.

I am not running in server mode, just have SageTV running all the time, so I think Sage and STBKeepAlive are running under the same user account. How would I check to be sure?

[shadeblue.com]

Originally Posted by lpott6

Thanks for the reply.

I thought of that, but it works in "Control Panel" mode with Sage running. I would think that rules out a contention problem.

I am not running in server mode, just have SageTV running all the time, so I think Sage and STBKeepAlive are running under the same user account. How would I check to be sure?

If STBKeepAlive is running in "Console" mode, then it is running under your current user logon context. Same thing for Sage, it you are not running it as a service, then it too is running under the same user context. If you are running these as a service, you can go to Control Panel / Administrative Tools / Services to see the listing over NT services. Here you can also edit each service and specify which account to run under. By default, they run under the "Local System" account. So you could try to configure STBKeepAlive to use the same user account that you are logging it with to see if that helps.

To verify what user context the program is running under, you can use the Windows Task Manager and select the "Processes" tab to see each process and which user account it is running as.

-SB

[shadeblue.com]

Originally Posted by something fishy

But yes please, if it were possible to poll NeilM's webserver to avoid rebooting the STB during an active recording session this would help me enormously

Thanks
Eric

Hi Eric,

Just an update ... I have written the logic to poll the web server and determine if the Sage server is busy recording. I just have to integrate it into the STBKeepAlive program now

If the HTTP/XML query results in an error, do you think STBKeepAlive should proceed with its timed IR commands, or should it prevent the IR command from being sent, just like if the Sage server were busy recording, because we could not verify that it is not busy?

Thanks,
SB

[lpott6]

Originally Posted by shadeblue.com

If STBKeepAlive is running in "Console" mode, then it is running under your current user logon context. Same thing for Sage, it you are not running it as a service, then it too is running under the same user context. If you are running these as a service, you can go to Control Panel / Administrative Tools / Services to see the listing over NT services. Here you can also edit each service and specify which account to run under. By default, they run under the "Local System" account. So you could try to configure STBKeepAlive to use the same user account that you are logging it with to see if that helps.

To verify what user context the program is running under, you can use the Windows Task Manager and select the "Processes" tab to see each process and which user account it is running as.

-SB

Now I understand, that is probably the answer. I will check it out tonight and see if that corrects the problem.
Thanks

[lpott6]

Originally Posted by lpott6

Now I understand, that is probably the answer. I will check it out tonight and see if that corrects the problem.
Thanks

Well that was it. I changed the service to login to the account that Sage runs in and voila, it works.

Now I don't have to hurry home every day to turn on the Dish STB so I don't miss any shows.

One more question. I have my logging threshold value="DEBUG". What is the value for normal operation?

Thanks for your patience.

[shadeblue.com]

I would set it to WARN or ERROR, I can't remember if there are any WARN messages, but WARN or ERROR should at least catch and log any program errors or exceptions :-)

Glad to hear it is all working now!

-SB

[lpott6]

Originally Posted by shadeblue.com

I would set it to WARN or ERROR, I can't remember if there are any WARN messages, but WARN or ERROR should at least catch and log any program errors or exceptions :-)

Glad to hear it is all working now!

-SB

Fantastic.

Thank goodness, one more item off my list.

[EmuZombie]

This is a great utility however I think I am using it for a unique reason that may help others down the road. Let me explain..

I have Time Warner Cable in the Milwaukee metro area where more then 50% of their HD channels use switched digital video (SDV). See here for more info. For those not familiar with it, it is basically like IPTV for cable. It is however, very buggy at the moment. Which brings me to how this program is helping me.

My STB's do not power off and / or sleep automatically, which is a blessing I know.

However, if the box has been on a SDV channel for a few hours it eventually loses its connection and displays a still frame of video. It will continue to do so until a channel change to a different channel (it ignores a change to the same channel) or the "A" button on the remote is pressed. This obviously sends the command to reconnect and continue video and/or tells the box someone is still watching.

I've set it up to send this A command every hour and no longer run into recordings of a still frame.

Thanks a lot.

[something fishy]

Hi Eric,

Just an update ... I have written the logic to poll the web server and determine if the Sage server is busy recording. I just have to integrate it into the STBKeepAlive program now

If the HTTP/XML query results in an error, do you think STBKeepAlive should proceed with its timed IR commands, or should it prevent the IR command from being sent, just like if the Sage server were busy recording, because we could not verify that it is not busy?

Thanks,
SB

apologies for being absent for so long.

For my purposes only sending the commands when there is a guarantee that Sage is not recording would be best.

I'm afraid I'm not sure under what conditions the webserver would return an error. However requiring a valid response from the webserver would require that it be installed and I wouldn't want to impose that on other users.

Cheers

Eric

[OldPCGUY]

I have been using this utility for 3 months now and it has worked great.

I have not rebooted my PC in 1 month and only had to stop and start Sage maybe 4 times oveer 3 months.

My Dish VIP612 Updates the Program Guide every night at 3:00am and then shuts down the output at the Component Output. This will hang SageTV.

Using ST KeepAlive I simply send a 'select' button command every 3 hours.
The Dish Box stays awake and Sage Never Hangs.

Many thanks to Shade Blue. My config file settings are below including my IR code for the DISH VIP 612

<Jobs>

<!-- ******************************************** -->
<!-- This default job will send a 'select' button -->
<!-- signal to Dish VIP612 STBs -->
<!-- at the scheduled times every day. -->
<!-- ******************************************** -->
<Job Name="VIP612 Wakeup" >
<Triggers>
<Trigger Name="Daily @ 03:08 AM" Type="Daily" Time="03:08" />
<Trigger Name="Daily @ 06:08 AM" Type="Daily" Time="06:08" />
<Trigger Name="Daily @ 11:58 AM" Type="Daily" Time="11:58" />
<Trigger Name="Daily @ 06:55 PM" Type="Daily" Time="18:58" />
<Trigger Name="Daily @ 11:58 PM" Type="Daily" Time="23:58" />
</Triggers>
<Commands>
<Command Name="Button - Select"
IR="0000 0047 0000 0011 0017 0166 0017 00A3 0017 0062 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 0062 0017 0062 0017 0062 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 00A2"
RepeatCount="4" />
</Commands>
</Job>

[shadeblue.com]

Originally Posted by OldPCGUY

I have been using this utility for 3 months now and it has worked great ...

Hi OldPCGUY,

Thanks for the post, that info you provided may help future users with similar setups. It's good to hear that this tool is useful for fellow Sage users and for different provider STBs.

Thanks again,
SB

[OldPCGUY]

Originally Posted by OldPCGUY

I have been using this utility for 3 months now and it has worked great.

I have not rebooted my PC in 1 month and only had to stop and start Sage maybe 4 times oveer 3 months.

My Dish VIP612 Updates the Program Guide every night at 3:00am and then shuts down the output at the Component Output. This will hang SageTV.

Using ST KeepAlive I simply send a 'select' button command every 3 hours.
The Dish Box stays awake and Sage Never Hangs.

Many thanks to Shade Blue. My config file settings are below including my IR code for the DISH VIP 612

<Jobs>

<!-- ******************************************** -->
<!-- This default job will send a 'select' button -->
<!-- signal to Dish VIP612 STBs -->
<!-- at the scheduled times every day. -->
<!-- ******************************************** -->
<Job Name="VIP612 Wakeup" >
<Triggers>
<Trigger Name="Daily @ 03:08 AM" Type="Daily" Time="03:08" />
<Trigger Name="Daily @ 06:08 AM" Type="Daily" Time="06:08" />
<Trigger Name="Daily @ 11:58 AM" Type="Daily" Time="11:58" />
<Trigger Name="Daily @ 06:55 PM" Type="Daily" Time="18:58" />
<Trigger Name="Daily @ 11:58 PM" Type="Daily" Time="23:58" />
</Triggers>
<Commands>
<Command Name="Button - Select"
IR="0000 0047 0000 0011 0017 0166 0017 00A3 0017 0062 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 0062 0017 0062 0017 0062 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 00A3 0017 00A2"
RepeatCount="4" />
</Commands>
</Job>

The VIP 612 Component output is connected to an HDPVR which is connected via USB to the HTPC(Sage TV Server). When the VIP 612 does a program update there is a limited time after the update that the display indicates " Press select to continue". After a period of time and if the select button is not pressed, the VIP 612 Shuts off the component output and Sage TV will show 'No Signal' for all channels until you press select. However, and worse Sage will hang if your try to record on a 'no signal' VIP 612 channel.

The ST Keep Alive solution fixes this issue. I just wanted to clarify the source of the problem with the DISH VIP 612 becuase other users may see a different interaction with Sage depending on the Sage release.

[jameslsnyder]

This may be answered somewhere else, but does STBKeepAlive run on Vista X64?

[shadeblue.com]

Originally Posted by jameslsnyder

This may be answered somewhere else, but does STBKeepAlive run on Vista X64?

Hi James,

I am not currently running it full time on Vista x64, but it was originally developed on a Vista x64 machine, so the program itself should have no problems. The one thing I can't remember is if the USB-UIRT driver worked properly on the Vista x64 machine. Hopefully some other users can confirm this question.

Thanks, SB

[jameslsnyder]

Originally Posted by shadeblue.com

Hi James,

I am not currently running it full time on Vista x64, but it was originally developed on a Vista x64 machine, so the program itself should have no problems. The one thing I can't remember is if the USB-UIRT driver worked properly on the Vista x64 machine. Hopefully some other users can confirm this question.

Thanks, SB

Here is the log file after starting the service.
I am running the latest X64 driver for the USBUIRT.
Is your STBKeepAlive utility available in source code so one could try to get it to work with X64. It would save a lot of time having to write one from scratch.

Thanks Jim


2009-02-26 18:11:51,303 [4] FATAL STBKeepAlive.Service [(null)] - STBKeepAlive encountered a fatal exception in 'STBKeepAlive::Program::Main()'
System.TypeInitializationException: The type initializer for 'UsbUirt.Controller' threw an exception. ---> System.ApplicationException: Unable to read UsbUirt driver version ---> System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at UsbUirt.Controller.UUIRTGetDrvInfo(UInt32& drvVersion)
at UsbUirt.Controller..cctor()
--- End of inner exception stack trace ---
at UsbUirt.Controller..cctor()
--- End of inner exception stack trace ---
at UsbUirt.Controller..ctor()
at STBKeepAlive.Service.StartService()
2009-02-26 18:13:04,872 [4] ERROR STBKeepAlive.Service [(null)] - Quartz.SchedulerException: The Scheduler has been Shutdown.
at Quartz.Core.QuartzScheduler.ValidateState()
at Quartz.Core.QuartzScheduler.GetJobNames(SchedulingContext ctxt, String groupName)
at Quartz.Impl.StdScheduler.GetJobNames(String groupName)
at STBKeepAlive.Service.StopService()
Quartz.SchedulerException: The Scheduler has been Shutdown.
at Quartz.Core.QuartzScheduler.ValidateState()
at Quartz.Core.QuartzScheduler.GetJobNames(SchedulingContext ctxt, String groupName)
at Quartz.Impl.StdScheduler.GetJobNames(String groupName)
at STBKeepAlive.Service.StopService()