Xibo

1.2.1 Client hangs/crashes

Asked by Shahid

Hello all,

Strange issue starting to pop up on my clients. After the 1.2.1 upgrade of the server and clients, a few machines have hung clients. From regions that have stopped functioning, down to entire client lockups (processor utilization stuck at 25%). These machines all are running XP with all of the latest .net's.

A little digging with sysinternal's ProcMon shows that the Xibo client is calling mscoree.dll and that thread is what is causing the lockup. I've managed to get one machine back to running order by uninstalling all of the client and .net packages and reinstalling only 3.5,3.0 sp2, and 2.0 sp2 (the latter 2 are required if running 3.5).

I'm still not 100% certain if that was the culprit. This is more FYI than anything in case anyone else has the issue. Any advice of course would be appreciated.

Thanks for your hard work!

Shahid

Question information

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

The changes 1.2.0 to 1.2.1 on the client are pretty minimal actually,
so I'd expect to see the same behaviour with 1.2.0 as 1.2.1 if there
were a general problem.

Alex

Revision history for this message
Shahid (smalik-albion) said : 		#2

Alex there were no problems until post 121 upgrade. Once I uninstalled and reinstalled all of the .net packages, things started to work correctly again. Oh, and I did forget one important interesting note: I had a layout scheduled on the affected machines that had a repeat set in the scheduler. (The layout was a simple jpg and some scrolling text) Once I removed all of the repeats and deleted all the appdata/blah blah/cachemanager.xml and associated files to let it all rebuild, things started moving again.

Once again, no changes on our clients other than the 1.2.1 upgrade. Will the 1.2.0 debug client work with the 1.2.1 server?

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

Yes, but not the other way around.

Alex

Revision history for this message
Shahid (smalik-albion) said : 		#4

OK, I'll dig through that and see what happens.

Thanks!