Can NEVER communicate with Serviio first time in Win 7

Hi,

I have Windows 7, and a Sony SMPN 200. Whenever I switch on my Win 7 PC Serviio automatically starts, and the Serviio console icon appears in the system tray, saying Serviio is running. I switch on the Sony, and there is no connection with Serviio. I then go back to my PC, open the console, and stop the serviio service, then close the console. I then go to Computer, right click, Manage, Services, and start the serviio service there, restart the console, and lo and behold the Sony now sees serviio and serviio sees the Sony.

I have tried powering the Sony first, rather than the PC, but still the same. I always have to stop then restart the serviio service.

Am I doing anything wrong? is there any way to avoid this?

Cheers

Rock

Bump:

nearly two months and no answer. Does anyone know?

Rock

[moltra]

Can you enable detailed logging. See signature. And start serviio then attach the serviio.log file.

Sent from my DROID RAZR using Tapatalk 2

[slyguy42o]

it sounds like the serviio service may be starting before the network is available, but lets look at the logs and see what they say.

[moltra]

You read my mind.

Sent from my DROID RAZR using Tapatalk 2

Here is the log.

Rock

[DenyAll]

+1 to the above- try delaying the startup of the Serviio service:

• Run service.msc
• Scroll down to the Serviio service
• Right click and select properties
• Change Startup Type from Automatic to Automatic (Delayed Start) and press OK

Restart PC to test.

[zip]

Also upgrade to 1.2.1

Upgraded to 1.2.1: no change.

Changed the seviio service from Automatic to Automatic (Delayed Start): this produced a different problem, I now get a serviio error message in the center of my screen which states:

'Cannot connect to Serviio, it doesn't seem to be running. Exiting...'

I am guessing that this error is coming from the Serviio Console, which checks for the serviio service, doesn't find it, and exits.

Back to the drawing board?

Rock

[DenyAll]

You are correct, the message you are seeing is from Serviio Console. However you don't need to start that at start-up (ie. Serviio works without the console running) so its not a major issue.

Does Serviio now work for you on the renderers (your Sony SMPN 200)? If so, then what is happening is for your system we have to delay Serviio startup until after your network fires up (the "Automatic (Delayed Start)" did this). Serviio Console can be started any time after the service starts (but unfortunately you can't have it in your startup group).

Don't know why your network takes so long to fire up - you're not unique though, others have had this problem. You may want to google your network card and see if there is a way to fire it up early, otherwise you are stuck with the delayed start for Serviio for now.

Thanks for that DenyAll.

Do you know how long a delayed start delays for? And can this time be adjusted?

I found in another thread a registry tweak that delays the Serviio service until the TCPIP service has been established (a dependency). I modified the registry and will test the results this evening, without the console in the Start-up group, and see what happens.

For information: I am using a wireless link to my Netgear router, and the Netgear software always seems to do a Network scan before connecting to my default Home network. I suppose I could download one of several utilities that allows you to set the start order of various start-up programs and processes, and put the network first and Serviio last, but I would imagine it would be easier for the writers of serviio to perform a network check before firing up the service, and if the network is not established yet to wait, say, 30 secs, then try again (and maybe a third time before exiting).

Rock

[DenyAll]

Hi Rock
I believe the Automatic (Delayed Start) simply places those items at the end of the queue ie. they run after all the Automatic Start items are complete - as such there is no set delay. I read the post on making the Serviio services dependant on TCP/IP - for other readers this is here - and it seems a sensible approach if you're comfortable editing the registry. It may even allow you to run the Console in start-up if it all happens fast enough.

Two other thoughts I had:

• firstly, are you using Netgear's Wireless manager software? If so, try just using the standard Windows wireless manager. Does the Netgear one do anything that you actually need (I gave up on third party wireless managers - the Win7 one does the job. Most third party ones in my experience just provide pretty interfaces and can cause issues);
• you should (if you are comfortable doing so) check your Windows Event logs. After startup, look for anything that is failing or taking a long time to start up. It could be that something else entirely is holding up the start-up of your network. A bad driver can do this.