Hi All - new to this forum and would appreciate some assistance.

I have inherited a solution which contains “webMethods Integration Server 6.1” as an element. We seem to have an issue starting the service since the latest round of MS patches were applied to the server. Is this a known issue? Are there any workarounds?

All the best!
Ross

Have you seen the logs…what is the specific error you are getting???

Are there specific webMethods logs?

All the windows system log gives me is :

“The webMethods Integration Server 6.1 service terminated unexpectedly. It has done this 1 time(s).”

There are webMethods specific logs in the below path

\IntegrationServer\logs

I think this is where the application is installed:

D:\EnterpriseOne\wsg\IntegrationServer\logs\

(.exe location is : D:\EnterpriseOne\wsg\IntegrationServer\bin\ISNTSvc.exe)

Unfortunatley the the newest log is dated 13/04 - the last time it was used…

Ross

so, look into the D:\EnterpriseOne\wsg\IntegrationServer\logs\ folder and see what’s the error in server.log or error.log
Without error, no one can help

I have finally managed to make it throw some logs today - these are now attached. I have also included the previous set of logs (4th Maty) which is the last time this has worked correctly.

Thanks for you help so far…
txout20130516.zip (50 KB)

I should add that this seems to have been generated by using

server.bat -debug 5 -log none

command line syntax as apposed to starting the service itself.

I can connect to developer on this node which is odd.

remove
-log none
from your command, so you can see the server log.
I guess the server actually loaded, at least partly.

I guess you are right LOCKFILE is created. Log attached.

Cheers
error20130516.log (39.7 KB)
server20130516.log (197 KB)

I think your broker is not running:

2013-05-16 17:36:38 BST [ISS.0099.0003E] Unable to create Broker Transport 10.205.0.210_5555_LoggingUtility_AC. Exception com.wm.app.b2b.server.dispatcher.exceptions.EndpointUnavailableException: [ISS.0098.9014] BrokerException: Comm Failure (102-2050): Unable to open connection to host ‘localhost’. Error ‘java.net.ConnectException: Connection refused: connect’ was reported by the socket call.

2013-05-16 17:36:38 BST [LGU.0001.0003C] Error creating broker admin client:
2013-05-16 17:36:38 BST [ADA.7180.0004D] Custom Classpath entries are:

try to bring up the broker (search services list for broker)

Ok - would that be a windows service? nothing obvious in the service’s snap in.
Sorry for being clueless with this one…

unable to connect to admin console either: http://localhost:5555 - using administrator credentials
although can connect to developer

yes, windows service.
older version called
webMethods broker …
newer:
Softwareag broker …

even older
Activeworks ?? borker or something like that

nothing at all with broker in the name. the only webMethods service is the IntegrationServer 6.1

what do you get with
http://localhost:5555

if it’s not login error, try:
http://localhost:5555/WmRoot

I lied - I hadnt appreciated username was case sensitive. I can login to the landing page. Not sure what i’m looking for though…

The error indicates the broker is on “localhost”
Try to find Broker dir next to your IS dir.
see if you can find any log for broker

Is it possible that broker was running command line, not service?

its possible but unlikely … i dont know how it would of started following patching etc…
screen shot attached - nothing obvious

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/e4688950032d175551b6ac0315d72330ce89ad2f_2_1035x588.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/e4688950032d175551b6ac0315d72330ce89ad2f_2_1380x784.jpeg 2x" data-dominant-color="E0E1E4">

is.jpg1544×878 142 KB

one step back, do you even use broker?

from the first a few lines in your log, services are working fine.
This may be all you need.
Check the other systems that are connecting/interacting with your WM instance, see any issue.

thats a very good question - excuse the ignornace but in this instance I dont know what broker is!
I cant test really as the interested user has gone for the day.

Is it possible the server is running without issues - just not via the windows service. Would it matter the windows service is not started?

if you start it with command line, just keep it running this way now.
Once verified working. try Windows service option later.
Good luck

Thanks for you help - before I let this very helpful person go, is there any way to verify via the admin webpage that all is as it should be?

It’s really depends on what services you are using on your system.
There is no single place that will tell you “everything is working or not”
You can login to admin, so the server is running.
Besides that, check server log for any event/errors.
Cheers,

Thanks for all your help guys. Looks like command line start of the server got us out of the mud. Will look into the service start failure in due course

Hello
Is your problem get resolved.
Thanks
Baharul