PT 2005 on Win2003 - Slow!

[tylan]

Does anyone have an idea why PT 2005 running on WinXP SP2 clients woould be painfully slow? The company resides on a Window 2003 server. The odd part is that it seems slowest on the XP sp2 machines. It doesn't seem all that bad on out Win 2K machines and XP sp1a machines.

We called PT support, and they just tell us that the problem is our company. They say the max company is 100mb, and ours is 108mb.

Here's the kicker... The afforementioned XP SP2 machines are NOT slow if they are the only one in the company. I've applied the hotfix listed here:

http://support.microsoft.com/kb/885451

It seemed to help a little but not as much as I would like. I'm leaning toward oplocks, but I don't know if that could cause corruption. Ideas?

 

[mattjurado]

I wouldn't mess with file locking yet. Question, if you copy the data locally, how is the speed then? And what exactly is slow? Login? Specific function?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[tylan]

Copying the data locally: haven't tried it. Pretty sure it would fix it. Tried it in a similar situation for another client. Data has to stay on our server.

What is actually slow: Login isn't quick. Once you are in, changing from module to module takes a minute or two. Moving record to record is bearable.

Don't miss this key piece in my first post "Here's the kicker... The afforementioned XP SP2 machines are NOT slow if they are the only one in the company". That means when a machine is the only one reading the data off of the server, everything about PT is faster!

 

[mattjurado]

Okay, do ALL of your XP SP2 computers work okay, if only one at a time is using Peachtree?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[tylan]

Yes. That is dead-on.

 

[tylan]

Has anyone ever seen this issue before? Help! I'm totally stumped! I'm looking for someone who has seen issues specifically linked to XP SP2. PT Claims there is no real reason for this, other than our DB size. Our DB works fine on all the other machines!

Thanks in advance!

 

[mattjurado]

I've googled the heck out of this, I'm not finding anything.

Before I make a suggestion on caching/file locking, what kind of network cards are in these boxes. Assuming your hub/switch is capable, have you tried forcing the link & speed to full duplex, 100mbps on these cards?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[tylan]

Stupid Me!

I can't believe this! After 5 or 6 calls to PT support, I decided that they were worthless. The only common denominator was SP2, so I decided to blow out one of the machines. Worked like a charm.

I was finishing up the first machine and realized it needed the AntiVirus re-installed. Then it hit me. AntiVirus. I looked to the other machine and it had "CA E-Trust" on it. The machine that I just formatted and reloaded w/ XP SP1a also had E-Trust on it originally. Everything else in the office has Symantec AntiVirus Corporate Edition. I disabled the CA, and PT worked great!

I called PT Support to tell them that they should have suggested that to me first! In all my years of tech work, the company who makes the software ALWAYS blames the AV by default! I can't believe that I missed this one!

All I can figure is that CA hangs up when it hits the *.lck files while SAVCE goes right past them. Problem Solved. Thanks for your efforts!

 

[mattjurado]

Glad you figured it out. Your symptoms sounded like a file caching or locking problem, but I've not seen this problem with SP2, nor did anyone else it seemed (after much googling). That's why I stayed away from going down that road, I really felt it was a communications issue, but as it turns out, just antivirus.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.