Weird process names

[VV_VV]

Hello,

I started seeing process names that look like this: {9080a8e1-dbec-4f2b-8482-2702fsd5v37c}. They only have a file connection reference, nothing else. What are they, and where did they come from?

Thanks!

[Adam]

In which tool? Workspace? Architect? Performance Modeler? Arc?

[lotsaram]

These are most likely unregistered processes which are created (and destroyed after executing) on the fly.

[Adam]

These are most likely unregistered processes which are created (and destroyed after executing) on the fly.

I’m not familiar with this concept at all. How or when is an unregistered process created?

[VV_VV]

I saw them on the server everywhere: Architect, PAW, Data folder. It turned out they were generated when an admin user manually created a dimension in PAW. I would expect them to be deleted later, but it did not happen.

[lotsaram]

I’m not familiar with this concept at all. How or when is an unregistered process created?

The Rest API allows to run an "unbound" or "unregistered" process where the process definition is passed, the process runs and then it's gone. The process is never registered as an object on the server and a .pro file is never created. You can think of it being like defining and running a function on the fly or the TI equivalent of a temporary subset or view.

When an unbound process runs you see either a GUID in the server message log or an empty string for the process name. I had assumed that the OP was seeing the process GUID names in the message log or maybe in a thread monitor session. However from the OP's description the processes with the weird GUID names aren't temporary but are permanently created. This seems like a bug in PAW as this is the sort of thing you would expect to use an unbound process for as opposed to creating a (permanent) process on the fly.