You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am on Windows 10 64bit. Latest version of fman and windows.
I observe some strange behavior for certain network folders.
Example:
if i try to access a network folder of my company, which looks somehow like this: \\abcdef012.eu.company.com\ABC-DEF\__PROJEKTE\PRJ-ABC\_Public\Trainings
nothing (besides the mouse pointer indicator changing to the loading icon) happens for some minutes (!) until the files in the folder show up.
After waiting, the files show up but it seems like fman crashed (pointer remains at loading icon) and if I click into the left or the right tab, fman gets grayed out.
Opening the folder in windows file explorer works flawlessly.
This sees to be true for some network folders. Unfortunately I didnt not find a certain pattern, which is causing this issue until now. Any suggestions?
The text was updated successfully, but these errors were encountered:
mherrmann
changed the title
fman crashes after not able to access certain network folder
fman freezes after not able to access certain network folder
Jun 30, 2022
I am on Windows 10 64bit. Latest version of fman and windows.
I observe some strange behavior for certain network folders.
Example:
if i try to access a network folder of my company, which looks somehow like this:
\\abcdef012.eu.company.com\ABC-DEF\__PROJEKTE\PRJ-ABC\_Public\Trainings
nothing (besides the mouse pointer indicator changing to the loading icon) happens for some minutes (!) until the files in the folder show up.
After waiting, the files show up but it seems like fman crashed (pointer remains at loading icon) and if I click into the left or the right tab, fman gets grayed out.
Opening the folder in windows file explorer works flawlessly.
This sees to be true for some network folders. Unfortunately I didnt not find a certain pattern, which is causing this issue until now. Any suggestions?
The text was updated successfully, but these errors were encountered: