Xibo

Urgent help needed, client gives multiple errors

Asked by Mike Lowrey

Info: windows7client with 1.6.2

Infoscreen error: Required files status: Error: Cannot redeclare class Region

When i try to save the log file, the client fails with this error, everything was working for months, i tried upgrading to 162 (from 1.6.0) today but errors kept the same.

System.UnauthorizedAccessException: Toegang tot het pad C:\Program Files (x86)\Xibo Player\XiboLog.txt is geweigerd.
(Access tot the path xxxxxx has beeen denied)
   bij System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bij System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   bij System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   bij System.IO.StreamWriter.CreateFile(String path, Boolean append)
   bij System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
   bij System.IO.StreamWriter..ctor(String path)
   bij XiboClient.Log.ClientInfo.saveLogToDisk_Click(Object sender, EventArgs e)
   bij System.Windows.Forms.Control.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bij System.Windows.Forms.Control.WndProc(Message& m)
   bij System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bij System.Windows.Forms.Button.WndProc(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladen assembly's **************
mscorlib
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5477 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
XiboClient
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Xibo%20Player/XiboClient.exe
----------------------------------------
System
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Web.Services
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
System.Deployment
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------
System.Deployment.resources
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment.resources/2.0.0.0_nl_b03f5f7f11d50a3a/System.Deployment.resources.dll
----------------------------------------
mscorlib.resources
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5477 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
7lfknvgj
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Management
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Windows.Forms.resources
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
jatmbfjj
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
csr186at
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.resources
    Assembly-versie: 2.0.0.0
    Win32-versie: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.resources/2.0.0.0_nl_b77a5c561934e089/System.resources.dll
----------------------------------------

************** JIT-foutopsporing **************
Als u JIT-foutopsporing wilt inschakelen, moet in het configuratiebestand voor deze
toepassing of computer (machine.config) de waarde
jitDebugging in het gedeelte system.windows.forms zijn ingesteld.
De toepassing moet ook zijn gecompileerd terwijl foutopsporing
was ingeschakeld.

Bijvoorbeeld:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Question information

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

Your CMS is broken by the looks of it.

The error suggests you extracted 1.6.2 over the top of an old installation
rather than deleting all the files except settings.php and then extracting
fresh.

You need to do that now, and it should then be OK

Revision history for this message
Mike Lowrey (jeroen-astongroep) said : 		#2

Done that. No rresults.

But what does explain the error on the client machine ? Thats has nothing to do with the server ?

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

The error is from the CMS - see the error about redeclaring the class
Region.

Is that error still showing up for required files?

Revision history for this message
Mike Lowrey (jeroen-astongroep) said : 		#4

I am sorry what do you mean ? There is a schedule now with multiple layouts... the Always did run.... and now the tryed adding a new layout/changed layout and this is the result.

So this error is also from the cms ?
System.UnauthorizedAccessException: Toegang tot het pad C:\Program Files (x86)\Xibo Player\XiboLog.txt is geweigerd.
 (Access tot the path xxxxxx has beeen denied)
    bij System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

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

Mike

In your first email, you put you have the following on the infoscreen:

Infoscreen error: Required files status: Error: Cannot redeclare class
Region

THAT error comes from the CMS because you didn't follow the
upgrade procedure in the release notes - and just extracted 1.6.2 over the
top of your old installation.

Have you now corrected that, and is that error still showing on the info
screen?

Alex

Revision history for this message
Mike Lowrey (jeroen-astongroep) said : 		#6

Yes, i corrected that, I removed all files from the server EXCEPT settings.php , after that i uploaded the source file. That should then be it ? right ? Fyi, I did not removed the library dir.

I have 2 other clients on the same server, the both DONT show this specific error.

I have a screen here from the client which has the problems : https://www.dropbox.com/s/3hg79ur6mzti6ay/screenshot_client4.png

Maybe you can use that...

And i just followed this:
Upgrading

There are significant database schema changes between the 1.4 series of Xibo and prior released. The upgrade wizard will take a prior database and convert it to a schema suitable for the 1.4 series to date. Note that this is a one-way conversion. Please do not upgrade your production database to test Xibo 1.6 functionality, and then expect to run a prior series code base against that database.

Instructions for cloning a Xibo database are available here Clone Database.
•Clone your existing Xibo database and grant permissions (see Release Notes:Clone Database for details)
•Backup settings.php from your installation
•Manually take a backup of your database
•Replace your existing installation with the new version from the tar.gz or zip file
•Replace your backup settings.php file in your Xibo installation directory
•Browse to http://your.server/pathas normal
•You will be prompted that an upgrade is required.
•Enter your xibo_admin password, and follow the upgrade wizard.
•The upgrade should run, and finally ask you to log in as you would normally.

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

Mike

I'm very short on time today. Does the error about redeclaring the class
Region still show on the client status screen?

Once you fix that, then clear the client library on that machine and then
re-run the client and it should start working.

You didn't follow those notes. You extracted a copy of the new CMS over the
old one - rather than replacing the old CMS completely by the new one. If
you had done it correctly you wouldn't be seeing that error.

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

You would need to have uploaded the tgz or zip file and extract it.

Then going to the CMS it will ask you to upgrade again. You'll need to
complete the upgrade routine

Revision history for this message
Mike Lowrey (jeroen-astongroep) said : 		#9

Oke back again.

Did the following:
Restored backup.

Uploaded/overwrited all the server files.

Started upgrade procedure ( said something like 52 tot 70 ). It finished.
All clients still give this message:
https://www.dropbox.com/s/443an02kul7f6yn/screenshot1001.png

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

Mike,

Go back to 1.4 as you had before (restore from backup, etc). Upload the 1.6 release into a NEW folder on your server, specifically NOT the same folder as your current install.

Copy settings.PHP into your new folder and follow the upgrade process.

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

Mike please

I didn't tell you to restore any backups!

I just said, delete the old files except settings.php, then upload fresh
1.6.2 copies and allow the upgrade routine to run. It would have done a nil
upgrade.

I'm afraid I don't have further time to help you today.

You need to get your CMS working properly and then the clients will work

Revision history for this message
Mike Lowrey (jeroen-astongroep) said : 		#12

already done that, and it said that it was already updated to something 70 of 70. What you are saying, is just simply not working.

Revision history for this message
Mike Lowrey (jeroen-astongroep) said : 		#13

Thx,

I restored the old version 1.42, server is running again and now the clients give this error again:
https://www.dropbox.com/s/qiibgs61a79px5f/screenshot2001.png

I haven’t done any upgrading yet, maybe we can fix this error first, so the system will run again, and after this, we can schedule a paid meeting for the upgrading somewhere next week.

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

I think we will still need to take a look with you - those messages are still from the CMS, so something isn't right. If we can have remote access I am sure we can get you back up and running.

Perhaps you can liaise with our support email (you already have a ticket)

Thanks,
Dan

Can you help with this problem?

Provide an answer of your own, or ask Mike Lowrey for more information if necessary.

To post a message you must log in.