In the web.config, you need a connection string in BOTH the connection section and the app section.  You don't need to modify development.config because it won't be used.  If your provider is using MS-SQL 2000 then it is the connection string for SQL Server 2005/2005 that should be used, not the one for SQL Express. The connection string for SQL Express should be commented out in both sections -  If your ISP is using SQL 2000, have they created the database for you?  Usually the provider sets it up first and provide you with the necessary info to connect.

---

Shadow

Hello joshy06

I have just managed to solve the problem, but I am not sure how this works. Only that it does and the site is now on line, as from an hour ago. Only time will tell if this causes extra problems.

My hosting provider is using MS SQL 2000.  So in my web config file I was commenting out both the connection strings for server SQLExpress. Uncommenting and setting values for MS SQL 2000.  I was very careful not to make a mistake.  But no matter how often I checked and re checked it just would not work and I was getting the same error.

'dbo.GetPortalAliasByPortalID' doesn't exist.

I have been trying for several days trying to install, without success.

Below is a section of my working web config file.  I deleted one of the connection strings for SQLEXpress:

DELETED (<add name="SiteSqlServer"  SQLEXORESS)

Set the values for SQL2000 the XXX represent my sql 2000 DB settings and left the rest as default.

<connectionStrings>

<add name="SiteSqlServer" connectionString="Server=XXXXXXX;Database=XXXXXX;uid=XXXXXX;pwd=XXXXX;" providerName="System.Data.SqlClient" />

</connectionStrings>

I left the appSettings as default.

<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=True;AttachDBFilename=|DataDirectory|Database.mdf;" />

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules

<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>

-->

The only other thing I changed was: from "RemoteOnly" to "Off"

<!-- permits errors to be displayed for remote clients -->

<customErrors mode="RemoteOnly" />

I am not a developer so I am not suggesting or recommending that you use this method, maybe it's a fluke, but it works for me, after days and days of maddening frustration.

However, I would be interested in the results if you do try it out yourself.

Thanks

---

www.seemalta.net