×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




(This was also posted to news group ibm.software.code400)

I recently tried the trick of adding multiple server names to the HOSTS
file, all pointing to the same IP address, each with their own library list
in the CODE/400 comm console.  It worked fine until I decided to open a
file from one of the newly defined servers.  From the Code Editor I chose
File | Open, then selected the server I wanted.  The window stayed there
for a short bit, then I got the dreaded visit from Dr. Watson.

Now, whenever I try to access the communication console, Watson rears his
ugly head.  I removed the new servers from the HOSTS file but that hasn't
made any difference - CommConsole still craters.

Here's my particulars:
        NT4.0 SP6a      128 Mb Ram
        WDT400, V4R5M1          (I installed SP2, but still show as V4R5M1?)
        OS/400, V4R5

When I click on the Start | Programs | IBM WebSphere... | Communications |
Communications Console icon, the communications daemon starts in my
traybar, then a few seconds later, <CRASH!>.

        "An application error has occurred and an application error log
                is being generated.

                evfcsvrd.exe

        Exception: access violation (0xc0000005), Address 0x500116f2"


Funny thing is, I get two of these at the same time...  ?

I finally let Dr. Watson log the error.  If anyone's interested, I can post
the gory details of that, as well.

Any help?
Anyone?



David Schopp
Computers Unlimited
2407 Montana Ave
Billings, MT 59102
v: (406) 255-9500
f: (406) 255-9693
---------------------------------------------------------
The sun got confused about daylight savings time. It rose
twice. Everything had two shadows.



This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.