I have an MTE install with iSymphony. Every time I modify an extension in a tenant that is set up to use iSymphony, it mangles the iSymphony config file, crashing the iSymphony server. It will not start again until the XML error is corrected (manually).
Any suggestions?
Christopher L. Elkin
Sr. Systems Engineer
EOS, Inc.
217-241-6000
Submitted by eeman on Thu, 02/17/2011
Permalink
DO NOT use the thirdlane setting to alter the XML files. Thirdlane used an old version of their XML schema fromway back in the days of build 1104. You should be running build 2185. The reason isymphony crashes is that any outside attempt to modify extensions.xml while running will break the open file pointer its using. A better way to add/modify the entry is by using the telnet port 50001 and executing the commands that way. This is automated via event hooks and shell commands.
Another option is to just use isymphony's admin interface and give your tenant the tenant level login and have them manage it. Its always possible that they may not want every extension added to iSymphony.