Page 1 of 1

Running a new blank unsaved TI... it executes a different TI

Posted: Fri Jan 12, 2018 5:42 am
by Andre_Wium
Hi gurus,

I found this interesting issue in TM1 today in our TM1 (v10.2.2 FP7).

Case 1:
We have several environments, but I am logged into Dev and Test only.
In Test, I create a brand new process, and immediately run this blank/empty process.
It then executes a different process in Dev!
The Dev log file confirms the execution of that process, but there is nothing in the Test log file at all about this activity.

Case 2:
I log out of Dev, so I am logged into Test only.
Again, I create a brand new process, and immediately run this blank/empty process.
I get an error message to say it could not execute the process, and to check the log file.
Nothing in the Test log file at all about this activity.

Of course, who would run a brand new blank TI... I agree it's a nonsensical activity... but still... why is this happening. And how does TM1 determine which other TI to execute and in which environment? Has anyone come across something like this before? The scary part is for me is, what if I was logged into Prod at the time? Perhaps running a new blank TI from another environment may just execute something in Prod!

Andre Wium

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Fri Jan 12, 2018 8:11 am
by gtonkin
When you say " I create a brand new process, and immediately run this blank/empty process."

How are you running the process?
-Right click on process, run
-Clicking the Run icon within the process
-Action Button
-Other

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Fri Jan 12, 2018 8:13 am
by Alan Kirk
In addition to George's question, where are you creating the process? Perspectives / Architect, or Performance Muddler?

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 12:02 am
by Andre_Wium
While in Perspectives, I run the blank new unsaved TI from the run icon within the TI. There is absolutely nothing inside the TI at that point. So the steps are:
1. Right-click on Processes, and "Create New Process"
2. Click the Run icon (the one to the right of the Save icon)

It then executes another "random" existing TI. Well, random in the sense that it will repeatedly be the same one in that current session, but once I log out and back in, it could be a different one (sometimes the same one again). But it's choosing different TIs for different developers doing the same thing around the same time.

Weird...

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 5:07 am
by macsir
Better to provide some log info and tm1top snapshots to prove your guessing.
If you create a new process and run it right away, TM1 will give you Error running the process issue immediately and won't trigger any other process to run.

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 5:55 am
by gtonkin
Are you running perspectives off your local machines or via a remote desktop/Citrix environment? Have seen some weird behaviour in a shared environment where users are not configured correctly and seem to share the same temporary folders and TM1 ini.

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 6:41 am
by Andre_Wium
Yes, this is using Perspectives in a Citrix environment.

For me, the most concerning part is that it can execute a TI in a different environment, i.e. running an unsaved blank TI in TEST then executes another TI in DEV.

I will post some log details and screenshots soon, hopefully where it crosses over the environments.

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 3:27 pm
by tm123
Actually I just tested this. I am running Perspectives from my own desktop, and if I Create a New Process and try to run it, Excel Crashes
EMpty_TI_Perspectives.GIF
EMpty_TI_Perspectives.GIF (7.59 KiB) Viewed 5162 times
If I do the same thing from Architect, then I get the error:
EMpty_TI_Architect.GIF
EMpty_TI_Architect.GIF (47.97 KiB) Viewed 5162 times

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 3:35 pm
by gtonkin
My Perspectives forces a save first (PA2.0.1) Architect gives same error.
Can only recommend that you save your process then run - without saving, the objects are probably not registered opening up a slew of possible issues.

Re: Running a new blank unsaved TI... it executes a different TI

Posted: Tue Jan 16, 2018 4:46 pm
by tm123
gtonkin wrote: Tue Jan 16, 2018 3:35 pm My Perspectives forces a save first (PA2.0.1) Architect gives same error.
Can only recommend that you save your process then run - without saving, the objects are probably not registered opening up a slew of possible issues.
That's why I never encountered that issue because I never tried to run an unnamed blank TI