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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogSQL Error on install of Blog5.0RC to DNN6.2SQL Error on install of Blog5.0RC to DNN6.2
Previous
 
Next
New Post
6/11/2012 7:40 PM
 

With a new install of 6.2.0 and I had gotten the error...

05.00.00 (RC) The stored procedure 'dbo.Blog_GetSettings' doesn't exist.

I ran the SQL script in this Thread to create the getsettings procedure.  Now get the following error....

A critical error has occurred. The stored procedure 'dbo.Blog_GetTermsByContentType' doesn't exist.

Seems like none of these procedures were created with the install.

 
New Post
7/30/2012 6:11 AM
 
Aha! :-) Most of the %Blog% items (tables, SPs, etc.) belong to/are named with the dbo. prefix, but the ones that are "missing" are named as . prefix, where is the user name that owns the DB.

So I think the important difference between my live system and my local system is that the live system uses SQL authentication and my local server is Windows auth.

I'm going to see if I can come up with a fix/workaround that does not involve uninstalling DNN. (Although the "live" server is still in testing/evaluation, and the domain has not been announced, so I could still remove everything..)

I think that a fix for a failed blog install is simply to change the DB owner (sp_changedbowner will do that).
 
New Post
7/30/2012 4:51 PM
 

Okay, I did manage to fix my system, and got the install to work on it. I should note that I have NOT done any in-depth testing, and only just placed the module on a page. But the errors that were there before have been fixed by the following.

The fix:

  1. Unzip the install zip.
  2. Open the "Install.05.00.00.SqlDataProvider" in a text editor.
  3. Replace all "CREATE PROCEDURE {objectQualifier}" with "CREATE PROCEDURE {databaseOwner}{objectQualifier}".
  4. Add that file back to the zip, replacing the original file. The resulting zip should install and work.

"Repairing" a broken SQL Server DB is a little trickier. This is completely unsupported, but if you need it, you can figure out how by following these steps:

  1. Back up everything. Twice. :)
  2. Uninstall the Blog module. This works, but leaves a few leftovers in the DB, so
  3. figure out the tables and procedures that you need to clean up. For tables, use "SELECT name FROM sys.objects WHERE name like '%Blog%' and type = 'U' order by name". For procedures, it's the same query, but change the 'U' to 'P'.
  4. I just copied these and saved to a text file, and inserted at the beginning of each row, "drop table " and "drop proc ", respectively, on each line.
  5. Run the resulting SQL.
  6. You should be ready to reinstall the ("patched") module!

This is totally unsupported, unsupported - so backup everything (again!) before you continue. Also note that running this against a working Blog system will certainly break it, and will cause you to lose all blog entries and data. If you still want to try, this is what worked for me:

drop table Blog_Blogs
drop table Blog_Categories
drop table Blog_Comments
drop table Blog_Entries
drop table Blog_Entry_Categories
drop table Blog_Entry_Tags
drop table Blog_MetaWeblogData
drop table Blog_Settings
drop table Blog_Tags

drop proc Blog_AddBlog
drop proc Blog_AddComment
drop proc Blog_AddEntry
drop proc Blog_DeleteBlog
drop proc Blog_DeleteComment
drop proc Blog_DeleteEntry
drop proc Blog_DelUnAppCommByEntry
drop proc Blog_GetAllEntriesByBlog
drop proc Blog_GetAllEntriesByPortal
drop proc Blog_GetBlog
drop proc Blog_GetBlogDaysForMonth
drop proc Blog_GetBlogMonths
drop proc Blog_GetBlogsByPortal
drop proc Blog_GetBlogViewEntryModuleID
drop proc Blog_GetComment
drop proc Blog_GetCommentsByBlog
drop proc Blog_GetCommentsByEntry
drop proc Blog_GetCommentsByPortal
drop proc Blog_GetEntriesByBlog
drop proc Blog_GetEntriesByDay
drop proc Blog_GetEntriesByMonth
drop proc Blog_GetEntriesByPortal
drop proc Blog_GetEntriesByTerm
drop proc Blog_GetEntry
drop proc Blog_GetSettings
drop proc Blog_GetTermsByContentItem
drop proc Blog_GetTermsByContentType
drop proc Blog_MetaWeblog_Get_DesktopModule_FriendlyName
drop proc Blog_SearchByKeyWordAndBlog
drop proc Blog_SearchByKeyWordAndPortal
drop proc Blog_SearchByPhraseAndBlog
drop proc Blog_SearchByPhraseAndPortal
drop proc Blog_UpdateBlog
drop proc Blog_UpdateComment
drop proc Blog_UpdateEntry
drop proc Blog_UpdateEntryViewCount
drop proc Blog_UpdateSetting
drop proc Blog_Upgrade_CategoriesGet
drop proc Blog_Upgrade_DeleteBlog
drop proc Blog_Upgrade_DeleteComment
drop proc Blog_Upgrade_DeleteEntry
drop proc Blog_Upgrade_GetCategoriesByEntry
drop proc Blog_Upgrade_GetSettings
drop proc Blog_Upgrade_GetTagsByEntry
drop proc Blog_Upgrade_ListBlogs
drop proc Blog_Upgrade_ListComments
drop proc Blog_Upgrade_ListEntriesByBlog
drop proc Blog_Upgrade_RetrieveTaxonomyEntries
drop proc Blog_Upgrade_TagsGet
drop proc Blog_Upgrade_UpdateModuleDefId

Best regards,
Leland...

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogSQL Error on install of Blog5.0RC to DNN6.2SQL Error on install of Blog5.0RC to DNN6.2


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