[SOLVED] Windows 10: “A referral was returned from the server”
lazarus / 34-Windows

----------------------------------------------------------------------
trev · 2019-10-19 02:44

All of a sudden, my Lazarus application is producing this error in
Windows 10 when I try to run the executable which then does not
appear. Previous versions do not trigger it. (The macOS, FreeBSD and
Linux versions have no similar issue.)

The changes were pretty minor but extensive (added a file of device
microprocessor defaults to be read; asterisk default values in combo
box lists; remove asterisks when copying config options to clipboard
etc, etc) and I suspect I'm going to have to go back and undo them one
by one to find the issue.

In the meantime, does anyone have any ideas?

----------------------------------------------------------------------
skalogryz · 2019-10-19 03:05

Operating Systems feels more and more like a prison these days.

https://answers.microsoft.com/en-
us/windows/forum/windows_7-windows_programs/always-getting-a-referral-
was-returned-from-the/8a5802c8-0815-4abc-aab2-ed49dbbfb971

https://www.repairwin.com/fix-a-referral-was-returned-from-the-server-
error/


PS:
new Catalina macOS is doing exactly what PC (with Vista) is
experiencing in this Mac commercial (2007):
https://www.youtube.com/watch?v=FxOIebkmrqs

...for whatever reason, I don't have a sense of security either  I'm
the one in prison.

----------------------------------------------------------------------
trev · 2019-10-19 03:30

If that was the issue I would have expected previous versions of the
application to also trigger the issue but they do not.

Anyway, I'll see what that is set to as soon as I can get Win10 up and
running again... it's updating...slowly updating...

[EDIT]
That option is already disabled

----------------------------------------------------------------------
trev · 2019-10-19 03:46

Right clicking the executable and choosing "Run as Administrator"
fails.

BUT

Right clicking, choosing Properties > Compatibility > Run this program
as Administrator works! Weird.

I'm going to have start undoing my changes to find what's triggering
it

----------------------------------------------------------------------
trev · 2019-10-20 01:21

This "error" also happens on Windows 7 (64 bit), but not Windows XP
(32 bit or 64 bit).

Now that I've wrangled my Windows 7 VMs back into shape after the last
Parallels Desktop upgrade, I'll go back to undoing my source code
changes to find out exactly waht is causing this issue to trigger.

----------------------------------------------------------------------
trev · 2019-10-22 06:32

I returned to an earlier version of the application and added my
changes back, one-by-one, and... there it no longer triggers this
issue with Windows 10 or Windows 7.

[The problematical code version still compiles and causes the issue.]

----------------------------------------------------------------------
trev · 2020-01-06 11:28

It happened again while I was testing a Windows executable cross-
compiled non macOS for win32.

This time I tracked it down to Project Options > Application > For
Windows  UI Access. Unchecked that and the blocking error disappeared!

The docs for Lazarus say:

QuoteUI Access
MS documentation: "Applications that are not providing accessibility
should set this flag to false. Applications that are required to drive
input to other windows on the desktop (on-screen keyboard, for
example) should set this value to true."

Hmmm.