Network: "Location currently not available"

[Borut]

v20.30.0011 - 2019-08-29 14:05
! Network: On some systems under certain conditions you got a "Location
currently not available" for an existing server path whereas the
corresponding IP path worked. Fix #2.

Still not working at my place. As before and with FIX#1, it does not work only the first time in a session. As soon as one does "parent folder (i.e. up), and then back" everything is ok. Some tabs in my tabsets point to such locations so I encounter it perhaps few times a day. But it is not a big deal, so I did not care to report it before.

Sorry if a thread for this already exists somewhere else.

[admin]

Next time it does not work run dlog; and show the results.

[Borut]

Log is in each such case completely empty (apart from your two header lines).

[Borut]

OK, I have meanwhile found the other thread, but will stick with this one.

When I start XY anew and paste the problematic \\server\... location in the AB, it works as expected (BTW, dlog result is empty in that case too)!!

None of my "Controls and More/Network"-settings are currently checked.

So, the bottom line (in my case):

Start the XY anew.
Open a tabset where one of the tabs has such a location (but not the one first shown).
Click on the tab with a problematic location.
Enumerating servers... runs.
List is empty/gray, saying "Location currently not available".

Does not occur again later in the same session.

[admin]

1) You say "problematic location". So this does not happen with all network locations? What have the "problematic locations" in common?
2) Are these password protected locations? = Do you get a login prompt?

[Borut]

1) I do not know. And - in my case - if I try to specify location with \\IP-number\..., it fails in the same way.

2) With another comparable system in network I do get a password dialog sometimes and never have any problems. With this one I do not get a password dialogue. It is strange, definitely.

Sorry. But, as I said, a minor problem - I can live with it.

[admin]

"Click on the tab with a problematic location."

And when you click another tab and then go back to this one, it works, right?

[Borut]

No, it does not.

I always use:
Dbl click on empty file list space (under the message), to go up.
Back.

This makes the target location content to appear in the list (and is necessary only once in a session).

[Borut]

DLog after first invocation (not successful):

Code: Select all

XYplorer 20.30.0013  -  Windows 7 Professional (Service Pack 1), 32-bit, Build 7601  -  2019-09-03 09:01:04.506
----------------------------------------------------------------------------------------------------

2019-09-03 09:00:26.072 >> mrbosco Tree Browse: C:\<deleted>\xyplorer\Data\Catalogs
2019-09-03 09:00:26.257 >> mrbosco Tree Browse: True
2019-09-03 09:00:26.261 >> mrbosco Tree Browse: C:\<deleted>\xyplorer\Data\Catalogs
2019-09-03 09:00:26.269 >> mrbosco Tree Browse: True
2019-09-03 09:00:26.270 >> mrbosco Tree Browse: Computer
2019-09-03 09:00:26.558 >> mrbosco Tree Browse: True
2019-09-03 09:00:44.108 >> mrbosco Tree Browse: U:\<deleted>\
2019-09-03 09:00:44.318 >> mrbosco Tree Browse: True
2019-09-03 09:00:44.542 >> mrbosco Tree Browse: U:\<deleted>\
2019-09-03 09:00:44.562 >> mrbosco Tree Browse: True
2019-09-03 09:00:46.983 >> mrbosco Tree Browse: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:00:53.162 >> mrbosco Tree Browse: False

Dlog after workaround (Up + Back):

Code: Select all

XYplorer 20.30.0013  -  Windows 7 Professional (Service Pack 1), 32-bit, Build 7601  -  2019-09-03 09:05:38.848
----------------------------------------------------------------------------------------------------

2019-09-03 09:00:26.072 >> mrbosco Tree Browse: C:\<deleted>\xyplorer\Data\Catalogs
2019-09-03 09:00:26.257 >> mrbosco Tree Browse: True
2019-09-03 09:00:26.261 >> mrbosco Tree Browse: C:\<deleted>\xyplorer\Data\Catalogs
2019-09-03 09:00:26.269 >> mrbosco Tree Browse: True
2019-09-03 09:00:26.270 >> mrbosco Tree Browse: Computer
2019-09-03 09:00:26.558 >> mrbosco Tree Browse: True
2019-09-03 09:00:44.108 >> mrbosco Tree Browse: U:\<deleted>\
2019-09-03 09:00:44.318 >> mrbosco Tree Browse: True
2019-09-03 09:00:44.542 >> mrbosco Tree Browse: U:\<deleted>\
2019-09-03 09:00:44.562 >> mrbosco Tree Browse: True
2019-09-03 09:00:46.983 >> mrbosco Tree Browse: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:00:53.162 >> mrbosco Tree Browse: False
2019-09-03 09:05:16.613 >> mrbosco Tree Browse: Netzwerk
2019-09-03 09:05:16.692 >> mrbosco Tree Browse: True
2019-09-03 09:05:19.168 >> mrbosco Tree Browse: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:05:19.317 >> mrbosco Tree Browse: True

P.S. The server in question has two "-" (minus) signs in its name, if this could be of importance.
P.P.S. In both cases no logon dialog.

[admin]

Thanks! The next beta will have more debug logging. Narrowing it down...

[Borut]

Just in case this is of importance here too... When I try the following (with deletions expanded, of course):

Code: Select all

::logon "\\<deleted>\e$\<deleted>\Scripts\";

no logon dialog shows up. The command is logged in the status bar however.

As mentioned above, my server name is something like \\V-ABCD-EFGHI

[admin]

Ok. The dialog will only show if needed (if that location is password protected).

[Borut]

In the following code box, the first dlog was invoked immediately after the problem, while the second dlog was invoked after workaround (Up + Back) (i.e. both reports in one box). Somehow I fear you will get out of ideas. Spannend...

Code: Select all

XYplorer 20.30.0014  -  Windows 7 Professional (Service Pack 1), 32-bit, Build 7601  -  2019-09-03 09:55:56.600
----------------------------------------------------------------------------------------------------

2019-09-03 09:55:37.365 >> mrbosco Tree Browse 1: U:\<deleted>\
2019-09-03 09:55:37.564 >> mrbosco Tree Browse 2: True
2019-09-03 09:55:37.769 >> mrbosco Tree Browse 1: U:\<deleted>\
2019-09-03 09:55:37.785 >> mrbosco Tree Browse 2: True
2019-09-03 09:55:42.209 >> mrbosco Tree Browse 1: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:55:48.358 >> mrbosco Tree Browse 2: False


XYplorer 20.30.0014  -  Windows 7 Professional (Service Pack 1), 32-bit, Build 7601  -  2019-09-03 09:57:23.349
----------------------------------------------------------------------------------------------------

2019-09-03 09:55:37.365 >> mrbosco Tree Browse 1: U:\<deleted>\
2019-09-03 09:55:37.564 >> mrbosco Tree Browse 2: True
2019-09-03 09:55:37.769 >> mrbosco Tree Browse 1: U:\<deleted>\
2019-09-03 09:55:37.785 >> mrbosco Tree Browse 2: True
2019-09-03 09:55:42.209 >> mrbosco Tree Browse 1: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:55:48.358 >> mrbosco Tree Browse 2: False
2019-09-03 09:57:06.787 >> mrbosco Tree Browse 1: Netzwerk
2019-09-03 09:57:06.850 >> mrbosco Tree Browse 2: True
2019-09-03 09:57:08.413 >> mrbosco DGLoc 1: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.413 >> mrbosco DGLoc 3: \\<deleted>\e$\<deleted>\Scripts\, Exist=True, UnAvailable=False
2019-09-03 09:57:08.413 >> mrbosco ASOTF 1: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.413 >> mrbosco ASOTF 2: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.415 >> mrbosco ASOTF 3: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.421 >> mrbosco ASOTF 9: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.421 >> mrbosco ASOTF 10: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.424 >> mrbosco DGLoc 4: \\<deleted>\e$\<deleted>\Scripts\, Added=True
2019-09-03 09:57:08.425 >> mrbosco Tree Browse 1: \\<deleted>\e$\<deleted>\Scripts\
2019-09-03 09:57:08.555 >> mrbosco Tree Browse 2: True

[admin]

This line comes right after/while you went UP, right?

Code: Select all

2019-09-03 09:57:06.787 >> mrbosco Tree Browse 1: Netzwerk

[Borut]

Correct. These two:

Code: Select all

2019-09-03 11:48:20.012 >> mrbosco Tree Browse 1: Netzwerk
2019-09-03 11:48:20.085 >> mrbosco Tree Browse 2: True

Note: Interestingly enough, the servers are being enumerated also when first going to that "problem location" (which ends with that error message in the list.) Even more: When I look the "Netzwerk" list of servers, that "problem computer" is not even listed there. But wait: Alphabetically it should appear at the absolute end of the list! Maybe just a coincidence... More probably something special with that computer and I do not know what it could be.