Search | Active Topics



Error using Access 2007 on Terminal server Options
PaulW
Posted: Friday, September 04, 2009 8:44:24 AM
Rank: New Poster
Groups: Member

Joined: 9/4/2009
Posts: 4
Location: United States
Folks,

Here is some background: Windows Server 2003 Standard Edition with SP-2, Office 2007 Professional with SP-2.
Our program is using your Access 2002 Wise installation scripts, Version 2.06, for our initial installation.

Problem: Periodically a client will get the following message if they Try to open their Database (Access 2002 format) using Access 2007:
"Automatic configuration of the current version of Microsoft Office Access has failed. Your database might not function correctly. This can occur if you do not have the necessary permissions to install Microsoft Office Access on this computer."

The only fix to this solution is to have the server administrator login to the Terminal Server and Open Access 2007, which, at that point gets a message Microsoft Access is reconfiguring/reinstalling.

Question: As mentioned earlier we are at Wise Installation Scripts for Access runtime version 2.06. I see there are 2 minor updates since then, would upgrading fix the issue next time it happens? Is this maybe caused by the Access Runtime environment not closing out correctly?

Thanks,
Chip
ColeS
Posted: Friday, September 04, 2009 9:25:34 AM

Rank: SageKey Staff
Groups: Administration , Member

Joined: 3/27/2009
Posts: 1,376
Location: Canada
Hi Paul,

Are you not distributing the Access 2002 runtime for your application to be run in? I'm not sure why you would be opening your 2002 program in Access 2007 to begin with.
If you have installed the runtime and are using a SageKey built shortcut then it should be launching in the runtime regardless of what version of Access is present on the machine.

I don't think the latest versions of the Wise scripts made any changes in that area, but as always it is best to be using the latest product for support and troubleshooting.
PaulW
Posted: Friday, September 04, 2009 10:35:09 AM
Rank: New Poster
Groups: Member

Joined: 9/4/2009
Posts: 4
Location: United States
Our application is a mixture of Access 2002 compiled program files and VB exe files. Our Main menuing application will start the appropriate module application using StartAccess.exe (your supplied file), which we renamed as RunAccess.exe, if it is an Access compiled program file. We have used this configuration for years with great success. The environment is a terminal server, which means our application, Client/Server, is installed on a single box. The folks login to the terminal server to run our application and if they want open Access 2007 to view/edit there Access 2002 databases.
ColeS
Posted: Friday, September 04, 2009 1:15:21 PM

Rank: SageKey Staff
Groups: Administration , Member

Joined: 3/27/2009
Posts: 1,376
Location: Canada

Do you know if you are using the latest service pack for your Access 2002 runtime? If all is running properly you should not be seeing a reconfiguration at all. We've seen Access 2002 runtimes reconfigure when not updated to SP3.
In the Gathering Required Files section of your Wise script help file should have links to the service pack information for you.

ColeS
Posted: Tuesday, September 08, 2009 9:20:41 AM

Rank: SageKey Staff
Groups: Administration , Member

Joined: 3/27/2009
Posts: 1,376
Location: Canada

Do you know if the application was installed as an administrator? If not they may not have all the required permissions for StartAccess to fully protect the program. The best way to install for Terminal Server is to install as administrator through the Add/Remove Programs tool.
PaulW
Posted: Tuesday, September 08, 2009 11:37:26 AM
Rank: New Poster
Groups: Member

Joined: 9/4/2009
Posts: 4
Location: United States
Yes, application was installed as administrator.
PaulW
Posted: Thursday, September 10, 2009 4:05:08 AM
Rank: New Poster
Groups: Member

Joined: 9/4/2009
Posts: 4
Location: United States
Folks, any idea? Do you need additional information?
ColeS
Posted: Thursday, September 10, 2009 9:28:35 AM

Rank: SageKey Staff
Groups: Administration , Member

Joined: 3/27/2009
Posts: 1,376
Location: Canada

Sorry for the delay in replying but I was trying to reproduce the error, though without success. Is this only happening on one machine or do you have multiple installs running into this issue?
Do you have any further information on what causes the error? Does it come up after the user opens Access 2007 after using the 2002 runtime?
Once you reconfigure as admin does it clear up or keep happening?

Sorry for all the questions, but we need to nail down at what point it starts to need to configure.

Users browsing this topic
Guest


Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS : RSS

Forum theme created by Colin Olson, SageKey Software.
Powered by Yet Another Forum.net version 1.9.1.8 (NET v4.0) - 3/29/2008
Copyright © 2003-2008 Yet Another Forum.net. All rights reserved.
This page was generated in 0.047 seconds.