I have a user that is trying to change his displayname and gets the comment that the displayname already exists. I double checked with the SQL statement from the pinned posting about the duplicates and no duplicates were found. However, when using the edit profile option in Active Social it keeps on telling me that there are duplicates.

Do you have multiple portals? Does the name exist in another portal?

Yes, I do have multiple portals. I have a user with the same display name and already changed that name to something else. But when I tried change the name back into the one that is supposed to be duplicate I got the message that the display name already existed.

I checked in my third portal and there it was again. I previously didn't check because I didn't use Active Social in that portal. It would be nice if vanity URLs do have to be unique within one portal and not throughout an entire DNN installation. Could you please implement this (if this is the true reason for my duplicate name)?

Thanks in advance

Will,

I forgot to mention that I already checked the "Unique Displayname Required" in the member config section of the control panel quite a while ago. These duplicates across the portals have been there all the time but this issue never surfaced because I didn't activate the vanity URLs up till now.

Will,

How can I get around this? Is this more or less the same issue as with post countings of users that have the same user name across different portals within one DNN installation? If so, I hope you can create a setting that makes it possible to enable/disable this behavior.

Thanks in advance.

i have this same problem. is there a resolution for this. In my case i created another column with the same name as another. then i deleted it. But the error says i still have duplicates. Did this go to some trash can somewhere that i can empty.

error log:
Error: Members is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The column name "email" specified in the PIVOT operator conflicts with the existing column name in the PIVOT argument. The column 'email' was specified multiple times for 'pu'. ---> System.Data.SqlClient.SqlException: The column name "email" specified in the PIVOT operator conflicts with the existing column name in the PIVOT argument. The column 'email' was specified multiple times for 'pu'. at System.Data.SqlClient.SqlConnection.OnError(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.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at Active.Modules.Social.Data.MembersDB.MembersList(Int32 PortalId, Int32 RowIndex, Int32 MaxRows, Int32 CurrentUserId, Boolean FriendsOnly, Boolean FriendStatus, String Alpha, String Fields, String Query, Int32 QueryType, Int32 Sort, Int32 GroupId, Int32 RoleId, CurrentUserTypes CurrentUserType, Int32 SortColumn, String SortDirection, Boolean IsAdmin, Boolean OnlineOnly) at Active.Modules.Social.Controls.MembersList.BindMembersList(Int32 pg) at Active.Modules.Social.Controls.MembersList.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Hi Richard,

I am not sure about your issue becasue I didn't create any additional email column. Hopefully someone else is able to comment on this. As far for the script you're referring to I don't believe there is any to solve the duplicate names accros multiple portals. The script you should be able to find in the forums over here is taking care of duplicate displaynames within the same portal.

If I recall it right I believe the reason for the current way of working is because it is convenient for users who use child domains within the same portal. This way they don't have to create another username. Unfortunately this is inconvenient for people who have multiple portals which are not related in any way but do have users which have similar names and also have similar display names.

So currently the only way to avoid this is to create another displayname.

I would like to see a resolution to this. Specifically, for the user names across multiple portals.

If "Joe" is an admin/user in Portal 1, can "Joe" (a different guy) be a user/admin in Portal 2? Both with the User Name/Login name of Joe...