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!
Weird process names
-
- Posts: 99
- Joined: Wed Apr 03, 2019 12:10 am
- OLAP Product: IBM PA
- Version: 2.0.9.x
- Excel Version: Microsoft 365 x64
Re: Weird process names
In which tool? Workspace? Architect? Performance Modeler? Arc?
Take care.
Adam
Adam
-
- MVP
- Posts: 3652
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Weird process names
These are most likely unregistered processes which are created (and destroyed after executing) on the fly.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- Posts: 99
- Joined: Wed Apr 03, 2019 12:10 am
- OLAP Product: IBM PA
- Version: 2.0.9.x
- Excel Version: Microsoft 365 x64
Re: Weird process names
I’m not familiar with this concept at all. How or when is an unregistered process created?
Take care.
Adam
Adam
-
- Posts: 6
- Joined: Wed Oct 14, 2015 1:49 am
- OLAP Product: Planning Analytics
- Version: 2.0...
- Excel Version: 2016
Re: Weird process names
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.
-
- MVP
- Posts: 3652
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Weird process names
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.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.