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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Upgrade from 7.03.04 to 7.04.00DNN Upgrade from 7.03.04 to 7.04.00
Previous
 
Next
New Post
8/7/2015 11:42 AM
 
As I said before... We thought the action your hoster took would have made it go away.

So it's a different error; the action didn't work; or we were wrong. We need accurate data to advise you.

Personally I have an intense dislike of changing the standard scripts. When you do that, you are in some way making your install non-standard. IMO that is a risky thing to do unless there is a really good reason. I believe it will make things harder later on.

I'd vote for getting the exact error message. Anything else is just guessing.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
8/7/2015 12:41 PM
 

I tried again and here is the exact error along with a screen shot.
I am going to have to restore again.

Hopefully this tells you something.

25% ERROR occured - System.Data.SqlClient.SqlException (0x80131904): Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteScriptInternal(String connectionString, String script) ClientConnectionId:342b9355-cdda-4f89-97ff-83cedbe4f1a7 -- make sure we don't have any duplicate amail addresses on portals where Registration_UseEmailAsUserName is turned on -- if so we need to turn off the feature here DECLARE @PortalId int DECLARE @DupCount int DECLARE Portals_Cursor CURSOR FOR Select PortalId from dbo.[PortalSettings] Where SettingName = 'Registration_UseEmailAsUserName' and SettingValue = 'true' OPEN Portals_Cursor FETCH NEXT FROM Portals_Cursor INTO @PortalId WHILE @@FETCH_STATUS = 0 BEGIN set @DupCount = ISNULL((SELECT COUNT(*) TotalCount FROM dbo.[Users] U Inner Join dbo.[UserPortals] UP on UP.[UserId] = U.[UserId] WHERE UP.PortalId = @PortalId GROUP BY U.[Email] HAVING COUNT(*) > 1), 0) if(@DupCount > 0) BEGIN Update dbo.[PortalSettings] set SettingValue = 'false' where SettingName = 'Registration_UseEmailAsUserName' and PortalID = @PortalId END FETCH NEXT FROM Portals_Cursor INTO @PortalId END CLOSE Portals_Cursor; DEALLOCATE Portals_Cursor; /******************************************************** * Table: PortalSettings (allow CultureCode Null, DNN-5743) ********************************************************/ --Drop Foreign Key IF EXISTS ( SELECT * FROM Sys.Foreign_Keys WHERE object_id = OBJECT_ID(N'dbo.[PortalSettings]') AND name = N'FK_PortalSettings_Portals') BEGIN ALTER TABLE dbo.PortalSettings DROP CONSTRAINT FK_PortalSettings_Portals END   

 

 

 
New Post
8/7/2015 2:03 PM
 
You will need to restore.

OTOH it was worth it. The error message ("Subquery returned more than 1 value. ...") tells us it's not a problem with ALTER. Possibly it never was.

Unfortunately, from the message and the pasted text, it's not clear to me exactly what it is complaining about. I think you need someone more expert in that area than I am.

The comments in that area suggest it is checking that there are no duplicate email addresses on portals that use the email address as the user name. The comments also say that it is supposed to 'correct' that by turning the setting off if needed. I see nothing obvious in the code that would cause it to fail in the way it has.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
8/10/2015 4:04 AM
 
There are known issues with 07.04.00.sqldataprovider file included with DNN.
I suggest re-starting the upgrade from scratch, but replacing this file with the version attached to https://dnntracker.atlassian.net/brow...

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/27/2015 10:33 AM
 

Hi Sebastian,

Thanks for the info.  I think I will wait until 7.4.2 comes out before I attempt another upgrade.  My site is back up and I will not have a window to upgrade until end of September.

Do you think I will still have to replace the file when it comes out or will the latest code have it included.

Thanks,

James

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Upgrade from 7.03.04 to 7.04.00DNN Upgrade from 7.03.04 to 7.04.00


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