Running 2.1 on DNN4.91

only a 1/3 of my imports came through.

Deleted all tried again with a smaller sample still only about 1/3 imported.

my scheduler is not any help, does not say why the records are not imported. This time my file was sorted to insure the importing will happen in the sequence of the records in the file.

All records imported seen to be fine, setting auto, role, and numerous fields.

I reran the same definition, and updated the file with a new one, and the same records are still not updating.

I do not know much about the scheduler, but the times that it ran do not coincide with my time. So it hard to understand when something ran before the time in question? I live in arizona, and do not know what time zone to set it to. none of the settings seem to adjust to the proper time for my portal.

Anyway why would only 300+ of 800 then 30+ of 80 import?

reviewing the data of those not imported to those that did nothing stands out.

 

Pat Byrnes

 

 

Hi, me again, I went back and looked all the way down past the run portion, and I finally seen the errors on the bottom.

While there are a few that have extremely long error codes, 90% of them have the below code

What does Object reference not set to an instance of an object

Does having Dynamic Login, Dynamic Registration, or 32bit or 64 bit systems effect this???

Pat

**** Error attempting to add record:86 Object reference not set to an instance of an object. at DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo user) at DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUser(UserInfo user) at DotNetNuke.Entities.Users.UserController.UpdateUser(Int32 portalId, UserInfo objUser) at DataSprings.DNN.Modules.UserImport.UserImportProcess.DoUserImport()

 

This tells me that it's having trouble updating a user's profile, most likely a result of invalid password setting. Can you list the columns that you are trying to update and what fields they are mapped to? Also, check that particular data that errored out by making sure your import has "enable logging" enabled. -- David

Hi David,

with only 300 of 800 records importing, reviewing the excel import file nothing stands out.

Maybe explain, with data springs collection, I have both the login and registration modules in place. any username and password beyond 4 characters should import. I looked at usernames that have spaces, passwords that are 4 characters that did import.

Does the registration and login modules override the DNN authenication defaults? why would some import and not others?

example below a couple of  highlited accounts that did not import.

 

^{<table border="0" cellspacing="0" summary="SignIn Design Table" cellpadding="0" width="359" runat="server" style="width: 359px; border-collapse: collapse; height: 182px">}