this is an issue of the forums module.

Jeff,

I did NOT do that in the beginning, because there was a web.config file provided DEVELOPMENT CONFIG huh?

Are there any new directions for 4.3.0?  All i could find was the ones for 4.0.3.

I am now going to wipe the db, erase the directory, create new DB and app dir, copy deveopment.config to web.config and try again.

thanks for pointing that out...will update here if works.

Thanks for all the help!

Ok, I tried development.config rename but same error... this time not even trying to install... it went straight to the error.

I am using the Install package, which is where my confusion was... Yes, i googled the error, but got information that points to (local) SQL installations.  I am on a remote shared hosting and <laugh> they refuse to bounce IIS.  So, I am kind of stuck.

Here is the error after wiping the db, creating a new one, deleting all files then FTP'ing install package files up again wiht the modified development.config to web.config.  I must be doing something wrong OR the Webhost is incompetent.  I mean it can NOT be this hard... modify a couple SQL lines for connectivity, comment out SQL Express since the WebHost does not have it installed and use only the two SQL Server lines under <connectionStrings> and <appSettings> plus identify the dbo in <providers>

Leupold, you mentioned that there was a change because of a prob and it was replaced in the package?  I d/l the package Wed, 6/14/06.  could it have changed after?  at least the original web.config file started the install, the renamed development did nothing but error this time.

Line 66: 
Line 67:             Dim AutoUpgrade As Boolean
Line 68:             If Config.GetSetting("AutoUpgrade") Is Nothing Then
Line 69:                 AutoUpgrade = True
Line 70:             Else

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42