Windows NT MS Access showing 99% CPU for TS users

  • Thread starter Thread starter Iain
  • Start date Start date
I

Iain

We have an application on the TS that uses access 2000 runtime.
the server is windows 2003 server standard.

A process access.exe keeps running at large CPU percentages causing the TS
to lock up.

The user can log off and the process keeps running.

I can't kill the process and have to restart the server to stop it.

Does any one know of problems running access runtime through TS?
 
Iain wrote:
> We have an application on the TS that uses access 2000 runtime.
> the server is windows 2003 server standard.
>
> A process access.exe keeps running at large CPU percentages causing the TS
> to lock up.
>
> The user can log off and the process keeps running.
>
> I can't kill the process and have to restart the server to stop it.
>
> Does any one know of problems running access runtime through TS?
>

please read previous posts - DON'T DO IT!!
ACCESS STINKS ON TERMINAL SERVER
 
I have looked at the previus logs. There are a couple of references to what
you say but with no detail.
We have no option the app uses access runtime.

Can the app be throttled to use less CPU time?
What is casuing the application to do this?

"ms support newsgroup" wrote:

> Iain wrote:
> > We have an application on the TS that uses access 2000 runtime.
> > the server is windows 2003 server standard.
> >
> > A process access.exe keeps running at large CPU percentages causing the TS
> > to lock up.
> >
> > The user can log off and the process keeps running.
> >
> > I can't kill the process and have to restart the server to stop it.
> >
> > Does any one know of problems running access runtime through TS?
> >
>
> please read previous posts - DON'T DO IT!!
> ACCESS STINKS ON TERMINAL SERVER
>
>
>
>
 
Iain wrote:
> I have looked at the previus logs. There are a couple of references to what
> you say but with no detail.
> We have no option the app uses access runtime.
>
> Can the app be throttled to use less CPU time?
> What is casuing the application to do this?
>
> "ms support newsgroup" wrote:
>
>> Iain wrote:
>>> We have an application on the TS that uses access 2000 runtime.
>>> the server is windows 2003 server standard.
>>>
>>> A process access.exe keeps running at large CPU percentages causing the TS
>>> to lock up.
>>>
>>> The user can log off and the process keeps running.
>>>
>>> I can't kill the process and have to restart the server to stop it.
>>>
>>> Does any one know of problems running access runtime through TS?
>>>
>> please read previous posts - DON'T DO IT!!
>> ACCESS STINKS ON TERMINAL SERVER
>>
>>
>>
>>
simple, access isn't designed for terminal server. Access is a poor
example of a database! At best it makes a nice front-end - that is as
far as it can go.

I'd suggest putting access on a winXP machine and have ONE user login to
it via RDP. That's usually the best way access works - on a dedicated
workstation. It's best if you look at getting away from access and use
a web-based setup via asp.net. On term server it's best to avoid using
access - it's not worth the trouble. There will be a lot of trouble!


Access is very prone to table corruption and has lots of built-in
limitations. Access also creates a lot of unnecessary LAN traffic. Who
designed your access application? Was it a programmer or some office
person who followed the access wizards. The wizards make things that
look pretty but they work very poorly. the code the wizards create is
just aweful. It's very bloated.

Even if it was a programmer - was it really a programmer or some person
who sees access as a hobby. I've seen lots of people who know a bit of
vba and consider themselves programmers! These people try to use access
for lots of things. Then they wonder why access gets no respect in the
IT world! these people are NOT programmers!!! At best they do this as
a hobby - but they are NOT programmers. That's why most access
applications stink!!
 
Hi, I have some questions for you:

You say process access.exe runs with large cpu percentage. Is
this correct? I ask because Microsoft Access is msaccess.exe

What error do you receive when attempting to kill the process?

What happens if you use kill.exe -f to terminate the process? Are
you able to terminate it then?

What are the specs of this server? RAM quantity, CPU type/speed/quantity,
Hard Drive type/size/speed & quantity, RAID configuration

Do you have any Antivirus or other security related software running
on the server?

How many concurrent users are on the server at any one time?

Where are the access backend data files located?

Where is the access frontend located? Are all users sharing the same
file, or do they have individual copies?

Have you compacted and repaired the backend and frontend files?

Does this problem occur only with certain users or all users?

Has the problem *always* happened or did it just start recently?

What is the user doing when the problem occurs?

Have you applied any relevant office 2000/Access/Jet service packs
and/or hotfixes?

Have you contacted the vendor or programmer who wrote this program
and asked them to investigate why it is using a large amount of CPU?

Have you asked the vendor or programmer if it is possible to update
to a newer version of Access, for example, version 2002 or 2003?

When the problem occurs, what numbers are you seeing in task manager
for commit charge total, physical memory, available memory, system cache?
In performance monitor, what numbers for Average disk queue length?

Access applications can run well under TS if done properly.

-TP

Iain wrote:
> We have an application on the TS that uses access 2000 runtime.
> the server is windows 2003 server standard.
>
> A process access.exe keeps running at large CPU percentages causing
> the TS to lock up.
>
> The user can log off and the process keeps running.
>
> I can't kill the process and have to restart the server to stop it.
>
> Does any one know of problems running access runtime through TS?
 
Back
Top