For The Record - The rule-based scheduling suite (8 Viewers)

[dvdfreak]

Yep everything is working, the services in IE also...

Excellent, if all testing goes this smoothly I'll have to hurry with uploading that WinForms test program

 

[LANJAN]

I downloaded and installed.
First thing I notice:
When I start the service, Windows tells me that the service has been started and immediately closed since it had nothing to do.
As a result of that nothing happens when I add XML files.

Hope that helps.

 

[jake78]

Everything worked great here as well...

// Jacob

 

[THDBASED]

Yep everything is working, the services in IE also...

Excellent, if all testing goes this smoothly I'll have to hurry with uploading that WinForms test program

Yes indeed!!

 

[dvdfreak]

I downloaded and installed.
First thing I notice:
When I start the service, Windows tells me that the service has been started and immediately closed since it had nothing to do.
As a result of that nothing happens when I add XML files.

Hope that helps.

Can you check with the Event Viewer (eventvwr.exe) if an error is logged when you try to start the service? Can you then tell me what the error was?

Thanks!

 

[LANJAN]

There are two entries in the eventviewer:
first in the application part:

Service cannot be started. System.IO.FileNotFoundException: Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
at TvScheduler.WindowsService.TvSchedulerService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

then the system part:
both messages issued by the Service Control Manager

The TvScheduler service was successfully sent a start control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and this:

The TvScheduler service entered the stopped state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Maybe as a side note (should have said that way earlier): I am running windows x64

hope that helps

 

[dvdfreak]

There are two entries in the eventviewer:
first in the application part:

Service cannot be started. System.IO.FileNotFoundException: Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
at TvScheduler.WindowsService.TvSchedulerService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

...

hope that helps

Yes! Did you install .NET Framework 3.0? My guess is you missed that requirement and that you don't have it installed?

 

[LANJAN]

OMFG I suck! I thought it was 2.0
I didn't even know that there was a 3.0 already.
That makes 3 installations on my pc :/
I'm so sorry. I'll let you know if it works with the 3.0.

 

[dvdfreak]

OMFG I suck! I thought it was 2.0
I didn't even know that there was a 3.0 already.
That makes 3 installations on my pc :/
I'm so sorry. I'll let you know if it works with the 3.0.

Hehe, no problem man, easy mistake to make!

But at least this explains the error you got. Perhaps I should add an extra check to the installer itself, not allow the service to install unless .NET 3.0 is detected... Will be clearer to the user than what you got.

 

[LANJAN]

I think that would be an excellent addition.