Application failed to start because propsys.dll not found

edbored

RB 21.01, D7 Ent.

Program running on Windows XP (yeah, I know - it's a shop floor data collector running a program that won't install on anything else).

I just updated one of my programs which ran well with an earlier version of RB.

Since v21.01 the program will not load - giving me an "Unable to locate component" dialog box with "This application has failed to start because propsys.dll was not found. Re-installing the application may fix this problem."

The program loads from a network share.

Is there likely to be any solution to this?

TIA

EdB

edbored

Looks like this is an issue getting file dialog options (available in Vista and later):
https://docs.microsoft.com/en-us/windows/win32/api/shobjidl_core/nf-shobjidl_core-ifiledialog-getoptions?redirectedfrom=MSDN

Is it likely this can be fixed with a check for Vista or earlier?

EdB

nicocizik

Hi Ed,

ReportBuilder uses the standard Delphi TOpenDialog to open files. In my simple tests, performing a simple File | Open from the designer in Delphi 7 does load the propsys.dll. I tested this with ReportBuilder 21, 20, and 19. All with the same result.

As another test, I placed a TOpenDialog on a form and loaded it without ReportBuilder. This too loaded the propsys.dll file.

Searching through our code, we were unable to find any new code for RB 21 that would change the way the open dialogs behave. Perhaps a simple example or some more information about your application would be helpful if tracking down the problem.

edbored

I must have a corrupt install then - there's something really wrong with the designer as well: it locks up (from within Delphi IDE or an application with pDesigner) -the menu bar disappears, there are no hints on icons, this goes into high cpu usage - just a mess ( in Delphi 10.4).

Thanks for checking this out for me.

nicocizik

Hi Ed,

The next test would be to create a minimal ReportBuilder app (Report/Designer on a form with a button) and test that with your environment. If this functions correctly, there is likely an issue with your main application causing the problem and it will need to be simplified to track it down.