My guess would be failed authentication, either because of credentials or network security config. Have you some way of testing your DB connection string from the production web server? Is there a firewall on the SQL Server that prevents connections from your production server? Remember also that there is two locations for the DB connection string in the web.config.

---

Colm Ryan Director
3rd i IT and Business Services Limited

www.actravia.com
Registration and Booking Solutions for Dotnetnuke
www.3rdi.ie
IMCA Registered Management Consulting Practice. Business and IT Strategy, IT Project Management and Product Development

i use the sql server proviedt my webhotel
i began to use by downloading the dnn source (the charp) version and edited the connectionstring to point to it from my local machine

This worked fine DNN created all Tables and Scripts and i succesfully Ran DNN in my developement enviroment connected to the SQLserver at my webhotel

I then compiled the code and uploaded it to my webhotel ( that means it is the same sql server i want to use)

I the created a new Portal in DNN - had to do this from my developement environment because that is the only place where DNN runs

and the i was just hoping that it would enough to make it run from my webhotel....

I think that if i can connect to the sql server from my developement enviroment over the internet - it should be less complicated to connect from my webhotel - where the sql server is also located



  

Considering to delete all table in the database and start all over  - to let DNN configure the portal itsselfes - and maybee when i Run it from my developement enviroment i will be able to debug the code and see exactly what the problem is - if I still get it