× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yep...i'd scrub the registry...unfortunately the uninstall leaves much
to be desired in that area. It leaves TONS of registry entries (or at
least it used to...) we have 10 iSeries boxes here. I only have that
issue with one machine..i just use Mochasoft when connecting to it. I
really don't think reinstalling is gonna help but let me know if it
does! Make sure that the service packs on the PC are up to date before
you nuke the install...


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Angus MacQueen
Sent: Friday, June 22, 2007 8:28 AM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Access for Windows problem

Michael, thanks for your reply, the user can sign on successfully from
other
PC's.

Guess it's down to scratching his iSeries Access install and starting
over.
Another thought tho' if I do that is - do I need to clean the registry
as
well?

Angus

On 22/06/07, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:

Is it the same user regardless of PC? Have you had the user try from a
known working PC? If the user can access the system from a different
PC, reinstall. If they can't, it's a user profile (I'll bet) issue.

On 6/22/07, Angus MacQueen <amacqueen@xxxxxxxxx> wrote:
We have one user who consistently cannot connect to one of our
boxes, no
other user has the same problem.

Server is at V5R3 and the client was at V5R2 but as of today is at
V5R3
with
the latest service pack and we're still getting the same error.

The error code is CWBLM0031 followed by RC1=2 and RC2=21, I've
searched
Google and the archives for a solution but to no avail. All the
suggestions
such as LICPGM's not being there, differences in CCSID's etc.
provide no
resolution.

The one possible solution suggests a conflict between an earlier
version
of
Client Access and iSeries Access. There is no evidence on the user's
PC
of
any residue of an earlier version so that may not be it, but who
knows
for
sure (we are talking Windows here).

Before I get him to go through the pain of trashing the PC install
of
iSeries Access and re-installing does anyone here have any wisdom on
this
one.

Many thanks

Angus
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.