Media Server Update Error

[swetterling]

I've recieved an error from a media server when trying to update it's configuration:
"Failed to notify server ERR: cannot open server connection"
Any ideas?

[keith]

Has the IP or machine name of the Media Server changed?


Usually what I do is restart the Media Server to see if that makes any difference: (in a command prompt window)
net stop wavemediaserver
net start wavemediaserver

If it does open, I put the Media Server into command line. You do this from a command prompt window as well, inside the \Program Files\Twisted Pair Solutions\WAVE\MediaServer subdirectory:
wavemediaserver --cmdline

That should tell you exactly what the problem is. If you are unsure what the logs mean, feel free to paste or attach them here.
You might have to open up wavemediaserver.ini in a text editor and change debug=n to debug=y.
(This is the same process as using DebugView, but does consume much more resources. We only recommend this for quickly troubleshooting something and do not leave this running in a production environment in cmdline mode)

Also make sure the URL located in wavemediaserver.ini in the same directory is correct. The %s at the end translates to the machine name and is ok. You can paste this url (changing the %s to the Media Server name which is probably the machine name) into a web browser from the Media Server machine to verify HTTP connectivity.

[swetterling]

I restarted the media server, and on the initial restart, it did grab the latest config. However, when I manually tried to reconfig the media server, I received the same error again. From the command line, I did get the following error: "onPreflight function failed". The error only seems to occur on successive reconfigurations after intial start-up,

[keith]

There's two messages that should have preceded the OnPreflight message are:
“Cannot create duplicate check handle”
“Another instance of this application is already running”

And its usually caused by trying to run 2 instances of the Media Server at the same time. You can use Task Manager to verify only one process is running.

Can you paste all your cmdline messages?

It might be nicer to save the logs using DebugView, here's a link to download it: http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

As long debug=y is in the wavemediaserver.ini you should see debug info once executing DebugView. This is superior to the cmdline method since it does not require direct screen writes so you can safely leave it in the background without taking up much more cpu.

[kcarpenter]

When you perform a reconfig selected on the Mgmt server it will open a TCP connection to port 31325 on the Media server to let it know it's time to get a new configuration. A simple test is to telnet to the IP of the Media server from the Mgmt server like this: "telnet 192.168.1.10 31325" without the quotes of course. If the screen clears then you have access and you should be able to reconfig successfully.

If you cannot access the Media server via telnet on 31325 then there is something else going on here, usually a DNS issue. Make sure the fields in the Media server's configuration page accurately reflect hostnames that match your DNS records, another option is to use IP addresses instead. Let us know if you have any questions.

Thank you,
Kenneth

[swetterling]

I've looked deeper into my servers and network, and I think I can attribute this error to a bad DNS entry. I've corrected the DNS issue and have not had the problem re-occur. Thanks for your help!

[kcarpenter]

Great news! Glad we could help.

Thanks,
Kenneth