mojoPortal Content Management System Welcome to mojoPortal Setup

Probing system...
File system permissions problems found.
The Data folder beneath the root of the web site is not writable by the ASP.NET worker process.

You need to make this folder and all its child folders and files writable before setup can proceed. mojoPortal needs this to be able to write search index files, error logs, image gallery uploads, and other important features.

Right Click the Data folder in Windows explorer, choose properties and go to the Security tab. (On XP if you don't see the security tab then google for XP Simple File sharing to learn how to make that tab appear.) On XP you typically need to give write permission to ASPNET user while on Windows 2003 you need to give it to IIS_WPG user.

Obviously, instructions are a little different on Linux/Mono but the same principle is true, the Data folder and all its child objects must be writable.

Folder Details

  • The Data folder is not writable.
  • The Data/Sites/1/ folder is not writable
  • The Data/Sites/1/systemfiles/ folder is not writable
  • The Data/Sites/1/index/ folder is not writable
  • The Data/Sites/1/GalleryImages folder is not writable
  • The Data/Sites/1/SharedFiles/ folder is not writable
  • The Data/Sites/1/SharedFiles/History/ folder is not writable

  • MSSQL database connection ok.
    database permissions are sufficient to alter schema.
    database initial schema already exists.
    database core schema needs upgrade.
    1 site(s) found.
    Running script mojoportal-core - 2.2.1.9 - 00:00:23.8388458
    System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at mojoPortal.Data.SqlHelper.ExecuteNonQuery(SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters) in C:\cst\360\current\mojoPortal\mojoPortal.Data.MSSQL\SQLHelper.cs:line 448 at mojoPortal.Data.DBPortal.DatabaseHelperRunScript(String script, String overrideConnectionInfo) in C:\cst\360\current\mojoPortal\mojoPortal.Data.MSSQL\dbPortal.cs:line 568 at mojoPortal.Data.DBPortal.DatabaseHelperRunScript(FileInfo scriptFile, String overrideConnectionInfo) in C:\cst\360\current\mojoPortal\mojoPortal.Data.MSSQL\dbPortal.cs:line 504 at mojoPortal.Business.DatabaseHelper.RunScript(Guid applicationId, FileInfo scriptFile, String overrideConnectionInfo) in C:\cst\360\current\mojoPortal\mojoPortal.Business\DatabaseHelper.cs:line 313 ClientConnectionId:2c2d611e-768d-42c1-87b5-6c3bff6d1871 Error Number:-2,State:0,Class:11 - 00:00:55.2073829
    Note: This page shows some information that is helpful during setup and upgrades but for security it would be best not to show any information when the system is up to date. You can disable setup and suppress all information on this page by setting DisableSetup=true in Web.config. When you need to upgrade, you can set this back to false. If you are logged in as Administrator setup will run and you will be able to see this page even if it is disabled in Web.config so you can easily leave it disabled and just login before upgrading. But if you are not logged in you will need to enable setup in Web.config.