こんにちは、
相互運用性に関していくつか問題が発生しています。開発中によくあることですが、Workbenchで同じワークスペースを複数回実行すると、Workbenchが「Starting Translation...」のメッセージでフリーズしてしまいます。
そのため、コンピュータのユーザープロファイルを再起動しなければなりません。
この問題に遭遇したことがある方はいらっしゃいますか？どのように解決しましたか？
There is no resolution since we still don't have exact repro steps. However, a better workaround is available.
"End" duplicates of fmeobjectworker.exe process in Task Manager -> Details pane. "Ending" the correct fmeworkobject.exe process leak frees up the memory to allow the Translation to run again.
Please save your workspace before attempting to "kill" any process.
A couple more suggestions:
1. Restarting the workbench app also works after deleting extra fmeobjectsworker.exe processes.
2. Use Feature caching sparingly, especially when the workspace is used in production. This would be counter productive for authoring but we believe there is a link between feature caching and this bug.
Hi, yes we have seen this intermittently but have not been able to isolate the cause.
If you are using a non-embedded workspace (i.e. your tool source is a .fmw file) then starting Workbench from the Windows Start menu should not error. If you see a .recover file with the same base name as the .fmw file then accept any message to use it - this will recover your latest edits.
I'll do what @BruceHarold to recover my last edits too.
To add more context, this behavior is a known issue that is triggered by a change in the workspace canvas. The behavior can happen with simple or complex workspaces.
During runtime, the user experiences this "Starting translation... " freezing log message in the Translation log or after restarting workbench stalls on the "Checking license" screen.
A memory leak happens during the author-test workspace lifecycle, freezing the run of the translation. Usually happens when the Feature Cache is enabled. There is no exact repro step identified yet except for these known behaviors.
The best way to check this behavior is to open Task Manager and click on the Details tab. If there are more fmeobjectsworker.exe process than fmeworkbench.exe, one of these processes is freezing the execution of fme.exe.
You will only see fme.exe when you click on the Run button on the Workbench app or its running a workspace headless on a scheduled task.
See my suggested workaround below.
Hi,
I´m glad for your message. I will try the ideas until the complete solution to the problem.
Thank´s
Has any resolution or have additional workarounds been identified? I am currently experiencing the issue. When closing the Workbench and attempting to reopen, I am stuck at the ArcGIS "Checking License" window. If I restart my computer, it will open. But, restarting a computer multiple times while developing a process is less than ideal.
Thanks for the update! Ending the duplicate fmeobjectworker.exe process(es) seems to unfreeze the Workbench, and I will keep the feature caching in mind.
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
