Xibo

Cleint Application will not run

Asked by Brooks

Hello,
I have Xibo running on two other clients perfectly. I’m trying to install it on a 3rd in the same manner, for some reason it installs perfectly but then when I try to run the setup or the actual player application, nothing happens. I ran it from the command prompt and saw no output.

I reinstalled all the .NET stuff and no better. Any ideas? I’m hoping to get this third display working very soon!

Thanks so much,
Brooks

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

Is there anything logged in the Windows event log?

I expect it's some corruption in the .net Frameworks. I'd suggest running "sfc /scannow" from an Administrator command prompt to check the integrity of the .net framework files.

If that doesn't solve it, and there's nothing in the event log then I'm out of ideas. You'd probably be best to reinstall Windows from scratch.

Alex

Revision history for this message
Bartek (czajka) said : 		#2

Hello,

There is a very handy tool to cleanup .net instalattions when there some problems with net installation. After cleanup You can reinstall .net sp3 sp1 again.

http://blogs.msdn.com/astebner/pages/8904493.aspx

Revision history for this message
Brooks (bwhiteford) said : 		#3

Turns out there is errors in the Event Viewer:

Error code is 7A09795E: ".NET Runtime 2.0.50727.3603 - Fatal Execution Engine Error"

Running the Player Settings program generates 437 instances of this error.

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

You need to remove/reinstall the framework. Use the tool Barrel linked.

Alex

Brooks <email address hidden> wrote:

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

    Status: Answered => Open

Brooks is still having a problem:
Turns out there is errors in the Event Viewer:

Error code is 7A09795E: ".NET Runtime 2.0.50727.3603 - Fatal Execution
Engine Error"

Running the Player Settings program generates 437 instances of this
error.

--
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

Revision history for this message
Brooks (bwhiteford) said : 		#5

Alrighty,
   I wiped all of the .NET stuff using that tool, and reinstalled just 3.5 from Windows Update. Now, I get the "encountered a problem a needs to close" box, and in the event viewer is a single error with code CLR20r3 which is a system.nullreferencexception.

Are we getting warmer?

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

Are you running in Virtual Box?

Brooks <email address hidden> wrote:

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

    Status: Answered => Open

Brooks is still having a problem:
Alrighty,
   I wiped all of the .NET stuff using that tool, and reinstalled just 3.5
from Windows Update. Now, I get the "encountered a problem a needs to
close" box, and in the event viewer is a single error with code CLR20r3
which is a system.nullreferencexception.

Are we getting warmer?

--
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

Revision history for this message
Brooks (bwhiteford) said : 		#7

Nope, running natively on XP. Thanks for your help so far by the way!

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

Can you try the 1.0.7 test client: http://dl.dropbox.com/u/353651/XiboClient-1.0.7-test.zip

Unzip those files into the existing XiboClient program folder.

Alex

Revision history for this message
Brooks (bwhiteford) said : 		#9

It's running!!!! What's different about 1.0.7? Thank you so so much!

Revision history for this message
Brooks (bwhiteford) said : 		#10

Thanks Alex Harrington, that solved my question.

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

Some BIOSes - and VirtualBox - don't return a CPUID when you ask Windows to provide it, and hence we get a null reference. Should have been fixed in 1.0.5 but it slipped through.

You can use 1.0.7 test for now, but should still upgrade when 1.0.7 comes out as there will probably be other fixes.

Alex