ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Sporadic >> SO-A Access Violation
http://www.istechforum.com/YaBB.pl?num=1175614976

Message started by kkmfg on 04/03/07 at 08:42:56

Title: SO-A Access Violation
Post by kkmfg on 04/03/07 at 08:42:56

Not every time but way too often this apparently happens:

They'll be in a sales order or purchase order and be in the line item screen to enter in parts. Sometimes, when trying to lookup the correct part number for what they want, the program will die horribly. It says access violation at 00424DDD read of address 20202020 (seems pretty fake to me!) and then access violation at 00438079 read of address 20202028. That happens twice. Then ntdll.dll goes into an infinite loop of AV's. It's great fun for the whole family.

Title: Re: SO-A Access Violation
Post by fast on 08/14/07 at 12:34:33

We get this from time to time as well as invalid pointer. Mostly from users on my Terminal Server. Able to resolve it?

Title: Re: SO-A Access Violation
Post by kkmfg on 08/19/07 at 19:46:26

Umm I don't remember hearing complaints about it recently. I think that it must have gotten better when we upgraded versions. I'll check though.

Title: Re: SO-A Access Violation
Post by LeAnn Cucchiara on 09/04/07 at 08:59:02

kkmfg wrote:

Umm I don't remember hearing complaints about it recently. I think that it must have gotten better when we upgraded versions. I'll check though.

Title: Re: SO-A Access Violation
Post by kkmfg on 09/04/07 at 09:25:11

LeAnn Cucchiara wrote:

[quote author=kkmfg link=1175614976/0#2 date=1187581586]Umm I don't remember hearing complaints about it recently. I think that it must have gotten better when we upgraded versions. I'll check though.

We get it way too often - we're on Windows XP SP2 OS - my last was: AV @ address 004046E0 in module TP7runtime.exe read of address 00001DF9 - then I get the gray screen of death & only ctrl, alt, delete can kill it. [/quote]

Hmm... Unfortunately the addresses don't do a lot of good to most people... Maybe not even Lynn and Alan and the gang. The fault address is a pretty nice piece of info if you've got the source code to the module that faulted. In this case it appears TAS did so we're potentially stuck scratching our heads.

So, I don't know what to tell you. It seems to not happen all of the time here but does sometimes.

Title: Re: SO-A Access Violation
Post by fast on 10/26/07 at 13:06:30

Anyone get a fix for this?