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...5.6.1 -> 5.6.2 upgrade gave SqlDataProvider Error5.6.1 -> 5.6.2 upgrade gave SqlDataProvider Error
Previous
 
Next
New Post
4/5/2011 2:20 PM
 
The upgrade mostly went fine, and the site seems to be working normally.  However there was one error that came up:
00:00:00.421 -   Executing Script: 05.06.02.SqlDataProvider Error! (see 05.06.02.log.resources for more information)

In that log there are 18+ errors.  Many of the errors are CREATE statements where the object already exists.  Yet when I look in the source, it does not match the SQL in the log:

e.g:
In the 05.06.02.log.resources Log file:

CREATE procedure dbo.DeleteFolder
 @PortalID int,
 @FolderPath nvarchar(300)
AS
 DELETE FROM dbo.Folders
 WHERE ((PortalID = @PortalID) or (PortalID is null and @PortalID is null))
 AND FolderPath = @FolderPath

System.Data.SqlClient.SqlException (0x80131904): There is already an object named 'GetFolderPermissionsByFolderPath' in the database.


The current code on the server is (did a script -> create to:):
CREATE PROCEDURE [dbo].[DeleteFolder]
@PortalID int,
@FolderPath nvarchar(300)
AS
BEGIN
IF @PortalID is null
BEGIN
DELETE FROM dbo.Folders
WHERE PortalID is null AND FolderPath = @FolderPath
END ELSE BEGIN
DELETE FROM dbo.Folders
WHERE PortalID = @PortalID AND FolderPath = @FolderPath
END
END


So there are 18 of these types of errors in the log.  Do I need to go through each one and make sure they are manually run?  Why did this error happen?   Any help would be greatly appreciated.

Thanks,
-Steve

 
New Post
4/5/2011 7:50 PM
 
In the specific error you posted, the Create Procedure apparently failed because the immediately prior attempt to drop the existing stored procedure either did not run or failed. Consequently the old (5.6.1 or prior) code remains in effect. I suspect that the other 18+ errors are similar. The question then is why did the upgrade script either fail to see that a stored procedure of the same name already existed and did not perform the drop or the drop failed. I checked the 5.06.02.SqlDataProvider script for this drop-create and a couple of others and all appears to be correct regarding proper use of the {objectQualifier} and {databaseOwner} tags which can sometimes be the cause of this problem.

Please check that the SQL login being used in the web.config connection string had been granted db_owner role on the database and that the objectQualifier=". . ." and databaseOwner= " . . . "  attributes in the <add name="SqlDataProvider" . . ./> node near the end of the web.config have the values of an empty string and "dbo" respectively and that those values did not change from the original installation.

If there were no other errors than what you found in the 05.06.02.log.resources file, I would try manually running each drop procedure-create procedure script in the Host-->Sql command window with "Run as Script" checked which will make the {databaseOwner} and {objectQualifier} token replacements automaticall or in SQL Server Management Studio after making the token replacements manually in the 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
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...5.6.1 -> 5.6.2 upgrade gave SqlDataProvider Error5.6.1 -> 5.6.2 upgrade gave 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