 |
|
|
www.devils-scorpions.co.uk
Joined: 3/19/2006
Posts: 5
|
|
|
trac3r726 wroteHello,
I am unable to get my SQL 2000 DB to connect. I am very sure i did not comment the connection correctly. Can someone help.
DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )
ERROR: Could not connect to database.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Steven
I have exactly the same error, Ive followed and read the upgrade instructions precisly, Ive not done this before so I dont even know where to begin with trying to solve it :(
|
| |
|
|
 | |
|
|
Joined: 8/23/2006
Posts: 3
|
|
|
gshergold wrote
dnn_johnny wrote
gshergold wrote
mjdarrow wrote
Greg:
I am just about to do an upgrade from 4.0.3 to 4.3.4. I have never done an upgrade before, and the upgrade document looks to be specific to upgrading from 3x to 4x. Can you point me towards instructions more specific to the upgrade I need to execute?
Kind Regards,
Mitch |
I'm doing this on the same upgrade path as you. I'm running on my test machine, and I am having nothing but nightmares. It doesn't seem to be a free and clear upgrade (as they have been in the past.)
There's nothing worse than looking at the upgrade process appear to work, then any of your current modules (eg anouncements, text/html modules comming up with errors, and not displaying any content) Thank goodness this is on a test system.
The one good thing durning this process, I am becoming an expert on restoring to the previous working state
Cheers,
Greg
|
I went through the process about four times last week. I had a problem with DNN not creating the DesktopModules directory. Finally, I had to use the VSI for Visual Studio compile and run everything and manually copy my DLLs and folders that were missing to my DNN directory. Don't know what I was doing wrong. I believe that is a real weakenss in DNN - the upgrade. I don't mean that disprespectful. Hey, the product is free. I'm thankful for it. But it is hard to upgrade. I was going from 3.3.3 to 4.3.4. I'm still not sure if it is working right. I had problems with pages not updating correctly www.mysite.com being different from mysite.com, errors with the host account controls. then they magically started working. I'll have to monitor it to make sure it keeps working. | I finally got mine to work on my test box. Most of it came down to the filling out of data in the release/web.config file properly. The couple gotchas that got me were: (BTW my setup is with SQL2K)
- By default, in the release.config file, the SQL Express stuff is enabled. Comment this stuff out.
- By default, in the release.config file, the SQL2003/SQL2000 stuff is commented out. Need to uncomment this stuff out and get the connection strings filled out.
- By default, the legacy conneciton strings are commented out for SQL2003/SQL2000. SQL Express is enabled. Had to uncomment and comment out like above.
- But for what ever reason (could be the editor I was using ) the connection string in the "legacy" section didn't copy properly. <--- This was the one that was really causing my issues. I'm not sure what happned at this step, but in my series of troubleshooting/restoring etc., I managed to make this error on each and every of the previous *5* upgrade attempts. I kept each of the previous unsuccessful upgrade attempts for comparison and did this on the previous ones also. I still don't know why this happened, but this is what was causing my upgrade woes.
- The encryption section made it over each and every time. I though this would have been this part that woudl have screwed me up.
So for the most part, my issues were with the release/web config file. So in the end, these were my final steps (note this is for and upgrade from 4.0.3 to 4.3.4):
- BACKUP! BACKUP! BACKUP! (back up that database, backup your files) I personally like burning it to CD since your file then won't get contaminated if you mess up on a copy location.
- Rename your current web.config file. I tend to use dates in my "renaming" process. So it ended up somthing like this... web.2006.08.12.config.old
- Extract the 4.3.4 upgrade package and copy everything from that into your DNN structure. Replace all files/directorys as needed.
- Make a copy of the release.config and rename that copy to web.config
- Make your changes to this new web.config file (comment out/uncomment you required connection string, fill out the proper information as required, don't forget your encryption keys also) Also if there are any custom modules/changes you have made, you will need to also add those in.
- Save your webconfig file, and cross your fingers.
- Go on to your website, and the upgrade process should start and do it's thing.
This was the process I ended up doing in the end. Pretty similar to what the docs recommend. All I say say, is make sure that web.config file is done properly. OHh yeah, and BACKUP, BACKUP, BACKUP!!!
Cheers,
Greg
I'm having similar problems. This is a fresh install of DNN 4.3.4. My hosting provider (Godaddy) is using MS SQL 2000 and provides DNN 4.0.3 for use. I am currently using that. I am developing a new website, though, so I don't have to upgrade; I can go with a new install.
I have commented out the connection strings for SQL 2005 Experess and uncommented the SQL2000/2005 connection strings. I get the error below. I have no idea how to interpret it.
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration> |
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration> |
|
| |
|
|
| |
|
|
Joined: 6/15/2005
Posts: 29
|
|
|
I'm having similar problems. This is a fresh install of DNN 4.3.4. My hosting provider (Godaddy) is using MS SQL 2000 and provides DNN 4.0.3 for use. I am currently using that. I am developing a new website, though, so I don't have to upgrade; I can go with a new install.
I have commented out the connection strings for SQL 2005 Experess and uncommented the SQL2000/2005 connection strings. I get the error below. I have no idea how to interpret it.
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".
I've run into this a few time. When couple times I have encountered it, it's due to the mis-configurations in the web.config file.
Connection strings, make sure they are correct. Make sure they are correct in both parts of the web.config file (the main connection string and the legacy connection string.) Also make sure your sever name/IP address and username/password are also correct for connecting to your database.
I'm not sure how Godaddy has their servers configured, but if you had a previous version running on it, I would compare the the web.config files (specificly the connection strings) to make sure things are the same.
Cheers,
Greg
Cheers,
Greg
|
| |
|
|
| |
|
|
Joined: 9/9/2006
Posts: 1
|
|
|
I am also installing DotNetNuke and am a little unsure of what to install.
I have Visual web developer 2005 Express installed. As I learn how to use DNN I do plan to develop skins and modules but for now I just want to work with it for a while.
Can I upgrade later to the full source and just use the starter kit to get started?
|
| |
|
|
| |
|
|
www.stadts.us
Joined: 7/30/2003
Posts: 5
|
|
|
Why are all the messages in this forum repeated. You get one question then an answer then the same question (not from someone else but the SAME QUESTION and then THE SAME ANSWER. Is this a robot like the recipe answer book for AIM from Bisquick or something. Things have gone terribly wrong in the installation process. Shawn (Shaun) whatever, is describing the different install packages but not the internals as to why they don't work. Have you taken a 2.1.2 with several portals and done a clean upgrade to 3.3.4. Obviously not because it doesn't work! I guess the europeans are right, we americans are just too stuck on ourselves to think that maybe something really is broken. Time to look for a some new revelations. For both of us! And by the way, get rid of the stupid smiley stuff. It looks so childish it is almost embarrassing! 
|
| |
|
|
| |