RE: Domino config in OpsNav with Win2K problem

Jim

I have 6 of them - none with your text. What I get is at the bootom of the
file:

Current Thread
Details

----------------------

     "Signal dispatcher" (TID:0x1058798, sys_thread_t:0xe70440, state:R,
native ID:0x33c) prio=5

Doesn't LOOK like an error, but a signal is some kind of problem, right?

I'm on V5R1 of OS/400

At 06:34 PM 8/8/02 -0500, you wrote:
>Vern-
>
>I found a log file in my c:\Program Files\IBM\Client Access\
>folder.  Do you have any recent file named javacorennnn.nnnnnnnnnnn.txt ?
>
>At the top lines of one of mine I see:
>
>Exception code: C0000005 ACCESS_VIOLATION
>Fault address:  0C071958 01:00010958 C:\Program Files\IBM\Client
>Access\Plugins\Lotus.Domino\cwb3udof.dll
>
>I've logged the problem to IBM's online support.  It's my first experience
>with their call-logging website, so I'm eager to see how things flow.
>
>I'd like to know if you're seeing the same error.
>
>-Jim
>
>-----Original Message-----
>From: Jim Damato [mailto:jdamato@dollargeneral.com]
>Sent: Wednesday, August 07, 2002 11:26 AM
>To: 'midrange-l@midrange.com'
>Subject: RE: Domino config in OpsNav with Win2K problem
>
>
> >Vern
> >The 400 is at V5R1, brand new box
> >Every time I double-click Network->Server->Domino, I get a message box
> >that cwbunnav.exe caused (or had) an error and a log is being written.
> >Log in question is a DRWATSON log and the error has to do with memory
> >access, as reported.
>
>I've had the same problem at V5R1 and a Compaq Armada laptop also running
>Win2K.  I gave up on it.  We're depending on the Domino client.  I haven't
>had time to call IBM for support.
>
>-Jim
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.