We have recently converted our 16 Bit (OI 3.7.4) application to 32 Bit (OI 7.0.0) which we have deployed to several customers, 2 of the customers who are on XP are experiencing daily freezes with our software sometimes upwards of 6 a day. The same freezes were not a problem on OI 3.7.4 and appear to be 32 Bit\XP related, one customer is on the Universal 3.0 Driver and the other is using the All Networks 2.1.

The tasks they are performing in our application are random as are the other applications which they have running at the same time e.g. Outlook, Excel so there isn't any real consistency with the freezes.

Once of ther customers is operating a 3 user licence and the other 25, the 3 user customer is only a relatively light user of the application as opposed to the 25 user system so it doesn't appear to be volume of workload.

The Server and Client details for one of our customers is provided below, the other customer is also running clients on XP with Service Pack 2 loaded:-

Server:

ProLiant G3 (Dual Xeon Processor, 1GB RAM)

Operating System is Windows 2000 Advanced server (SvPK4)

Clients;

Minimum Client spec is P4 2Ghz with 256Mb Ram

XP/2000 Client OS

All Part of an Active directory domain

All clients are XP Service Pack 2

Any suggestions on how to resolve this issue would be greatly appreciated we don't really want to suggest a re-install of OpenInsight as this would not really be feasible.

Jon

Do you have any Anti-virus on server or W/S that is scanning real time? Critical to ensure *.LK and *.OV are not scanned.

I would also look for a network issue.

Hi Richard

Thanks for your response.

One of the first things we did was to ensure that we shut down any virus checking on the .LK and .OV files this has unfortunately made no difference.

One of our Product Engineers dialled into one of the offending client PC's and used a piece of software called Process Explorer which is essentially a more detailed version of the Task Manager utility. The OInsight.exe process had stopped as it was waiting for a response to a request entitled 'WRUserRequest' whatever this may be.

Each of the two customers are on different Server software, one on Windows 2000 and the other on Windows 2003, the only common software between the 2 environments being Windows XP Client machines with Service Pack 2 installed.

We have tried setting OpenInsight to run in its won memory space but this also didn't make any difference.

Jon

is windows operating system stuff.

Sounds as if you are calling some 16bit code via thunk driver or whatever. Check the DLL's and get rid of all 16bit stuff in OI DLL declarations.

Thats my best guess.

We hit something similar last week. We have deployed to about 50 sites, and our application exhibited something similar to your problem.

The application would simply stop for as much as 15 - 50 seconds and then take off like there was nothing wrong. All users connected to the application were affected.

We were able to re-create the same by attaching workstations on Ethernet using auto connect at the switch and auto connect at the workstation. Some of teh auto connects would not load the application and some loaded very slow, yet each was able to load the application after setting each to 100/Full. We did have one workstation that would not operate on anything better than 100/Half. During the times of the slow down went with poorly connected workstations attempting to load the application. The switches involved were Bay and CIsco and the lines had been certified and the workstations were a variety of newer Dells, so brand really was no factor, as opposed to the actually ability of the device(s) to properly connect.

It was troublesome because the old app in AREV 3.111 did not exhibit the symptom, but that seems to have cured it. Their network people were to have re-combed the network and stations to appropriately configure the remaining devices this week.

Thanks

Dana

Process Explorer will show what DLLs are in use by a process. Switch the lower pane view from Handles to DLLs.

This is one of the best diagnostic tools I've found. www.sysinternals.com freeware.

Thanks for all your responses, we are due to go on site to visit the customer this Wednesday (31/05/06) so I will provide an update then.

Since my original post we found out last week that we have a customer who has recently upgraded to our 32 Bit product from 16 Bit (OI 3.7.4 to 7.0.0) and is succesfully running the product (so far) on XP Service Pack 2 Client machines.

This would again suggest it's some form of environment issue.

Thanks

Jon

Initial indications are that this was down to a memory leak occasioned by a 3rd party DLL. This was established using a combination of three third party tools for

thread and process analysis

network traffic analysis

memory leakage analysis

Since replacing the errant DLL we have been unable to recrash the system and the memory leakage has all but stopped.

The Sprezzatura Group

World leaders in all things RevSoft

View this thread on the forum...