Imran -

I took a look at the source code related to this issue and can see that with the introduction of the new DST aware time-zone feature, an automatic update to a user's profile information may occur when their profile information is first loaded and that this issue could happen if a newly created user's UserId is still -1 at the time the update to the preferred time-zone profile property occurs. I was, however, not able to reproduce the issue in either a fresh DNN 6.01.01 source install or in one that was upgraded through several versions from 5.06.03.

Please answer the following questions to help reproduce and track down the cause of this issue:

1. Which user registration mode is selected in Site Settings, Advanced Settings, Security Settings? Private, Public, or Verified?

2. Are any non-default options for registration set in User Accounts, User Settings, User Account Settings?

3. Is the requirement for a valid user profile on registration enabled in User Accounts, User Settings, User Account Settings?

 

---

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

Hi Daniel,

William, hit it on the spot.  A User Profile Property is trying to be inserted for a UserID with an id of -1.  To correct this, one of the stored procedures need a tweak, namely UpdateUserProfileProperty.

The ELSE in the sproc needs to have the following conditional statement on it: 

ELSE IF @UserID IS NOT NULL AND @UserID > -1

This should hopefully resolve your Foreign Key issue.

.::. Vince.

It's a long shot, but I'm having the SAME exact issue. Did you ever figure out how to fix this?

Thanks!

Josh