Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Flexibility on Terminal Server

Status
Not open for further replies.

wcompute

Programmer
Nov 11, 2005
4
US

I am trying to use Flexibility on terminal server
Every thing works ok other than I get the following warning every time the first screen with flex loads.




Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 5/25/2006
Time: 7:39:44 AM
User: ACTECH-LENZE\ewillett
Computer: UXBS-TERM
Description:
Detection of product '{00010409-78E1-11D2-B60F-006097C998E7}',
feature 'OfficeUserData', component '{C9AF9050-C8BE-11D1-9C67-0000F81F1B38}' failed.
The resource 'HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Common\UserData' does not exist.

Flex runs ok, but I do not want the user to see the
warning dialog box the first time they load Flex's VBA
screen.


My question is what Office components are required for Macola's VBA implementation to work.

The terminal server that I am using has some strict group policy settings and I need to know if this above registry tag is required????

Thanks in advance for any help on this

--Ernie

 
Hello,
No Office components are required for Macola's VBA to work. The only references that are required for a Flexibility project to work are the following:

Visual Basic for Applications
vbaConnect
OLE Automation
vbaConnectEx

You may need office components if you have built in office integration through flexibility, otherwise it is not needed.

If you are still receiving this error after having removed all office components or if your application requires office integration and you have retained the problem office components, then I would suggest following Microsoft's special instructions on how to install Office 2000 on a Terminal Server. There is a problem with the Microsoft installer that causes all kinds of problems on a Terminal Server.

Scott Travis
 
The problem here may be that you need to adjust the group policies under TS to allow the proper access to the ODBC reg settings and more importantly insure that EVERYONE has COMPLETE access to the C:\TEMP folder. This is required on TS and is often not a problem since most admins dont lock the TS down frequently enough. When admins start locking them down they often overlook application specific setting requirements.



Andy Baldwin

"Testing is the most overlooked programming language on the books!
 

Thanks for the responses.
My application does not require office integration.

I have just realized that the application log is getting this event for some users even when a flex screen is not open. But the event definitely happens every time a flex screen first opens.

Everyone seems to have access to c:\temp

Again, there are no references to Office.
All I have referenced are the following:

Visual Basic For Applications
vbaConnect
vbaConnectEx
Microsoft Activex Data Objects 2.8 Library

The previous administrator, did indeed lock down the system fairly tightly, and as administrator the error does not happen. Thus it is some kind of permission setting that allows the key to be created. But I still am not sure why the office key is required at all.

Thanks for the responses. I am still trying to figure out how I can stop this from happening





 
I would go back to the problem with the Office 2000 installation process on Terminal Server. Have you ever noticed how Office 2000 is constantly asking for the Office 2000 CD when logging in to a system as a new user that already has the software installed? This is ultimately a problem with the Microsoft Installation Services 1.0 that is used for the Office 2000 install. It is constantly trying to check the validity of shared components against against the original file in the CAB file associated with the installation. This is what created this nightmare. There are instructions from Microsoft on how to install this product properly for Terminal Services/Citrix but it is a manual process. You many find that you also have to unlock some of the users to make this happen.

To shortcut this, you may find that if you elevate the privelages of your users to Administrator, have them login and open Word and Macola Progression, then logout, restore their original rights, and then have them log back in, then you may allow Office to do what it needs to do so this error no longer occurs.

Scott Travis
 
What version of Office on the TS and what OS on the TS server?

FYI, to properly install Office on a TS you need to look for a file in microsoft site called TERMSRVR.MST

This setup will allow you to properly install office on a ts. I know you dont think this is part of the problem, but here is why Scott and I keep coming back to the office and security setup on TS.

1. Flex by definition is Macola's implementation of VBA inside macola. VBA is the macro language originally installed and utilized in the macro language of the office products. Any other application that utilizes VBA requires some of the objects, registry settings, and security settings that in your case may have already been installed. If they were not installed properly in the first place then Macola's flex will have inherited problems.

2. When you said that everyone seems to have rights to the temp folder did they have FULL access to it or just write. Please insure that they have FULL priviledges.

3. Run Regedit on the terminal server as an admin and temporarily change the privilegs to the key in question to full for all users. If that works I would start with a reinstall of Office using the file you download above. Then check it again.

This error tends to point to an improper installation of Office on Terminal services and since flex (VBA) is a subset of that product then this may be the issue.



Andy Baldwin

"Testing is the most overlooked programming language on the books!
 
Thanks for all your help guys.

It was an improper install of Office.

I had to wait until a weekend to have it reinstalled, that's why it took so long to report on the solution.
 
Your welcome.


Andy Baldwin

"Testing is the most overlooked programming language on the books!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top