Thanks for replying... Here are answers to your questions
1. The previous owner has zipped up the files and the database.
2. I restored the database onto my SQL Server 2005
3. I unzipped the files into a directory and setup IIS 6.0 on my Win2003 server
4. Modified the connectionStrings area to point to my server (as best I could figure out.
Version of DNN is 4.3.4
Here is the message in the Log Viewer:
ModuleId: 1278
ModuleDefId: 99
FriendlyName: Home Page Archives
ModuleControlSource: DesktopModules/HTML/HtmlModule.ascx
AssemblyVersion: 04.03.04
PortalID: 0
PortalName: Society for Academic Emergency Medicine
UserID: 4
UserName: bholland
ActiveTabID: 36
ActiveTabName: Home
RawURL: /Home/tabid/36/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://estest.saem.org/Home/tabid/36/ctl/Login/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 2a4a1b87-5ba8-43b9-83fc-2315571b7394
InnerException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.ProviderBase.DbConnectionPool.GetConnection
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Modules.Html.SqlDataProvider.GetHtmlText(Int32 moduleId) at DotNetNuke.Modules.Html.HtmlTextController.GetHtmlText(Int32 moduleId) at DotNetNuke.Modules.Html.HtmlModule.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Source:
Server Name: CURRY