Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 207254" data-attributes="member: 21313">The same problem Visteon is having <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />I'd really like to get to the bottom of this one.&nbsp; I'm wondering if it has anything to do with the broken installer from the previous versions, in that they leave something behind somewhere.Here's my start code:[code]&nbsp; &nbsp; &nbsp; &nbsp; protected override void OnStart(string[] args)&nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TvScheduler.ServiceImplementation.EventLogger.Initialize();&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; try&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; // Start all services&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _tvGuideServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.TvGuideService));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _tvSchedulerServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.TvSchedulerService));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _logServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.LogService));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _configurationServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.ConfigurationService));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; string exePath = System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Directory.SetCurrentDirectory(Path.GetDirectoryName(exePath));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; // XMLTV Imported Thread&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _xmltvImportThread = new XmlTvImportThread();&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; _xmltvImportThread.Start();&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; catch (Exception ex)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TvScheduler.ServiceImplementation.EventLogger.WriteEntry(ex);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; throw;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; TvScheduler.ServiceImplementation.EventLogger.WriteEntry(&quot;TvScheduler service started.&quot;, EventLogEntryType.Information);&nbsp; &nbsp; &nbsp; &nbsp; }[/code]What's puzzling me is that in all error cases it will log an error in the event-log.&nbsp; So it almost looks like the service simply isn't loading.&nbsp; Or the error must occur in EventLogger.Initialize() which is also hard to imagine.Can you try the following: use a command prompt and go to the &quot;TV Scheduler&quot; directory in program files, then run TvScheduler.WindowsService.exe manually.&nbsp; Does it simply complain that it is a service and can't run that way?&nbsp; Or do you get an error?----<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp; Hmmmm...&nbsp; Perhaps I should &quot;ghost&quot; the menu instead?&nbsp; Or isn't this more a matter of getting used to it?</blockquote>

[QUOTE="dvdfreak, post: 207254, member: 21313"] The same problem Visteon is having :( :( I'd really like to get to the bottom of this one. I'm wondering if it has anything to do with the broken installer from the previous versions, in that they leave something behind somewhere. Here's my start code: [code] protected override void OnStart(string[] args) { TvScheduler.ServiceImplementation.EventLogger.Initialize(); try { // Start all services _tvGuideServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.TvGuideService)); _tvSchedulerServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.TvSchedulerService)); _logServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.LogService)); _configurationServiceHost = OpenNewServiceHost(typeof(TvScheduler.ServiceImplementation.ConfigurationService)); string exePath = System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName; Directory.SetCurrentDirectory(Path.GetDirectoryName(exePath)); // XMLTV Imported Thread _xmltvImportThread = new XmlTvImportThread(); _xmltvImportThread.Start(); } catch (Exception ex) { TvScheduler.ServiceImplementation.EventLogger.WriteEntry(ex); throw; } TvScheduler.ServiceImplementation.EventLogger.WriteEntry("TvScheduler service started.", EventLogEntryType.Information); }[/code] What's puzzling me is that in all error cases it will log an error in the event-log. So it almost looks like the service simply isn't loading. Or the error must occur in EventLogger.Initialize() which is also hard to imagine. Can you try the following: use a command prompt and go to the "TV Scheduler" directory in program files, then run TvScheduler.WindowsService.exe manually. Does it simply complain that it is a service and can't run that way? Or do you get an error? ---- :) Hmmmm... Perhaps I should "ghost" the menu instead? Or isn't this more a matter of getting used to it? [/QUOTE]

Verification