Terminal server error

pts.
Tags:
Microsoft Windows
Hello - I have a terminal server that I just recently upgraded the office version from 2000 to 2003, it mostly works with the exception of Access - every time I go to launch an access database I get the following error: Cannot find the file 'd:folderfile.mdb' (or one of its cmoponents). Make sure the path and filename are correct and that all required libraries are available. When I installed it I did it through addremove programs as recommended. When customers click on the Microsoft access to launch it nothing happens. I'm just a bit stumped and could use some advice, any chance somebody out there knows how to fix this? thanks! Lirria

Answer Wiki

Thanks. We'll let you know when a new response is added.

Sounds like it’s looking for your database files somewhere other than where they actually reside or the installation didn’t complete locally.

1. Double check that the file paths are correct.

2. Did you deploy an msi file from the server to be published to computers/users and then go to the workstation and install through add/remove programs? Where are the install files coming from a CD or a server? These areas could be issues.

3. What version of Office 2003 did you install? I believe that Small Business (and some other versions) doesn?t come with Access. So if a 2000 version with Access was uninstalled before the 2003 installation, you would be missing Access files all together.

Don’t know if this helps. Just my two cents.

Discuss This Question: 15  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Lirria
    OK - Thanks for the help - let me say that I'm new to the whole terminal server thing so I may have done something wrong. 1 - if you mean the file paths to the data, yes they are actually there - if I run it from my local workstation the files open with out issue. 2 - On the server I went to add remove programs and installed via the add new programs. I did a complete install. (Never worked with terminal server before so don't know if I did anything wrong here). Word, PowerPoint and Excel work fine (well word gets a macro security when launching, related to CambridgeSoft Corporation (CFWord.dot) certificate has expired)Access always goes throught the configuration phase when opening (that just seems odd)none of the other applications do. 3. Office Professional 2003 (full version with powerpoint, access etc) I appreciate the advice and help! Lirria
    0 pointsBadges:
    report
  • Swiftd
    I'm just going to throw out a suggestion, although I will admit that I don't use straight Terminal Services for serving out applications to users. And at that, my information is a bit dated, since we are running MetaFrame 1.5. I typically would use Citrix for that. With Citrix, whenever you install applications like Office, you commonly have to run a application compatibiity script in order for it to function in a multiuser environment like Terminal Services and Metaframe. Here's a link to a page that talks about this: http://citrixfaq.msterminalservices.org/faqs2.cfm?id=49&category=2%2C3&sortby=date Also, here's a MS article on installing Office 2003 on Terminal Server: http://office.microsoft.com/en-us/assistance/HA011402071033.aspx If nothing else works, you might want to uninstall the upgraded version and start again. I'd make a backup of the server first, or even try restoring an image o the server prior to the upgrade and then removing/reinstalling a fresh office. Hope this points you in the right direction.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, This may be a little late in coming, but try this if you have not already resolved your problem. Open Terminal Services Configuration (Start => Programs => Admin Tools)and check your security settings. Set security to Relaxed Security. Many times using the full security setting with TS will cause problems with applications and file access. This is especially true with older application versions. If all else has failed this certainly can't hurt anything. Good luck!
    0 pointsBadges:
    report
  • Lirria
    Hi all - When I go into terminal server configuration I don't see a security setting. All that is in there is Terminal Server mode, Delete Temporary Folders on exit, use temporary folders per session, internet connector licensing, active desktop and permission capatibility - what am I missing? Lirria
    0 pointsBadges:
    report
  • Lirria
    Hey all - I just finished reinstalling Office (uninstalled, rebooted, when to add remove programs and installed from there, added sp2 the same way - followed the link posted above) and lucky me - I get the same problem. I am having the customer try to launch access and see if she can (she couldn't before) I wish I knew what I was missing here - any other advice? Lirria
    0 pointsBadges:
    report
  • Lirria
    I just heard back from the customer - same thing - won't launch access - they get the splash screen then nothing. They are on the end of a really slow link but I wouldn't think that would do it. They are VPN'd in (using checkpoint secure client, but are on a different domain). This all worked before I upgraded to 2003 (yes I know I may have to downgrade it back to 2000). When I remote into the server and log on as myself it works fine (I get the can't find file error, but can launch access and open files). The customer is currently a member of the power users group on the server - I don't think that would be the problem. thanks! Lirria
    0 pointsBadges:
    report
  • Lirria
    Here's some more information - In an effort to figure out what is going on - I have found that if the customer is a member of the local Administrators group, access will run - but not if they are a member of anything lower (including Power User). We really don't want to give them admin rights. I have noticed that there are Event 577 errors: Event Type: Failure Audit Event Source: Security Event Category: Privilege Use Event ID: 577 Date: 3/21/2006 Time: 8:45:33 AM User: domainnameusername Computer: servername Description: Privileged Service Called: Server: Security Service: - Primary User Name: username Primary Domain: Domainname Primary Logon ID: (0x0,0xFEEEC1A) Client User Name: - Client Domain: - Client Logon ID: - Privileges: SeIncreaseBasePriorityPrivilege For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I'm guessing this is what is causing the problem but don't know how to fix it. I checked the group policy and it's all set up correctly. Any other thoughts? Lirria
    0 pointsBadges:
    report
  • Swiftd
    Use the tools filemon and regmon from Systernals (www.systernals.com) to monitor what the app is trying to access. Again, however, it sounds like you did not run the App compatbility script for Office. They commonly create dirs, reg folders, and set permissions so that a regular user can run the apps. This is normally required for the first time it is run. Swiftd
    0 pointsBadges:
    report
  • Lirria
    Office 2003 does not have the compatability script - it's suppose to just work. I have run Regmon and see red flags -I'll try again and see what I come up with in the am. thanks! Lirria
    0 pointsBadges:
    report
  • Petroleumman
    Hello, All 577 errors relate to security privelages which indicate that your problem most likely lies somewhere with permissions. Have you checked the permissions on the Access folder, it's database and residing drives? You'll want to compare NTFS and if applicable, the share permissions and look for clues. Also check the advanced permissions and effective permissions for each object and compare with those of a known working account. What makes permissions a likely cause is the fact that you stated the client can run Access with elevated permissions of an Administrator. Good luck!
    0 pointsBadges:
    report
  • Lirria
    First off - I want to say thanks for all the help and apologize if I've been short (just stressing over this - been struggling with it over a month now). I have run filemon and regmon - it looks like the problem lies in the access denied on the 'HKLMsoftwarepoliciesmicrosoftwindowsinstaller' key, I also see an error referencing Terminal Server application compatibility DLL (Tsappcmp.dll) which I don't have - that may be the file you all have mentioned but from all the reading I've done it wasn't mentioned (so again my apologies if this is the problem). So to fix this - (remember I'm a bit of a newbie here so please be kind) I can't change permissions on the registry key so just what do I need to do? Is there a way to not have it run the installer *every* time access is launched? The permissions on the msaccess.exe are exactly the same as the ones on winword.exe. I know I have 2 separate issues here the inability to run access and the inability to double click the file (ok they may be related - I just don't know) but I'm more interested in fixing the former, then I can work on the later. I agree that it has something to do with security - I'm just not sure where. I know that if I run from my normal desktop everything works fine, but it gets weird when I remote into the terminal server - so I suspect it's something there. If it helps, I started here 2 months ago after their Admin quit suddenly about 8 months prior to me starting - many of the issues I have been seeing are fall out from no maintenance or monitoring for over 8 months and trust me there have been a lot. I know that I have a ton to learn and have been reading and trying things out. So again I really appreciate all of the assistance from you folks. (ok enough babbling...) thanks! Lirria
    0 pointsBadges:
    report
  • Petroleumman
    Hello, The file Tsappcmp.dll is included in the Windows Server 2003 SP-1 files. Try re-installing the service pack and see if that resolves your problem...considering your running on Windows Server 2003 server. You may have a corrupt install of Terminal Server. You could also try copying the file from another 'working' Terminal server and place it in the C:WindowsSystem32 folder. Good Luck!
    0 pointsBadges:
    report
  • Lirria
    OK - I got the dll replaced and now that error is gone - but the stupid access installer is still running all the time - anyway to make it run the installer once and not everytime you run msaccess.exe? Lirria
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Now that you have the Tsappcmp.dll file replaced and cleared those errors,uninstall Access from the server, then reinstall it according to TS application install procedure. The theory here is that with the proper .dll file loaded your application will install according to TS specs. Good Luck!
    0 pointsBadges:
    report
  • Lirria
    *sigh* unfortunately the same thing is still happening - for some reason the installer has to launch to start up access - it doesn't make any sense, none of the other applications are having this problem. (I uninstalled and reinstalled access) Still having the pathing problem too, just wish I could figure out what I did wrong. Lirria
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following