Skip to main content
5-Regular Member
May 24, 2021
Question

Config.sup file paths

  • May 24, 2021
  • 5 replies
  • 6638 views
I am using Creo Parametric 4.0 M040

Issue revolves around config.sup paths to formats and start parts. Same config.sup file is used on 2 machine. On machine #1, paths work correctly. On machine # 2 belonging to a new user with new install, paths appear to work for some items (ex. start parts) but not not others (ex. formats) It is the exact same config.sup file. Ideas or suggestions appreciated.

    5 replies

    kdirth
    21-Topaz I
    21-Topaz I
    May 24, 2021

    A couple of things to look at that I have seen in the past:

    • Make sure mapped drives are identical on both computers
    • Ensure Target in the program shortcut is correct and any files targeted are there especially the users config.pro file.
      • Ensure the users config.pro is not in conflict with the config.sup

    If either of these are incorrect Creo will not be able to find the path to the correct files.

    kdirth_0-1621883556709.png

     

     

    There is always more to learn.
    dthornton5-Regular MemberAuthor
    5-Regular Member
    May 25, 2021

    Checked those items and all were good.

     

    I totally agree... there's ALWAYS something more to learn with both Creo and Windchill ðŸ˜€

    23-Emerald III
    May 24, 2021

    Do you have multiple lines of the same config option in the config.sup file?

    I am assuming you copied the config.sup file from machine 1 to machine 2.

     

    Those settings are not normally in a config.sup but in the system config.pro.

     

    Paste the config.sup file so we can look at it.

     

    dthornton5-Regular MemberAuthor
    5-Regular Member
    May 24, 2021

    Yes... copied the config file from machine 1 to machine 2

    Also put it in the config.sup file since my entire group uses the same formats and kept people from inadvertently editing them

    dthornton5-Regular MemberAuthor
    5-Regular Member
    May 24, 2021

    Config file below since I'm having issues getting the file itself to upload

     

     

    pro_symbol_dir wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Symbols

    rem pro_dtl_setup_dir wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Setup_Files/drw_setup.dtl

    pro_format_dir wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Format

    pro_table_dir wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Tables

    drawing_setup_file C:\PTC\Creo 4.0\M040\Common Files\text\new_drw_setup.dtl

    pro_font_dir c:\windows\fonts

    trail_dir C:\PTC\Creo 4.0\drafting\Trail Files
    pro_plot_config_dir C:\PTC\Creo 4.0\drafting\ProPlot Files
    pen_table_file C:\PTC\Creo 4.0\drafting\Pen Tables\table2.pnt.2
    system_colors_file C:\PTC\Creo 4.0\drafting\System Colors\syscol.scl

    sketcher_intent_manager yes

    start_model_dir wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Setup_Files

    template_designasm wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Setup_Files/neptune_start_asm.asm

    template_solidpart wtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Setup_Files/neptune_start_part.prt

    force_new_file_options_dialog yes

    save_texture_with_model yes

    23-Emerald III
    May 24, 2021

    Do both computers have the Windchill server defined as EngWCApp-p-t

    If one user defined it differently that will prevent Creo from seeing it, check for capitalization, too.

    Do you have any of these settings also in a config.pro file? If the Windchill server name is wrong, the config.pro settings may come into play.

     

    One of things PTC told us when we configured Windchill was to put the templates and start parts on disk and not in Windchill. The only file I have pointing to a Windchill library is the pro_format_dir setting. 

     

    dthornton5-Regular MemberAuthor
    5-Regular Member
    May 25, 2021

    Good morning Ben.... yes, both servers are defined the same, caps and all. None of the config.sup settings are included in the config.pro file

     

    Are you saying that PTC recommended putting the templates and start parts on the hard drives of each individual and pointing to those paths? I've actually done that if I have a user who is running Creo in stand-alone mode and not connected to our Windchill system, but this guy is connected to Windchill.

    24-Ruby III
    May 25, 2021

    @dthornton wrote:
    I am using Creo Parametric 4.0 M040

    Issue revolves around config.sup paths to formats and start parts. Same config.sup file is used on 2 machine. On machine #1, paths work correctly. On machine # 2 belonging to a new user with new install, paths appear to work for some items (ex. start parts) but not not others (ex. formats) It is the exact same config.sup file. Ideas or suggestions appreciated.

    Hi,

    I would check new user's access rights intowtpub://EngWCApp-p-t/Libraries/Library/ProE Standards/Format directory. Is he able to browse into this directory and open drawing format manually ?

    dthornton5-Regular MemberAuthor
    5-Regular Member
    May 25, 2021

    Good morning Martin... yes, he has permission to that area. Right now, that is his work around, browse to this directory and open drawing format manually 

    12-Amethyst
    September 22, 2021

    Did you ever get this resolved? I'm experiencing this exact behavior now, and have conducted the same troubleshooting steps. The only variable factor I've found is that some users have the default cache location (C;|PTC\wfroot\), and some have it in APPDATA. But the issue is still not consistent to either setup.

    kdirth
    21-Topaz I
    21-Topaz I
    September 22, 2021

    Try going to  File / Help / System Information.  

     

    Near the bottom is a section on Configuration files read.  Is the config.sup listed?.

    There is always more to learn.
    12-Amethyst
    September 22, 2021

    Yep. The launch script I wrote copies the standard configs (.sup, .pro) into the application folders (C:\Program Files\....\Common Files\Text, and then launches Creo reading the configs in proper order, no conflicting .pro files in the path.