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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...DNN Upgrade 6.0DNN Upgrade 6.0
Previous
 
Next
New Post
8/1/2011 9:27 PM
 
Clive, your error should be safely ignored, did it show up in 06.00.00.log file or one with a previous version number?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/2/2011 12:51 AM
 
Hi Sebastian,

It showed up in the version 6 log file. Everything is still working fine so I will ignore it.

Thanks for letting me know.
 
New Post
10/2/2011 4:30 PM
 
Is it possible that this error would affect File Manager? I've got a similar error (See log below)

System.Data.SqlClient.SqlException: There is already an object named 'FK_Files_Folders' in the database.
Could not create constraint. See previous errors.
   at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)






ALTER TABLE jumphrey_usra6bc80f541c5e90fbed457cfb25bb95a.[Files] ADD
CONSTRAINT [FK_Files_Portals] FOREIGN KEY ([PortalId]) REFERENCES jumphrey_usra6bc80f541c5e90fbed457cfb25bb95a.[Portals] ([PortalID]),
CONSTRAINT [FK_Files_Folders] FOREIGN KEY ([FolderID]) REFERENCES jumphrey_usra6bc80f541c5e90fbed457cfb25bb95a.[Folders] ([FolderID]) ON DELETE CASCADE


And now File Manager is giving me the following.


Error: File Manager is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.FileSystem.FolderProvider.Instance(String friendlyName) at DotNetNuke.Services.FileSystem.FolderMappingInfo.get_ImageUrl() at DotNetNuke.Modules.Admin.FileManager.FileManager.PreloadFolderImages() at DotNetNuke.Modules.Admin.FileManager.FileManager.InitializeTree() at DotNetNuke.Modules.Admin.FileManager.FileManager.OnLoad(EventArgs e) --- End of inner exception stack trace ---

Help????
 
New Post
10/2/2011 8:32 PM
 
Clive and Jon,

It appears that there is a missing {databaseOwner} token in the portion of the 06.00.00.SqlDataProvider script which is supposed to drop the existing FK_Files_Folders foreign key constraint before it is re-created:

IF EXISTS (SELECT * FROM sys.foreign_keys WHERE object_id = OBJECT_ID(N'{databaseOwner}[FK_{objectQualifier}Files_{objectQualifier}Folders]') AND parent_object_id = OBJECT_ID(N'[dbo].[{objectQualifier}Files]'))
 ALTER TABLE {databaseOwner}[{objectQualifier}Files] DROP CONSTRAINT [FK_{objectQualifier}Files_{objectQualifier}Folders]
GO

In the above (copied from 06.00.00.SqlDataProvider), I have highlighted in yellow the incorrect reference to [dbo]. as the database owner. These characters including the period should be replaced with

{databaseOwner}

This will affect only those installations using a non-dbo database owner such as "nicebloke" or jumphrey_usra6bc80f541c5e90fbed457cfb25bb95a in Clive's and Jon's installations.

I will log this as an issue in Gemini. I am not sure if Jon's File Manager error is related or due to some other issue. As Sebastian noted, an error involving failure to drop/recreate a foreign key constraint can often be ignored if no other issues with the upgrade are noted.

In the meanwhile if Clive can confirm the same File Manager error as Jon, and if you created good filesystem and database backups prior to the upgrade I would suggest rolling the installation back to the prior versions, making the above change to the 06.00.00.SqlDataProvider script, then re-applying the upgrade (including the corrected script).

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
10/2/2011 8:56 PM
 
I have logged the missing {databaseOwner} issue to Gemini as DNN-18044 as it did not appear to have already been reported. I also noted that Jon has already logged his (possibly related) FileManager issue ad DNN-18043.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...DNN Upgrade 6.0DNN Upgrade 6.0


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