Hello,

I recently set up a DotNetNuke 6.2.3 instance (it was a copy of a site that was upgraded from DotNetNuke 5.6.3). Now, the site shows up fine (no errors) and I can navigate to most sections of the website with the exception of the Site Settings page and things like the File Manager.

When I try to access these pages I get the following error message. Why do I get these timeout messages?

Everywhere within the Web.config file has the correct SQL Server settings but I still get this message.

Thanks.

AssemblyVersion: 6.2.3

PortalID: 0

PortalName: (Portal Name)

UserID: 1

UserName: host

ActiveTabID: 44

ActiveTabName: Site Settings

RawURL: /Admin/SiteSettings.aspx

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: http://{Portal URL}/Admin/LogViewer.aspx

UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; BOIE9;ENUS)

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: 5502e879-7982-4ba7-bcc5-868b8992cfdc

InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Data.SqlClient.SqlConnection.

StackTrace:

Message: System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.GetFoldersByPortalAndPermissions(Int32 PortalID, String Permissions, Int32 UserID) at DotNetNuke.Services.FileSystem.FolderManager.GetFoldersByPermissionSortedCallBack(CacheItemArgs cacheItemArgs) at DotNetNuke.Common.Utilities.DataCache.GetCachedDataFromRuntimeCache(CacheItemArgs cacheItemArgs, CacheItemExpiredCallback cacheItemExpired)

Source:

Server Name: {Server Name}

 Thanks for the help.

Here is how I copy a website:

1. If one doesn't exist I create a new testing alias within Portal Aliases of the Host Administration section of the existing site.
2. Stop the application poll and web service for the existing site (this is IIS7.5 I am using).
3. Zip all files in the application root (wwwroot in this case).
4. Create a full backup of the database.
5. Go to the new (testing) web server and either create or clear the existing folder for the site.
6. Unzip the files copied such that all of the existing files go into the new folder. Set the permissions for Network Service for all files.
7. Either create a new IIS site or, most likely, doublecheck the existing IIS site to make sure everything is the same as the existing one.
8. Restore the database to the same testing server as the site I just copied. Most likely I can keep the database name the same but if not I change it and make note of the name change.
9. Delete and readd the Database User for this database I copied. I keep the password the same.
10. Open and change the web.config file for the new "testing" site and change the database settings as appropriate to match the new testing environment. This includes the two sections within the web.config file for the database.

Now, the site was working fine but as mentioned this site was 5.6.3 (we are running an older version of DNN in production and would like to have a test environment for the new version).

I started to have the mentioned problems after the upgrade to 6.2.3. I checked the web.config file after the upgrade and all was well.

Anything else I missed?

Thanks.