Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...04.05.01.SqlDataProvider Error04.05.01.SqlDataProvider Error
Previous
 
Next
New Post
5/16/2007 5:46 PM
 
I have some simple questions related to the upgrade of DotNetNuke from 04.04.00 to 04.05.01 as an non experienced DotNetNuke admin.
 
1)      There are many articles on the web proposing that an “<add key =”InstallationDate” value=?” /> should be added to the web.config file. In the case that the web.config file does not include this value, how do one determine at correct date? In the catalog Providers\DataProviders\SqlDataProvider there are some version.log files. Can one determine installation date based on the date of the first version.log (in my case 03.01.01.log) file, or just any date just to prevent encryption keys to be overwritten? Can this be confirmed?
  
2)      There is upgrade problems related to “04.05.01.SqlDataProvider Error!”. These problems seems to be related to SQL routines 04.05.01.SqlDataProvider (..\Providers\DataProviders\SqlDataProvider), that in my case are missing ObjectQualifier has been used in the web.config file. Apparently this problem can be fixed (see below). Thise will make may website function in may test environment. Can this be confirmed?
 
BEFORE:
/* correct any File folderpaths which do not match the value in the Folders table */
update {objectQualifier}Files
set Folder = FolderPath
from    {objectQualifier}Folders
where {objectQualifier}Files.FolderID = {objectQualifier}Folders.FolderID
and Folder <> FolderPath 
GO
 
AFTHER:
/* correct any File folderpaths which do not match the value in the Folders table */
update {databaseOwner}{objectQualifier}Files
set Folder = FolderPath
from    {databaseOwner}{objectQualifier}Folders
where {databaseOwner}{objectQualifier}Files.FolderID = {databaseOwner}{objectQualifier}Folders.FolderID
and Folder <> FolderPath 
GO
 
3)      When the abow fix has been entered the “04.05.01.SqlDataProvider Error!” will still appear in may case. The fix as I understand this is therefore to delete double records in the files xxx_Files and xxx_Folder, and this can be done by deleting all record with <Null> in the portal ID column. Can this be confirmed?
 
New Post
5/17/2007 10:13 AM
 

1.  You can put any date in that is prior to today for the installationDate value as far as I know.  The purpose of that key is to prevent DotNetNuke from changing your machineKey values

2.  Yes, as far as I know that is the only object qualifier issue within the upgrade script

3.  I believe you are correct, the biggest thing is to remove anything where the same file/folder is declared twice for the same portal.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
5/17/2007 5:08 PM
 
Tank you for our help!
 
Reporting back
I have done it. I am now reporting back my experience to others that may need it. In my case I could not delete records containing <Null> in the PortalID field. These records seems to relate to the super user account, and they existed in the catalog structure on disk. I therefore started with the xxx_Folders file. Using MS Access unique query, I found duplicates Folder Paths. Using these FolderIDs I then investigated the xxx_Files listing file names and investigating these items for duplications. A tedious job for me because I have some thousand screen shot files.
 
New question
Lest say that I have deleted a catalog and some files to many. Will the new version repopulate this in a correct manner using file manager in DotNetNuke after the upgrade?
 
New Post
5/18/2007 10:09 AM
 

Just to ensure everyone looking here I will repeat my answer from my webiste.

Yes, the sync operation "SHOULD" find all files.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
7/10/2007 6:28 PM
 
Tank you Mitchel!
You where a life saver!
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...04.05.01.SqlDataProvider Error04.05.01.SqlDataProvider Error


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out