ActivConsole.exe reference memory errors

[jlesins1]

We are using JDE Enterprise One, version B7334 SP22. We are running the Enterprise client on a Windows 2003 server and users access it through Terminal Services. Lately we have been getting the following error:

The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read". Click Ok to terminate the program. Click Cancel to debug the program.

The client then crashes and sometimes users can just go right back in through the same terminal server session and sometimes we need to boot them off the session and then they relog.

Can anyone tell me what could be the cause of this issue? There does not seem to be a pattern to this.

Thanks in advance!!

 

[Sebastian Sajaroff]

Hi,

SP22 is too old, probably doesn't even work with W2003.
You should upgrade your Service Pack level to SP24.

 

[klwong]

Unfortunately, I didn't think to start archiving MTR documents until the middle of 2009 ...

But the oldest one I have for Xe/ERP8 Terminal Servers (06/03/2009) says that Windows 2003 is supported with SP22.

However, Windows 2003 SP1 was not supported until SP23, and Windows 2003 SP2 was not supported until SP23_R1.

 

[peterbruce]

Ken,

[ QUOTE ]

Unfortunately, I didn't think to start archiving MTR documents until the middle of 2009 ...


[/ QUOTE ]

Now that is very handy to know. Thanks for having the forethought to do that - even if it is only from "the middle of 2009."

 

[klwong]

Forgot to comment on the original issue ...

Unfortunately, this could come from several causes, ranging from NTFS file system corruption, to mismatched patch levels between the Client Access ODBC driver and the AS/400.

If you search Oracle's Knowledge Jungle, you'll see what I mean. This also makes it a little hard for us to help further without more information on your system configuration.

 

[jlesins1]

Sebastian -- thanks for the suggestion.

Klwong, what else do you need to know?

 

[klwong]

Personally, I find it extremely difficult to troubleshoot this sort of intermittent problem remotely. As I mentioned above, the number of bug reports that you find when searching Oracle's web site show many possible causes.

The easy possibilities to eliminate are checking to make sure the disk isn't corrupted, and that the Client Access patch level installed on the Terminal Server matches what you have on the AS/400. This assumes, of course, that you are using an AS/400, but right now, only you know whether or not you are.

If these aren't the problem, then I suggest you search Oracle's web site for the term "memory could not be read," and you'll see the other things you could check for.

 

[riko44]

Nice to know someone did it . I am wondering if you have archive MTRs for Client and JAS server circa Sep-Oct 2010 (thats Tools Release 8.98.3, - before 8.98.4)

Apparently Published MTR changed a lot after 8.98.4 was released, but were are not planning to upgrade to 8.98.4
Thanks a lot!!

 

[klwong]

For the client, I have Aug. 31, 2010, Sept 17, 2010, Oct. 20, 2010, and Nov. 19, 2010.

For the JAS Server, I have Aug. 12, 2010, Sept. 14, 2010, Nov. 5, 2010, and Nov. 19, 2010.

 

[jlesins1]

Klwong, sorry for the delay in answering. This is a Windows server, not an AS400 server.

Jenny