I just uploaded the User Directory module, added it to a page and clicked the setup initial settings. And the following error occured. I've deleted and uploaded the module again with the same error result. Please Advice?  thank you

ERROR!:Incorrect syntax near 'and'. 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 DataSprings.DNN.Modules.DynamicUserDirectory.Data.SqlDataProvider.DataSprings_RetrieveDNNUserProfileData(Int32 PortalID, String RoleFilter, String LimitResults) at DataSprings.DNN.Modules.DynamicUserDirectory.Business.DynamicUserDirectoryController.DataSprings_RetrieveDNNUserProfileData(Int32 PortalID, String RoleFilter, String LimitResults) at DataSprings.DNN.Modules.DynamicUserDirectory.Common.GetDotNetNukeUserFields(Int32 PortalID, Int32 TabId, Int32 ModuleID) at DataSprings.DNN.Modules.DynamicUserDirectory.Settings.BindDotNetNukeFields() at DataSprings.DNN.Modules.DynamicUserDirectory.Settings.LoadSettings()

Hi. Well we recently covered this issue in a support case (not sure if it was yours) but we are aware of what is happening.

Basically, Dynamic User Directory changed the way it works with the latest edition, in that all profile properties were built together in a very complex stored procedure which drastically speeds up displaying user data within the directory. It does this by 'building' a SQL query in the stored procedure called 'DataSprings_RetrieveDNNUserProfileData'. The problem with this (especially with SQL Server 2000 and not 2005) is that the text ends up being over 8000 characters on some implementations that use a large number of profile properties), and the SQL server doesn't allow for more character than that. So, whats happening is that because your DNN installation includes a large number (I am guessing more than 30-40 or so?) extra profile properties its getting truncated at character 8001 and now allowing it to be able to work properly. so... A few options.

1. You can delete some profile properties but you probably don't want to do that You can view your entire list under Admin, User Accounts, Manage Profiles Properties.

2. We can get you the version before this latest one. The previous version will be a little slower but it should allow for as many profile properties as you need.

3. You can tell us a 'specific category' such as 'Admin' or 'Professional Preferences' and we can exclude that within the query. Therefore, when it renders it will ignore those profile properties and should work.

My vote is for number 3, are there any specific profile properties that can be excluded from the directory, or do you need them all?

Finally... One last option is to get you a refund if this will not work for you. We will continue to research what we can do on this end, we have only a limited number of users running into this at this time (you are the 2nd one) but based on performance reasons we really had to head in this direction for this module.

Oh... And for us to assist with number 3 you will need to open a support ticket, or I can tell you the lines within the stored procedure if you are familiar with modifying a stored procedure.


-Chad

Number 3 is working for me. Excluding some profile properties from the directory -which I wasn't using for this module anyway- did the trick. The module is working great now. Thanks for the fast support. Great service !