RE: iSeries Access and Windows 7

["Reinardy, James" <jreinardy@xxxxxxxxxxxxxxx>]

I ran fine as well for about a month.  It seemed to start when my
password neared expiration and I changed it.  Something to watch for.

Jim 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Larry Bolhuis
Sent: Thursday, October 01, 2009 7:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Access and Windows 7

I've been on 7 most of a week. Only issue I'm encountering is that 
creating a 5250 session from Navigator (right click -> Display 
emulator)  gives me the error "The PC5250 emulator could not be 
started." It's claiming that I have no access to the folder with the 
emulation files.  Changing directories or permissions does no good. 
Using the session manager, however, the sessions create, run, and save 
just fine however. Hmmmm.

  - Larry

Reinardy, James wrote:
> Hi,
>
>  
>
> Anybody out there running Windows 7 yet?  We are doing some testing
with
> the final build on some of our machines in IS.  It is working great
for
> all applications except iSeries Access.  It worked for a while, then
all
> of a sudden I am getting the "CWBML0011 An internal license error has
> occurred rc=6211". It seemed to start after I was forced to change my
> passwords for the i.  IBM Software Support does not officially support
> Windows 7 yet, but tells me it has something to do with access
> privileges on My Documents where the install puts some libraries.  I
now
> have full access to that directory, as well as registry entries and
the
> Program Files\IBM directory itself, but I can't get past the error.
> Even a complete uninstall and reinstall of the application failed to
fix
> the issue.
>
>  
>
> It occurs on both of our partitions after entry of the login
> credentials, though Navigator works fine with the same credentials.
We
> are running V5R4 on the i and using the V6R1 version of iSeries access
> with the latest service pack installed.
>
>  
>
> It's a bit of a long shot, but I was hoping maybe somebody had run
> across the issue and found a fix.
>
>  
>
> Thanks!
>
>  
>
>