The explore output doesn’t seems to work, it doesn’t open anything.
Strange. It seems to be working here just fine. Can you send us the Monitor log?
Thanks! The logs show that the Monitor lost connection to the database a couple of times, but there are no error messages regarding output exploring. We do have error handling code around that function, so if an error was occurring, it would show up in the log.
I still can’t reproduce here…
Funny, I started working on something completely different, and then I ran into this problem. It turns out that only Windows UNC paths are affected, and this can be dealt with a simple workaround on our end. This will be fixed in beta 10.
Just to confirm, are you trying to explore UNC paths?
Yes It is a UNC Path