Registering Clients, Value cannot be null.

Asked by Jack Rowley

Ive read a number of similar questions and havent been able to find any clear reason for this, or a method to correct it.

I have 10 Screens, all of them have been registered previously i beleive around 1.0.4, around the same time as they registered succesfully they stopped being able to be registered and stopped receiving updates from the server, we decided to upgrad the server to 1.0.6 and the clients to 1.0.5 to see if this solved the problem, however were still having issues, sometimes the screens will update on their own, other times they wont, it seems i cant register any screens now, ive just tried to install a fresh 1.0.5 client on this machine and its not having it. According to the admin page none of the screens are logged in, when i know atleast 9 of them should be active.

Anyone got any ideas or suggestions? Im at abit of a loss of where to go.

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Alex Harrington
Solved:
Last query:
Last reply:
Revision history for this message
Alex Harrington (alexharrington) said :
#1

On the client, go to the Register tab and click the Register button.

What message is displayed in the white box?

Revision history for this message
Jack Rowley (jrowley) said :
#2

Value cannot be null.
Parameter name: stream

Revision history for this message
Alex Harrington (alexharrington) said :
#3

OK. In a web browser, go to:

http://your.server/path/xmds.php

What do you get?

Revision history for this message
Jack Rowley (jrowley) said :
#4

"NuSOAP: xmds

View the WSDL for the service. Click on an operation name to view it's details."

Various links to details.

I would expect its what im supposed to see.

Revision history for this message
Alex Harrington (alexharrington) said :
#5

OK.

In the client options, can you check the following:

Xibo Settings Tab:
Your server key isn't empty (ie you have a non-null server key and it's correct).
The client key isn't empty
Your server URI is in the same format as you used in the browser: http://example.domain.com/xibo

Register Display Tab:
Display Name isn't empty and doesn't contain non a-z A-Z characters.

Alex

Revision history for this message
Jack Rowley (jrowley) said :
#6

Server key is populated and correct.

Client key is populated.

The Server URI is identical.

Display name is populated and is in a normal format.

Revision history for this message
Alex Harrington (alexharrington) said :
#7

OK.

On the server, can you please run through the "Report Fault" routine on the Management menu.

At the point where it asks you to recreate the problem, click register on the client application.

Once you have the troubleshoot.txt file, please email it to <email address hidden>

Cheers

Alex

Revision history for this message
Alex Harrington (alexharrington) said :
#8

There's nothing in the log section of the troubleshoot file.

Did you step through all the steps in the routine and then hit register on the client at the appropriate point?

I would expect to see at least the log of you turning debug/audit on and off as well as the webservice logging the connection.

Alex

Revision history for this message
Alex Harrington (alexharrington) said :
#9

One thing I notice from the dump is you're running PHP 5.3.0.

Some people report problems with nuSOAP on PHP 5.3.

nuSOAP (not part of Xibo, but what we use to provide the webservice) is a dead project. The next series of Xibo will be using PHPs own SOAP implementation.

You might try switching to PHP 5.2 in the interim.

Alex

Revision history for this message
Jack Rowley (jrowley) said :
#10

I stopped at step 4 because you said to email you as soon as i had the troubleshoot.txt file...so i did...

I just followed all of the steps and the file is identical. So i dont really know what to tell you, the server isnt logging correctly.

Revision history for this message
Best Alex Harrington (alexharrington) said :
#11

That's fine.

In that case I'd say there's something fundamentally broken with the server - probably in PHP - or you have some strange options enabled somewhere.

I'd try downgrading to PHP 5.2 if you're in a position to do so.

Alex

Revision history for this message
Alex Harrington (alexharrington) said :
#12

One other thing that just occured.

You might check that the server is in "Production" mode, not "Test" in the settings.

Alex

Revision history for this message
Jack Rowley (jrowley) said :
#13

Im using the xampp webserver that is needed for this guide: http://wiki.xibo.org.uk/wiki/Install_Guide_Xibo_Server , as far as i was aware it came "fully loaded" so to speak, i now have to downgrade what the guide says i need? Because i mean, we havent modified it. Except for the upgrades to the xibo server itself.

The server is in production mode.

Im looking into downgrading php currently.

Revision history for this message
Alex Harrington (alexharrington) said :
#14

When I wrote the guide the link went to a version of XAMPP that came with PHP 5.2.9 I think. Certainly not PHP 5.3.

As I said some people (on Linux) run PHP 5.3 without issue but I know of one other person running Windows who had issues with nuSOAP on PHP 5.3.

I'll see if I can find you a download for the old version of XAMPP.

Alex

Revision history for this message
Alex Harrington (alexharrington) said :
#15
Revision history for this message
Jack Rowley (jrowley) said :
#16

Alright ill take a look at that.

Revision history for this message
Jack Rowley (jrowley) said :
#17

Thanks Alex Harrington, that solved my question.

Revision history for this message
Jack Rowley (jrowley) said :
#18

Specifically downgrading PHP to 5.2.9, instead of 5.3, appears to have corrected the updating, the registering and the clients appearing to be logged off when they should be logged on.

I look forward to your updates in the future and thanks for your constant support.

Cheers, Jack.

Revision history for this message
Alex Harrington (alexharrington) said :
#19

No problem.

I've added a note to the wiki warning people using Windows to use 1.7.1 version of XAMPP.

Regards

Alex

Revision history for this message
fengqiang@mwi.com.sg (fengqiang) said :
#20

Hello Alex, when I install Xampp 1.7.1, xibo client cannot register to the server, it says: "There was an error during asynchronous processing. Unique state object is required for multiple asynchronous simultaneous operations to be outstanding.", after sometime, Windows platform shows that There is a problem with Apache HTTP Server has stopped working. it seems that the http://localhost/xibo/xmds.php is not working, although I still can log into the xibo admin web page

However, for Xampp 1.7.3, it works. I am using windows vista home premium.

Thank you very much!

Revision history for this message
Alex Harrington (alexharrington) said :
#21

You'll see in the install instructions we recommend that version of xampp for exacrly this reason. The 1.2 series doesn't use nusoap and therefore doesn't suffer from this.

Alex

--- original message ---
From: "<email address hidden>" <email address hidden>
Subject: Re: [Question #103713]: Registering Clients, Value cannot be null.
Date: 11th July 2010
Time: 3:31:05 am

Question #103713 on Xibo changed:
https://answers.launchpad.net/xibo/+question/103713

<email address hidden> posted a new comment:
Hello Alex, when I install Xampp 1.7.1, xibo client cannot register to
the server, it says: "There was an error during asynchronous processing.
Unique state object is required for multiple asynchronous simultaneous
operations to be outstanding.", after sometime, Windows platform shows
that There is a problem with Apache HTTP Server has stopped working. it
seems that the http://localhost/xibo/xmds.php is not working, although I
still can log into the xibo admin web page

However, for Xampp 1.7.3, it works. I am using windows vista home
premium.

Thank you very much!

--
You received this question notification because you are a member of Xibo
Developers, which is an answer contact for Xibo.

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer