I can't get any results to show up in the DUD either from a page load or from a user-initiated search.

DNN Version: 5.4.4
DUD Version: 3.0.30

I've set up DUD along with Dynamic Registration on one portal, and after fixing the widely-reported issue where 5.4.4 won't allow the scheduler entry to be installed, I'm still having an error.

I've been through all of the steps found here: http://www.datasprings.com/News/Blo...ation.aspx

The tempDUDPIVOT and tempDUDProfile tables are populated.

There are 117 users on this portal, so there are results to be had.

The scheduler task runs successfully on both servers (it's a web-farm setup). Completion time is around 150ms. The event viewer shows no errors for this process or time period.

What am I missing?

Hello,

If you go to Host -> Schedule and go to the DUD scheduler and click "History" does it show successful creation of the tempdudpivot table?

Does it show failure?

Can you please go to Admin -> Event Viewer and tell me if you see any errors that look like they're related to the DUD scheduler?

If you have any questions please let me know.

Thanks,

Ryan

Hi... I am really not sure what else would cause the problem, if you can verify that the tempDUDPivot/Profile have data in them that is typically the biggest hurdle.

Do you have any other specifics specified such as record count, or maybe 'Disable results until search'? What about maybe a filter or anything?

Any other specifics on the server, does this site have an object qualifier? Is this the main portal or a child portal?

There is a 'Debug' mode that you can enable and you might want to enable it to see if this spits out some additional details.

-Chad

The scheduler is showing that it succeeds each time it runs. The tempDUD* tables are populated with data.

The event viewer does not have any errors related to DUD.

As for the module itself, 'Disable results until search' is unchecked. There is a filter for PortalID = 1, though it makes no difference if it's there or not, as I've tested without the filter, and nothing shows up. There are three search fields: username, first name, and last name.

Here's what 'Debug mode' shows when I click the 'A' link on the alphabetical filter:

([username] like '%%' OR [username] Is Null) and ([firstname] like '%%' OR [firstname] Is Null ) and ([lastname] like '%%' OR [lastname] Is Null ) and ( [username] like 'A%' )

Note that I removed the PortalID restriction for now.

If I run the following query against the database directly, I get 5 results.

select * from tempDUDPIVOT WHERE  ([username] like '%%' OR [username] Is Null) and ([firstname] like '%%' OR [firstname] Is Null ) and ([lastname] like '%%' OR [lastname] Is Null ) and ([username] like 'A%')

Hi,

Well actually portal ID is also already added as a filter to the query already (this way users don't show on portal 1 for portal 0 etc...). So, are you on portal 1? How many portals are on this installation?

Also, do you have the include or exclude by security role checked?

Thanks,

Chad

I have exclude selected, and only Administrators is checked, but I think your other statement settles why I'm not seeing anything.

If it already filters by portal, then it's not going to show me anything right now. I found that the users showing in the tempDUD* tables are all from the other portals on this installation. This portal has no users according to the tempDUD* tables. The portal does have 117 users, but they're apparently not picked up by the scheduler for some reason.

Hi. Well are these users authorized? Do they have valid data in profile fields that are marked as visible? Finding out why these users are not getting generated would probably be the next step I guess.

-Chad

The users are all authorized, and have proper usernames, first names, last names, etc. (These all come from the {objectQualifier}Users table anyway.)

I've noticed that some of the users in portal 1 are listed, but they have a PortalID of NULL.

Numerous users of the other 4 portals on this installation are in the tempDUD* tables.

Hi... In this case I really don't know why it would happen... Was this an upgrade or fresh installation? This would have to be setup within the stored procedure that 'creates' the TEMPDUDPIVOT which is this:

You might drop your procedure and recreate it such as below:
if exists (select * from dbo.sysobjects where id = object_id(N'{databaseOwner}{objectQualifier}DataSprings_RetrieveDNNUserProfileData3') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure {databaseOwner}{objectQualifier}DataSprings_RetrieveDNNUserProfileData3
GO



CREATE Procedure {databaseOwner}[{objectQualifier}DataSprings_RetrieveDNNUserProfileData3]
(@PortalID int,@RoleFilter nvarchar(1000),@LimitResults nvarchar(100),@Authonly int,@Filter nvarchar(4000))


AS

BEGIN


if exists(select top 1 * from sysobjects where xtype = 'U' and name = 'tempDUDProfile') and (@PortalID = 999)
begin
drop table {databaseOwner}tempDUDProfile
end

if exists(select top 1 * from sysobjects where xtype = 'U' and name = 'tempDUDPivot') and (@PortalID = 999)
begin
drop table {databaseOwner}tempDUDPivot
end

-- generate tempDUDProfile table
-- create table tempDUDProfile if not exists
If not exists(select top 1 * from sysobjects where xtype = 'U' and name = 'tempDUDProfile')
BEGIN

select U.userid,U.username,U.firstname,U.lastname,U.email,U.Displayname,UP.propertyvalue,
P.propertyname, P.PortalID into {databaseOwner}tempDUDProfile

from {databaseOwner}[{objectQualifier}Users] U inner join {databaseOwner}[{objectQualifier}userprofile] UP on U.userid = UP.userid
inner join {databaseOwner}[{objectQualifier}profilepropertydefinition] P on UP.propertydefinitionid = P.propertydefinitionid

--where U.userid In (Select userid from {databaseOwner}[{objectQualifier}UserPortals] where PortalID = Convert(varchar(3), @PortalID))

where P.Visible=1
--AND P.PortalID = @PortalID
AND P.Deleted=0
AND P.PRopertyName <> 'FirstName'
AND P.PropertyName <> 'LastName'
AND P.PRopertyNAme <> 'E-Mail'
AND P.PRopertyNAme <> 'Email'
AND P.PRopertyNAme <> 'Username'
AND P.PRopertyNAme <> 'Displayname'

AND P.PropertyName Not Like '%[.#)(&[@!^!]]%' ESCAPE '!'

exec {databaseOwner}[{objectQualifier}DataSprings_RetrieveDNNUserProfileData3a]

END



If (@PortalID <> 999)
BEGIN
Declare @MySQL nvarchar(max)
-- check if DNN version is 5.0 or higher
if exists (select * from INFORMATION_SCHEMA.COLUMNS where TABLE_NAME like '%userportals%' and COLUMN_NAME = 'IsDeleted')
and exists (select top 1 * from INFORMATION_SCHEMA.COLUMNS where TABLE_NAME like '%users' and COLUMN_NAME = 'IsDeleted')
BEGIN
Set @MySQL = 'select ' + @LimitResults + ' A.* from {databaseOwner}tempDUDPivot AS A' + '
inner join aspnet_users AS B on B.username = A.username
inner join aspnet_membership C on B.userid = C.userid '
+ replace(@Filter,'[','A.[')
+ replace(@RoleFilter,'[','A.[')
+ ' AND ((C.IsApproved = 1) OR (' + Cast(@AuthOnly as varchar(2)) + ' = 0))'
+ ' AND A.PortalID = ' + cast(@PortalID as varchar(3))
+ ' AND A.userid not in (select userid from {databaseOwner}[{objectQualifier}users] where issuperuser = 1 and isdeleted = 1)
AND A.userid not in (select userid from {databaseOwner}[{objectQualifier}userportals] where isdeleted = 1 AND portalID = '
+ cast(@PortalID as varchar(3)) + ')'
EXECUTE(@MySQL)
END
else
if exists (select * from INFORMATION_SCHEMA.COLUMNS where TABLE_NAME like '%userportals%' and COLUMN_NAME = 'IsDeleted')
and not exists (select top 1 * from INFORMATION_SCHEMA.COLUMNS where TABLE_NAME like '%users' and COLUMN_NAME = 'IsDeleted')
BEGIN
Set @MySQL = 'select ' + @LimitResults + ' A.* from {databaseOwner}tempDUDPivot AS A' + '
inner join aspnet_users AS B on B.username = A.username
inner join aspnet_membership C on B.userid = C.userid '
+ replace(@Filter,'[','A.[')
+ replace(@RoleFilter,'[','A.[')
+ ' AND ((C.IsApproved = 1) OR (' + Cast(@AuthOnly as varchar(2)) + ' = 0))'
+ ' AND A.PortalID = ' + cast(@PortalID as varchar(3))
+ ' AND A.userid not in (select userid from {databaseOwner}[{objectQualifier}userportals] where isdeleted = 1 AND portalID = '
+ cast(@PortalID as varchar(3)) + ')'
EXECUTE(@MySQL)
END
else
-- if DNN version is lower than 5.0
BEGIN
Set @MySQL = 'select ' + @LimitResults + ' A.* from {databaseOwner}tempDUDPivot AS A' + '
inner join aspnet_users AS B on B.username = A.username
inner join aspnet_membership C on B.userid = C.userid '
+ replace(@Filter,'[','A.[')
+ replace(@RoleFilter,'[','A.[')
+ ' AND ((C.IsApproved = 1) OR (' + Cast(@AuthOnly as varchar(2)) + ' = 0))'
+ ' AND A.PortalID = ' + cast(@PortalID as varchar(3)) +''
EXECUTE(@MySQL)
END
--PRINT(@MySQL)
END

END

GO

It's a fresh installation of the module. We just purchased it, installed it (and noted the error from 5.4.4), and set it up. The 5.4.4 install fix was added shortly before I posted here the first time.

Note that this is 5.4.4 Professional Edition, upgraded from 5.1.2 Community Edition a couple of months ago.

I've run the above script and force-run the scheduler task. Still nothing. There are 119 portal users now, but the tempDUDPIVOT stays static at 37 rows, and most are from portals 0, 3, and 4. A few are marked as being from a NULL portal, including the portal admin for portal 1. The tempDUDProfile table still has 106 rows.

I've got the same problem on a fresh install of 5.5.0 Community Edition for another client. That one's not upgraded from an earlier DNN, and uses the same 3.0.30 version of DUD (also not an upgrade).

Hi... Thanks for the updates, at this point I think we need host rights to the site so that we can review why the query above isn't working for some of these users and their profile fields.

The only other thing I see is where it shows 'P.Visible' meaning that the profile properties listed under Admin, User Accounts, Manage Profile Properties are set as 'Visible'?

If you can open a support ticket or click the 'Contact Us' and provide us with your invoice ID we can check this out for you.

Thanks,

Chad

I checked the profile property visibility like you asked, and only first name and last name were visible. I checked all the rest that apply in this case, then re-ran the scheduled task, and... GREAT SUCCESS!

Thank you.

Hello ThrottleNet Developers,

We're glad to see that you've found resolution to this issue.

In the future, if you ever have any questions please let us know.

Thanks,

Ryan