We have seen numerous posts pertaining to issues and challenges when installing the latest version of DotNetNuke in our shared hosting environment. There are two versions one can download from DotNetNuke's website "http://www.dotnetnuke.com/tabid/125/default.aspx". You can either download the "Community Edition," which is free to the public, or the "Professional Edition". The "Community Edition" will have certain product features that are available with the "Profession Edition". However, for the most part the "Community Edition" will fit the needs of most users. To see a comparison of the "Community Edition" and the "Professional Edition", try this link. As I mentioned before, some users have encountered issues when they tried installing the DNN version 5.2. If you downloaded the Community Edition version 5.2 you should not encounter any resistance as long as you follow the instructions they gave you. I tried this myself using my test account and I was able to install it. The test account does not have any special administrative privileges. It carries the same permission as any other account, which is the ASPNet IUSR having Read and Write permission on the root and all subfolder under it. The trust mode was set to Medium, and the installation completed without any problems. The difficulties I suspect that our customers are encountering are with DotNetNuke Professional Edition version 5.2. I tested this application by using my test account to install it and I too, encountered problems. The symptom you will see during the installation will be an error when running the database script against our SQL 2008 server. The first error you will see on the browser is.. Installing Database - Version 05.00.00...FAILURE ERROR: See E:\web\[site account name]\Providers\DataProviders\SqlDataProvider\05.00.00.log for more information If you navigate to the DNN folder and go to Providers/DataProvider/SQLDataProvider you will see a number of new files created with an extension of .log. When you open that file you will see a log entry with… System.Data.SqlClient.SqlException: Cannot find the user ‘[Database Login]’, because it does not exist or you do not have permission. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.GrantStoredProceduresPermission(String Permission, String LoginOrRole) GRANT EXECUTE TO [Database Login] The root cause of this problem is the way we have mapped the database user name assigned to your account on the server. The db user name is mapped on the SQL 2008 Server in a way so that it prevents the listing of all the other databases to be seen when you connect to our server using SQL Server 2008 Management Studio. If we mapped the database user name in a way that will work around this DNN error message, everybody will see all the databases active on that SQL 2008 server; as you can guess this will be unacceptable to the majority of our customers. Unfortunately at this time we do not have a resolution to this problem. We are still investigating a work around to this issue, however currently the DotNetNuke Community Edition version 5.2 is the only version that will run on our system, and DotNetNuke version 5.2 Professional Edition is not compatible (unless you have another external SQL Server you can use, in which case you should be able to setup remote connection with that SQL Server and point the connection string to that SQL Server).