Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Really odd logging directory problem

Featured Replies

I'm using the standalone version of SuperContainer, v2.792 on a Windows Server 2008 Enterprise SP2 machine. Installed and configured just fine and running as expected.

Until I restart the program or reboot the machine. After that point it gives the following error message when starting SuperContainer -

"Cannot run SuperContainer Server: java.lang.runtimeexception: logging directory is not writeable, please verify that the Files folder is in a folder SuperContainer can write to."

Apparently others have come up with this problem as well - http://attic.fmforums.com/forum/showtopic.php?tid/217642/ I checked the permissions on the folder C:\Users\Administrator\Documents\SuperContainer (where the log file is located), and 'Everyone' has full permissions, so I don't know what more to do at this point.

Something odd I noticed is that if I remove any references to 'supercontainer' in the registry and run it again, it'll run just fine. Of course I have to reset all of the option values. Until I stop the program or reboot the server, then this starts all over again.

There is no problems if I just stop and start the server using the button in the SCServer window.

Any other ideas that I might of missed?

Check and make sure that the directory is not set to be read only. This definitely sounds like some sort of permissions issue on your computer. As I recommended in the other thread check and make sure that there isn't any antivirus software which might be cracking down on your. AV software is often a culprit in situations like this.

  • Author

The directory is not set to read only. The server is running Symantec Endpoint, but even when I made an exception for that directory and even disabling the AV program altogether still gives the same results.

Any other ideas?

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.