Hi
WMS works 100% when not running as a service, but once I install it as services it become very unstable.
Some movies won’t play, no internet radio, and transcoding display does not work, once it’s NOT a service, all it well again.
I have tried uninstalling, reinstall, clean registry, uninstalling & reinstall VLC player.
The only thing that makes a difference is giving the service the "everyone" permission, but it is still not totally stable.
This has been link this ever since I installed it 4+ months, I would really like to get it fixed.
Any help would be appreciated
WMS 1.09.1, windows 7 x64 unlimited SP1, Norton 360
Installing as a service problems
Re: Installing as a service problems
Hi,
Control Panel - System and Maintenance - Administrative tools - Services - "Wild Media Server (UPnP, DLNA, HTTP)" - right click - Properties - Logon - This account - ...
Control Panel - System and Maintenance - Administrative tools - Services - "Wild Media Server (UPnP, DLNA, HTTP)" - right click - Properties - Logon - This account - ...
Re: Installing as a service problems
Hi Eugene,
I have encountered the same issue after upgrading from 1.08.2 to 1.09.1 on Windows 7 Ultimate (SP1). I have done several upgrades before with no issue. Switching from the Local System account to an administrative account didn't have any effect. My symptoms are that I can browse the folders from my clients (Philips & Panasonic DLNA tv's), and I even see the thumbnails of the movies, but when I start any movie, it just flickers and immediately returns to the list with movies. This is irrespective of the chosen transcoding. When switching to manual start of the server, everything works as before.
I didn't try it, but might it be related to Windows 7 SP1? Last time I upgraded was before applying SP1.
I'd really like to test with an older version of Wild Media Server. Do you have a link to previous WMS distributions so I can check whether it's WMS or SP1 related?
Thanks,
Radboud
I have encountered the same issue after upgrading from 1.08.2 to 1.09.1 on Windows 7 Ultimate (SP1). I have done several upgrades before with no issue. Switching from the Local System account to an administrative account didn't have any effect. My symptoms are that I can browse the folders from my clients (Philips & Panasonic DLNA tv's), and I even see the thumbnails of the movies, but when I start any movie, it just flickers and immediately returns to the list with movies. This is irrespective of the chosen transcoding. When switching to manual start of the server, everything works as before.
I didn't try it, but might it be related to Windows 7 SP1? Last time I upgraded was before applying SP1.
I'd really like to test with an older version of Wild Media Server. Do you have a link to previous WMS distributions so I can check whether it's WMS or SP1 related?
Thanks,
Radboud
-
- Posts: 98
- Joined: Sat May 08, 2010 8:12 pm
Re: Installing as a service problems
Hi,
The same happens within Windows XP so probably this is something Win7 SP1 has nothing to do with.
I was running my WMS as a service in the context of a restricted user on a virtual Windows XP box. After 1.09.x update it stopped working normally and the symptoms are similar to this topic. The problem was solved by giving that account administrator's privileges. But let's not forget Win7 is quite different from XP. Try switching off UAC on Win7. Also keep in mind the difference between services running in the local system context and those under a specific user's account. The later are non interactive thus they can't be given anything if they don't have the privileges to access it. I presume that since 1.09x WMS probably does use something which is subject to access restrictions. But I won't bet on that. Only Eugene could give an answer. Talking about him he hasn't been around for a while, has he?
Regards
The same happens within Windows XP so probably this is something Win7 SP1 has nothing to do with.
I was running my WMS as a service in the context of a restricted user on a virtual Windows XP box. After 1.09.x update it stopped working normally and the symptoms are similar to this topic. The problem was solved by giving that account administrator's privileges. But let's not forget Win7 is quite different from XP. Try switching off UAC on Win7. Also keep in mind the difference between services running in the local system context and those under a specific user's account. The later are non interactive thus they can't be given anything if they don't have the privileges to access it. I presume that since 1.09x WMS probably does use something which is subject to access restrictions. But I won't bet on that. Only Eugene could give an answer. Talking about him he hasn't been around for a while, has he?
Regards
Re: Installing as a service problems
Hi Eugene,
Since today, the issue got worse: I am no longer able to play any movie, either when running WMS as a service or as a 'normal' application. I can still browse my movies, but when I try to start one, it flickers and then returns me to the movie browser. The same behaviour occurs on both my Philips and my Panasonic TV.
I didn't make any changes. The only thing I can think of is that I have started WMS once when I was logged on with a non-admin account, while I normally launch WMS when logged on as admin (I know...not best practice
Is there any way I can 'downgrade' to the previous stable version?
Thanks,
Radboud
Since today, the issue got worse: I am no longer able to play any movie, either when running WMS as a service or as a 'normal' application. I can still browse my movies, but when I try to start one, it flickers and then returns me to the movie browser. The same behaviour occurs on both my Philips and my Panasonic TV.
I didn't make any changes. The only thing I can think of is that I have started WMS once when I was logged on with a non-admin account, while I normally launch WMS when logged on as admin (I know...not best practice

Is there any way I can 'downgrade' to the previous stable version?
Thanks,
Radboud
Re: Installing as a service problems
Thanks Eugene,
Tested that and it worked! I'm now able to run as a windows service again. No requirements to use a different account, just using 'local system'.
Thanks again,
Radboud
Tested that and it worked! I'm now able to run as a windows service again. No requirements to use a different account, just using 'local system'.
Thanks again,
Radboud