+7
Started

Upgrade v19.5.x Unhandled Exception

TechCare 2 weeks ago updated by Eric Davis (SDT) 3 days ago 17

Hi again. In the last 4 or 5 years that I have been using ScreenConnect the upgrades have been smooth and brilliant. But with the broken "stable" version v19.4.x I had to upgrade to v19.5.x to fix the mobile app issue.


Server details:

Ubuntu 18.04.3 LTS

Latest packages installed of everything stock

Nginx reverse proxy (can send config files, but that isn't the problem here)

When I upgrade (even now with the latest variant of v19.5.x) it shows the following:

Unhandled Exception:
System.Xml.Xsl.XslTransformException: Attribute and namespace nodes cannot be added to the parent element after a text, comment, pi, or sub-element node has already been added.
at System.Xml.Xsl.Runtime.XmlQueryOutput.ThrowInvalidStateError (System.Xml.XPath.XPathNodeType constructorType) [0x000cf] in :0
at System.Xml.Xsl.Runtime.XmlQueryOutput.ConstructInEnumAttrs (System.Xml.XPath.XPathNodeType rootType) [0x0001f] in :0
at System.Xml.Xsl.Runtime.XmlQueryOutput.WriteStartAttribute (System.String prefix, System.String localName, System.String ns) [0x0001e] in :0
at System.Xml.Xsl.Runtime.XmlQueryOutput.WriteStartAttributeLocalName (System.String localName) [0x00000] in :0
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.Root(System.Xml.Xsl.Runtime.XmlQueryRuntime)
at (wrapper dynamic-method) System.Object.Execute(System.Xml.Xsl.Runtime.XmlQueryRuntime)
at System.Xml.Xsl.XmlILCommand.Execute (System.Object defaultDocument, System.Xml.XmlResolver dataSources, System.Xml.Xsl.XsltArgumentList argumentList, System.Xml.Xsl.Runtime.XmlSequenceWriter results) [0x00020] in :0
at System.Xml.Xsl.XmlILCommand.Execute (System.Object defaultDocument, System.Xml.XmlResolver dataSources, System.Xml.Xsl.XsltArgumentList argumentList, System.Xml.XmlWriter writer) [0x0004f] in :0
at System.Xml.Xsl.XslCompiledTransform.Transform (System.Xml.XmlReader input, System.Xml.Xsl.XsltArgumentList arguments, System.Xml.XmlWriter results, System.Xml.XmlResolver documentResolver) [0x0000d] in :0
at System.Xml.Xsl.XslCompiledTransform.Transform (System.String inputUri, System.Xml.Xsl.XsltArgumentList arguments, System.IO.Stream results) [0x00029] in :0
at Xsl.Program.Main (System.String[] args) [0x0007b] in :0
[ERROR] FATAL UNHANDLED EXCEPTION: System.Xml.Xsl.XslTransformException: Attribute and namespace nodes cannot be added to the parent element after a text, comment, pi, or sub-element node has already been added.
at System.Xml.Xsl.Runtime.XmlQueryOutput.ThrowInvalidStateError (System.Xml.XPath.XPathNodeType constructorType) [0x000cf] in :0
at System.Xml.Xsl.Runtime.XmlQueryOutput.ConstructInEnumAttrs (System.Xml.XPath.XPathNodeType rootType) [0x0001f] in :0
at System.Xml.Xsl.Runtime.XmlQueryOutput.WriteStartAttribute (System.String prefix, System.String localName, System.String ns) [0x0001e] in :0
at System.Xml.Xsl.Runtime.XmlQueryOutput.WriteStartAttributeLocalName (System.String localName) [0x00000] in :0
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.(System.Xml.Xsl.Runtime.XmlQueryRuntime,System.Xml.XPath.XPathNavigator)
at (wrapper dynamic-method) System.Object.Root(System.Xml.Xsl.Runtime.XmlQueryRuntime)
at (wrapper dynamic-method) System.Object.Execute(System.Xml.Xsl.Runtime.XmlQueryRuntime)
at System.Xml.Xsl.XmlILCommand.Execute (System.Object defaultDocument, System.Xml.XmlResolver dataSources, System.Xml.Xsl.XsltArgumentList argumentList, System.Xml.Xsl.Runtime.XmlSequenceWriter results) [0x00020] in :0
at System.Xml.Xsl.XmlILCommand.Execute (System.Object defaultDocument, System.Xml.XmlResolver dataSources, System.Xml.Xsl.XsltArgumentList argumentList, System.Xml.XmlWriter writer) [0x0004f] in :0
at System.Xml.Xsl.XslCompiledTransform.Transform (System.Xml.XmlReader input, System.Xml.Xsl.XsltArgumentList arguments, System.Xml.XmlWriter results, System.Xml.XmlResolver documentResolver) [0x0000d] in :0
at System.Xml.Xsl.XslCompiledTransform.Transform (System.String inputUri, System.Xml.Xsl.XsltArgumentList arguments, System.IO.Stream results) [0x00029] in :0
at Xsl.Program.Main (System.String[] args) [0x0007b] in :0

ConnectWise Control Version:
19.5
Server Affected:
Host Client Affected:
Guest Client Affected:
+1

Same, due to the horrific and ongoing issues we've had with v19.4, I decided to try v19.5 and got this exact error message.

Server is CentOS 7 and yes it uses HAProxy.

Server appears to be active, but it draws some of the graphic page elements and cannot provide list views of the content. CPU usage very high, I let it churn for about an hour before rolling back the upgrade. 

I don't know if this is a cause to the above mentioned issue but now any new support downloads fail with "Application validation error"

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of https://PATH_TO_SERVER/bin/hash.blahblahblah resulted in exception. Following failure messages were detected:
+ File, ScreenConnect.Core.pdb, has a different computed hash than specified in manifest.

That's a new bug (and unrelated to the Linux installer error messages) that we just started working on.

A workaround is to use ClickOnceBootstrap rather than ClickOnceDirect. (Not ideal, but it does work.)

Same issue here when upgrading! and we cant seem to downgrade please advice !

@Eric Davis- sorry this isn't enough detail for me to understand- where do I find 'ClickOnceBootstrap' ?

oops sorry I see you were replying to TechCare, never mind

Same issue here

Cannot even function after the upgrade

If you follow the upgrade guides you will have made a copy of the old /Screenconnect folder before taking any action. I also snapshot the VM. It's pretty easy to revert if you do these things, especially as v19.5 is not marked stable. 
I understand this isn't much help to some so please accept my apologies 

+1

V19.5 IS marked stable. We always wait some time to upgrade. Its marked stable on the downloads and also the output stream page. 

I got it finaly working again after copying some folders and web.config from the old directory to a new fresh install dir because you cant seem to downgrade using the .installer.sh script.

I also looked for a clear downgrade guide for linux on premise version but cant seem to find anything?

Can confirm it is definitely marked as stable, though i have to admit i was also guilty of installing without doing a manual backup first - all these years of upgrading and i've never noticed the "backup" it mentions in the upgrade process is only of the config files.. my bad.

@M Stroeve can i ask which files specifically you had to bring across to get 19.4 up and running again?

+1

i renamed the failed existing screenconnect folder to screenconnect.old in the /opt folder.
Did a fresh 19.4 install and:

cp -R App_ClientConfig/ ../screenconnect

cp -R App_Extensions/ ../screenconnect

cp -R App_Data/ ../screenconnect

cp web.config ../screenconnect

I'am not sure if i mis anything but it works again and i can see our custom extensions. 

It would be nice if techsupport would post a definitive guide for downgrading for future reference.

I'm extremely tempted to try this, but with version 19.3 because it was working just fine. However the questions I have to this are:

1) What happens to the unattended clients? Their version will be higher then the server version. Can I just mass select and reinstall?

2) Does this break anything? (further I mean :p)

ok at the risk of making more enemies here it wasn't marked stable for me last night- Yep-


I have VERY different expectations when I install stable software- this does not meet those requirements
Just in case this helps anyone- I cp the opt/Screenconnect folder to /Documents before upgrading. If something goes wrong I stop the service, delete the new folder and put the old one back and reboot.

+1

@adam.connor yep, i'll be adding that step to my upgrade workflow from here on out! 


It's frustrating that the "Released" date on the website doesn't reflect when it was actually made available as Stable to users.. I normally wouldn't upgrade software on the server with something less than 24 hours old for precisely this reason, but when something has supposedly been released for over a week i figure it would have been pulled by now if it had a showstopper like this.

+1

what I find extremely frustrating is this statement:

The high CPU usage/inaccessibility issue after upgrading to 19.5 isn't directly related to the thread topic, but here's a workaround:

In web.config, change "127.0.0.1" to "localhost" (there should be two references, under system.servicemodel toward the end of the file).

If this doesn't work, let me know. Should have this fixed in the installer soon.