new citrix server, word error

Lynne Desrochers · December 04, 2013, 12:17:49 PM

I'm trying to get a new citrix server (2008 R2) into production, but I keep getting an error when I test out formletters. I am able to add the formletter, but when I go to Add Ins / Applied / Save and Exit, i get the following error: Microsoft Visual Basic / Run-time error '429', ActiveX component can't create object. then I click end a few times finally I am able to get out then I get to the Save / Don't Save and if I click Save, it wants to save the RTF and Don't Save gives me another error.
I feel like this is just a simple setting somewhere, but I don't know where.
Has anyone seen this before? Thank you.

Jeff Zylstra · December 04, 2013, 02:06:23 PM

Have you tried running TAMCLient.exe /RR? That should re-register all of the files and hopefully, that is your problem.

Lynne Desrochers · December 04, 2013, 02:16:40 PM

Yes, yes I have... i was hoping as well.

Jeff Zylstra · December 04, 2013, 02:57:16 PM

Perhaps renaming the \Wintam folder and then reinstalling might be the way to go, since it's just local program files and not TAM data files. Not sure if there is a special software switch like "/rr" that you must use for Terminal server or not.

Alice Mooney · December 04, 2013, 03:19:44 PM

This may be a silly question, and may no longer be necessary, but did you put the server into install mode before installing MS Office? Then put back to execute mode before anyone to use it?
Our techs say to always do that b/c some times the built-in install/execute is finicky some times.

GeorgeW · December 04, 2013, 03:48:49 PM

I found some old notes from when we were on citrix and were getting the error. Don't know if all citrix is setup like this, but our users had a J:\Windows directory inside citrix. That is where our wintam.ini and wtsetup.ini files were for the user. When they got the exact error you state above, we would delete or rename those two files and then run "tamini.exe" from the wintam directory which recreates the wintam.ini file. They would lose their personal settings in TAM since we had removed the wtsetup.ini file but it always fixed this error for us. Also, in the J:\Windows directory we had a copy of the asword.dot file

Again, this was from a couple of years ago when we were still on TAM and also still used Citrix so might not be valid any longer.

Lynne Desrochers · December 05, 2013, 05:05:21 PM

Thank you all! I wish I had seen George's note before I took the extreme measures of uninstalling and reinstalling office. It is now working properly. So Alice, you may have been right, but I didn't do the initial MS Office install.
Jeff Z another good suggestion that I tried, however you always make me feel like my troubleshooting skills aren't totally out of whack.
Thanks.

Jeff Zylstra · December 06, 2013, 10:26:41 AM

Quote from: Lynne Desrochers on December 05, 2013, 05:05:21 PM
Thank you all! I wish I had seen George's note before I took the extreme measures of uninstalling and reinstalling office. It is now working properly. So Alice, you may have been right, but I didn't do the initial MS Office install.
Jeff Z another good suggestion that I tried, however you always make me feel like my troubleshooting skills aren't totally out of whack.
Thanks.

It's not hard for me to make you feel good about your troubleshooting skills since mine are in the basement!

There's usually more than one way to skin the cat (even though I like cats - most of the time

) Glad you got it fixed!