Synergy-core: Synergy fails to get desktop path, no drop target available

[the-wes]

1. Start Synergy
2. Often, error "failed to get desktop path, no drop target available, error=2" is printed
3. Always when this error occurs, Drag and Drop doesn't work

Synergy 1.7.4, Windows Vista, 7, 8, 8.1, 10

[the-wes]

https://github.com/synergy/synergy/blob/02902066a4778062e9148c986bc1d848b45d8c6c/src/lib/platform/MSWindowsScreen.cpp#L160

"SHGetFolderPath is deprecated in vista, but use it for xp support"

But yet, XP is not supported.

Sounds like we need to use the new function here.

[XinyuHou]

@the-wes bug fix will be in 1.8.1

[spronkey]

Can we get an option to just outright disable drag and drop while we're at it?

[vanowm]

Works fine on Windows 10 but on Windows 7 it fails find the path.
v1.8.0 alpha-85088ba

[vrtareg]

latest beta - failing:
ERROR: failed to get desktop path, no drop target available, error=2

[vrtareg]

latest release - same for me ...

[nullfx]

v1.8.2-stable-36cd521 same here

[threespoons]

Just updated to 1.8.2 after being almost begged to by an email from Synergy and now nothing works due to the same error!
[2016-08-17T10:34:27] ERROR: failed to get desktop path, no drop target available, error=2

[vrtareg]

same for me - no reply from vendor.
Looks like they are busy with new releases and don't care about bug fixing ...

[rmSoft]

I went back to v1.7.5 (only on a windows 10 client; Ther server side is still v1.8.2.).
(Don't forget to uninstall 1.8.2 before re-installing 1.7.5.)
It looks to work fine, although getting the same error message:
[2016-08-30T01:21:10] ERROR: failed to get desktop path, no drop target available, error=2

[trentapple]

I get this error message on Windows 10 (latest version): 1.8.2-stable-36cd521.

[damacguy]

I'm running 1.8.3-stable-db918b on Windows 7x64. Same error.
"ERROR: failed to get desktop path, no drop target available, error=2"

[the-spyke]

I have the same bug on Windows 10 x64 running Synergy 1.8.3-stable-db9181b.
"ERROR: failed to get desktop path, no drop target available, error=2"

[jmamundin]

Got a workaround to work. This should do while waiting for a fix.

My previous setup: Server (Win10) - 1.8.4, Client (Ubuntu) 1.8.4
My server is also getting the same error:
ERROR: failed to get desktop path, no drop target available, error=2

My current working setup: Server - 1.8.3, Client 1.8.4
Downgraded server. Client connecting again.

[RemiKalbe]

Same here. I'm on Windows 10 (host) & macOS Sierra (client). With synergy 1.8.4

[LizJB]

Same issue. Server - Win 10 1706, client Win 10 1511. I went back to Synergy 1.7.6 and that works fine. (1.7.5 is newest version available as an alternate download at http://symless.com/download/?alt. I had 1.7.6 locally.)

[xpac1985]

Server is Win 8 64bit, Synergy 1.8.4 stable
Client is Win 7 64bit, Synergy 1.8.4 stable
Same problem here. Opening the Synergy tool on both devices somehow magically fixed the drag and drop capability, at least for now.

[russellsch]

Server and client on Win 7 64-bit with 1.8.5 stable
Same issue, opening the window on both had no effect.

[claude-ws01]

Hi,
ERROR: failed to get desktop path, no drop target available, error=2
client & server: win7pro sp1
Synergy: v1.8.5-stable-a18eba7

I'm not a C++ nor windows programmer, still I did some investigation with the hypothesis that something might be missing in the registry.

• Ran SysInternal's ProcessMonitor to watch registry queries (& more)
• included the program block that generates the error

if (SUCCEEDED(SHGetFolderPath(NULL, CSIDL_DESKTOP, NULL, 0, desktopPath))) {
            m_desktopPath = String(desktopPath);
            LOG((CLOG_DEBUG "using desktop for drop target: %s", m_desktopPath.c_str()));
        }
        else {
            LOG((CLOG_ERR "failed to get desktop path, no drop target available, error=%d", GetLastError()));
        }

• tested with win 8.1pro (as client) to compare
• tested with 3 different windows 7 pro installations (32 & 64, physical & virtual) (as client & server)

So far

• win 8.1 did not give the error, and all win 7 machines did.
• I did not noticed any relevant (from my understanding) differences in the registry queries and results with regards to the SHGetFolderPath function
• One main difference between 7 and 8.1 tests, is the path used in the attempt to CreateFile:
  
  
  
  • win7
  
  

synergys.exe    8544    RegCloseKey HKU\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders  SUCCESS 
synergys.exe    8544    CreateFile  C:\Windows\System32\config\systemprofile\Desktop    NAME NOT FOUND  Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

• win8.1

synergyc.exe    3028    RegCloseKey HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders  SUCCESS
synergyc.exe    3028    CreateFile  C:\Users\Administrator\Desktop  SUCCESS

AND both 7 & 8.1 get the same returned value <%USERPROFILE%\Desktop> which I tested in a command windows and both point to which it should.

~ ~ ~
within the limits of my understanding and experience...

• I wonder why the desktopPath check is not more elaborate, considering that windows versions may (and seems to) behave differently.
• Adding the option to manually specify the desktop path (as suggested previously) sounds to me, for one, like a valid quick workaround,
  and two, <%USERPROFILE%\Desktop> does not always point to the "actual" desktop (on one of my win 7 machines, the desktop folder is on another drive, but still <%USERPROFILE%\Desktop> points to the C:\Users\Username\Desktop folder!!)

thx :)

[ericR-123]

Fix it! I'm on 1.8.7 and still have this error.

[mhidro]

ERROR: failed to get desktop path, no drop target available, error=2

1.8.8-stable-c30301e still same error, Windows 10 host, Windows 7 client.

[trentapple]

Same error 1.8.8 Windows 10 host, Windows 10 client.

[huwei88]

I also hit this issue running 1.8.8 in win10.

[russellsch]

I have this issue 1.8.5 on win 7 host and client

[Road-hog123]

Both machines running 1.8.8-stable-c30301e on Windows 10 build 14393 here. Same error message on both machines. Doesn't prevent use of the program though, just means I can't drag+drop between them. If automatic detection of the Desktop path is not working, perhaps an option to manually configure it would work?

[clomedico]

started having the same issue today. Uninstalling app from both clients (Mac OS 10.12 and Windows 10). Reinstalled... nothing...

[kndol]

I have the same issue v1.8.8-stable-25a8cb2-Windows-x64 on Windows 10 build 14393.

[clomedico]

The problem was actually with McAfee ENS firewall policy that we have in
place. My imac is a "lab" computer in my office. ENS was updated and
blocked it. I permanently disabled the ENS firewall and it worked.

On Thu, Apr 13, 2017 at 1:34 PM, KnDol [e-mail] wrote:

I have the same issue v1.8.8-stable-25a8cb2-Windows-x64 on Windows 10
build 14393.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy/issues/4987#issuecomment-293969471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZgnjKa_tyeuaPWBso7C97bcwyU5yRumks5rvlyugaJpZM4Fx_wo
.

--

Cheryl Lomedico
Email: [email protected]

[kndol]

The problem was actually with McAfee ENS firewall policy that we have in
place. My imac is a "lab" computer in my office. ENS was updated and
blocked it. I permanently disabled the ENS firewall and it worked.

I'm not using McAfee.

[mhidro]

No firewalls or AVs here.

[oucil]

Same issue on 1.8.8-stable-c30301e, Win10 15063.413

[clomedico]

just upgraded to 1.8.8 and first set of logs after re-connection (from
windows 10 laptop):

[image: Inline image 1]

Seems to work still

From Mac OS X sierra:

[image: Inline image 2]

On Fri, Jun 23, 2017 at 11:01 AM, Kevin Farley [e-mail]
wrote:

Same issue on 1.8.8-stable-c30301e, Win10 15063.413

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy/issues/4987#issuecomment-310689216,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZgnjEBEsBMYrTz-X5WwbFTmsedId7Dwks5sG9M_gaJpZM4Fx_wo
.

--

Cheryl Lomedico
Email: [email protected]

[nicky2983]

Same issue on synergy-v1.8.8-stable-25a8cb2-Windows-x64,
Server:Win10 Pro 1607 OS Build 14393.1358
Client:Win10 Home 1703 OS Build 15063.447
Today suddenly do not work.

[claude-ws01]

here's my update from #5419

Cubuss commented on Feb 28

For people who aren't able to drag n drop files between 2 windows 10 PC's try the following:
Go to "Configure Server..." then drag both pc 1 grid up en press Ok then hit Apply.

Im able to drag and drop files without any issues after following those steps.

_As silly as it may sound..._

I tested Cubuss's advice, to move the computer icons 1 grid up (in the server's configuration), with 2 win7 machines and it worked (!!!), drag'n drop now works, BUT FYI it did not work with the "elevate" setting at "always".

Go figure !?!

thx @Cubuss.

[Jameskholliman]

That worked for me! two windows 10 running 1.8.8. Moving the icons up and changing "elevate" to as needed.

[mcswizzle]

Just got this working with the following setting suggestions from this thread and troubleshooting

OSes:
Windows 10 running 1.8.8-stable-25a7cb2
Fedora 26 running 1.8.8-stable-25a7cb2

Settings
~~~~~~~~~~
Both Systems:

Disable "Use SSL Encryption" on both systems
Set Port to default, 24800 on both

Windows 10, Client:

Choose Client with "Auto config" unchecked, then fill the Server IP filled in. Once IP is
filled click the "Auto config" checkbox
Set "elevate" to "As needed" on the Windows system under Edit>Settings>Elevate

Fedora 26, Server

Choose Server
Set to "Configure Interactively", set up Screen Name only under "Screens and Links",
disable "Enable drag and drop file transfers"
Set Windows to the middle screen, Fedora to the bottom screen, both center column in the grid
~~~~~~~~~~

Apply all of the settings on both, then start the server, then the client.
This resolved both the following error/warning messages for me:

"WARNING: failed to connect to server: Connection was refused"
and
"failed to get desktop path, no drop target available, error=2"

[tinustate]

The solution to get copy & paste working again is to disable "Enable drag and drop file transfers" in server menu Edit > Settings. Next stop and start server.

This solved the "failed to get desktop path, no drop target available, error=2" for me and copy & paste are working again.

[seanvikoren]

Still getting this error on startup.
Windows 7, Synergy 1.8.8-stable-25a8cb2
My Desktop is in an unusual place, but can not be moved back.

[patefoniq]

Change "Elevate" from "Always" to "As Needed" :) This will fix the problem :)
I think it's connected with the fact that when you elevate the privileges you are doing it in user profile context so de facto you are not a regular user but the administrator.

[claude-ws01]

DRAG & DROP
v1.10.2 - works partially.
win7pro & win7ultimate
my users: administrator

• agreed - Change "Elevate" from "Always" to "As Needed", otherwise get a "failed to get desktop path..."

• works partially:
  a. filename: "Synergy fails to get desktop path, no drop target available · symlesssynergy-core.txt: copies as "Synergy fails to get desktop path", truncated at the "," and without file extension.
  b. copying a file that already exist on the destination overwrites WITHOUT user approval.
  c. this filename will NOT copy: <(EWO) — test1.txt> ; without the "—", it copies fine.

[Bistoman]

I still have the error "failed to get desktop path, no drop target available, error=2" on server/client win7 with Barrier 2.3.2

It seems the same situation occurred 5 years ago :)

There is a solution for this issue, also even installing and old Barrier release?

Thanks

[Robinzon100]

is there any fix?

[jacksoncool]

they suck. I don't know why i waste my time with this anymore. same results for years.

[Bistoman]

When a bug is present for more than 5 years with so many complaints it means that... the coder is dead :D

(I hope not)

[mcsab]

Did anyone figure this out?

[jacksoncool]

yes,

http:/www.sharemouse.com

[Bistoman]

http:/www.sharemouse.com doesn't work if you are in different networks. This is the reason why I am here as an ex sharemouse user

[jacksoncool]

valid point. I'm on the same network and it works pretty solid.

On Wed, May 20, 2020 at 1:51 PM Bistoman [e-mail] wrote:

http:/www.sharemouse.com doesn't work if you are in different networks.
This is the reason why I am here as an ex sharemouse user

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/symless/synergy-core/issues/4987#issuecomment-631628702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7ON6MTAFHMVTRDBVGAF6TRSQKDTANCNFSM4BOH7QUA
.

[Whiax]

It worked after I changed the logging level for barrier (barrier>change settings>logging>logging level = debug instead of error), then stop and re-start

[EmmanVazz]

The above comment fixed it for me. Really odd bug.

[arnabsen1729]

The above comment fixed it for me. Really odd bug.

I don't think it fixed anything, since you changed the log level to Debug it is simply not displaying the errors.

[cenzwong]

For me, i suffer from this problem too. But it turns out that it is because my keyboard has turn on scroll lock accidently and makes it not work. and have "ERROR: failed to get desktop path, no drop target available, error=2" this error. Turning off scroll lock on your keyboard and it will become normal again.

[Jekabs123]

I am also having this issue, turning on/off scroll lock didnt not fix it

[ShineSmile]

[dkilleensri]

If on windows this could be due to an app network option too(Public network vs private). No fixes above worked for me but changing the app network settings from private to public worked for me. Your mileage may vary with this but its all to do with your own network setup.