Ok, this is the third time iv tried to migrate a DNN install... I am begening to wonder if it is even possible. The last two I ended up recreating everything....

So, I have the SQL 2005 database setup correcty at DotNetPark.com I can connect to it using SQL Server Managment Studio just fine as well as through the web management interface...

But I am getting a named pipes providor error when I try to open the site.

1- I have set up the potal alias
2- I have verified the ASP.NET machine has read/write access
3- I have verified my Username/ password and database name are all correct
4- I have changed BOTH connection strings in my web.config file

The host says thier sample script works and thier is nothing wrong.

At first I was using the public IP address and the said the change to the local address for the SQL server... But it gave the exact same error.

I have attached my sanitized connection string:

Any ideas what I can check next??? I can always try to install a blank copy of DNN and reconfigure it but I really don't feel like totally redoing ANOTHER site!

My Host says this is not a connection issue.. they suggested recompiling the database but I don't think that is possible... it it?

Thank you, Jacob Bushnell

Finally found a modification to the connection string that seems to work for now.

I am running into the same problem. I am new at this have any tips. I have been watching the videos but I get stuck at the part where it says:

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 20
Number: 2
Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

See if you can connect to the database using MS SQL Server Management Studio. That might help identify errors.

Hello Guys,

I have the same and exact problem, I can access the database using MS SQL Server Management Studio.
What could I check ?

Thanks for your help,
DV FX

Are you running SSMS from the same machine that runs DotNetNuke?

Are you using the same credentials that are in your web.config file?

Have you checked that BOTH connection strings in web.config are the same?

Hello Joseph,

Thanks for answering and taking care.
I am running SSMS from the same machine that runs Dotnetnuke, yes.
I use the same creditential than my web.config, yes

I have checked BOTH connection strings in web.config, but I am not sure of the exact string...
I have listed it here: http://www.dnncreative.com/Forum/ta...fault.aspx

Thanks,
DV FX

I get it working !! Thanks !!!! It was a problem with the login in the Database > Security tab (not under the general server, but database). It was not correctly attached to db_owner...
Now that's ok (excepted that I am redirected to the production website, but I will find the solution I hope).

DV FX

You will be redirected to the production site if you have not altered the PortalAlias table in the database.

You'll need to enter an alias that points to your local (test) site. You may need to remove aliases that point back to your production site.