Dynamics Community Forum Thread Details

web client error

Good Morning,

I am attempting to test the web client with GP 2016. When going to the web address, I get an unhandled exception error. I checked the applications event viewer and find the following error in the dynamics section. I have checked and verified asp.net impersonation is disabled. The sql server, web server, server, dynamics database names do not have spaces in their names. Are there any ideas on what could be throwing this error?

-	EventData

An unexpected exception was thrown checking the domain for user membership. The exception details are: System.ArgumentException: Server names cannot contain a space character. at System.DirectoryServices.Protocols.LdapDirectoryIdentifier..ctor(String[] servers, Boolean fullyQualifiedDnsHostName, Boolean connectionless) at System.DirectoryServices.Protocols.LdapConnection..ctor(String server) at System.DirectoryServices.AccountManagement.PrincipalContext.ReadServerConfig(String serverName, ServerProperties& properties) at System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval() at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name, String container, ContextOptions options, String userName, String password) at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name) at Microsoft.Dynamics.GP.Web.Foundation.DirectoryServices.PrincipalManager.GetPrincipal(String userName) at Microsoft.Dynamics.GP.Web.Foundation.DirectoryServices.PrincipalManager.IsIdentityInPrincipalCollection(String userName, IEnumerable`1 principals) at Microsoft.Dynamics.GP.Web.Foundation.DirectoryServices.PrincipalManager.IsUserMemberOf(String userName, String principalCollectionKey) at Microsoft.Dynamics.GP.Web.Services.Session.Service.SessionCentralService.ValidateCallerIsMemberOf(String principalCollectionKey)

Hello Michael,

With the 'Server names cannot contain a space' message from Web Client, you're correct in that it's rarely actually a server name with a space or even special character in the name.

We haven't seen this error much, but a 2-3 cases, and in those, we've seen this caused by different things, such as:

>>We've seen this error caused when the account running the 'GP Session Service' and 'GP Session Central Service' don't have permissions to read the OU and Active Directory to validate the security groups and users you specified to have access to Web Client, which is what it is doing when you attempt to initially login to Web Client.

>>This can also be caused by users and groups, given permissions to access Web Client, are nested in multiple OUs and folders, in Active Directory.

>>The account running the application pool for the IIS site that Web Client is installed onto, doesn't have sufficient permissions needed on the machine and/or the Registry.

If you haven't already, I'd recommend opening a support case as troubleshooting Web Client cases like this are tough if not impossible, going through Forums.

Thanks,

Quick Links

Leaderboard