Nested Variable / Clientname

Post beta version feedback on MainLobby releases
Bago
Intermediate
Intermediate
Posts: 452
Joined: Mon Dec 29, 2003 3:02 pm
Location: Potomac, Maryland
Contact:

Nested Variable / Clientname

Postby Bago » Tue May 16, 2006 10:42 pm

So here is my simple command:
MLServeCmd.{{{{clientname}}play}}

The server does not resolve clientname (dell), much less the full variable of dellplay.

I am using Ml 2.96.6 and MLS 2.0.247

User avatar
DavidL
Simply Incredible
Simply Incredible
Posts: 11071
Joined: Sat Feb 08, 2003 9:39 am
Location: Metamora, Michigan
Contact:

Postby DavidL » Tue May 16, 2006 11:16 pm

What is that suppose to do?
Doesn't look like a support syntax.

MLServeCmd.DellPlay ?

Bago
Intermediate
Intermediate
Posts: 452
Joined: Mon Dec 29, 2003 3:02 pm
Location: Potomac, Maryland
Contact:

Postby Bago » Wed May 17, 2006 8:20 am

First of all, this command worked prior to the beta versions.

What I did is establish variables that contain MLS commands for controlling dvd playback. By using this method as oposed to the default playback commands, I am able to establish controls based on the client location very easily.

Again, this command has worked in the past.

User avatar
mcascio
Founder
Founder
Posts: 8270
Joined: Tue Jan 28, 2003 4:03 pm
Location: Kenosha, Wi
Contact:

Postby mcascio » Wed May 17, 2006 12:31 pm

Barry,

Can you turn on verbose logging and see what's going on in the server? That should help you.

Are you trying to call a Macro?
Mario Cascio
Cinemar, Inc.
http://www.cinemaronline.com

Bago
Intermediate
Intermediate
Posts: 452
Joined: Mon Dec 29, 2003 3:02 pm
Location: Potomac, Maryland
Contact:

Postby Bago » Wed May 17, 2006 1:51 pm

The variable is a full blown MLS command (ofcourse I am not at home now to post it).

I have in the past been able to have a button as descrbed above call a client specific varible and then have the command associated with that variable run.

That is not happening now :cry:

When I get home I will post the commands, variables and the log.

Barry

User avatar
CinemarDave
Site Admin
Site Admin
Posts: 10535
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth
Contact:

Postby CinemarDave » Wed May 17, 2006 3:41 pm

DellPlay is a command map so just lose the MLServeCmd. and let it resolve as DellPlay.

User avatar
mcascio
Founder
Founder
Posts: 8270
Joined: Tue Jan 28, 2003 4:03 pm
Location: Kenosha, Wi
Contact:

Postby mcascio » Wed May 17, 2006 3:48 pm

Actually, if you assume Dell = clientname.
He's sending:
MLServeCmd.{{Dellplay}}

So the server would look up Dellplay and see what value it is set to.

So I'm assuming you have a variable that equals DellPlay in MLServer.

But as Dave mentioned, lose the beginning MLServeCmd.

If the macro name is in Fact Dell Play then it would be:
{{clientname}}Play
Mario Cascio

Cinemar, Inc.

http://www.cinemaronline.com

Bago
Intermediate
Intermediate
Posts: 452
Joined: Mon Dec 29, 2003 3:02 pm
Location: Potomac, Maryland
Contact:

Postby Bago » Fri May 19, 2006 9:08 pm

OK - I figured out the root of the problem, now I need help with the answer.

The primary server is prossessing the command properly. Here is the log

5/19/2006 10:04:18 PM Push dell MLServeCmd.{{{{clientname}}play}}
5/19/2006 10:04:18 PM Processing dell MLServeCmd.{{{{clientname}}play}}
5/19/2006 10:04:18 PM Subst In dell MLServeCmd.{{{{clientname}}play}}
5/19/2006 10:04:18 PM Subst Out dell MLServeCmd.MLRedirect|htpc::5005::MLServeCmd.MLZoomPlayer|PLAYPAUSE

What is not happening is the actual re-direct to the remote server. If I resent the final command from the primary server, the play command does trigger. So I looked at the remote server and got this log:

5/19/2006 10:07:15 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:15 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:15 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:15 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:15 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:15 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:15 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:15 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:15 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:16 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:16 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:31 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:31 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:32 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:32 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:32 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:32 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:32 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:32 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:32 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions
5/19/2006 10:07:32 PM Error CheckForconditionals Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by CheckForconditionals
5/19/2006 10:07:32 PM Error ExecuteConditions Error# -2147217865 - The Microsoft Jet database engine cannot find the input table or query 'Conditions'. Make sure it exists and that its name is spelled correctly. raised by ExecuteConditions

So what does this all mean?

User avatar
DavidL
Simply Incredible
Simply Incredible
Posts: 11071
Joined: Sat Feb 08, 2003 9:39 am
Location: Metamora, Michigan
Contact:

Postby DavidL » Fri May 19, 2006 11:06 pm

It probably means your databases are out of date. See a couple of posts by DaveP on the fix. Update to the latest MLServer and run the DB Updater and report back. If that doesn't work then do the fixes that DaveP has posted in the MLServer Beta thread.

User avatar
mcascio
Founder
Founder
Posts: 8270
Joined: Tue Jan 28, 2003 4:03 pm
Location: Kenosha, Wi
Contact:

Postby mcascio » Sat May 20, 2006 10:22 am

Hi Barry,

Looks like you are using an old Redirect command which should still work but isn't...perhaps Dave can address.

Here's a snippet from the following thread that you might try with the new syntax in the meantime:.
http://www.cinemaronlineforums.com/foru ... php?t=5946

- Retired Plug-In MLRedirect

The functionality of MLRedirect has been incorporated into the core server. Therefore MLRedirect is no longer included in the package. This introduces some changed functionality.

First, compatibility. The old syntax of MLServeCmd.MLRedirect... is still supported so none of your scenes need to be edited. However there is new syntax for sending redirects and you should migrate your commands to this new syntax.

The old syntax

MLServeCmd.MLRedirect|<server>::<port>::<command> .. is replaced with

MLServeCmd[<server>:<port>] ...

this can be further simplified to

MLServeCmd[<server>] ...

if you want to use the default redirect port as specified in Tools/Options

For example the old command

MLServeCmd.MLRedirect|Nemo::5004::Setvariable|Message~Hello World

will now be written as

MLServeCmd[Nemo:5005].Setvariable|Message~Hello World

Since port 5005 is the default port the command can be further simplified to

MLServeCmd[Nemo].Setvariable|Message~Hello World

Any of your existing MLRedirect commands that reference port 5004 will automatically be sent to port 5005.

Now let's talk about ports. In previous versions of the server MLRedirects were sent over the same port as the clients communicate on, typically 5004. These redirects consumed a client slot while in use and the processing of the command involved the creation of a communication channel, verifying the link, sending the command and finally tearing down the link. A lot of steps.

In the new scenario the link is established on the first redirect and then left up. Chances are if you did one redirect to a server you'll do another. The redirects communicate on a different port, 5005 by default. They no longer consume client slots.

The clients window has been modified to now display connected clients and connected remote servers.

Note: It is illegal to redirect commands to yourself.
Mario Cascio

Cinemar, Inc.

http://www.cinemaronline.com

Bago
Intermediate
Intermediate
Posts: 452
Joined: Mon Dec 29, 2003 3:02 pm
Location: Potomac, Maryland
Contact:

Postby Bago » Tue May 23, 2006 9:51 pm

OK - I fixed the error by deleting the commands database, and the server errors are cleared. Unfortunatly I still am not getting the redirect to the remote server (htpc). Here is the log from the primary server. The remote server log is empy.

If I send the last command from the primary server itself, the command works fine.

I am out of ideas?

5/23/2006 10:46:08 PM Push dell MLServeCmd.{{{{clientname}}pause}}
5/23/2006 10:46:08 PM Processing dell MLServeCmd.{{{{clientname}}pause}}
5/23/2006 10:46:08 PM Subst In dell MLServeCmd.{{{{clientname}}pause}}
5/23/2006 10:46:08 PM Subst Out dell MLServeCmd.MLRedirect|htpc::5005::MLServeCmd.MLZoomPlayer|PAUSE

User avatar
DavidL
Simply Incredible
Simply Incredible
Posts: 11071
Joined: Sat Feb 08, 2003 9:39 am
Location: Metamora, Michigan
Contact:

Postby DavidL » Tue May 23, 2006 10:19 pm

Bago,
Are you using the latest mlserver on both MLServer PCs?

Bago
Intermediate
Intermediate
Posts: 452
Joined: Mon Dec 29, 2003 3:02 pm
Location: Potomac, Maryland
Contact:

Postby Bago » Thu May 25, 2006 9:20 pm

Sorry it is taking me so long to respond, I am building a house, selling a house and, oh yea, running a business. :shock:

Anyway, I am running 2.0.247 on both systems. Frankly, this feature was lost a long time ago, but I simply have not realy tried to deal with it since I have not had time for movies for severa months.

I simply think that once the variable has been reconciled, the fact that it is a valid MLS command is not even being tested for, therefore it is not being run.

Like I said, this was working in the pre-beta versions.

User avatar
DavidL
Simply Incredible
Simply Incredible
Posts: 11071
Joined: Sat Feb 08, 2003 9:39 am
Location: Metamora, Michigan
Contact:

Postby DavidL » Thu May 25, 2006 9:23 pm

Bago, I assume you will be upgrading to ML3. Upgrade and then try. There have been so many changes that it's much more efficient to get on the latest and we'll go from there.

User avatar
CinemarDave
Site Admin
Site Admin
Posts: 10535
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth
Contact:

Postby CinemarDave » Thu May 25, 2006 9:26 pm

In theory the old MLRedirect commands are still supported but the server will translate them into the new syntax. You should see entries in the event log complaining about the old syntax. I agree with David. Upgrade to version 3.0.4 of the server that was released tonight and then let's go from there.


Return to “MainLobby Beta”

Who is online

Users browsing this forum: No registered users and 1 guest