Serviio

Just upgraded to 1.3 pro from 1.21 pro and Serviio no longer starts automatically. Now, I have to manually start Serviio after a reboot. It auto started before the update.

I have both 32 and 64 bit Java installed. I already uninstalled all Java and Serviio and re-installed but it made no difference.

The error below is from the Windows Event Viewer:

...
The Serviio service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

- System

- Provider

[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager

- EventID 7030

[ Qualifiers] 49152

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8080000000000000

- TimeCreated

[ SystemTime] 2013-08-08T23:19:34.563989800Z

EventRecordID 27178

Correlation

- Execution

[ ProcessID] 768
[ ThreadID] 3568

Channel System

Computer No1

Security


- EventData

param1 Serviio

...

Which version of Windows?

Also, let us know the state of your Interactive Services Detection (start service.msc) service - whether running or not and whether set to start Automatically, Manually or is Disabled.

Windows 7 x64.

Interactive Services Detection service is disabled.

Serviio service is set to automatic.

After using ccleaner a couple of times and rebooting a couple of times it started working again. I don't know what causes this but I seem to remember it doing this last time I updated Serviio.

Have three Windows PC's here (one 32 bit, two 64 bit) - on all of them the service is set to Manual (and this is something we would never have tinkered with). I think this may be the issue ... for next time it arises

That's the first thing I checked. It was always set to automatic so something else is causing this to happen.

Still not working correctly.

The console is no longer starting on boot. However, the Serviio service is running.

But it has changed - originally the service wasn't starting..?

Post a detailed log showing when you are attempting to start the console. If it is only that the console is not starting with Windows, maybe the console is trying to start before the service has started? Do you get any messages? Leave detailed logging on and do a restart.