<div dir="ltr">Jason, <div><br></div><div>In the past when I've had a similar problem I've opened the XML in IE, which I think will complain about an error on a specific line. Worth a shot.</div><div style><br>Carl</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On 11 April 2013 17:38, Jason Taylor <span dir="ltr"><<a href="mailto:jtaylor@morrislaing.com" target="_blank">jtaylor@morrislaing.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sometimes, after editing a package definition, wpkg will start complaining about malformed XML and no root elements. Could anyone give me some pointers on how to identify where the problem is? In my editor (ST2) it doesn't show any inconsistent highlighting or anything that screams "invalid XML!"<br>
<br>
The last couple times this happened, I just re-wrote the file from scratch and the problem went away. I would rather find out what I'm doing wrong than re-writing it every time this happens.<br>
<br>
These are the debug messages I'm getting:<br>
---<br>
Error parsing xml '//domain/it/software/wpkg/packages/WorkshareProfessional.xml': The stylesheet does not contain a document element. The stylesheet may be empty, or it may not be a well-formed XML document.<br>
No root element found in '//domain/it/software/wpkg/packages/WorkshareProfessional.xml'.<br>
---<br>
<br>
And here is the package definition in full:<br>
---<br>
<?xml version="1.0" encoding="UTF-8"?><br>
<packages xmlns:packages="<a href="http://www.wpkg.org/packages" target="_blank">http://www.wpkg.org/packages</a>" xmlns:wpkg="<a href="http://www.wpkg.org/wpkg" target="_blank">http://www.wpkg.org/wpkg</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>" xsi:schemaLocation="<a href="http://www.wpkg.org/packages" target="_blank">http://www.wpkg.org/packages</a> xsd/packages.xsd"><br>
<br>
<package id="WorkshareProfessional" name="Workshare Professional" revision="201304040"><br>
<br>
<!-- Current version --><br>
<variable name="WORKSHAREVERSION" value="7.50.15000.1000" /><br>
<br>
<variable name="WORKSHAREOPTIONS" value="Workshare_Options_x64.reg"><br>
<condition><br>
<check type="host" type="architecture" value="x64" /><br>
</condition><br>
</variable><br>
<br>
<variable name="WORKSHAREOPTIONS" value="Workshare_Options_x86.reg"><br>
<condition><br>
<check type="host" type="architecture" value="x86" /><br>
</condition><br>
</variable><br>
<br>
<!-- Always consider this package installed --><br>
<check type="file" condition="exists" path="%WINDIR%\explorer.exe" /><br>
<br>
<upgrade cmd='msiexec /qn /i "%SOFTWARE%\Workshare\Professional\Professional.msi"'><br>
<condition><br>
<check type="uninstall" condition="versionsmallerthan" path="Workshare Professional" value="%WORKSHAREVERSION%" /><br>
</condition><br>
</upgrade><br>
<br>
<upgrade cmd='msiexec /qn /i "%SOFTWARE%\Workshare\Professional\WorksharePdfConverter.msi"'><br>
<condition><br>
<check type="uninstall" condition="versionsmallerthan" path="Workshare Professional" value="%WORKSHAREVERSION%" /><br>
</condition><br>
</upgrade><br>
<br>
<upgrade cmd='%COMSPEC% /c copy "\\mlebk.local\it\software\Workshare\Professional_Perm.lic" "%PROGRAMFILES(X86)%\Workshare\Modules\"'><br>
<condition><br>
<check type="uninstall" condition="exists" path="Workshare Professional" /><br>
</condition><br>
</upgrade><br>
<br>
<upgrade cmd='%COMSPEC% /c regedit /S "%SOFTWARE%\Workshare\%WORKSHAREOPTIONS%"'><br>
<condition><br>
<check type="uninstall" condition="exists" path="Workshare Professional" /><br>
</condition><br>
</upgrade><br>
<br>
<upgrade cmd='%COMSPEC% /c "%PROGRAMFILES(X86)%\Workshare\Modules\WMConfigAssistant.exe" /install /silent'><br>
<condition><br>
<check type="uninstall" condition="versionsmallerthan" path="Workshare Professional" value="%WORKSHAREVERSION%" /><br>
</condition><br>
</upgrade><br>
<br>
</package><br>
<br>
</packages><br>
---<br>
<br>
This package definition broke after I added the two WORKSHAREOPTIONS variable assignments, and the regedit upgrade command. I don't see anything wrong with those items, though. I don't think it's a file encoding problem as this, and all other, files are UTF-8.<br>
<br>
Any advice on finding out what's wrong here would be greatly appreciated!<br>
<br>
<br>
Jason Taylor<br>
Morris, Laing, Evans, Brock & Kennedy<br>
300 N Mead Ste 200<br>
Wichita, KS 67202<br>
316-262-2671<br>
<a href="mailto:jtaylor@morrislaing.com">jtaylor@morrislaing.com</a><br>
<br>
-------------------------------------------------------------------------<br>
wpkg-users mailing list archives >> <a href="http://lists.wpkg.org/pipermail/wpkg-users/" target="_blank">http://lists.wpkg.org/pipermail/wpkg-users/</a><br>
_______________________________________________<br>
wpkg-users mailing list<br>
<a href="mailto:wpkg-users@lists.wpkg.org">wpkg-users@lists.wpkg.org</a><br>
<a href="http://lists.wpkg.org/mailman/listinfo/wpkg-users" target="_blank">http://lists.wpkg.org/mailman/listinfo/wpkg-users</a><br>
</blockquote></div><br></div></div>