Hi,

We use dynamic logon authentication provider and DNN 5.2.3 (and dnn 5.6.2, which we are testing).

When testing version 4.0 of dynamic login I get an error (A critical error has occurred Object reference not set to an instance of an object) when i click on the edit button in the extensions page. Also the module doesn't seem to work (can luckily still login through default dnn module which i put on the same page... )

The manual says it should work for version 3.3 and up, 3.3 works fine on our portal......

Without the authentication provider  there are no problems with version 4.0 (in both dnn releases) but we need the provider to overcome same login problems in relation to DMX.

Anybody any suggestions ?

Regards
Antoine

Hi Antoine,
If you look in the Event Log, you should see errors. If you look, you might get an idea as to which module is generating the error. Knowing that would be quite helpful.

Sounds like DMX is a recognized problem as you are dealing with the provider for something there right? If you have a problem with DMX then it might be best to sort that out first then see if Datasprings Dynamic Login is an issue. The current version of DL is 4.0. to 3.3 is a ways back. 3.3 may be fine on DNN 5.2.3 but then on 5.6.2 you have a different animal. You can even step up to DL 4.0 with a Free Trial and do some testing against it in your 5.6.2 envioronment and see if this issue with "object reference not set to an instance of an object" error goes away.

There are other posts on issues with DataSprings modules where error states "object reference not set to an instance of an object". It is with DR and not DL but check them out here as there may be some relationship that is common:

https://www.datasprings.com/dnn-modules/dynamic-registration/a-critical-error-has-occurred--object-reference-not-set-to-an-instance-of-an-object-/

Good luck and let me know if any of this helps

Hi Don,

thx for your suport.

It is not DMX related but DNN; DNN doesn't always handle authorisation requests properly when you use an alternate login page, doesn't matter which module you use to login. It is a bug wich is still not resolved in 5.6.2. With the authentication provider it works ok.

I use the datasprings collection 4.0 and prior to that the 3.0 collection so i have all the relevant versions of your software. The error is with version 3.2 of the authentication provider in combination with version 4.0 of the login module.

The combination of authentication provider 3.2 and login module 3.3 works fine on both dnn releases, but i would like to be able to use the new functionality in 4.0.......

I am not the technical guy, so i don't have the event log. As soon as I have it I will send it to you. If you want I can give you access to our test site.

Regards
Antoine Rengers

Hi Antoine,
You won't need to send it. Try going to Admin>Event Log and read what the log says and see if there is an error there that will talk about one of these modules having an error.
Thanks

this is the event log

AssemblyVersion: 5.6.2
PortalID: 1
PortalName: Nederlandse Vereniging voor Kindergeneeskunde
UserID: xxxx
UserName: xxxxx
ActiveTabID: 654
ActiveTabName: Extensions
RawURL: /bestuur/Admin/Extensions/tabid/654/ctl/Edit/mid/1709/PackageID/204/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://nvk561.cestuswebsites.nl/bes...sions.aspx
UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20100101 Firefox/6.0
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 4f16cb67-e4c2-4342-96bd-ce4c601add13
InnerException: Could not load type 'DataSprings.DNN.Modules.DynamicLogin.Auth_ControlPanel'.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.GetType
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Could not load type 'DataSprings.DNN.Modules.DynamicLogin.Auth_ControlPanel'. ---> System.Web.HttpParseException: Could not load type 'DataSprings.DNN.Modules.DynamicLogin.Auth_ControlPanel'. ---> System.Web.HttpParseException: Could not load type 'DataSprings.DNN.Modules.DynamicLogin.Auth_ControlPanel'. ---> System.Web.HttpException: Could not load type 'DataSprings.DNN.Modules.DynamicLogin.Auth_ControlPanel'. at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase, Boolean throwOnError) at System.Web.UI.TemplateParser.ProcessInheritsAttribute(String baseTypeName, String codeFileBaseTypeName, String src, Assembly assembly) at System.Web.UI.TemplateParser.PostProcessMainDirectiveAttributes(IDictionary parseData) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.Modules.Admin.Authentication.AuthenticationEditor.get_SettingsControl() at DotNetNuke.Modules.Admin.Authentication.AuthenticationEditor.Initialize() at DotNetNuke.Modules.Admin.Extensions.EditExtension.BindData() at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Naam: xxxxxx

Hi guys...

I think that this can happen if you have installed the Dynamic Login Authentication Provider but have not yet installed the Dynamic Login module directly.

Under Host/Extensions does it show that both the module and authentication provider are installed or only one? Also what versions does it show they are?

Thanks!

-Chad

hi don, I posted the error log. as I understand it, it is an error of the authentication provider ??

regards
Antoine

sorry, missed this one (da...d browsercache )

Both modules are installed and appear in the extension list; version 3.2 of the provider, 4.0 of the login module. DNN version 5.2 and 5.6.2

The combination of authentication provider 3.2 and login module 3.3 works fine , but i would like to be able to use the new functionality in 4.0.......

regards
Antoine

Hi Antoine,
One last thought and I would be tapped out. Chad may have some other ideas but what about this? Set up a local environment with the latest DNN which is 6.0. Then see if your version of DMX works there and you have Dynamic Login working there also. I am not familiar with DMX but Dynamic Login 4.0 has been checked out on DNN 6 and is working there as well as 5.6.2. Throughout this whole thread seems like we have really been dealing with some kind of compatibility issue. Seems like you need a place where you can have Dynamic Login 4.0 function but also this DMX will work as well.
Thanks

hi don, thx for your reply,
I will try that, but it is still strange that the authentication provider doesn't work with the login module version 4, as I understand from the manual that the provider should work with version 3.3 and up.

It is not a really big problem at the moment because everything works fine now with version 3.3. of the login module, but i would like to be able to upgrade to new versions of both dnn and the datasprings software.

regard
Antoine

Hi Antoine,
In the reply did you try Chad's suggestion first? I don't see any follow up on what he suggested.

Hello Don,
see my reply on 09-08-2011 01:27 AM.

thx
antoine

Hi Antoine,
Ok as it sometimes is with emails I think there may be confusion. Lets summarize things. Your goal is to have DMX work with Dynamic Login (DL) version 4. Your system works fine with DMX and DL 3.3 per above but you want DL 4.0 so you can have DL 4 functionality..

So here is what Chad may be saying above with the quote which I have copied below:

"I think that this can happen if you have installed the Dynamic Login Authentication Provider but have not yet installed the Dynamic Login module directly."

He may be saying make sure to install DL first then install Authentication Provider. In your reply on 9/8 you are confirming that DL 3.3 works fine with Authentication provider. We all know that but it is DL 4 that gives you the object reference error. Chad is probably referring to a sequence of installation with DL 4 with Authentication Provider as being crucial to proper functioning and so that you don't get that object reference error. This is what I meant by asking if you did what Chad recommended. . . Did you install DL 4 first then Authentication provider and then do both show up under Host>Extensions and with properly labeled versions.

If Chad truly isn't referring to that or if you did just as he said then I have to ask you if you have tried to set up a local environment with DNN 6 where you can then install DL 4 and then Authentication Provider. You see if you can install both items in DNN 6 in this kind of a test environment without the issue of the Object Reference error then you have found a place for them to be compatible together and a test that would warrant going forward with upgrading to DNN 6. Someday you probably want to do that anyway. Perhaps the time to do that is now.

I know this is a long and verbose reply but hope this helps.

Thanks & have a great day

Hi DOn,

Thx for your clear reply, sorry for not understanding directly.

Her is what I did:

• i removed both th DL 4 and the provider, with the remove files checkbox checked
• reinstalled dl 4 and set initial settings + template. module seemed to work ok
  
• reinstalled the provider
• clicked on the edit button of the provider in the extensions view
• same error appeared

We want to be carefull with upgrading DNN and and don't want to be in the front line. We are now testing to upgrade to 5.61 we will finish that first. after that we will try your suggestion to test Dl with dnn 6.0 and plan the next update.

I will keep you posted.

Thx for your time so far.
antoine