When I installed VISTA, it made it appear that I had two databases of the same name. One as c:\documents and settings\Ley\My Documents\My Web Sites\ClubWebSite1\App_Data\ASPNETBB_Parley.MDF and another as Desktop\Ley\Documents\My Web Sites\ClubWebSite1\App_Data\ASPNETDB_Parley.MDF. I realized what was happening - two separate paths to the same file - and moved the site to a new location in which there would only be one path. I deleted the old location but that did not solve the problem. Now when you run ASP NET CONFIGURATION, I get the following message:
'C:\Documents and Settings\Ley\My Documents\My Web Sites\ClubWebSite1\App_Data\ASPNETDB_Parley.MDF' already exists. Could not attach file 'C:\WebPages\lkwdfirstlions\App_Data\ASPNETDB_Parley.MDF' as database 'ASPNETDB_Parley'.
I guestion is "how can the ClubWebSite1 still exist? I deleted the folder, files and all." SQL thinks its still there!
I had a hard time finding aspnet_regsql.exe. I ran it and it reports:
System.Web.HttpException: Unable to connect to SQL Server database. ---> 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.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity,
and so forth
Thank heavens the hosted site is still running correctly, but I can not run the site on my machine.