attempt to connect was forcefully rejected (O4W)
At 28 AUG 2020 08:50:52AM Richard Richter wrote:
Good Morning
I upgraded to 10.0.8 and now I can't login to my website either localhost or remotely. I get the following error message:
Unable to connect to Engine Server localhost:18088 - The attempt to connect was forcefully rejected.
I assure you I did nothing but the upgrade. I checked and the OEngineServer 10 is running though now it seems to turn itself off when I shut down. That's a problem for another time. How do I fix this?
Richard Richter
At 28 AUG 2020 09:17AM bshumsky wrote:
Good Morning
I upgraded to 10.0.8 and now I can't login to my website either localhost or remotely. I get the following error message:
Unable to connect to Engine Server localhost:18088 - The attempt to connect was forcefully rejected.
I assure you I did nothing but the upgrade. I checked and the OEngineServer 10 is running though now it seems to turn itself off when I shut down. That's a problem for another time. How do I fix this?
Richard Richter
Hi, Richard.
I think this may be related to whether or not you chose to install the "included" java runtime during the 10.0.8 install/update process, and whether you had previously installed an engine server service.
The first thing I would do is turn off the engine server service, and start up the engine server in 'debug' mode in a DOS cmd box.
There should be a shortcut in your OI 10.0.8 "Start Programs" folder, called "Engine Server (Debug Mode)". Click that to start up the engine server in debug mode.
If that shortcut doesn't exist, you can manually start up the engine server in debug mode IF YOU DID NOT USE THE INCLUDED JAVA RUNTIME (if you used the included java runtime, the "path" isn't set in windows, so it's more complicated).
This can be done by opening up a DOS cmd box, moving ("cd") to your OI folder, and typing in the following:
java -jar oesocketserver.jar -d 3
that is, java space minus jar space oesocketserver dot jar space minus d space 3
In either case, when you start the engine server in debug mode, does it start up? Does it show any errors? If so, what do they say?
Please let me know what you find, and we can proceed from there.
Thanks,
- Bryan Shumsky
At 28 AUG 2020 09:51AM Richard Richter wrote:
Good Morning
I upgraded to 10.0.8 and now I can't login to my website either localhost or remotely. I get the following error message:
Unable to connect to Engine Server localhost:18088 - The attempt to connect was forcefully rejected.
I assure you I did nothing but the upgrade. I checked and the OEngineServer 10 is running though now it seems to turn itself off when I shut down. That's a problem for another time. How do I fix this?
Richard Richter
Hi, Richard.
I think this may be related to whether or not you chose to install the "included" java runtime during the 10.0.8 install/update process, and whether you had previously installed an engine server service.
The first thing I would do is turn off the engine server service, and start up the engine server in 'debug' mode in a DOS cmd box.
There should be a shortcut in your OI 10.0.8 "Start Programs" folder, called "Engine Server (Debug Mode)". Click that to start up the engine server in debug mode.
If that shortcut doesn't exist, you can manually start up the engine server in debug mode IF YOU DID NOT USE THE INCLUDED JAVA RUNTIME (if you used the included java runtime, the "path" isn't set in windows, so it's more complicated).
This can be done by opening up a DOS cmd box, moving ("cd") to your OI folder, and typing in the following:
java -jar oesocketserver.jar -d 3
that is, java space minus jar space oesocketserver dot jar space minus d space 3
In either case, when you start the engine server in debug mode, does it start up? Does it show any errors? If so, what do they say?
Please let me know what you find, and we can proceed from there.
Thanks,
- Bryan Shumsky
Hi Bryan,
I started the command prompt manually, changed to OI10 and tried to run java. This is the result:
C:\>cd\revsoft\oinsight10
C:\Revsoft\OInsight10>java -jar oesocketserverjar -d 3
Error: Unable to access jarfile oesocketserverjar
C:\Revsoft\OInsight10>
I think Java is running but oesocketserver.jar is in never never land. What's happening?
Richard Richter
At 28 AUG 2020 09:54AM Donald Bakke wrote:
C:\Revsoft\OInsight10>java -jar oesocketserverjar -d 3
Make sure you spell it as oesocketserver.jar. You are missing a period.
At 28 AUG 2020 09:55AM Andrew McAuley wrote:
Did you miss the "."? As in oesocketserverjar is not oesocketserver.jar
World leaders in all things RevSoft
At 28 AUG 2020 09:56AM Andrew McAuley wrote:
2 seconds! :D
World leaders in all things RevSoft
At 28 AUG 2020 09:59AM bshumsky wrote:
Hi, Richard. Can you also tell me whether you installed the "included" java runtime, or if you opted to use your own java runtime, during the installation process? And whether there is indeed a shortcut "Engine Server (debug mode)" in your Start Menu under OpenInsight (or a batch file, EngineServerDebug.bat, in your OI folder if you opted to not create shortcuts during the installation)?
Thanks!
- Bryan Shumsky
At 28 AUG 2020 10:11AM Richard Richter wrote:
Hi, Richard. Can you also tell me whether you installed the "included" java runtime, or if you opted to use your own java runtime, during the installation process? And whether there is indeed a shortcut "Engine Server (debug mode)" in your Start Menu under OpenInsight (or a batch file, EngineServerDebug.bat, in your OI folder if you opted to not create shortcuts during the installation)?
Thanks!
- Bryan Shumsky
I ran the update install with no changes so I assume I installed the "included" java runtime. EngineServerDebug.bat is in the OI10 folder.
I corrected the java command and got the following results:
C:\Revsoft\OInsight10>java -jar oesocketserver.jar -d 3
Version: 3.0.0.573 - Licensed for use to CN=Revelation Software
Started at 2020-08-28 10:00:51
2020-08-28 10:00:51:758 - EngineServer started on port 18088
In Phantom, about to process *1SYSPROGSYSPROGSYSPROG3REVCMD_LISTENER*
In Phantom, about to process *1SYSPROGSYSPROGSYSPROG3REVCMD_LISTENER*
In state *0*, asked to execute command *1*, *7* parameters
In state *0*, asked to execute command *1*, *7* parameters
In LOGGED OUT state
In LOGGED OUT state
In SetProperties, mode is *3*
In SetProperties, mode is *3*
thisSetting[1] is now *SYSPROG*
thisSetting[1] is now *SYSPROG*
thisSetting[2] is now *SYSPROG*
thisSetting[3] is now *SYSPROG*
thisSetting[2] is now *SYSPROG*
thisSetting[4] is now *3*
thisSetting[3] is now *SYSPROG*
thisSetting[5] is now thisSetting[4] is now *3* thisSetting[6] is now *REVCMD_LISTENER* thisSetting[5] is now
thisSetting[7] is now *65*
thisSetting[8] is now *1*
thisSetting[6] is now *REVCMD_LISTENER*
thisSetting[7] is now *65*
thisSetting[9] is now thisSetting[10] is now
thisSetting[8] is now *1*
Connecting to engine, servername is , application is *SYSPROG*, user is *SYSPROG*, procedure is *REVCMD_LISTENER* thisSetting[9] is now
in EngineFactory: Checkout, bAlwaysCreate is *true*, bCheckZombies is *false*
thisSetting[10] is now Creating new engine Connecting to engine, servername is , application is *SYSPROG*, user is *SYSPROG*, procedure is *REVCMD_LISTENER*
in EngineFactory: Checkout, bAlwaysCreate is *true*, bCheckZombies is *false*
Creating new engine
Using default home dir
Switching to directory *C:\Revsoft\OInsight10\*
Using default home dir
Switching to directory *C:\Revsoft\OInsight10\*
About to create engine, servername *\\.\L_18088_791990625067500*, appName: *SYSPROG*, createFlags: *65*, shutdownFlags: *1*
About to create engine, servername *\\.\L_18088_791990615194100*, appName: *SYSPROG*, createFlags: *65*, shutdownFlags: *1*
About to create queue, queuename: *Q_18088_791990625067500*, appName: *SYSPROG*, username: *SYSPROG*, password: *SYSPROG*
Adding to lSynchronous
EngineStarted is *true*
Returning *00\\.\L_18088_791990625067500Q_18088_791990625067500SYSPROG651SYSPROGREVCMD_LISTENER0W10020600*
outputLine is *00\\.\L_18088_791990625067500Q_18088_791990625067500SYSPROG651SYSPROGREVCMD_LISTENER0W10020600*
In Phantom, about to process *3DO_LOGINPROC (.*
In state *1*, asked to execute command *3*, *2* parameters
Requeuing synchronous engine (if required)
Checking SYNCHRONOUS engine #1 for existing engine match
Found match in synchronous list - exiting
In LOGGED IN state
doing CALL
received local command request
received local command request
received local command request
Returning *00*
outputLine is *00*
In Phantom, about to process *3RTI_OEMONITOR_INDEX*
In state *1*, asked to execute command *3*, *2* parameters
Requeuing synchronous engine (if required)
Checking SYNCHRONOUS engine #1 for existing engine match
Found match in synchronous list - exiting
In LOGGED IN state
doing CALL
Returning *00*
outputLine is *00*
In Phantom, all done with commands
In OEngineFactory: RemoveEngine - removing used engine from lSynchronous
Have 1 entries to check
checking entry #0
found the entry in the lSynchronous
Closing engine
I couldn't find an error but then again I have trouble finding my elbow.
Richard Richter
At 28 AUG 2020 10:14AM bshumsky wrote:
Hi, Richard. Thanks for the response.
While the engine server is running in this "debug" mode, do your connections from O4W work?
- Bryan Shumsky
At 28 AUG 2020 12:01PM Richard Richter wrote:
Hi, Richard. Thanks for the response.
While the engine server is running in this "debug" mode, do your connections from O4W work?
- Bryan Shumsky
When I try to login, after several minutes this is the error message that I get:
HTTP Error 502.1 - Bad Gateway
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".
I swear I didn't touch IIS!
Richard Richter
At 28 AUG 2020 01:10PM bshumsky wrote:
Hi, Richard. Thanks for the response.
While the engine server is running in this "debug" mode, do your connections from O4W work?
- Bryan Shumsky
When I try to login, after several minutes this is the error message that I get:
HTTP Error 502.1 - Bad Gateway
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".
I swear I didn't touch IIS!
Richard Richter
Hi, Richard. From your description, it seems like the problem is in the OECGI connection between IIS and the engine server, not the engine server itself, at this point.
Is it possible antivirus, or something, has "quarantined" the oecgi4.exe that was just installed?
If you right-click and choose "Properties" on the oecgi4.exe program (located in your <OI10>\o4w folder), does it say anything about being "blocked"?
Also, can you check in your <OI10>\o4w folder for a file named "web.config" or something like that? There shouldn't be one there, but if it does exist, it might "mess up" how IIS is working in that folder.
Thanks,
- Bryan Shumsky
At 28 AUG 2020 04:11PM Richard Richter wrote:
Hi, Richard. Thanks for the response.
While the engine server is running in this "debug" mode, do your connections from O4W work?
- Bryan Shumsky
When I try to login, after several minutes this is the error message that I get:
HTTP Error 502.1 - Bad Gateway
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".
I swear I didn't touch IIS!
Richard Richter
Hi, Richard. From your description, it seems like the problem is in the OECGI connection between IIS and the engine server, not the engine server itself, at this point.
Is it possible antivirus, or something, has "quarantined" the oecgi4.exe that was just installed?
If you right-click and choose "Properties" on the oecgi4.exe program (located in your <OI10>\o4w folder), does it say anything about being "blocked"?
Also, can you check in your <OI10>\o4w folder for a file named "web.config" or something like that? There shouldn't be one there, but if it does exist, it might "mess up" how IIS is working in that folder.
Thanks,
- Bryan Shumsky
I found a win.config and renamed it. I found nothing in the oecgi4.exe properties. When I try to login I get the same message.
HTTP Error 502.1 - Bad Gateway
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".
What next?
Richard Richter
At 28 AUG 2020 04:20PM bshumsky wrote:
Well, here's another question. When you downloaded the 10.0.8 zip file, did you right-click and "unblock" the zip file before unzipping it? If you still have the downloaded zip somewhere, can you right-click and check "properties" and see if it says it might be blocked?
Other than that, the only thing I can think of is that some antivirus may have quarantined the oecgi4.exe…
- Bryan Shumsky
At 28 AUG 2020 08:01PM Richard Richter wrote:
Well, here's another question. When you downloaded the 10.0.8 zip file, did you right-click and "unblock" the zip file before unzipping it? If you still have the downloaded zip somewhere, can you right-click and check "properties" and see if it says it might be blocked?
Other than that, the only thing I can think of is that some antivirus may have quarantined the oecgi4.exe…
- Bryan Shumsky
Sorry. I can't find the file. I've got everything backed up to the minute, how about a clean install?
Richard Richter
At 28 AUG 2020 08:05PM bshumsky wrote:
Sure, if you don't mind. Here's how I'd proceed:
- download the zip file;
- right-click after download, choose Properties, and see if it's "blocked" - if it is, unblock it;
- Unzip the zip file
- RESTART THE SERVER (to make sure nothing is "locked" in memory;
- IF YOU HAVE ANTIVIRUS SCANNING THE OI FOLDER (or the setup.exe file), disable it for the duration;
- IF YOU HAVE AN OENGINESERVER SERVICE RUNNING, disable it;
- Run the setup.exe;
- Run the clientsetup.exe afterwards
- IF YOU HAVE AN OENGINESERVER SERVICE RUNNING BEFORE, you should uninstall it and then install the new service (if you've switched from your own java runtime to the "included" java runtime)
Let us know if that all makes any difference?
Thanks,
- Bryan Shumsky
At 31 AUG 2020 01:15PM bshumsky wrote:
To bring everyone up to date…
Richard uninstalled his OI 10 (after saving his application in an app backup), and we made sure to remove (through add/remove programs) any other instances of v10 client files as well. After re-installing the OI 10, we made sure to remove the engine server service that did NOT use the included java runtime (there's a batch file, uninstallservice_no_jre.bat, located in the oeserver folder in your OI 10 directory, that's designed to remove the service that DOESN'T use the included java runtime if you ARE running the included java runtime. Similarly, there's a bt file uninstallservice_with_jre.bat that will remove the service that DOES use the included java runtime if you AREN'T running the included java runtime).
We also made sure to run the engine server in 'debug' mode first, and we saw that Windows Firewall was blocking access to the engine server. We told it to allow connections from the local network, and it was able to run. We could then start it up as a service, as well, and it continued running.
- Bryan Shumsky