Forums

by Kern Carboni >> Tue, 29 Aug 2000 21:56:37 GMT

We are trying to run jadrap as a service on a couple of sites but have
a few problems - when we run jadrap as a server all client workstations run as normal, change to service and a -104 error with a 10061 error in jommsg.log. Any idea?

Regards
Kern

by Krull >> Tue, 29 Aug 2000 23:08:39 GMT

Kern,

A 10061 error is a 'Connection Refused'; the connection is being refused due to some internal error detected by the TCP/IP protocol stack on the server machine.

To obtain some further info, can you try the following:

1) Before starting the service, execute 'netstat -a' from a command prompt and ensure that there are no TCP Listen sockets bound to the address and port number you specified for the database server.
2) Start the service
3) Execute 'netstat -a' and check that you now have a LISTEN socket for the sepcified address and port.

Note: If you are using the default 'Listen on all interfaces', look for address 0.0.0.0 in steps 1) and 3)

by Kern Carboni >> Thu, 31 Aug 2000 4:12:43 GMT

Is the "listen on all interfaces" an NT setting?

by Krull >> Thu, 31 Aug 2000 4:43:47 GMT

Is the "listen on all interfaces" an NT setting?

It's a JADE 5.1 TCP/IP setting that can be set from jadrap and is saved in the JADE INI file. Listen on "All Interfaces", is the only option for releases prior to JADE 5.1.

by Kern Carboni >> Mon, 11 Sep 2000 21:37:52 GMT

I ran netstat before and after starting service and captured output to file. Both are the same, in content, and indecipherability. Any pointers towards what I am looking for?

Regards
Kern

by Krull >> Mon, 11 Sep 2000 22:06:02 GMT

I ran netstat before and after starting service and captured output to file. Both are the same, in content, and indecipherability. Any pointers towards what I am looking for?

If you didn't see a new entry after stating the service, then it sounds like jadserv is not offering a TCP listen connection. When you start the JADE database server, either as a RAP (jadrap) or service (jadserv), netstat -a should show an entry similar to the following:

Proto Local Address
Foreign Address State
TCP <computer name>:<port number> 0.0.0.0:0 LISTENING

where <port number> is the TCP listen port you specified via jadrap or directly in the JADE INI file.

If you are on 5.0.16, did you check that you have the jomsrvr.dll update as mentioned in a prior post?

by Michael Jones >> Thu, 31 Aug 2000 0:03:36 GMT

if you're running 5.0.16 : it needs to be patched, before it can be run as a service.

by Krull >> Thu, 31 Aug 2000 1:18:18 GMT

if you're running 5.0.16 : it needs to be patched, before it can be run

as a service.

That's correct, if you are on 5.0.16 you will need the 5.0.16.14 patch version of jomsrvr.dll, which is included in the 5.0.16 update available on the web site.

by Kern Carboni >> Tue, 3 Oct 2000 23:16:14 GMT

Not so lucky. Currently running 4.2 on some sites. A bit more info: when you select Start Service on jadrap it registers the service
but does not start it; when you go through Control Panel to services and try start the service manually we get a 2140 NT error - cannot start service....only happens on 2/6 sites.

Another hairy one.....trying to run serverexecute methods - again on 4.2....... works on some sites; on others we get - "a method executing on remote node was aborted" error with a "key path component does not have inverse to prior component" error. If we stop the service and run standard jadrap method works fine; method also works if we comment out serverexecute; just can't have service and serverexecute which is
slowing down our processing. Any ideas......and don't suggest upgrade.

Regards
Kern

by BeeJay >> Thu, 5 Oct 2000 21:30:25 GMT

Not so lucky. Currently running 4.2 on some sites. A bit more info: when you select Start Service on jadrap it registers the service
but does not start it; when you go through Control Panel to services and try start the service manually we get a 2140 NT error - cannot start service....only happens on 2/6 sites.

When you select the run as service option, you then need to shutdown the jadrap and then use either the NT Services dialog or restart the JadRap and choose the File | Start Service option. If you try to start the service while the jadrap is still running immediately after choosing the run as service option, you will get a 2140 exception due to the jadrap still having the JADE Database open at this time. Also, you may want to try adding the ini= option to your jadrap shortcut to specify the ini file that is to be used. The jadsrv inherits the ini option from the jadrap so this is the best way to ensure it uses a specific ini file. ________________________________________________________________

Another hairy one.....trying to run serverexecute methods - again on 4.2....... works on some sites; on others we get - "a method executing on remote node was aborted" error with a "key path component does not have inverse to prior component" error. If we stop the service and run standard jadrap method works fine; method also works if we comment out serverexecute; just can't have service and serverexecute which is
slowing down our processing. Any ideas......and don't suggest upgrade.

I would suspect here that the jadsrv is not using the same ini file as the jadrap - try checking the registry for your JADE service and see if it has a specific ini file included in it's target line information. The reason I suspect it's using a different ini file when running jadsrv versus jadrap is because the "key path component does not have inverse to prior component" exception can be avoided by overriding this requirement with an ini file setting. This is suggestive that the ini file used by the jadrap has this setting whilst the ini file being used by the jadsrv does not have this setting. Try de-registering the service via the jadrap, change your jadrap shortcut to explicitly specify your ini file on the target line for the jadrap shortcut and then re-register the service and see if this behavioural difference no longer occurs.


Hope this helps,
BeeJay.