Directory Browsing not working?

[SoftDux]

I created a sub directory directory and enabled Directory Browsing (Enkompass > Advanced > Directory Browsing > choose directory > Enabled.

Yet, when I goto the subfolder on my domain, I get:

403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.

?
Is there anything else I need todo?

[cPanelThrash]

After Directory Browsing is enabled it goes into the queue of changes for the next time Enkompass updates IIS.
This update will happen within 10 minutes of your change.
I just tested and as soon as I enabled the browsing I got the same 403 error but after the update I was able to view the files.

[SoftDux]

thanx,I can see how this is going to be a support nightmare. Is there any way to implement the change immediately?

[cPanelThrash]

The interval could be changed. The problem is that corruption could occur
if one push isn't done and another one starts as the overall quantity of
accounts increases. Due to differences in a server's configuration, available
resources, and the server load at the time a config push is done it isn't easy to
say what lower interval is acceptable.

Through testing we found that 10 minutes gives the best option for a server to
process everything that needs to be done without stepping on it's own toes for
the next scheduled push.

[SoftDux]

ok, maybe I'm spoilt too much with Linux, where thing work much easier than this. But, surely it should be possible to achieve this kind of thing without a process queue? Or is this just the design of Windows / IIS in general?

[cPanelThrash]

Perhaps 'queue' is an over simplification. Enkompass has a process that checks to see if a change was made.
If nothing got changed, the configuration update waits until the next scheduled interval.
If a change has been made then Enkompass republishes the configuration, in full, to IIS.

I've spoken at length with the developer of this feature. He confirmed that we have
set Enkompass up to operate this way because of the unpredictable nature of IIS and
how it manages it’s configuration files. By doing it the way we do it, it helps keep site
configurations intact and changes published in a timely fashion.