I’m able to login using my domain credentials, and I believe the LDAP integration is working properly. We had a new (to CI) user try to login, he gets the ‘Welcome to Continua’ ‘dialog’ however when pressing start using continua nothing happens except a momentary hourglass.
I noted the message on the Welcome dialog says "Continua has found the curent user ‘’ in an Active Directory group linked to a registered user group…’. Not sure why the current user is a blank string.
CI logs the following error when the '‘start using continua’ button is pressed:
The web server reported the following error:
Exception: FaultException1 <br>Message: PartialEvalException (NullReferenceException ("Object reference not set to an instance of an object."), null.ToLowerInvariant()) <br>Stack Trace: <br>Server stack trace: <br>at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) <br>at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) <br>at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) <br>at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) <br><br>Exception rethrown at [0]: <br>at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) <br>at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) <br>at Continua.Common.Services.Contracts.IMembershipService.RegisterLdapUser(String sid, UserDTO userDTO, Boolean firstUser) <br>at Continua.Web.Controllers.AccountController.<>c__DisplayClass13_0.<welcome>b__0(IMembershipService x) in W:\CI_WS\Ws\733589\Source\CT_Source\Source\Continua.Web\Controllers\AccountController.cs:line 384 <br>at Continua.Web.ContinuaController.With[TService](Action1 action, ServiceEndpointOptions options) in W:\CI_WS\Ws\733589\Source\CT_Source\Source\Continua.Web\Controllers\ContinuaController.cs:line 825
at Continua.Web.Controllers.AccountController.Welcome(WelcomeModel model) in W:\CI_WS\Ws\733589\Source\CT_Source\Source\Continua.Web\Controllers\AccountController.cs:line 388
We suspect this may be due to backing up on one server and restoring to another. I reviewed the postgresql backup file and didn’t see any obvious problem. The linkage to our admin group seems to be correct, and that’s the only LDAP group linked to CI at this time.
I had that user try from IE on a domain connected PC and a non-domain connected PC, same result either time. Another developer had tested the LDAP integration prior to restoring the database and he had no problem getting back the ‘Welcome’ dialog so I’m fairly sure out IIS and service configuration are correct.
As a test one of my coworkers just reinstalled Continua and created a new DB. That resolves the problem, however now we have to either re-create the builds we have manually… or figure out how to import just the project configuration. In our case we only have a few setup so it’s not a big deal, however I think it would be nice to know how to backup and restore to a different server without breaking this.
Problem appears to be specific to one user (so far). The user in question has the same domain privileges as I do (mine worked fine). We’re at a loss as to what is going on, however at this point it appears to be a bug in ContinuaCI 1.7.1.177
More information. ContinuaCI is unable to see some domain users, others no problem. That seems likely the source of the original problem and the missing user name in the message. We’re asking our IT guys to look into permissions/privileges on the domain user that ContinuaCI runs as.
Got our domain admins involved, they found that CI is searching on “User logon name” field in Active Directory, theory is that some migration (these accounts are from NT server days, probably 3.x 
didn’t fill that value in.
I think that CI should raise an error rather than displaying the ‘Welcome to Continua’ page, OR fall back to a different field when ‘User logon name’ is empty? Not my call of course, just documenting what I know.
Problem we were having is gone now that our domain admins filled in that field.
Hi
Apologies for the delay in replying. Glad you got past the problem, obivously there is something we need to handle better. It’s difficult to test because AD will not let us define a user without a user logon name. We’ll look into it.
Thanks. These users have been with the company for 30+ years. If you could catch that the information is missing and just display an error about the problem, I think this is a pretty extreme edge case to not likely to be an issue for many.
At least this thread should provide some documentation of the problem, might help someone else down the line.
Hi,
We have now updated the code to display a descriptive error message if the Active Directory user does have a “user logon name”. This will be included in the next version.
Thank you for reporting this.