MDS User Defined Support ERROR

 

Does this mean AVEVA supplied User Defined Supports which can readily be activated in paragon but cannot readily be used in design??

you should add mds DBs to your current MDB

 

Thanks for replies..
I manually add the tags in the [LEFT][COLOR=#333333]SupportConfiguration.xml file, and it worked.. I guess I need to do this again and again for the other user defined supports..[/COLOR][/LEFT]

[QUOTE=ce_amcastillo_82;109189]Thanks for replies..
I manually add the tags in the [LEFT][COLOR=#333333]SupportConfiguration.xml file, and it worked.. I guess I need to do this again and again for the other user defined supports..[/COLOR][/LEFT]

I have the same problem . [COLOR=#333333]I manually add the tags in the [/COLOR][COLOR=#417394]SupportConfiguration[/COLOR][COLOR=#333333][FONT=Verdana].xml file BUT not worked.
any other thing I should do?

[/FONT][/COLOR]

add through DimensionControlDesigner.exe from installation folder.

add through DimensionControlDesigner.exe from installation folder.

It works . tnq for your help.

Is there any way to change user defined support names in catalouge and set my pre created cata ?

Hi Everyone

Our projects are located in a server and, the projects, reference a master project with our MDS customization and config.

Is there a way that the SupportConfiguration.xml file would be located (and be read from) the project path?  we are having issues when new custom ancillarys are created because the same error (of the first post) appear in every support user and to modify the xml file in every user, every time a new custom support appear seems to me unefficient.


what's your experience? how do you solve this issue?