The Documents module (most recent release 04.01.00) appears to use of the "legacy" database connection string defined in the <appSettings> section of your site's web.config file. Often the problem is not in the connection string itself but in the improper placement of comment markers around the connection string node.

Note that the value of the "legacy" connection string should be the same as that given to the connectionString attribute of the site's primary connection string located in the <connectionStrings> section of web.config.

If you are not able to correct the problem yourself, please post the following sections of your web.config for us to examine:

<connectionStrings>
   <add name="SqlSiteServer" connectionString=" . . . . ." />
</connectionStrings>
<appSettings>
     <add key="SqlSiteServer" value=". . . . ." />
     <add key="InstallTemplate" value="DotNetNuke.install.config"/>

NOTE: When posting these sections to the forum, replace database name, username, password with xxxxx.

Also, when you upgraded to 5.4.2, from what version did you upgrade and is the site running under ASP.Net 2.0/3.5 or ASP.Net 4.0?

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Bill, Was wondering if you could help me out!? I am having the same exact problem except I did not do an upgrade, I started with DNN 5.04.02 (66) already installed fresh. I tried figuring it out on my own but am afraid to mess up the web.config file. I am still new to all of this, so i don't really know what I am doing. I am posting the info from the file as you asked Jeannine to do above if she could not figure it out. Hope you can help, and hope you don't mind me posting on an old thread. Thanks in advance, Aaron FYI: Site uses .NET 3.5