creo 6 crashes with cinfig option pro_format_directory set

[ptc-1204517]

I am using Creo Parametric Release 6.0 and Datecode6.0.3.0

Creo 6 crashes due to config options after upgrading from creo 3

[StephenW]

So if you removed the option pro_format_directory from the config, Creo doens't crash?

[ptc-1204517]

yes..

[StephenW]

Does your format directory have spaces? I think they fixed that but it may still cause problems.

[ptc-1204517]

It doesnt have any spaces. to test i pointed it to another folder..still its crashing.

pro_format_dir wtpub://Windchill/Libraries/Templates/DrillBits/Drawing_Formats

[remy]

Can you confirm that a path to your hdd is stable? or have tried another path to wtpub?

[StephenW]

Do you have other options set to windchill? We've noticed that the server name, I think in your case is "Windchill" is case sensitive. So you may want to verify your server name is specifically Windchill and not windchill or WINDCHILL. 

[ptc-1204517]

these are other properties...Creo crashes only when i uncomment pro_format_dir

pro_dtl_setup_dir wtpub://Windchill/Libraries/Templates/DrillBits/Start_Parts/Drw_Properties
drawing_setup_file wtpub://Windchill/Libraries/Templates/DrillBits/Start_Parts/Drw_Properties/in_ems_bits.dtl|-.0

!pro_format_dir wtpub://Windchill/Libraries/Templates/DrillBits/Drawing_Formats

start_model_dir wtpub://Windchill/Libraries/Templates/DrillBits/Start_Parts

[remy]

Thank you for the additional options and pathes.

let's roll back a little and proceed by elimination.

When you say that Creo crashes, does it leave a traceback.log file? 

Does the exit happen instantly or does Creo goes unresponsive for some amount of time?

Then did you try setting the option with a path to your C drive for example? just for the sake of a test. This will enable to know if the crash  is related to Windchill. 

[ptc-1204517]

it leaves a traceback.log file..

only crashes when pro_format_dir is pointed to Windchill folders...local drives creo doesnt crash..

below is the output from traceback log..

Thread 21440
=====================
0x00007FF8BF74CDC4 NULL (NULL:0) (ntdll:0x00007FF8BF6B0000) ( 0x1, 0x7dbc2a4d, 0x81a2bbe0, 0x81a2c680 )
0x00007FF8BD311ACE NULL (NULL:0) (KERNELBASE:0x00007FF8BD2F0000) ( 0xf456e548, 0x0, 0x0, 0xb54 )
0x00007FF86AD51697 NULL (NULL:0) (baselibmt:0x00007FF86AD20000) ( 0xf456e548, 0x81a2bbe0, 0xf456e548, 0x81a2bbe0 )
0x00007FF87DBC2D65 NULL (NULL:0) (asyncoremt:0x00007FF87DB90000) ( 0xf21d08f0, 0x0, 0x81a124e0, 0x0 )
0x00007FF87DBC305F NULL (NULL:0) (asyncoremt:0x00007FF87DB90000) ( 0xf4a69470, 0x0, 0x0, 0x0 )
0x00007FF8BD631BB2 NULL (NULL:0) (ucrtbase:0x00007FF8BD610000) ( 0x0, 0x0, 0x0, 0x0 )
0x00007FF8BDA57034 NULL (NULL:0) (KERNEL32:0x00007FF8BDA40000) ( 0x0, 0x0, 0x0, 0x0 )

Thread 21516
=====================
0x00007FF8BF74CDC4 NULL (NULL:0) (ntdll:0x00007FF8BF6B0000) ( 0x10, 0x81b91fdb, 0xf47d1720, 0xf20d0870 )
0x00007FF8BD311ACE NULL (NULL:0) (KERNELBASE:0x00007FF8BD2F0000) ( 0x878342c8, 0x0, 0x0, 0xb50 )
0x00007FF86AD5166B NULL (NULL:0) (baselibmt:0x00007FF86AD20000) ( 0x0, 0x1, 0x8, 0xf21d0bf8 )
0x00007FF86AE16BE5 NULL (NULL:0) (baselibmt:0x00007FF86AD20000) ( 0x8783ef00, 0x0, 0x878342b0, 0x7fffffff )
0x00007FF8BD631BB2 NULL (NULL:0) (ucrtbase:0x00007FF8BD610000) ( 0x0, 0x0, 0x0, 0x0 )
0x00007FF8BDA57034 NULL (NULL:0) (KERNEL32:0x00007FF8BDA40000) ( 0x0, 0x0, 0x0, 0x0 )

Thread 20432
=====================
0x00007FF8BF74CDC4 NULL (NULL:0) (ntdll:0x00007FF8BF6B0000) ( 0x81a1df50, 0xf21d0000, 0x0, 0x0 )
0x00007FF8BD311ACE NULL (NULL:0) (KERNELBASE:0x00007FF8BD2F0000) ( 0x878343c8, 0x0, 0x0, 0xcf8 )
0x00007FF86AD5166B NULL (NULL:0) (baselibmt:0x00007FF86AD20000) ( 0x0, 0x1, 0x8, 0xf21d0bf8 )
0x00007FF86AE16BE5 NULL (NULL:0) (baselibmt:0x00007FF86AD20000) ( 0xf4a6f400, 0x0, 0x878343b0, 0x3c )
0x00007FF8BD631BB2 NULL (NULL:0) (ucrtbase:0x00007FF8BD610000) ( 0x0, 0x0, 0x0, 0x0 )
0x00007FF8BDA57034 NULL (NULL:0) (KERNEL32:0x00007FF8BDA40000) ( 0x0, 0x0, 0x0, 0x0 )

[remy]

Thank you for sharing the content of the traceback. Your test, by elimination, confirms that the issue lays somewhere in the Creo and Windchill Interaction. 
Being an exclusive Creo specialist, this is out of my personal scope.
I recommend that you either change your thread to Creo-Windchill and/or file a case and set the Technical Area with Creo Windchill Interaction.
This is mandatory when you need to have the traceback analyzed by our services.
Good luck.

[KenFarley]

I don't know if this is a useful comment, but for my path specifications, they're of the format:

pro_format_dir c:\ptc\Formats

In other words, with backslashes, "\", not forward slashes, "/". The same is true if I'm giving the network path, that starts with "\\", not "//".

Might this be causing trouble?

I'm not sure if Creo "interprets" forward slashes to be "backwards" when in the Windows environment.

[BenLoosli]

I have both in my group config.pro:

template_drawing X:\OR\Engineering\Systems\PTC_Settings\Templates\cts-d.drw
pro_format_dir wtpub://PDM-CTS/Libraries/System Config Library/Main/PTC Settings/Formats

[TomU]

There were a couple builds of Creo 6.0 and 7.0 that had serious stability issues.  I can't remember if 6.0.3.0 was one of those or not.  Have you tried using the latest build (6.0.6.0) to see if the issue is still reproducible there?  Something else to try is removing ALL of your config options except just this one.  It's possible that while this config option is causing crashing, it only happens in conjunction with some other config option.