XAL 3.5 on SQL Server 2000 Users crashing.

Hi

I'm affraid I don't know anything about XAL so any help would be much 
appreciated.

We have a customer who we just upgraded to Windows 2003 Server .There XAL 
consultant's then came in and installed  SQL2000 & XAL 3.5.
All users are running Windows XP .
The problem is that XAL keeps crashing on all users.
Here are the error messages from the event log on the users PC’s

Event Type:	Error
Event Source:	Application Error
Event Category:	None
Event ID:	1000
Date:		20/11/2007
Time:		14:15:45
User:		N/A
Computer:	
Description:
Faulting application dxalw32.exe, version 3.55.0.0, faulting module 
dxalw32.exe, version 3.55.0.0, fault address 0x000a1eee.


Event Type:	Error
Event Source:	Application Hang
Event Category:	(101)
Event ID:	1002
Date:		16/11/2007
Time:		11:05:00
User:		N/A
Computer:	
Description:
Hanging application dxalw32.exe, version 3.55.0.0, hang module hungapp, 
version 0.0.0.0, hang address 0x00000000.
  
The XAL consultant that they use doesn’t have any ideas and just seems to 
keep passing it over to us!
He’s say’s it might be down to collisions on the server with other 
applications ??
There are no other application’s running on the Server apart from Sophos 
anti-virus, but it does have all the users data folders on it and a shared 
folder with just data in, wouldn’t have thought this would be a problem.


Thanks in advance.

> We have a customer who we just upgraded to Windows 2003 Server .There XAL
> consultant's then came in and installed  SQL2000 & XAL 3.5.
> All users are running Windows XP .
> The problem is that XAL keeps crashing on all users.

Try checking for network problems. XAL is very sensitive if it looses 
connection to the server for a few miliseconds. It crashes immidiately.

Also try to disable on access virus scanning i the XAL catalog on the server 
and also for XAL-temp files in the clients TEMP-catalogs (if i'm not 
remembering it wrong XAL-tmp files all have .$$$ extensions). Some 
antivirus-solutions locks files while scanning them - that can make XAL (and 
other programs) crash.

Hope it helps

Regards
     Gert Lynge 

Thanks for responding to my post.
We have already tried disabling on access scanning on the server and it was 
still the same, but we have not tried disabling the scanning of temp files on 
the clients workstations yet will give that a go and alsp check the network 
thanks.

This is the error message produced on the workstations when it crashes, just 
incase you have come across it.

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
> (WrapperWrite()). 

Thanks again.

Stu


"Gert" wrote:

> > We have a customer who we just upgraded to Windows 2003 Server .There
XAL
> > consultant's then came in and installed  SQL2000 & XAL 3.5.
> > All users are running Windows XP .
> > The problem is that XAL keeps crashing on all users.
> 
> Try checking for network problems. XAL is very sensitive if it looses 
> connection to the server for a few miliseconds. It crashes immidiately.
> 
> Also try to disable on access virus scanning i the XAL catalog on the
server 
> and also for XAL-temp files in the clients TEMP-catalogs (if i'm not 
> remembering it wrong XAL-tmp files all have .$$$ extensions). Some 
> antivirus-solutions locks files while scanning them - that can make XAL
(and 
> other programs) crash.
> 
> Hope it helps
> 
> Regards
>      Gert Lynge 
> 
> 

> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
>> (WrapperWrite()).

I can't recall having seen that one before. My guess is network problems 
(but you should still disable scanning of temporary $$$ files - I've seen 
scanning of them crashing XAL when printing).

You could try to start a ping -t in a dos window on the client and let it 
run. Then break it when a client crashes and see how many packets was lost.
No packet lost is NOT a sign of no network problems at all (could be some at 
a higher level) - but if you loose packes you got one for sure (a normal Lan 
should not loose packets if you are not messing with cables etc.)

Regards
    Gert Lynge