Error opening Outlook 2003 under Terminal Server user session

I've just recieved a brand new server from HP with Windows Server 2003 R2 loaded on it. This server is to be used as a terminal server for our employees working outside our office. However, I've run into a problem once MS Office was loaded on this machine. Whenever a user opens up Outlook, an error message pops up saying "Failed to start the Expression Service. The Espression Service may not be installed. This problem may be resolved by using Detect and Repair on the help menu, or by re-running Office 2003 setup." Obviously the first thing I tried was doing exactly that, which didn't work. I do know that if a user has local administrative access to that computer, the error message does not pop up. Any thoughts on getting rid of this message for ordinary users would be greatly appriciated.

What's somewhat strange is that our existing terminal server has the same software loadout, except it didn't come with the HP software, and it's Windows 2003 w/SP2 instead of Windows 2003 R2.
tomethAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PlaceboC6Commented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tomethAuthor Commented:
I've tried that. MDAC 2.8 SP1 won't install on windows 2003 w/SP2 stating that it's not a supported operating system.
0
tomethAuthor Commented:
I'm almost positive that this has something to do with the fact that under a regular user account MS Access won't start up at all. And when run under an administrative account, it fires up the windows installer every time...
0
tomethAuthor Commented:
The problem was caused by some software installed for our HR department called Staff Files. It was corrected by running these commands.

1)       regsvr32 c:\windows\system32\VBAJET32.DLL

2)       regsvr32 c:\windows\system32\MSJTES40.DLL

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.