Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
I am using Windchill Enterprise Systems Integration Release 11.2 and Datecode with CPS 11.2.1.0
I tried to create a new distribution target with the type as "file", but
When it was completed, the following error was output.
"No group information element with DeletedSCCResourceLinks is included."
This seems to be caused by the incorrect description in the ESIResponseMetaInfo.xml file.
It is unclear which specific description should be corrected.
Translated by the Community Moderation using Google Translate
-----------------------------------------------------------------------------------------------
I am using Windchill Enterprise Systems Integration Release 11.2 and Datecode with CPS 11.2.1.0
新規で配布ターゲットを、タイプを「ファイル」として作成しようとしましたが、
完了としたときに以下のようなエラーが出力されました。
「DeletedSCCResourceLinksを持つグループ情報エレメントが含まれていません。」
ESIResponseMetaInfo.xmlファイルに正しい記載がないことが原因と思われますが、
具体的にどこの記載を修正すべきか不明です。
t
Solved! Go to Solution.
Have edited the ESI meta info file ?
anyways here is a copy of the OOTB file, kindly take a copy of your actual file , and use the one attached and let me know how it goes .
,On teh other hand seems to be an issue addressed in WC12
https://www.ptc.com/en/support/article/CS342745
Thank you for your reply.
I rewrote the file in OOTB and it succeeded in creating the distribution target.
It looks like I have successfully output the file thanks to you, but I don't know where it was output to.
I thought the "path" of the attribute item of the distribution target was the output destination, but after linking the distribution target and the part I created, I couldn't find the file when I tried to "send distribution target".
share a screenshot of your DT ,destination information:
anyways we have a preference
A copy of the XML file should be stored under <Windchill home>/logs/esicache
Thank you very much for your kind advice.
I have restarted the Windchill service and have confirmed the output of files to the path and cache path.
The problem has been resolved.
You are welcomed, would you mark this post as resolved