* I did not do it in that precise order, I uninstalled the old
version, installed the new version, then rebooted (when I saw it was not
working). For the avoidance of doubt, I have just repeated the process with
a reboot after removing the old version, same result. I then uninstalled the
newer version, reinstalled the old one and it began working again, without a
reboot.
Do I assume this is all fixed now?
Kevin Brown
Executive Vice President, Sales & Marketing RenderX, Inc.
(650) 327-1000 Direct
(650) 328-8008 Fax
(925) 395-1772 Mobile
skype:kbrown01
<mailto:kevin@renderx.com> kevin@renderx.com
<mailto:sales@renderx.com> sales@renderx.com
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.renderx.com_&d=DwMF
Aw&c=-5LgSL_TkF3nGRQI95ci6eeFVMQ5VESHPf5koMIAxOA&r=yVuryK9i5mTC1HwUhhk11jhcf
oM_R79kcOemHB3wJKI&m=_pMuyWQwWjkweA_2ZgroeXdOPL47i9HXHONuCevGjNA&s=VFnYR1htD
Hu9RCll2WrcHORu2W57P6A8xvtq01n2caU&e=> http://www.renderx.com
From: Darren Munt <darrenm@ardex.com.au>
Sent: Monday, May 20, 2024 5:17 PM
To: kevin@renderx.com; RenderX Community Support List
<xep-support@renderx.com>
Subject: RE: [xep-support] Re: Issue installing WinXEP on Windows 10
Please define "no longer found": was working fine prior to the version
update, after the upgrade could not connect to, was unavailable, did not
respond, insert your preferred terminology.
I did not do it in that precise order, I uninstalled the old version,
installed the new version, then rebooted (when I saw it was not working).
For the avoidance of doubt, I have just repeated the process with a reboot
after removing the old version, same result. I then uninstalled the newer
version, reinstalled the old one and it began working again, without a
reboot.
I am running this with JRE6 version 6.0.250.6.
I also note that when I make the call to XEP to process an FO file, I see an
entry in the Cliser log file that corresponds to that request as per normal:
10:07:46 AM Received a request: /create-formatter/
Current formatter: 0
At least I see plenty of these in the production log, so I assume that is
normal.
That would suggest the service is actually being located and called
successfully but that either Cliser is either not responding or is returning
some error, you would know better about that than I.
Here is the full log from a failed test with the new version:
10:07:39 AM
Starting Cliser service ...
JAVA-HOME=C:\Program Files (x86)\Java\jre6
JAVA-CLASSPATH=
JAVA-OPTIONS=
XEP-LICENSE=C:\Program Files\RenderX\XEPWin\xep\license.xml
XEP-CONFIG=C:\Program Files\RenderX\XEPWin\xep\xep.xml
XEP-JAR=C:\Program Files\RenderX\XEPWin\xep\lib\xep.jar
CLISER-JAR=C:\Program Files\RenderX\XEPWin\xep\lib\cliser.jar
CLISER-SERVERS=1
LOG-FILE=C:\dev\logs\cliserservice.log
CLISER-CONTROL-PORT=6997
CLISER-PORT-RANGE=6570-6770
DISABLE-CLISER-ENGINE-HTTP-CONTROL-PORT=False
Calculating Cliser ports ...
Starting servers ...
Starting java: -Xrs -Dcom.renderx.xep.CONFIG="C:\Program
Files\RenderX\XEPWin\xep\xep.xml" -Dcom.renderx.xep.LICENSE="C:\Program
Files\RenderX\XEPWin\xep\license.xml" -cp "";"C:\Program
Files\RenderX\XEPWin\xep\lib\cliser.jar";"C:\Program
Files\RenderX\XEPWin\xep\lib\xep.jar" com.renderx.xepx.cliser.Engine -port
6570 -hcport 6571
Starting load balancer ...
10:07:46 AM Received a request: /create-formatter/
Current formatter: 0
And from a successful test with the old version:
10:15:10 AM
Starting Cliser service ...
JAVA-HOME=C:\Program Files (x86)\Java\jre6
JAVA-CLASSPATH=
JAVA-OPTIONS=
XEP-LICENSE=C:\Program Files (x86)\RenderX\XEPWin\xep\license.xml
XEP-CONFIG=C:\Program Files (x86)\RenderX\XEPWin\xep\xep.xml
XEP-JAR=C:\Program Files (x86)\RenderX\XEPWin\xep\lib\xep.jar
CLISER-JAR=C:\Program Files (x86)\RenderX\XEPWin\xep\lib\cliser.jar
CLISER-SERVERS=1
LOG-FILE=C:\dev\logs\cliserservice.log
CLISER-CONTROL-PORT=6997
CLISER-PORT-RANGE=6570-6770
Calculating Cliser ports ...
Starting servers ...
Starting java: -Xrs -Dcom.renderx.xep.CONFIG="C:\Program Files
(x86)\RenderX\XEPWin\xep\xep.xml" -Dcom.renderx.xep.LICENSE="C:\Program
Files (x86)\RenderX\XEPWin\xep\license.xml" -cp "";"C:\Program Files
(x86)\RenderX\XEPWin\xep\lib\cliser.jar";"C:\Program Files
(x86)\RenderX\XEPWin\xep\lib\xep.jar" com.renderx.xepx.cliser.Engine -port
6570 -hcport 6571
Starting load balancer ...
10:15:16 AM Received a request: /create-formatter/
Current formatter: 0
From: Xep-support <xep-support-bounces@renderx.com
<mailto:xep-support-bounces@renderx.com> > On Behalf Of Kevin Brown
Sent: Tuesday, May 21, 2024 2:41 AM
To: 'RenderX Community Support List' <xep-support@renderx.com
<mailto:xep-support@renderx.com> >
Subject: [xep-support] Re: Issue installing WinXEP on Windows 10
* the Cliser service can no longer be found.
Please define "no longer found"
* I assume you uninstalled the old version, rebooted and then
installed the new version. If you didn't, then 6570 would be unavailable as
it would be bound to the old one. You cannot have two Windows services with
the same name.
Kevin Brown
Executive Vice President, Sales & Marketing RenderX, Inc.
(650) 327-1000 Direct
(650) 328-8008 Fax
(925) 395-1772 Mobile
skype:kbrown01
<mailto:kevin@renderx.com> kevin@renderx.com
<mailto:sales@renderx.com> sales@renderx.com
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.renderx.com_&d=DwMF
Aw&c=-5LgSL_TkF3nGRQI95ci6eeFVMQ5VESHPf5koMIAxOA&r=yVuryK9i5mTC1HwUhhk11jhcf
oM_R79kcOemHB3wJKI&m=_pMuyWQwWjkweA_2ZgroeXdOPL47i9HXHONuCevGjNA&s=VFnYR1htD
Hu9RCll2WrcHORu2W57P6A8xvtq01n2caU&e=> http://www.renderx.com
From: Xep-support <xep-support-bounces@renderx.com
<mailto:xep-support-bounces@renderx.com> > On Behalf Of Darren Munt
Sent: Sunday, May 19, 2024 7:26 PM
To: RenderX Community Support List <xep-support@renderx.com
<mailto:xep-support@renderx.com> >
Subject: [xep-support] Issue installing WinXEP on Windows 10
I am attempting to install WinXEP on a new development machine. I have
installed a version from 2016 (I think). Setup file version is
11.50.0.42619. This is working fine.
However when I install a more recent version from the XEPWin.msi dated
13/12/2019, the Cliser service can no longer be found. The install works
fine, the Cliser service starts and there are no errors in the Cliser log,
but the .Net client reports 'Unable to connect to [machine-name]:6570 CLISER
server'.
I have opened ports 6570, 6571, and 6997. Given it works fine with the
earlier version, what else might be stopping it from connecting?
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
Received on Mon May 20 17:17:07 2024
This archive was generated by hypermail 2.1.8 : Mon May 20 2024 - 17:17:12 PDT