Hi all,
I previously had a working custom install of Xibo 1.8.6 with 1 registered win7 display.
I had been waiting on the V2 public release so I could upgrade to my new PHP7 server build on WAMP. With the new version released I sideways copied my existing 1.8.6 server folder to the new server, and overstamped it with the V2 release files, then transferred the mySQL tables with the data migration utility of the mysql editor. In preparation, I also had to get zmq loading in php which is now running (never had that working in v1.8.6).
I then hit trouble when trying to load and config the new release.
After much googling and community support, I found out the migrate option that had to be run from DOS. This completed cleanly. I then found I could sign into the Xibo front end.
My next task was to then build a new Win10 windows player client. I got a PC built and installed the client, but can not get it to register as no matter what I do, i get the following client response;
There has been an unknown error with XMDS, it has been logged. Please contact your administrator…
Googling this, I saw a couple of posts about how the web server must publish the /web as a document root folder, so have made the changes with the alias statement in apache config, and can now access the web folder directly from {server}/xibo, which seems to work well, and I can still access the cms front end on the server. The URL rewrite also appears to work as I dont have to specify index.php
But my fault with the windows 10 player issues still stands.
I see no log detail in the cms logs relating to any connection attempt, and google searching that phrase only leads me back to the issue about how /web must be document root (which it now is), and also another thread about display name must be the same in both default-config.xml and config.xml, which I have manually altered in default-config.xml to match the config.xml displayname.
I am now stuck.
Would appreciate any pointers as to what else this may be.
FYI, I found in another thread that communication to XMDS is done via a URL command. I disabled firewall thinking that may be impacting, if it was using some additional ports, but this made no difference. I can query the XMDS.php and I do receive a response.
If I try http://{server}/xibo/xmds.php I receive the following back;
<?xml version="1.0" encoding=" ISO-8859-1"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>Bad Request</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>