Access 97 on Tserver 2003

[Richard]

We've just had to move over an old Access 97 application from Win2000
TServer to Win2003 TServer.

After the usual fiddling around to get things working (permissions etc) like
often with TS apps, there's one problem left. The server is very slow. The
access.exe process that every TSuser uses is at the top of the CPU list all
the time, one after the other. CPU is 100% loaded. We've tried several
things without results.

Even when we use a simple test Access MDB on the Tserver, the CPU goes to
100%.

I'm beginning to think Access 97 doesn't like Win2003, or vice versa. Could
this be the case ?

 

[Douglas J Steele]

Take a look at http://support.microsoft.com/?id=160819

While it looks as though Access is hogging the CPU, it should not be
impacting the performance of any other applications.

 

[Richard]

Well it certainly affects the performance of the server, or at least other
processes on the server.

 

[never_be_read]

Richard,

As far as I remember, Access 97 always show up as running 100%
even on NT4. I think it may have something to do with the old way
Windows application do things - non-pre-emptive??

I am not a TS guy. Can't help you. Sorry. Duncan

 

[Tony Toews]

I'm beginning to think Access 97 doesn't like Win2003, or vice versa. Could
this be the case ?

Correct. A client reported the exact same problem with A97 on a TS
system. I don't recall though if the OS was Win 2000 Server or Win
2003 Server.

Once they installed Access 2000 all was fine.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Rick Brandt]

Correct. A client reported the exact same problem with A97 on a TS
system. I don't recall though if the OS was Win 2000 Server or Win
2003 Server.

Once they installed Access 2000 all was fine.

Tony

Our company's experience was the same. The high cpu utilization that was
"harmless" in NT 4.0 brought the Server 2003 box to its knees. Going to Access
2000 fixed it.