Hi,

After a new installation of 2.1 in DNN 5.6 enviroment I get the following error after I add the module to a new page:

Error: User Import is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Value cannot be null. Parameter name: connectionString ---> System.ArgumentNullException: Value cannot be null. Parameter name: connectionString at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DataSprings.DNN.Modules.UserImport.Data.SqlDataProvider.GetUserImportByPortals(Int32 PortalID) at DataSprings.DNN.Modules.UserImport.Business.UserImportController.GetByPortals(Int32 PortalID) at DataSprings.DNN.Modules.UserImport.UserImport.LoadImportDefinitions() at DataSprings.DNN.Modules.UserImport.UserImport.SetUserInterface() at DataSprings.DNN.Modules.UserImport.UserImport.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Seems odd that it can't find the connectionString.

Thanks,
Chuck

Hi Chuck,

We are working to change this in the future to use the most current DNN connection string. Right now there are two areas you can maintain the connection string in the web.config file and you probably are only setting the connection string in one of those versions (and not the older method DNN used to use). We use the older method because many customers will use this module on older systems to export users out etc...

So, if you open a support case and send us your web.config we can show you where its missing, I believe its under app settings.

-Chad