Peter Kipper
Customers
Post Count:2
 |
| 12 Jul 2010 11:39 AM |
|
After Installation and configuring, i have an error on the Profile Page. Under the Profile Image, ther is the error, that Active Social is not available, although on the Page Social Members. I dont know, where I must search for the incorrect Entry "Status". Error: ActiveSocial is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Der Spaltenname 'Status', der im PIVOT-Operator angegeben ist, steht mit dem vorhandenen Spaltennamen im PIVOT-Argument in Konflikt. Die 'Status'-Spalte wurde für 'pu' mehrmals angegeben. ---> System.Data.SqlClient.SqlException: Der Spaltenname 'Status', der im PIVOT-Operator angegeben ist, steht mit dem vorhandenen Spaltennamen im PIVOT-Argument in Konflikt. Die 'Status'-Spalte wurde für 'pu' mehrmals angegeben. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.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 --- |
|
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
 |
| 12 Jul 2010 12:01 PM |
|
This means you have a duplicate profile field named "Status". Once you rename the property in DotNetNuke this error will no longer appear. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Matt Marlor
Customers
Post Count:375
 |
| 12 Jul 2010 02:31 PM |
|
Adding onto Will's comments - even if the profile field has been deleted, it will still exist in the database and will need to be renamed via SQL query. |
|
| AuTechHeads - An Australian group for geeks. Visit us at
http://www.autechheads.com! |
|
|
Peter Kipper
Customers
Post Count:2
 |
| 13 Jul 2010 02:22 PM |
|
Thank you, it was the right way. There was only one Item "Status", but after deleting in Profile ans Database, the error was gone. |
|
|
|
|
Jacob Black
Registered Users
Post Count:11
 |
| 20 Jul 2010 07:11 PM |
|
I get a similar thing when trying to perform a search in the member's list. The event view shows this error: ModuleId: 750 ModuleDefId: 143 FriendlyName: MHPN Online Members ModuleControlSource: DesktopModules/ActiveSocial/Main.ascx AssemblyVersion: 5.4.1 PortalID: 0 PortalName: Mental Health Professionals Network UserID: 2 UserName: admin ActiveTabID: 190 ActiveTabName: Members RawURL: /MHPNOnline/Members/tabid/190/query/j/Default.aspx AbsoluteURL: /Default.aspx AbsoluteURLReferrer: http://mhpn.org.au/MHPNOnline/Members.aspx UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729) DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: 7ccf3250-0e4b-48e6-87da-532472a414af InnerException: The multi-part identifier "up.PropertyValue" could not be bound. FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: System.Data.SqlClient.SqlConnection.OnError StackTrace: Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The multi-part identifier "up.PropertyValue" could not be bound. ---> System.Data.SqlClient.SqlException: The multi-part identifier "up.PropertyValue" could not be bound. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.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 --- Source: Server Name: DL00009 |
|
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
 |
| 21 Jul 2010 10:41 AM |
|
Jacob, This error occurs when change the default sort order for the members list to a profile property that not all users have or updated. Change the sort order back to UserId and the error will no longer occur. Before you can use the other sort order again you will need to make sure all users have a value stored for that property. I would also suggest updating the profile property so that it has a default value. This will make sure the problem doesn't happen again. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Jacob Black
Registered Users
Post Count:11
 |
| 21 Jul 2010 08:36 PM |
|
Thanks Will, that's fixed it finally. |
|
|
|
|
Untanglemyweb
Customers
Post Count:31
 |
| 06 Oct 2010 02:38 AM |
|
Posted By Will Morgenweck on 21 Jul 2010 11:41 AM
Jacob, This error occurs when change the default sort order for the members list to a profile property that not all users have or updated. Change the sort order back to UserId and the error will no longer occur. Before you can use the other sort order again you will need to make sure all users have a value stored for that property. I would also suggest updating the profile property so that it has a default value. This will make sure the problem doesn't happen again.
Hi Will , I got exactly the same error as Joe. I also noticed it only happens when doing a search in Member directory view with sorting by "Last Name" field, or"First Name". I can do search if sorted by "UserID".
You suggested that "Before you can use the other sort order again you will need to make sure all users have a value stored for that property. " The problem is the "Last Name" field is compulsory in DNN. So every user should have the value stored, thus I should be able to sort by that field. Am I right?
Appreciate your help. Thanks, Alan |
|
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
 |
| 06 Oct 2010 06:26 AM |
|
You suggested that "Before you can use the other sort order again you will need to make sure all users have a value stored for that property. " The problem is the "Last Name" field is compulsory in DNN. So every user should have the value stored, thus I should be able to sort by that field. Am I right? Yes and No. Yes the field is required, but that doesn't mean DNN stored the data properly or that all users actually provided a valid entry. If this is a brand new site and all users were created directly from the registration form then I would suspect some other problem. However, if this is a site that has been upgraded from several versions of DotNetNuke OR users were imported then more often than not, there might be some bad data in the profile tables. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Untanglemyweb
Customers
Post Count:31
 |
| 06 Oct 2010 08:36 PM |
|
if this is a site that has been upgraded from several versions of DotNetNuke OR users were imported then more often than not, there might be some bad data in the profile tables. Hi Will, Thanks a lot for replying. I checked and the error still occurs. Our site was created with DNN5.4.4, and the users were imported. Then we upgraded DNN to 5.5.1. But the problem(sorting by LastName) with search has always existed. I carefully checked the dob.Users table with 'LastName' field. And I made sure there were no bad data, meaning just one word last name. And the same error message occurs. I also checked the dbo.profile table, did not think there were anything wrong. When you say "there might be some bad data in the profile tables.", did you mean just dbo.users, and dbo.profile ? or you meant other table? I know this is really weird, and I really can't think of any other reason. Do you have any other ideas. Thanks, Alan |
|
|
|
|
Untanglemyweb
Customers
Post Count:31
 |
| 07 Oct 2010 09:24 AM |
|
hi Will, the information give is very useful. But we still can't get it working. Same error. I tested with another DNN live demo site, also got the same error when sorting by "LastName", It's so strange. Seems other people have no problem at all. And we have this problem for two standalone DNN sites. Any thoughts? Thanks Alan |
|
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
 |
| 07 Oct 2010 04:19 PM |
|
The LastName is actually a profile property. The first name and last name fields in the users table are there for backwards compatibility in legacy modules. When you import users, at a minimum, for every user in the users table there should be row in the UserProfile table for FirstName and LastName. If those fields don't exist then data for the user isn't valid. When I say isn't valid, I mean that the records in your database don't follow the same structure as when DNN would create a new user. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Untanglemyweb
Customers
Post Count:31
 |
| 07 Oct 2010 10:17 PM |
|
Hi, Will I do appreciate your help and patience very much. I thought this could solve the problem. But unfortunately it did not solve the error. We have made sure that every user in the users table have record in UserProfile table for Firstname and LastName. Actually I found that only host account does not have FirstName and LastName in the UserProfile table. The rest of the users do have record in both tables. I also tested this approach in another test live site whose users were not imported, and tested on a localhost DNN instance. They all threw the same error. I really don't know what was wrong. As I said seems most people don't have this problem except me. I feel sorry to have to drag you for this problem. Any help would be appreciated. Thanks Alan |
|
|
|
|
Will Morgenweck
Forum Admin
DotNetNuke Staff
Post Count:7672
 |
| 07 Oct 2010 10:30 PM |
|
Are you able to reproduce this on a clean DotNetNuke install with users that have been manually created? We can't reproduce it at all. I even just tested again on ActiveSocial.com and this site and it worked fine. The last time a similar issue was raised by a customer we spent several hours going through a customer database only to find out that profile data was missing. I don't want you to think I'm doubting you, but most of the import tools will leave data incomplete. Are you sure you are getting the same exact error as indicated above? There are two errors in this thread, both mean different things. Since you quoted Jacob I assumed you were referring to his error, but if you are getting the error that started this thread then we have another solution. |
|
Will Morgenweck
Director of Product Management
DotNetNuke Corp.
|
|
|
Gary
Customers
Post Count:46
 |
| 12 Mar 2011 03:36 PM |
|
Will / Matt
What is the script to renamed "Status" via SQL querye . I'm having the same problem. I have deleted the the field but need to have it renamed. I not familiar with SQL scripts or commands.
Thanks, Gary |
|
|
|
|