Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

PCSWS.exe errors when starting a .ws session with a GUI application

1,899 views
Skip to first unread message

Megan Kauffman

unread,
Apr 8, 2004, 2:57:25 PM4/8/04
to
Hello,
Here are the specs:

PC:
Dell OptiPlex GX70 PC.
3 GHz
1 GB Ram
80 GB Hard Drive
Windows XP Professional
Novell Network
iSeries Access 5.2

AS/400:
Our AS/400 system is running OS/400 V5R1.


Here is our problem:
We use a GUI (Graphical User Interface) to launch our sessions (.ws
sessions created and saved using iSeries access, saved in the default
location...C:\Program Files\IBM\Client Access\Emulator\Private). The
GUI is launched and the user tells the GUI which display session to
start. No matter which session (each PC typically has 5
pre-configured sessions saved to it) is started by the GUI, the user
receives a pcsws.exe error. The error comes up on the screen and
says, "PCSWS.exe has encountered an error and needs to close.....".
The user cannot even get to the security login for the AS/400 system
before the error window appears. If we start the sessions manually
without the GUI there are no errors. Also, if we start the session
without the GUI and then pick the session up with the GUI (overlay the
GUI on an already started session) there are no errors. We have no
problems with any other brand of PC in our organization (compaq and
acer..they all work fine). We have tried everything!!!!! Could the
processor speed have anything to do with this error?? Someone please
help me!!

Thank-you!!!

Megan

Jonathan Ball

unread,
Apr 8, 2004, 3:09:41 PM4/8/04
to

Just a guess: either some expected parameter is not
being passed, or a bad value in a parameter is being
passed.

Jon

unread,
Apr 12, 2004, 8:29:42 PM4/12/04
to
Up-to-date on iAWin service packs ? Is the GUI you refer to one you
wrote or are you using pcsfe.exe -- the Personal Communications
Session Manager ? If it's the IBM-supplied one and you are up-to-date
on SPs, then consider contacting Service ?

Or run drwtsn32 -i to ensure Dr. Watson is installed as the default
application debugger, then reproduce the problem and have a developer
familiar with Windows take a look at the resulting drwtsn32.log and
user.dmp. WinXP creates minidumps by default, personally I prefer the
transportable full dump, tho it'll be big -- 30Mb.

Jon

myka...@masonichomespa.org (Megan Kauffman) wrote in message news:<afe95a9.04040...@posting.google.com>...

<snip>

Megan Kauffman

unread,
May 10, 2004, 8:59:17 AM5/10/04
to
We figured this out. We had to disable hyperthreading in the system
BIOS and the GUI works fine, not the best solution because we are
giving away our hyperthreading abilities, but our app works.

Thanks!!

jkw...@excite.com (Jon) wrote in message news:<c776aaac.04041...@posting.google.com>...

Jon

unread,
May 17, 2004, 8:56:47 AM5/17/04
to
Good to hear you found a workaround to the bug! Please consider
reporting said bug together with the Dr. Watson dump so it can get
fixed and you can re-enable HT :-).

$.02,
Jon

mcal...@masonicvillagespa.org (Megan Kauffman) wrote in message news:<9f9d5641.0405...@posting.google.com>...

0 new messages