Home Forums General XMetaL Discussion Need to find out which parts of the "machine.config" file are related to XMetaL Reply To: Need to find out which parts of the "machine.config" file are related to XMetaL

Bill Vlach

Reply to: Need to find out which parts of the "machine.config" file are related to XMetaL

Hi Derek:

Thanks for the reply. We're baffled, too, but seems odd that, with only XMetaL installed on this failing installation, it opens fine. But once the SDL plug in (Authoring Bridge) is installed, we get the following error messages that we have to click through before the XMetaL window launches:

1. TrisoftApplication.constructor: Following error occured:
    (there is no “following” information besides the successive error pop-up windows)
2. Trisoft Application.initialize: Following error occured: 'this.trisoftDocuments' is null or not an object
    (the XMetaL window opens after clicking OK on pop-up error #2 but then get the following pop-ups)
3. Error_FollowingErrorOccurred_Tpl
    (there is no “following” info, just another instance of this same pop-up error message.
4. Error_FollowingErrorOccurred_Tpl

After clicking OK to the second “Tpl” pop-up error, the window is opened but the SDL Trisfot menu plug-in that should appear instead says “InfoShareMenu_Text” and all menu items in that menu also include the “_Text” suffix and none perform any actions.

Then, when we close XMetaL, we get the following error:
5. TrisoftApplication.terminate: Following error occured: 'this.trisoftDocuments' is null or not an object

Click OK and the XMetaL window closes.

We have been told that SDL is dependent on .NET Framework 2.0 so we have focused mostly there. And the error messages in a log file we were just able to produce from the failing machine seems to confirm that the error messages point to .NET 2.0 files. But initial feedback from some other folks has us feeling less than confident that this log file holds the key.

And, to reiterate from my initial post on this thread, on a known good system (mine), I can change the name of the machine.config file so that it does not exist and it causes the exact same series of error message pop-ups and failed menu item that we get on the failing installation. So we were hoping that either the machine.config file or the machine.config.default file (which doesn't get run, either, if the first does not exist) might point us to the cookie, file, setting, or other attribute that is corrupt or missing/incorrect on the failing instance. Any ideas?

(Not sure what is safe/unsafe to add as an attachment but will find out and provide it or specific info if you think it might be helpful.)

Thanks for your help!

Reply

Products
Downloads
Support