joannew
DNN Creative Magazine Subscriber
Nuke Ace
Posts:58
 |
| 07 Aug 2008 5:58 AM |
|
Hi, I've followed your tutorial for restoring a live website to localhost but have run into some problems. I've been working with two websites and am using Windows XP Prof & SQL 2005 Express
Website 1: DNN 3.3.7 ASPNET 1.1.4322.2407 SQL Server 2000
The error I currently get is Error Installing Dotnetnuke. Current Assembly Version 3.3.7. ERROR: Could not connect to database specified in connectionString for SylDataProvider.
Website 2: DNN 4.5.5 ASPNET 2.0 SQL Server 2005
Unable to restore database on SQL 2005 Express, how do you fix this problem?
Any suggestions or things to check would be appreciated please? Thanks alot, Cheers Jo... |
|
|
|
|
jncraig
DNN Creative Staff
Nuke Master II
Posts:2157
|
| 07 Aug 2008 8:09 AM |
|
For the first site, make sure that both connection strings are set in web.config. If you are having trouble, you can test the connection using SQL Server Management Studio Express. If you can connect with SSMSE, use the same database name, username, and password in your connection string, and make sure that you use the SQL Server Express version of the connection string if you are using that in your localhost installation.
For the second site, what errors are you getting? |
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|
joannew
DNN Creative Magazine Subscriber
Nuke Ace
Posts:58
|
| 07 Aug 2008 9:31 AM |
|
Thanks for your reply...
For my first site, I can look at the connection settings (does this mean I'm connected?) and have checked the user name held here with the username in my webconfig, but still no luck... does it matter how Sql has been installed, ie whether sql authentication or windows?
For my second site, I was getting the error below... but its now fixed by changing security settings on my sql backup folder... restore worked!
System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\a3250233test_1.mdf'. (Microsoft.SqlServer.Express.Smo)
|
|
|
|
|
joannew
DNN Creative Magazine Subscriber
Nuke Ace
Posts:58
|
| 07 Aug 2008 1:45 PM |
|
| I think my problems are to do with the web config and database user name and password but also because my SQL Express connects using Windows Authentication and it was installed using Windows Authentication Mode. I've read that this needs different code in web config. I'm going to try reinstalling sql. |
|
|
|
|
jncraig
DNN Creative Staff
Nuke Master II
Posts:2157
|
| 07 Aug 2008 1:56 PM |
|
| If your SQL server isn't configured to do user/password authentication, you can turn that on. You don't need to reinstall, but that advice probably is too late. |
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|
joannew
DNN Creative Magazine Subscriber
Nuke Ace
Posts:58
|
| 07 Aug 2008 2:02 PM |
|
| thanks for the advice, I was just about to do it... so how do you turn the authentication on? |
|
|
|
|
joannew
DNN Creative Magazine Subscriber
Nuke Ace
Posts:58
|
| 07 Aug 2008 3:09 PM |
|
Okay, I've now got a version working locally I think these instructions helped:
...In the web.config file, add the following: (this time without the user name and password). Then, from IIS Manager, right click on the virtual directory assigned to your application and select “Properties”. Click on the “Directory Security” tab, then under “Anonymous access and authentication control” click “Edit”. If you are going to allow anonymous access to the application (not requiring users to login with windows authentication each time they access this web application), make sure “Anonymous access” checkbox IS checked. Then uncheck “Allow IIS to control password”. In the “User Name” field, type in (or you can browse to) the domain account (domain\user) and type in the password for the domain account in the “Password” field (By default IIS uses IUSR_machinename for the anonymous account, you can refer to this page if you would like to find its default password in case you want to change it back later for some reason) . Then under “Authenticated Access”, make sure NONE of the boxes are checked. Press “OK” and “OK” to save the settings and exit IIS.
Then in web.config use this connection string: "data source=yourservername;initial catalog=databasename;Integrated Security=SSPI"
From this source: http://weblogs.asp.net/achang/archive/2004/04/15/113866.aspx
|
|
|
|
|
joannew
DNN Creative Magazine Subscriber
Nuke Ace
Posts:58
|
| 07 Aug 2008 4:45 PM |
|
My first website is currently running in a browser and the. login is okay but some modules show errors and are not displaying, such as Quick Links Module, Announcements Module, Nuke News Module & Ultra Photo gallery.
Also the website is running very slow...
Any ideas where to start fixing these problems?
thanks alot... |
|
|
|
|
leesykes
DNN Creative Staff
Nuke Master III
Posts:3112
|
| 11 Aug 2008 4:50 AM |
|
Hi Jo,
For some reason this post caused an error in the forum so I had to delete it, but here is a copy:
Error with Nuke News
Module fixed by editing Controls/TextEditor.ascx
changed to
http://www.codeflakes.net/blog/post/Windows-update-causes-DotNetNuke-to-fail.aspx
Still looking to solve:
QUICK LINKS
Error: Quick Links is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException:
C:\DotNetNukeSites\rainfordwebsite_337\DesktopModules\Links\Links.ascx(7):
error BC30451: Name 'NoWrap' is not declared. --->
System.Web.HttpCompileException: C:\DotNetNukeSites\rainfordwebsite_337
ANNOUNCEMENTS
Error: Notice Board is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException:
C:\DotNetNukeSites\rainfordwebsite_337\DesktopModules\Announcements\Announcements.ascx(7):
error BC30456: 'Page' is not a member of
'ASP.desktopmodules_announcements_announcements_ascx'. --->
System.Web.HttpCompileException: C:\DotNetNukeSites\rainfordwebsite_337
|
|
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts |
|
|
leesykes
DNN Creative Staff
Nuke Master III
Posts:3112
|
| 11 Aug 2008 4:56 AM |
|
You should not need to make changes to the modules when installing on localhost, they should just work. I would double check that your web.config file has the connection string changed in both places - there are 2 places int he web.config file to enter the connection string.
The problems may still be coming from the setup of your SQL Server.
|
|
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts |
|
|