Concorde XAL 2.64/2.80 - Faulting application OXALW32.EXE

Concorde XAL 2.64/2.80 - Faulting application OXALW32.EXE

Post by Jespe » Sat, 03 Jul 2004 16:10:53


This is not Axapta but Concorde XAL issue (but I cannot find a forum for
this related application).

In Terminal Server 2003 environment, we have daily problems with high CPU
utilization due to OXALW32.EXE processes. Somehow, both internal and
external users manage to open several OXALW32.EXE processes (sometimes one
user has 11 OXALW32.EXE processes running) but they have only one
application open. We cannot find out why this happens and our users suffer
from poor overall performance on the server.

We are advised to upgrade the core from 2.80 to 3.5 but no cure is
guarantied.

Here what we find daily in our event log: (the fault address changes between
0x000148eb and 0x00012eb7)

Application Event 1000 error:
Faulting application OXALW32.EXE, version 0.0.0.0, faulting module
OXALW32.EXE, version 0.0.0.0, fault address 0x000148eb.

Thanks a lot for any assistance on this matter ...
Jesper
 
 
 

Concorde XAL 2.64/2.80 - Faulting application OXALW32.EXE

Post by Rene PE1R » Sat, 03 Jul 2004 19:22:04


Two things:

1. The XAL Oracle clients (OXALW32) don't start themselves, so what probably
happens: people get kicked out of XAL and restart again. The first instance
still runs though.

2. XAL 2.8 does not work well with Windows XP, 2003. So do a kernel upgrade
3.5.


So the best thing:

1. Restart the terminal server every morning

2. Find out why people get kicked out of XAL.

3. Try a kernel upgrade

Rene

--
RenAltena - PE1RA
Nijverdal - The Netherlands - JO32FJ
pe1ra @ amsat.org - http://www.yqcomputer.com/

Go QRP! Radio spectrum is too valuable for QRO!

 
 
 

Concorde XAL 2.64/2.80 - Faulting application OXALW32.EXE

Post by Jespe » Sat, 03 Jul 2004 20:22:31

Thanks you Ren
I will follow your advise ...

/Jesper




>>>> This is not Axapta but Concorde XAL issue (but I cannot find a forum >>>> for this related application). >>>> >>>> In Terminal Server 2003 environment, we have daily problems with high >>>> CPU utilization due to OXALW32.EXE processes. Somehow, both internal >>>> and external users manage to open several OXALW32.EXE processes >>>> (sometimes one user has 11 OXALW32.EXE processes running) but they >>>> have only one application open. We cannot find out why this happens >>>> and our users suffer from poor overall performance on the server. >> >> Two things: >> >> 1. The XAL Oracle clients (OXALW32) don't start themselves, so what
probably >> happens: people get kicked out of XAL and restart again. The first
instance >> still runs though. >> >> 2. XAL 2.8 does not work well with Windows XP, 2003. So do a kernel
upgrade >> 3.5. >> >> >> So the best thing: >> >> 1. Restart the terminal server every morning >> >> 2. Find out why people get kicked out of XAL. >> >> 3. Try a kernel upgrade >> >> Rene >> >> -- >> RenAltena - PE1RA> > Nijverdal - The Netherlands - JO32FJ> > pe1ra @ amsat.org - http://www.yqcomputer.com/ ; >> > Go QRP! Radio spectrum is too valuable for QRO!> >> >
 
 
 

Concorde XAL 2.64/2.80 - Faulting application OXALW32.EXE

Post by Rene PE1R » Sun, 04 Jul 2004 22:32:56


And try the advise in a testing environment first!
>> >> /Jesper >>

Good luck,

Rene
>>


>>>> This is not Axapta but Concorde XAL issue (but I cannot find a forum >>>> for this related application). >>>> >>>> In Terminal Server 2003 environment, we have daily problems with >>>> high CPU utilization due to OXALW32.EXE processes. Somehow, both >>>> internal and external users manage to open several OXALW32.EXE >>>> processes (sometimes one user has 11 OXALW32.EXE processes running) >>>> but they have only one application open. We cannot find out why >>>> this happens and our users suffer from poor overall performance on >>>> the server. >>> >>> Two things: >>> >>> 1. The XAL Oracle clients (OXALW32) don't start themselves, so what >>> probably happens: people get kicked out of XAL and restart again. >>> The first instance still runs though. >>> >>> 2. XAL 2.8 does not work well with Windows XP, 2003. So do a kernel >>> upgrade >>> 3.5. >>> >>> >>> So the best thing: >>> >>> 1. Restart the terminal server every morning >>> >>> 2. Find out why people get kicked out of XAL. >>> >>> 3. Try a kernel upgrade >>> >>> Rene >>> >>> -- >>> RenAltena - PE1RA>>>> Nijverdal - The Netherlands - JO32FJ>>>> pe1ra @ amsat.org - http://www.yqcomputer.com/ ;>>>>>>> Go QRP! Radio spectrum is too valuable for QRO!

--
RenAltena - PE1RA
Nijverdal - The Netherlands - JO32FJ
pe1ra @ amsat.org - http://www.yqcomputer.com/

Go QRP! Radio spectrum is too valuable for QRO!