Hi

After my last post, I tried to resolve the duplicate database issue by

• In SQL Server Management Studio:
  • deleting the DotNetNuke database (after stopping and starting SQL Express to gain exclusive access)
  • renaming the database "C:\DotNetNuke\App_Data\Database.mdf" to DotNetNuke
• Changing web.config so both connect statements include "Database=DotNetNuke;"
• Re-installing the Repository module

This time, no duplicate database was created, but the Repository module still does not appear in the Modules table, or in the drop down list of available modules, although it is shown in the Host>Module Definitions page and it is in the ModuleDefinitions table.  I manually added a Repository row to the Modules table, but it still did not show in the drop-down list.  Added row to PortalDesktopModules - still no show

My web.config now includes:

<

connectionStrings> Connection String for SQL Server 2005 Express -->add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=False;AttachDBFilename=c:\DotNetNuke\App_Data\Database.mdf;Database=DotNetNuke;" providerName="System.Data.SqlClient" /> Connection String for SQL Server 2000/2005-->connectionStrings>appSettings> Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=False;AttachDBFilename=c:\DotNetNuke\App_Data\Database.mdf;Database=DotNetNuke;" />

Any ideas?

Richard

<!--

<

<!--

<add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;" providerName="System.Data.SqlClient" />

</

<

<!--

<

Glad to see it’s working for you. This was primary cause of your problems with “duplicate” db and had implication with module installation difficulties.