Microsoft Access Generating Tmp File

We are accessing a database using Microsoft Access 2003 on a Terminal Server. On the Terminal Server when we generate a report it takes a long time to get the results yet the very same report on a workstation is fast. With Filemon (Systermals) running on the terminal server we see that there are hundreds of writes being done to the local user profile creating a JETE917.TMP file. This turns out to be a zero byte file. This file is not created when the same process is run from a workstation. Looking for clues to why this is happening on the terminal and not on the workstations. It is severly impacting performance on the terminal server. The terminal server is also running Access 2003 on a Windows 2003 Server environment.
FortrakAsked:
Who is Participating?
 
FortrakAuthor Commented:
Created a Microsoft support case on this and after a few days we found the solution to the problem in a hot fix released for the Jet 4.0 database engine. Applying the hot fix from KB954193 solved the problem and the Jet no longer makes thousands of writes to the temp file. Performance improved significantly.
0
 
Jeffrey CoachmanMIS LiasonCommented:
Fortrak,

You have left out a great deal of info on this setup.
For example:
"it takes a long time to get the results yet the very same report on a workstation is fast. "
If the DB is local on the workstation, then it will always be faster the TS.
How fast is your network?
Is this the exact same database file(s) used in both tests?
Is the database "Split"? If so, where is the back end and where is the front end.

Thanks

JeffCoachman
0
 
FortrakAuthor Commented:
Gigabit network. FE is on the workstation and local on the terminal server for the users there, BE is on the network. Exact same database in both tests. The configuration is identical on the workstations as on the terminal server. The main difference on the terminal server is that it is writing to a Jet temp file in the users profile hundreds of times during the query while on the workstation it is not. I suspect it has something to do with the way a terminal server manages Access in a multiuser environment like terminal services?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Jeffrey CoachmanMIS LiasonCommented:
Your Spec and configuration seem OK.

I am not sure about the temp file though, we run Citrix where I work.

But today many of the Experts will be back from the extended US weekend.

So let's wait for some more input...

;-)

Jeff
0
 
FortrakAuthor Commented:
I ran Filemon on the terminal server again and took a screen shot (attached). You can see here that Access is writing to the Jet temp file in the local user profile thousands of times. Needless to say this is severely impacting performance. This does not happen at all on a workstation as mentioned earlier.
JetTmp.jpg
0
 
Jeffrey CoachmanMIS LiasonCommented:
Congratulation!
;-)

Jeff
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.