XYplorer Beta Club

Hi,

I've looked for this, I've read through many of the threads dealing with RDP shared drives but I have not seen this issue:

1. I use RDP to connect to a remote windows machine
2. one of the local drives is shared with the remote machine
3. I run the newest XYplorer version on the remote machine (everything working as expected)
4. I can connect to \\tsclient\T using windows explorer just fine
5. I can connect to \\tsclient\T using TotalCommander just fine (I'm never going back there though )
6. I CAN NOT connect to the same address using XYplorer. XYplorer gives the error "could not find \\Tsclient\t Probably the server is currently not available" .... when it clearly is (see screenshot win-explorer of the left)

I've tried everything I could think of. Any ideas welcome!

Here's the screenshot from the remote machine.

I have tried it using different RDP client computers.... doesn't work for any of the machines I use to access (2xwin, 1xmac)

Weird. Try this script, what does it return?:

I rand the script in the address bar and had to wait a while... then got this popup window:

Alright, the next beta should fix it.

.... I was about to guess if this could be windows rights issue on the remote server for XYPlorer...
just out of interest ... what do you rekon the problem was instead?

amazing support as usual then!!!

I do some pre-checks for existence to fail more gracefully and save time (wasted on browsing a non-existent server in vain). However, for unknown reasons, this "\\tsclient" server fails the checks even if it exists. So my solution is: don't check this server.

admin wrote: ↑14 May 2020 21:11 ...However, for unknown reasons, this "\\tsclient" server fails the checks even if it exists. So my solution is: don't check this server.

I must misunderstand.... you're not hardcoding an exception for this this specific server name!?
oh well, I guess it is specific to Ms RDP and thus not as rare as any ordinary servername.

I have nothing better. This is the only server name that makes such problems.

I tested the beta 20.90.0303 and it works fine!
no worries, as the RDP shared drive 'network' is always called tsclient this should be useful to many and remain an exception.

many thanks!

It seems that accessing RDP shared drives is broken again (for some time). Trying to access them takes some time and then I get this message:

Error:  	9 (0x00000009)
Desc:   	Subscript out of range
Dll:    	0
Proc:   	doGoPath

Source: 	XYplorer
XY ver: 	XYplorer 23.60.0004
OS:     	Windows 10 Pro, 64-bit, Version 22H2, Build 19045.2251 (10.0)
Locale: 	1031 (de-DE)
ANSI:   	1252, ACP: 1252  (ANSI - Lateinisch I)
Font:   	MS Sans Serif 8,25, Tahoma 8,25, DBCS: No
DPI:    	96 (100%), 1294x891

This message is from 23.60.0004 (2022-09-07 09:51), and it's one of the versions with "special debug code". This is a nice example for what this code does. A normal instance would just have crashed without further notice. So here's a nasty crash bug, and now we have a trail of blood!

The next beta (v23.80.0005) will show additional information when this error occurs.

Oops, yes, my version was a little bit outdated.
I just noticed that I didn't get a beta e-mail since 13.11...
Also, no notification about your post.

I will test it tomorrow.

About 2 weeks ago, on 2022-11-14, my provider switched to PHP 8, and the forum software is not fully compatible. Currently I have no time to upgrade to the latest forum version (which is always a terrible ordeal). Later...

Have you already removed the additional info? Today I've tested it again with version 23.80.0013 and I don't see much more info:

Error:  	9 (0x00000009)
Desc:   	Subscript out of range
Dll:    	0
Proc:   	doGoPath@100

Source: 	XYplorer
XY ver: 	XYplorer 23.80.0013
OS:     	Windows 10 Pro, 64-bit, Version 22H2, Build 19045.2251 (10.0)
Locale: 	1031 (de-DE)
ANSI:   	1252, ACP: 1252  (ANSI - Lateinisch I)
Font:   	MS Sans Serif 8,25, Tahoma 8,25, DBCS: No
DPI:    	96 (100%), 1294x891

Date:   	2022-11-29 09:35:22