Link to home
Start Free TrialLog in
Avatar of nelsonnr
nelsonnr

asked on

Application hang on Windows network

In November 2008 we went live with a new application on our local area network. The application is called Bond Adapt version 9.2.6 (www.bondadapt.com)

This application is a CRM product. It is a traditional 32 bit client / server application and we have about 30 users on our local area network.

We have a dedicated server running this application. The application on the server uses its own version of SQL. The server is a high specification HP Proliant DL580 with four CPUs (Dual-Core Intel Xeon) and 4GB of RAM.

Our LAN consists of 30 Windows XP PCs most of which are running Service Pack 3. They have Office 2003 installed on them and this Adapt application. 26 PCs are connected to the nework at 100MB. 4 PCs are connected at 1000MB.

Intermittantly (there is no pattern and hence this question) the Adapt application completely hangs (freezes, locks up) on individual PCs. The user does nothing specific on the application to cause the hang. To recover from this we need to open Windows XP task manager, find the adapt.exe process and end it. We then login to Adapt and continue as normal.

We are seeing these Adapt hangs intermittantly about twice per day (10 per week) across 30 PCs. Its not a problem that is causing us major disruption, its more of a nuisance.

The software companies helpdesk for the application have not (and will not) take any responsibility for this hang. They say that this does not occur across their customer base and that it must be a problem on our local area network.

I am at the end of my wits and would really appreciate some advice on how best to troubleshoot this issue. We have taken detailed logs of when the hangs occur and can see absolutely no frequency on which to create an anchor point to begin troubleshooting.

I have 11 years experience of IT support and am (nearly) CCNA qualified (exam in May) so I understand, from the ground up how this application communicates on our network. But I have no idea of how resolve this issue and feel completely isolated in trying to find a solution as the software company have backed off. I am considering logging a support call with Microsoft to put responsibility toward the operating system being at fault - but realistically there are too many things to consider / blame.

Just to finish - before we went live with this application in November 2008, we saw absolutely no issues on our local area network. We were using an old CRM application that worked fine. We upgraded and migrated to this new app and although we are reaping the benefits of how the new app functions - the freezing of the app is obviously detremental.

Many many thanks and look forward to some help.

Neil Robb
IT Manager
Avatar of borgunit
borgunit
Flag of United States of America image

Have you checked network speed during "hang ups"? Some apps have trouble when they do not get their "answers" in a timely matter on a network. Just an idea.
Avatar of kadadi_v
Is CRM  is webbased application or installable product...?
and its compatible with your server or desktop operating system..means any installation(dll files
)issues and if you work on single pc (server/client)...then its working properly..?
Did you seen the demo for CRM application used on network..or may be its upgade copy having some bugs..?
And check your Antivirus firewall prevting to adapt.exe ..so try to add as a trusted application antivirus integrated firewall if you are using sysmatec/Mcaffe corporate edition.

Regards,
vijay kadadi
Avatar of nelsonnr
nelsonnr

ASKER

Hi borgunit,

This is a good idea. I have not checked the network speed during the application hang. How do you think I could easily monitor the speed of the network on individual PCs?

Neil
Hi vijay,

The CRM application is not web based. It is installed as a 32 bit application.

It is compatible with our client operating system yes, the client OS is Windows XP SP3

We did not see a demo of this application working on the manufacturers network. We never tested this application on our network before we committed to buying it unfortunately.

I am just checking to see if we have excluded it locally from our McAfee Anti-virus on the PCs. I will report back.

Thanks,

Neil

If the application hangs on client machines, the first place to check is the event logs
start>run>eventvwr.msc 
check the application & system Event tabs for any related events
if you found any related errors to adapt.exe please copy the text here, as well as the event ID 

Hi Admin3k,
Unfortunately the app doesn't write to the system or application event logs when a hang occurs. This is what is causing the frustration. The hangs are so intermittant, and nothing is logged. I don't even think the app has a debug mode which will allow us to enable deeper logging.

I have downloaded Windows Debugging tools and am currently learning about how to attach windbg.exe to the app with the hope of finding the cause.

I have also enabled the ability to create kernal dumps through the keyboard (CTRL+SCROLL LOCK key twice) so that I can perhaps begin analysing the dump files. It seems like a steep learning curve though so I don't expect to be able to debug very quickly, if at all.

We did not have local anti-virus excluding the local program files (C:\Program Files\Adapt92\adapt.exe * adaptnotify.exe) so we have just pushed that out to all PCs using McAfee Protection Pilot policies.
I see, you can try using tools like ProcmonProcess explorer to get a better look at the process in action, this has helped me solve many similar problems .


Thanks admin3k - I will look into Procmon & Process explorer just now.

Neil
ASKER CERTIFIED SOLUTION
Avatar of nelsonnr
nelsonnr

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
In the end we had to rebuild the client PCs. We used Microsoft Sysprep to create a ghost build an wiped each PC one by one.

This solved the problem, but we still never found the cause which was extremely frustrating.