Forums

Hi,

I'm having an issue with running a web service where the browser page when I'm trying to test the method (URL: http://localhost/jade/jadehttp.dll?Router) is returning "Service Unavailable" - This Service is currently unavailable at this time.

When trace is turned on - I get the following in the log file:
2010/08/25 22:27:28.859 01474-151c Trace Info - Received request Application=Router
2010/08/25 22:27:28.859 01474-151c Attempting open of Tcp connection DEV port=4010
2010/08/25 22:27:28.859 01474-151c Opened a tcp connection for application Router connectionGroup (unnamed) - tcp address = DEV port=4010 (id=2)
2010/08/25 22:27:28.875 01474-151c Tcp read of data from Jade aborted/reset - network Error =10054 A existing network connection was forcibly closed by the remote host.
2010/08/25 22:27:28.875 01474-151c JadeHttp.dll version check failed, connection terminated
2010/08/25 22:27:28.875 01474-151c Request rejected - service unavailable

Which would possibly suggest the dll version is different from what is expected, though I have copied it from the bin folder the jade system is running from. I have made sure the dll has permissions to run in IIS web extensions so I'm at a bit of a loss as to what is going wrong.

Does anyone have any thoughts on where to look at next?

Thanks.

Hi Chris,

Have you tried restarting the w3 windows service on the IIS server (or restarting the web site), sometimes IIS can keep the dll in memory and not pick up changes.

Alternatively, have you checked that the version of the jadehttp.dll matches the JADE version of the web application that you are connecting to? i.e The version of the JADE web service application listening on DEV port=4010

regards,
Dr Danyo

Thanks for the reply. I've restarted the IIS websites/applications and removed/re-added the dll as a valid web extension but doesn't seem to make any difference.

At the start of the trace file it has "Starting jadehttp.dll Version 6.3.05.002" which matches what is visible in the dll properties window for jadehttp.dll.

I run jverinfo.exe and it provides the following information
drdanyo.exe 6.3.05.002 Thu Jun 17 00:37:42 2010 I386 WinCUI i686-msoft-win32-ansi release
jadapp.exe 6.3.05.038 Tue Jul 27 17:31:48 2010 I386 WinGUI i686-msoft-win32-ansi release
jadappb.exe 6.3.05.038 Tue Jul 27 17:31:48 2010 I386 WinCUI i686-msoft-win32-ansi release
jadclient.exe 6.3.05.002 Thu Jun 17 00:37:48 2010 I386 WinCUI i686-msoft-win32-ansi release
jaddinst.exe 6.3.05.002 Thu Jun 17 00:37:49 2010 I386 WinGUI i686-msoft-win32-ansi release
jade.exe 6.3.05.042 Tue Jul 27 18:22:50 2010 I386 WinGUI i686-msoft-win32-ansi release
jadeadmin.exe 6.3.05.002 Thu Jun 17 00:37:53 2010 I386 WinCUI i686-msoft-win32-ansi release
jadepg.exe 6.3.05.034 Tue Jul 27 18:22:50 2010 I386 WinGUI i686-msoft-win32-ansi release
jadload.exe 6.3.05.002 Thu Jun 17 00:38:01 2010 I386 WinGUI i686-msoft-win32-ansi release
jadloadb.exe 6.3.05.002 Thu Jun 17 00:38:02 2010 I386 WinCUI i686-msoft-win32-ansi release
jadrap.exe 6.3.05.002 Thu Jun 17 00:38:07 2010 I386 WinGUI i686-msoft-win32-ansi release
jadreg.exe 6.3.05.002 Thu Jun 17 00:38:08 2010 I386 WinGUI i686-msoft-win32-ansi release
jadregb.exe 6.3.05.002 Thu Jun 17 00:38:08 2010 I386 WinCUI i686-msoft-win32-ansi release
jadserv.exe 6.3.05.002 Thu Jun 17 00:38:08 2010 I386 WinGUI i686-msoft-win32-ansi release
jdbadmin.exe 6.3.05.002 Thu Jun 17 00:38:09 2010 I386 WinCUI i686-msoft-win32-ansi release
jdbreorg.exe 6.3.05.002 Thu Jun 17 00:38:09 2010 I386 WinCUI i686-msoft-win32-ansi release
jdbutil.exe 6.3.05.002 Thu Jun 17 00:38:10 2010 I386 WinGUI i686-msoft-win32-ansi release
jdbutilb.exe 6.3.05.002 Thu Jun 17 00:38:11 2010 I386 WinCUI i686-msoft-win32-ansi release
jddlutl.exe 6.3.05.002 Thu Jun 17 00:38:11 2010 I386 WinGUI i686-msoft-win32-ansi release
jddlutlb.exe 6.3.05.002 Thu Jun 17 00:38:12 2010 I386 WinCUI i686-msoft-win32-ansi release
jverinfo.exe 6.3.05.002 Thu Jun 17 00:38:35 2010 I386 WinCUI i686-msoft-win32-ansi release

Now I assume that when the database server is started (jadrap) that the web service will be running under that version(?). (note I think that the later jade.exe version is due to some hotfixes being applied to the system)

I have also downloaded Jade 6.3.06 and copied the jadehttp.dll from the bin across to the system I am working with (the dll is version 6.3.06.003) and after restarting IIS the new dll is detected (version displayed in the trace file) however the same version check failed error occurs.

Hi Chris,

The original log sample you supplied shows jadehttp.dll is getting a 10054 error when attempting to communicate on port 4010. This is a TCP error raised by the operating system and is summarised as:

10054

WSAECONNRESET -- Connection reset by peer. This occurs when an established connection is shut down for some reason by the remote computer.

Is there a local firewall that's blocking activity on port 4010? Can you use another port, e.g. 6305, is this more successful?

Thank you,

Thanks for your replies. It wasn't a firewall issue in the end - probably just an understanding issue on my part but I had the ConnectionName parameter matching the application name when it needed to be the URL + port of the connection. Once this was updated to be URL + port (localhost:4010) then everything worked beautifully.