"Location currently not available" on mapped network drive
Forum rules
You might want to read this if you're looking for priority service
Please Include The Following Information
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
Use Your Profile Or Signature
We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.
How To Attach Images
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
You might want to read this if you're looking for priority service
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
Try the "exist" command again with the full location (not only \\MYTESTSERVER). Do this in the "Location currently not available" state, not when the location has already become available.
FAQ | XY News RSS | XY X
-
Borut
- Posts: 1472
- Joined: 19 Oct 2010 19:29
- Location: Win10 Pro 64b 22H2, @120DPI (125%)
Re: "Location currently not available" on mapped network drive
Location NEVER comes available in XY, even when explicitly written in AB - that is the problem. Nevertheless, here:
Code: Select all
Exist
\\MYTESTSERVER\c$
XYplorer 20.60.0002 - Windows 7 Professional (Service Pack 1), 32-bit, Build 7601 - xxxx
Path: \\MYTESTSERVER\c$
Real Path: \\MYTESTSERVER\c$
ExistFile: False
ExistPath: True
ExistFolder: False
ExistItemFF: False
ExistPathFF: True
ExistPathOrFile: True
ExistPathOrFileShell: True
ExistIcon: True
IsNetworkLocation: True
GetDriveType: 0 (DRIVE_UNKNOWN)
GetItemType: 5
GetFileAttributes: 0x16 (22)
Owner:
This path available in Tree: False
Current node available in Tree: True
Watchable: True
FilenamesCaseSensitive: False
AssumeServersExist: 1
PrecheckServers: 0
CacheServers: 0
CheckServerMethod: 0
CheckServer3: 0
NetworkNetServerEnum: 1
ShowAllServers: 1
MiniTreeVerifyOnSelect: 0
TreeSkipVerifyOnSelect: 0
ExistItemUNC: False
ExistPathUNC: True
ExistPathUNCQuick: True
ExistServer: True - AccessDenied: False - AccessErrorCode: 0
IsShareAccessDenied: False - AccessErrorCode: 0
IsServerConnected: True - Return/BufferType: 0/3Win 10 Pro 64bit
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
Thanks. This never worked. I'm not sure at the moment whether it can be made to work.
FAQ | XY News RSS | XY X
-
mumajs
- Posts: 80
- Joined: 03 Nov 2018 16:47
- Location: Win11, 150% scaling on 3840 x 2400
Re: "Location currently not available" on mapped network drive
Hello All,
I am using xyplorer for long time and I never had problem to access my qnap nas or my intel NUC. From version 20.60 to which I updated I still got the error "Location currently not available.". I see the message very often and of cours always when I need it to be working. I NEVER had this problem before, really never! From build 20.60 I see that mostly always and it is really pitty. I am not using any feature in the "Safety Belts, Network". All network checkboxes are disabled and I never tick any of them. But I had problems with last version. There is really something buggy inside what should be solved! Something changed and it is annoying.
I am using xyplorer for long time and I never had problem to access my qnap nas or my intel NUC. From version 20.60 to which I updated I still got the error "Location currently not available.". I see the message very often and of cours always when I need it to be working. I NEVER had this problem before, really never! From build 20.60 I see that mostly always and it is really pitty. I am not using any feature in the "Safety Belts, Network". All network checkboxes are disabled and I never tick any of them. But I had problems with last version. There is really something buggy inside what should be solved! Something changed and it is annoying.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
1) How do you try to access the network location? Tree, List, Mouse, Keyboard...?
2) Is it UNC or mapped?
3) Is it a server, a share, or a folder on a share?
2) Is it UNC or mapped?
3) Is it a server, a share, or a folder on a share?
FAQ | XY News RSS | XY X
-
mumajs
- Posts: 80
- Joined: 03 Nov 2018 16:47
- Location: Win11, 150% scaling on 3840 x 2400
Re: "Location currently not available" on mapped network drive
1) I hope I got the question correctly, but I have the UNC path in catalog so I can quiclky clik on it... but also ctrl+g and typing \\pc-name returns te same message (explorer and another file managers works)
2) it is UNC path in both cases. Because mostly I am using DNS I tried a while ago also just IP but the same result... error
3) in both cases it is DNS name or IP of the PC or NAS, not specific share.. something like \\nas_ip or \\nas_name, \\pc_ip or \\pc_name
2) it is UNC path in both cases. Because mostly I am using DNS I tried a while ago also just IP but the same result... error
3) in both cases it is DNS name or IP of the PC or NAS, not specific share.. something like \\nas_ip or \\nas_name, \\pc_ip or \\pc_name
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
I did not see anything obvious that could cause this. So I added some debug logging to the next beta version. Please check out the next beta version and post the debug log when you hit that "Location currently not available" again. This command (through XY address bar) will show the log:
FYI, you should be able to get rid of that "Location currently not available" message by ticking Configuration | General | Safety Belts, Network | Network | Assume that servers are available. But then you won't get any Logon dialog in case of password-protected locations.
Code: Select all
dlog;FAQ | XY News RSS | XY X
-
Borut
- Posts: 1472
- Joined: 19 Oct 2010 19:29
- Location: Win10 Pro 64b 22H2, @120DPI (125%)
Re: "Location currently not available" on mapped network drive
Hi Don,
Let me answer this, since I deeply believe that 20.60 has a serious problem with Network...
Here is why:
I made the following test (working via RemoteDesktop where I can test it):
Took a zip of 20.40.0000 from the fridge (https://www.xyplorer.com/freezer.php?ver=20.40.0000).
In such a fresh, in a Network settings group checked only "Assume that servers are available" (others three unchecked)
Wrote in AB \\MYTESTSERVER\c$ and hit enter.
No Problems at all - after some moments of waiting (enumerating servers, I think) the location appeared in the list and tree.
Did the same with a fresh of 20.60.0005.
Nope, this version is not capable of doing that anymore: "Location currently not available".
Just to repeat: \\MYTESTSERVER\c$ is a location in another subnet, which will appear in no explorer, unless written explicitly in AB.
So, the bottom line is:
What you believe "never worked and perhaps never will" (approx. citation), *definitely already worked before*. Before, XY performed as MS FileExplorer. Not any more. It is a regression.
Let me answer this, since I deeply believe that 20.60 has a serious problem with Network...
Here is why:
I made the following test (working via RemoteDesktop where I can test it):
Took a zip of 20.40.0000 from the fridge (https://www.xyplorer.com/freezer.php?ver=20.40.0000).
In such a fresh, in a Network settings group checked only "Assume that servers are available" (others three unchecked)
Wrote in AB \\MYTESTSERVER\c$ and hit enter.
No Problems at all - after some moments of waiting (enumerating servers, I think) the location appeared in the list and tree.
Did the same with a fresh of 20.60.0005.
Nope, this version is not capable of doing that anymore: "Location currently not available".
Code: Select all
::dlog;
XYplorer 20.60.0005 - Windows 7 Professional (Service Pack 1), 32-bit, Build 7601 - xxxx
-------------------------------------------------------------------------
2019-11-23 12:51:59.925 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVER
2019-11-23 12:51:59.933 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVER
2019-11-23 12:51:59.933 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVER
2019-11-23 12:51:59.933 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVER
2019-11-23 12:52:00.049 >> mumajs - NOT FOUND IN TREE: Users
2019-11-23 12:52:00.049 >> mumajs - NOT FOUND IN TREE: Users
2019-11-23 12:52:00.049 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVER
2019-11-23 12:52:00.049 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVER
2019-11-23 12:52:00.049 >> mumajs - NOT FOUND IN TREE: \\MYTESTSERVERSo, the bottom line is:
What you believe "never worked and perhaps never will" (approx. citation), *definitely already worked before*. Before, XY performed as MS FileExplorer. Not any more. It is a regression.
Win 10 Pro 64bit
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
In 20.40.0000, is that server then added to the tree?
FAQ | XY News RSS | XY X
-
Borut
- Posts: 1472
- Joined: 19 Oct 2010 19:29
- Location: Win10 Pro 64b 22H2, @120DPI (125%)
Re: "Location currently not available" on mapped network drive
Yep. Definitely. Checked now again, just to be sure.
Win 10 Pro 64bit
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
OK, I compared the flow in 20.40 and 20.60, found a difference that might explain it, and removed that difference in 20.60.0006. Let's see if that fixes it...
FAQ | XY News RSS | XY X
-
Borut
- Posts: 1472
- Joined: 19 Oct 2010 19:29
- Location: Win10 Pro 64b 22H2, @120DPI (125%)
Re: "Location currently not available" on mapped network drive
Yep, fixed for my case. Great! 
Win 10 Pro 64bit
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
Yeah, thanks for your help! 
FAQ | XY News RSS | XY X
-
mumajs
- Posts: 80
- Joined: 03 Nov 2018 16:47
- Location: Win11, 150% scaling on 3840 x 2400
Re: "Location currently not available" on mapped network drive
Sorry guys, I was not at home during the weekend. Just returned and read the message from Don. I cannot download 20.60.0005 suggested to me anymore, but version 20.60.0007 works without issue.
-
admin
- Site Admin
- Posts: 67271
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: "Location currently not available" on mapped network drive
Alright, thanks for the feedback. I'll upload a new official version today.
FAQ | XY News RSS | XY X
XYplorer Beta Club