Twonky Forum

I evaled Twonky on v4, and it worked a treat on Windows Server 2008. I purchased Twonky, but the key was for v5, which I downloaded and installed.

The v5 server service crashes within a few seconds on start on Windows Server 2008. I tried it on XP as well, and it crashes as well. I reinstalled v4 on an XP machine in eval mode and it works again.

However, the v4 eval will expire soon on my XP machine, and has already expired on my Server 2008 machine,

I have emailed support (from the web site), several times with no response. Frankly I would be happy to stick with v4 if only Twonky would supply a valid licence key.

Anybody else having problems with the server service crashing in v5? I only have about 5,000 songs in WMA format in the library - ripped from the CDs I've purchased over the years.

Thanks

Try moving out you media to a different directory that is not included in TMS sharing, as it may be the file scanner that's crashing due to a corrupt media file.

Thanks for the advice. I found 1 faulty track out of 5,440. The software doesn't seem very robust. That fixed that problem... now I need to resolve the next problem... v5 doesn't work properly with the Roku Soundbridge any more

jeremy.lloyd wrote:Thanks for the advice. I found 1 faulty track out of 5,440. The software doesn't seem very robust. That fixed that problem... now I need to resolve the next problem... v5 doesn't work properly with the Roku Soundbridge any more

Keep that corrupt file handy. Twonky support may want to look at it, see why v5 server crashes and V4 does not.

kiltbear wrote:

mgillespie wrote:Try moving out you media to a different directory that is not included in TMS sharing, as it may be the file scanner that's crashing due to a corrupt media file.

Then why does TwonkyMedia Server 4.4.9 have no issues with my media and never crashes?

Do you have any idea what a monumental task it is to find out which file among tens of thousands of photos, videos and audio files is causing the new version to trip ands crash?

I am assuming it would be far easier on the user base to have the software behave as before, just skipping over files it doesn't like instead of going *poof*

The new server does indeed seem to have major stability issues and IHMO is not quite ready for prime time.

The trick here, is to move all your media out to a different directory, make sure the server then behaves itself. Switch on the debug logging, shutdown the server, move all the media back (or I would suggest, part by part if you can, i.e. photos, then movies, then music). When the server crashes, open the log file, it should indicate the last item the filescanner was processing. This file is your likely suspect.

I found the problem the other way, by redirecting TMM to an empty folder and moving the media across in blocks until TMM crashed, then slowly deleting files and folders until it worked again.

In my case the problem was a WMA of 6k, so perhaps the best place to start is a Windows search for all audio files below a certain size (eg 20k).

I found the Twonky log to be a little coarse, but it confirmed my analysis. The log file, BTW, is in c:\windows\temp\TwonkyMediaServer-log.txt.

Regards

I have the same problem.

since i upgraded to twonky media server 5.0.40 the server crashes after 2 or 6 minutest after start.
this only happens, if i include an 6gb music folder. Its very difficult to find the file, which causes the problem!

with twonky media server 4.4.9, this folder can be scanned with out any problems. but this version has problems with my 12mpx pictures.

I payed for the version 4 and also for the version 5 so i hope that this problems will be fixed at time.

--
Server: Ubuntu 8.04 x68
TMS: 4.4.9 (image size problem) and 5.0.40 (music problem)
Client: PS3 2.52
Network: 100Mbit wired