Thanks everyone.

I renamed release.config to web.config, added in the login credentials:

<add
      name="mydatabase"
      connectionString="Server=(local);Database=DNN;uid=DNNUSER;pwd=password;"
      providerName="System.Data.SqlClient" />
  
    </connectionStrings>

and

 <add key="mydatabase" value="Server=(local);Database=DNN;uid=DNNUSER;pwd=password;"/>

Then commented out the SQLExpress code. Then I uploaded the new web.config file to the server by FTP.

Then, hoping for the best I refresh my browser and I get.........the same runtime error! :-(

I am dealing with a really unhelpful, uncooperative web host. I need to be sure I have done all that I can.....as far as I know I have? Would the consensus of opinion now be that the server error must be fixed somehow by the web host? Is there anything else that I can do without direct access to the server? Just want to make sure that I am on solid ground here.

Many thks.

Hi!

I had the same problem when first using DNN. I use Godaddy hosting, and used their automatic installation of DNN to a subdirectory I named /dnn.  I had a website previously set up (in the root directory) on the same domain I was installing DNN. I called for help from Godaddy support, and they said in the root was a web.config file that was interfering with the one DNN was using in /dnn, so I renamed it, and voila! no more problems (with DNN)

Of course, now my old webpages won't work, but that is a minor inconvenience right now.

Hope this helps!

Doris

Got wick?