When Active Directory authentication is active, why do I get the error "AD Server name not specified along with username"?
Last Updated June 17, 2010
After activitating Active Directory auto-authentication in Servicedesk, when users log into the system, they recieve the the following error, and users cannot log into the Servicedesk portal.
AD Server name not specified along with username.
You can see this error message below:
This same error has also been seen in the Application logs of the event Viewer, and can be encountered error when attempting to enter a change request or when opening the advanced incident form.
This message comes from the fact that, during the user login process to the Servicedesk Portal, group memberships and other items are checked and tested, so that the user has access to all of the necessary portal pages. One check includes reading the Ensemble web.config file, found in ...\Program Files (x86)\Altiris\Workflow Designer\Ensemble\ for certain portal admin rights. Specifcally, the following item is checked:
If the value does not have a valid domain suffix, such as "logicbase.com", the login attempt will fail. It is recommended that this not be changed from the default value of "
email@example.com", as shown above. In the customers case, only a user name, without the domain suffix was in place, thus causing the error.
This will address the impact of the inability to access the portal, but may not resolve it when attempting to use the Workflow Designer or to open up the the Change or Advanced Incident forms, once in the portal. If you still get the error or see the form error out, open the Task Tray Tool, and Click on Settings. in the Servers section, highlight the server:(local) option and then click Edit. You will see the screen below:
This screen shows that the UserID: was set to 'administrator', which is NOT correct. This likely indicates that the SD system was installed with this account, and may have corruption in other locations. This account also must be
'firstname.lastname@example.org, with a password of 'admin', as shown below, to work correctly:
This will temporarily resolve the issues. It is possible, that, because the system was installed with an incorrectly formatted account, that other issues may arise. The system should be re-installed with the correct USERID and syntax.
Imported Document ID: TECH133290
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe