That one we discussed here White screen of death - #14 by Olga
and it is not 2024.2 specific, 2024.1 had it too, it depends on user machine
1 Like
We skipped the 2024.1 upgrade completely so this would be new to us. I’ll check out that thread. Thanks!
Hi Olga - I took a look at the other thread and I’m not sure that’s is. Since Saturday, I don’t know how many times I have cleared “all” the cache and re-installed Pilot. Here is my PowerShell result based on the thread and I get the error discussed.
One difference I do see in the config folder (in a machine that is working) is an additional sysconfig file that I do not have on my machine. Looks like it was created today when that machine downloaded the new client.
This error is not related to cache, it is related to the fact that system pipes created by 3rd party programs on your computer contain symbols that cause this command to fail.
The fix will be available soon, until then your only way is to delete those pipes or applications.
3 Likes
Looks like System File Checker may need to be ran
Go get your on-prem 2024.2 people! Help us cloud users further test this release candidate!
3 Likes
We’re looking at it…LOL.
1 Like
This weekend!
Sigh.
3 Likes
Who needs errors. Those are so 2024.1.
7 Likes
That’s the same behavior we’ve seen in 2023.2 on occasion…and that’s where the Application Studio Band-Aid came from…and I know there are other threads on it. Recommendation was to simply open the base layer, then exit out - don’t make/save any changes, just get out - and then try to reopen the screen in question. Usually works but occasionally took multiple attempts.
2 Likes
I was told to go to 2023.2 to resolve this issue as we face it in 2022.2. Are you still on patch .11 because that may have been fixed
also, heavily considering 2024.X instead of 23. probably going to throw .2 up on the dev infra and see how it goes upgrading the 2023 db there.
1 Like
Another UGH that I just noticed. In 2024.1 our job entry screen was perfectly fine. Now in 2024.2 it says that we have orphan components that I cannot find anywhere. Is there a way to just disable that warning from popping up at all?
2 Likes
We were able to identify the root cause of our internal issue (with a grateful 11th hour assist from @hmwillett…I owe her dinner and wine!). It was a pdf rendering exe.
It is called “PrintDist” and included the following in our system pipe:
ActMaskPrtDisp|1
ActMaskPrtDisp|Sys
Here is the record within Task Manager:
We renamed the .exe in the Windows32 folder and pushed out scripts that removed the registry files. After a reboot, Pilot loads fine. It was observed that all of our users experiencing this issue had PrintDisp installed.
Hope this can help someone else!
8 Likes
Seems like malware to me 
It’s a part of ALL2PDF Creator
2 Likes
As always, be careful what you install on your PCs. 
3 Likes
Does anyone know how to access the Test ReCoder UI Test Tool that was announced in “What’s new in 2024.2” It would be nice to use that during Pilot testing.
2 Likes