Running 6.0.30 on Win 7 - 2nd Instance

[rednaxelan]

Has anybody out there successfully installed a 2nd instance of TMS on Windows 7? I tried following the instructions in the readme.txt file but I always get the following errors:

C:\Program Files\TwonkyMedia>twonkymediaserver -installandstart 1
TwonkyMedia Version 6.0.30
01/09/11 11:55:42:951 [Critical] - LOG_DB:upnp_database_view_files_init : views
\view-definitions.xml missing
01/09/11 11:55:43:974 [Critical] - LOG_HTTP:remote_access_lock : critical secti
on not initialized
01/09/11 11:55:43:992 [Critical] - LOG_HTTP:remote_access_unlock : critical sec
tion not initialized

I'm sure that something simple has changed between the version I have and the version the instructions where written for, but I don't know enough about the TMS file structure (other than customizing nav trees).

Any suggestions would be greatly appreciated.

[parnott]

Has anybody out there successfully installed a 2nd instance of TMS on Windows 7? I tried following the instructions in the readme.txt file but I always get the following errors:

C:\Program Files\TwonkyMedia>twonkymediaserver -installandstart 1
TwonkyMedia Version 6.0.30
01/09/11 11:55:42:951 [Critical] - LOG_DB:upnp_database_view_files_init : views
\view-definitions.xml missing
01/09/11 11:55:43:974 [Critical] - LOG_HTTP:remote_access_lock : critical secti
on not initialized
01/09/11 11:55:43:992 [Critical] - LOG_HTTP:remote_access_unlock : critical sec
tion not initialized

I'm sure that something simple has changed between the version I have and the version the instructions where written for, but I don't know enough about the TMS file structure (other than customizing nav trees).

Any suggestions would be greatly appreciated.

I don't how it works in Windows but in Linux NAS devices the parameter is -instance followed by an instance number. You also need an -appdata parameter followed by a directory path to make sure the data from the two instances don't get mixed up.

[rednaxelan]

Thanks for you quick reply, the -instance command does seem to work, I think it creates all of the files it should (if I use the -appdata param it creates them in the directory specified, else it just creates a db[n] directory). It still however throws the same 3 errors after and will never start the instance. I did notice that the twonkymediaserver.exe will throw the same errors if I simply put -? as its only parameter:

C:\Program Files\TwonkyMedia>twonkymediaserver -?
TwonkyMedia Version 6.0.30

usage: twonkymediaserver

all params from the .ini file can be used as an option, preceded by a -
e.g. twonkymediaserver -v 255
-inifile path and filename of ini file
-inipath path to ini file
-ininame filename of ini file
01/09/11 13:25:41:205 [Critical] - LOG_DB:upnp_database_view_files_init : views
\view-definitions.xml missing
01/09/11 13:25:42:257 [Critical] - LOG_HTTP:remote_access_lock : critical secti
on not initialized
01/09/11 13:25:42:299 [Critical] - LOG_HTTP:remote_access_unlock : critical sec
tion not initialized

[parnott]

Thanks for you quick reply, the -instance command does seem to work, I think it creates all of the files it should (if I use the -appdata param it creates them in the directory specified, else it just creates a db[n] directory). It still however throws the same 3 errors after and will never start the instance. I did notice that the twonkymediaserver.exe will throw the same errors if I simply put -? as its only parameter:

C:\Program Files\TwonkyMedia>twonkymediaserver -?
TwonkyMedia Version 6.0.30

usage: twonkymediaserver

all params from the .ini file can be used as an option, preceded by a -
e.g. twonkymediaserver -v 255
-inifile path and filename of ini file
-inipath path to ini file
-ininame filename of ini file
01/09/11 13:25:41:205 [Critical] - LOG_DB:upnp_database_view_files_init : views
\view-definitions.xml missing
01/09/11 13:25:42:257 [Critical] - LOG_HTTP:remote_access_lock : critical secti
on not initialized
01/09/11 13:25:42:299 [Critical] - LOG_HTTP:remote_access_unlock : critical sec
tion not initialized

I'm only speculating here, but as Twonky is not finding the view file then I think your current directory needs to be-
C:\Program Files\TwonkyMedia>twonkymediaserver

before you start.

I always set the current directory to where the twonky exe is before I start it. But as I said this is with Linux so I do not know if this is needed for Windows..






'

[rednaxelan]

Thanks, directory was set correctly.

[phibertron]

I went down the same path as you, with same results

I then started to read the file "C:\Program Files\TwonkyMedia\ReadMe.txt" which also stated to do the install like so
twonkymedia -install
twonkymeida -install 1
I then noticed the typo on the, which got me to thinking, there is no file twonkymedia.exe
that is the old way/old name from 4.x up to 5.x if memory servers me right
which is when they started to use the name twonkymediaserver.exe in 5.x at some point
they used to also create a registry entry to launch twonkymediaserver.exe as a service
which then got me to thinking to what they use now, which is twonkymediaserverwatchdog.exe
as a service to launch twonkymediaserver.exe

so i tried "twonkymediaserverwatchdog.exe -install 1"
BAM! it worked

It copied and created all that it had to
The first question I had was, what port did it put in the server ini if at all
it did not put ports in either
but I took a guess that if service 1 was 9000 then service 2 must be 9001
which it was

beyond what i just did, thats all i know about it, will play with it more later

I did the above with 6.0.31

have fun

[phibertron]

If your interested, I put up a post on putting the whole thing together
with custom navtree's for each media type per instance

http://twonkyforum.com/viewtopic.php?f=2&t=9408