IN WINDCHILL, Actions, Save As = grey but no error message and action never completes

[Jos]

Hi everyone,

we are using a windchill 9.1 M20 after a migration. we had several issues but there is a major one we do not know how to fix :

from commun space directly in PDMLINK/WINDCHILL interface, from any object, there is this ACTION menu (i circled in green in the picture attached) It should enabled anyone to go on the SAVE AS option (enregistrer sous) and this is the case, but then when the SAVE AS window opens, it stays grey without any error message. And clicking on the up right cross closes the window without any problem or message. The logs were sent to support but there is no error message inside neither.

Is there anyone who encountered this issue before even in another release ? We can not go live this way...

Any idea would be very appreciated !

Thanks in advance for any advise

Bye

[Jos]

The special characters were not on the folder/project but on a product... and as i am not so familar with terms in pdmmlink...

So we here learn something today.

Even when working on product with no special caracter inside, windchill scans ALL products to check for any dependencies.

Why no error shown in logs (errors, debug), this is only seen in a trace log but still without error in... and why is it possible to input special characters in these names if we know it generates troubles afterward...'looks like a lack of integrity constraint... (could there be a change in future releases ? or maybe it is usefull like it is set today for other people)

[Jos]

no special characters nowhere ! Even if PDM allows it at first

[ptc-3143537]

Do you know how to use Log 4J? Directions are in System Administrator's guide.

try logging all types of Log 4J output for packages and then send output to PTC support:

com.ptc.windchill.uwgm.cadx.request

com.ptc.windchill.uwgm.cadx.saveas

More like this inside:

codebase/com/ptc/windchill/uwgm/cadx.properties

Also need to try and do save as outside of workspace on same data that causes problem in workspace as the save as code is different between workspace and commonspace. The commonspace might alert you to some javascript error.

David DeMay