Using IS 6.1 connected to Broker 6.1 - nonclustered Windows 2000 environment.

The IS server.log has the following exception:
005-01-28 00:18:17 EST [LGU.0002.0001E] Error getting broker log length: The connection is closed.
2005-01-28 00:18:17 EST [ISS.0098.0035V1] EBZ303.Triggers:EBZ303_MapBlendSpecification detected Endpoint Unavailable. Going into a wait state.
2005-01-28 00:18:20 EST [ISS.0098.0035V1] XES100.Triggers:XES100_TRG_OrderCreate detected Endpoint Unavailable. Going into a wait state.

All IS triggers become disconnected and queue up the documents but donot process them anymore. Restarting the IS is not possible because the IS process does not shutdown completely. Booting the Windows Server is the only option.

The WmUtilLog package is enabled and there is only one IS connected to a broker.

Sorry to ask an obvious question, but…

Are you sure your Broker is running?

Ofcourse, the Broker is running.

We have kind off observed a similarity on the occurence of the issue.

It looks like we see this disconnect when there is a WAN/Network connectivity issue between the Broker and the IS. So has anybody noticed this?.

Yes, we’ve seen the same messages when the IS cannot connect to the Broker. Network issues were the cause for us as well.

So how did you get this issue resolved?.