Unable to register screen(s) with server

Asked by MCowley

Good afternoon.

Whenever I try to register any PC with the server, I receive the following error message.

Value cannot be null.
Parameter name: stream

I have checked all the information I have entered within the settings tabs and they all appear to be correct. Thus far I have had no issues with accessing any part of the web console.

Thanks in advance for your advice.

Question information

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

Hi

Thanks for trying Xibo. Where is that error message reported? In the status window above the Register button?

Revision history for this message
MCowley (m-cowley) said :
#2

The error is shown in the Client Options screen in the Register Display tab's Results box once the Register button is clicked.

I have done a bit of looking into this, and I think it may be something to do with DotNet. An error is also created in the Event Viewer with the following info:

------------------------------------------------------
Source: Userenv
Type: Error
Event ID: 1041
User: NT AUTHORITY\SYSTEM

Details:
Windows cannot query DllName registry entry for {CF7639F3-ABA2-41DB-97F2-81E2C5DBFC5D} and it will not be loaded. This is most likely caused by a faulty registration.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------

Hope this helps.

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

OK. In theory, it only requires .net 2.0 but if you don't mind installing 1.1 and 3.0 and 3.5 to be sure :D

Failing that, try the 1.0.0-rc1 client and see if that gives the same messages?

Revision history for this message
MCowley (m-cowley) said :
#4

The odd thing is, I write programs in 3.5, and so have already got that installed and updated on all the PCs I have tried thus far. The client is also the latest version (downloaded yesterday).

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

Strange. Do you have the same problem with the 1.0.0-rc1 client?

Revision history for this message
MCowley (m-cowley) said :
#6

Ok, sorry for the delay.

Turns out I was running the RC1 client. I have removed that version from the 2 test PCs and installed the RC2 version. Both PCs still experience the same error message when trying to register with the server.

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

OK. And you filled in the URL of your server install, key etc and clicked Save. Then went and clicked Register?

Revision history for this message
MCowley (m-cowley) said :
#8

All settings saved and register clicked with same error.

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

OK. Leave it with me. I'll try and reproduce it here.

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

Do you have IE8 installed? Or have you had IE8 installed on those machines?

Revision history for this message
MCowley (m-cowley) said :
#11

No, both are running fully patched IE7.

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

I've been and tried to replicate this, but couldn't. Dan will take a look for you later.

Revision history for this message
Dan Garner (dangarner) said :
#13

Hi there, sorry for the delay.

I've just refreshed my memory on the code behind the Register button and it is basically all down to VS2005. The only thing the button does is call the SOAP service which resides on the server (XMDS.php). It is all running through the web reference classes created by VS.

I have built you another version of XiboClient.exe which will also print a Stack Trace in the results text box - hopefully this will give us a better understanding of where the error is occurring. I have also rebuild the web reference in this version, just in case.

I have created a bug: https://bugs.launchpad.net/bugs/337372 and attached the Newer Build in a ZIP. (This patch is the debug build)

If you could also check in the "Display Admin" section of the Web Console - it may be that your client is present in the list of displays (meaning the request did get through, it just blew up on the response).

Thanks for trying Xibo!

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

For info.

We tested against our test server and the client worked fine. I've been unable to reproduce this error against IIS 5.1 which is the platform OP is using.

Revision history for this message
Dan Garner (dangarner) said :
#15

I have just (accidentally ill admit) been able to reproduce this bug.

I believe the XMDS on your installation is raising a fatal error and therefore outputting a blank response to the client (stream = null).

If you have the time there are some possible steps to getting this resolved. The server application includes a debugging and auditing system which can be enabled in the settings. Could you:

1. Go to Management > Settings
2. Go to the Error tab
3. Set Debug and Audit to "On"
4. Go to Management > Log

5. Open the Options for the client
6. Click Register

7. Back in the server. Click Refresh on the Log
8. Disable the debug and audit (will fill up the database if left on)

If you could paste a dump of the log contents. If there was nothing you can open the filter and adjust the number of seconds to go back.

I am hoping there will be an error raised by XMDS!

Thanks

Revision history for this message
MCowley (m-cowley) said :
#16

Hi Dan.

Thanks for the suggestion. I have made the changes you suggested to start the log. When I attempt to add a client I receive the same error in the client system, but there is no entry added to the server log apart from those showing that the report SQL has been run.

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

What if you just go to http://your-server/path/xmds.php

Does it report any error there?

Revision history for this message
MCowley (m-cowley) said :
#18

Ok, now we're getting somewhere. xmds.php gives an error 500 - Internal Server Error.

If I turn off friendly error messages the page is completly blank with no error shown.

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

Hi

That error 500 should raise an event in the event log - hopefully with some kind of useful error?

Alex

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

Just to clarify I mean the Windows Event log, rather than Xibo's own logging.

A

Revision history for this message
MCowley (m-cowley) said :
#21

Ok, I’ve done a little more digging to see what I can work out. There are no entries in the Event Viewer of the server when the xmds.php is access from a client PC.

Not sure if this is of any help, but I attempted to run the xmds.php file from the command line and received the following error:

PHP Parse Error: Parse error in c:\server\lib\xmds.inc.php on line 55.

From looking at the scripts, this seems to be a problem with the settings.php file. To make sure there were no problems with the installation, I re-added the install.php file and created new databases. The error still persists. The settings file seems quite short, is this normal?

--------------------------------------------------------------------------------------------
<?php /* * Xibo - Digital Signage - http://www.xibo.org.uk * * This file is part of Xibo - and is automatically generated by the installer * * You should not need to edit this file, unless your SQL connection details have changed. */ defined('XIBO') or die("Sorry, you are not allowed to directly access this page.<br /> Please press the back button in your browser."); global $dbhost; global $dbuser; global $dbpass; global $dbname; $dbhost = 'localhost';
$dbuser = 'xibo';
$dbpass = 'xibo';
$dbname = 'xibo_v2';

define('SECRET_KEY','rM2bfT2r0vnE');
?>
--------------------------------------------------------------------------------------------

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

The settings file looks fine.

There was a bug in 1.0.0-rc1 surrounding line 55 of xmds.inc.php

Can you go here: http://bazaar.launchpad.net/~xibo-maintainers/xibo/dev/files/12/server//lib/

and find xmds.inc.php, and at the end of that line there is a little file with a green arrow pointing down. That should let you download just the one file. Replace the version you have with the one you just downloaded. (it lives in lib).

If that fixes it, it looks to me like you're running 1.0.0-rc1 not 1.0.0-rc2, in which case I'd strongly suggest you upgrade as there are a few bugs in 1.0.0-rc1 that break it in places.

Cheers

Alex

Revision history for this message
MCowley (m-cowley) said :
#23

Thats got it! Thanks a lot for the help and good luck with the rest of the project.