- Related Products
- ADAudit Plus
- ADSelfService Plus
- EventLog Analyzer
- Exchange Reporter Plus
- AD360
- Log360
1. When I start ADManager Plus, none of my domains are discovered. It says "No Domain Configuration available". Why?
ADManager Plus, upon starting, discovers the domains from the DNS server associated with the machine running the product. If no domain details are available in the DNS Server, it shows this message.
2. When I add my domains manually, the Domain Controllers are not resolved. Why?
This problem occurs when the DNS associated with the machine running ADManager Plus do not contain the necessary information. You need to add the Domain Controllers manually.
3. When I add the Domain Controller, I get an error as "The Servers are not operational". What does it mean?
This error could be due to any of the following reasons:
4. When I add the Domain Controller, I get an error as "Unable to get domain DNS / FLAT name". What does it mean?
This error could be due to any of the following reasons:
5.The status column in the domain settings says that the user do not have Admin Privilege?
This is a warning message to indicate that the specified user do not have administrator privileges i.e., the user is not a member of Domain Admins Group. Hence permissions applicable to Administrator may not be available to this user.
6.When I add an additional Domain, I get the error message "License is applied only to "n" Domains". What should I do now?
This is a warning message to indicate that you are trying to exceed the maximum number of domains that can be added in the purchased license. To add another domain , you must either delete an existing domain or purchase a license for additional domains based on your requirement.
7.When I try to install ADManager Plus, I get the error " The InstallShield Engine (iKernel.exe) could not be installed. What should do?
This is a warning message to indicate that you do not have appropriate rights/privileges to copy iKernel.exe to the desired folder where you want to install ADManager Plus.
1. SMS server settings and SSLHandshakeException errors
Why does this error occur?
This occurs when the configured SMTP mail server or the web server configured with SSL in ADManager Plus uses a self-signed certificate. As self-signed certificates will not be trusted by the Java Runtime Environment used in ADManager Plus, unless they are explicitly imported, it is recommended that the following troubleshooting steps are followed.
Step 1: Download the required certificates
1. While creating a user, I get the following error "Error in setting the Password. The network path not found - Error Code: 80070035"
While setting the password for the user, if the target machine could not be contacted, this error is shown. The possible reasons could be:
2. While creating a user, I get the following error "Error in setting the Password. There is a naming violation - Error Code : 80072037"
One possible reason for this error could be creation of a user in an invalid container.
3. While creating/modifying a user, I get the following error "The server is unwilling to process the request - Error Code : 80072035"
Possible reasons for this error could be:
4. While creating a user, I get the following error " Error In Setting Terminal service Properties. The specified user does not exist - Error Code : 525"
One possible reason could be that the user or the system account as which the product is run do not have an account in the target domain. Terminal Service properties can only be set if the user account or the system account (applies when ADManager Plus is run as a service) that runs ADManager Plus has an account on the target domain.
5. I have updated the Exchange attributes using ADManager Plus, but the properties are not updated in the Exchange Server yet.
ADManager Plus modifies the Exchange properties in the Active Directory. The changes may not be immediately reflected in the Exchange Server. It will get updated after some time.
6. Legacy Mailboxes
Prerequistes for Exchange 2007
1. 64 bit Edition of ADManager Plus should be installed on a compatible machine. (You can find the architecture of the existing installation from the "Product.conf" file located at
2. To create Mailbox Enabled Users in Exchange 2007, you would require the corresponding version of Exchange Management Console (EMC) in the same machine where ADManager Plus is installed, failing which the legacy Mailbox will be created.
3. If ADManager Plus is running in console mode, then you must log on to the machine as an administrator (Exchange administrator).
4. If ADManager Plus is installed as a service, kindly configure the service account with administrator (exchange administrator) privileges by following the below procedure,
Prerequisites for Mailbox Creation in Exchange 2010
7. I am not able to set the Terminal Services properties for the user?
One possible reason could be that the user or the system as which the product is run do not have an account in that domain.
Refer to here for starting ADManager Plus in User or System account.
8. I am getting an error as "The attribute syntax specified to the directory service is invalid - Error Code : 8007200b"?
This error could popup in the following scenarios:
9. When I create/modify a user, I get the following error " A device attached to the system is not functioning - Error Code : 8007001f "
The possible reasons for this error could be:
10. Email address for user not showing up or not set properly?
The possible reason could be:
11.Error-The server is unwilling to process the request while setting Password which not matches to password complexity
The possible reason could be:
You may not have specified or opted for any options in 'Password Complexity' while creating user account.
Ex: There will be options for password complexity like length of password, characters that can be used or number of bad login attempts etc. You need to select any degree of complexity. Ignoring so will throw above error.
12. Error code: 8007052e
This error is caused when the supplied credentials are invalid.
13. Error code: 80070775
Reason: The referenced account is currently locked out and may not be logged on.
14. Error code: 800708c5
Reason: The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.
14. 5 -Access is denied (Terminal Service / Folder Creation)
Reasons:
16. No such user found. Verify the LDAP attribute in search query
Reason: No Users in AD matches with the criteria provided by you. Try choosing the correct matching attributes by checking with the query provided in the "Match criteria for Users in AD", this is obtained by clicking on "Update in AD" button and expanding "Select Attributes" box. Also, ensure that the help desk technician has rights/privileges in that particular OU.
17. Error Code 80072035 : Error In Setting Attributes. The server is unwilling to process the request.
Reason: The primary group specified in User Creation has been moved or deleted.
18 Error Code : 80072030 : Error In Setting Attributes. The server is unwilling to process the request.
Reason: The primary group/container specified in User Template that was selected during User Creation has been moved or deleted. (You are
trying to create a child object inside an OU, but that parent OU does not exist)
19. Error Code : 80070005 - Access Denied
Reason: The User may be trying to access an object to which he has no permissions granted.
20. Error Code : 80072014 Error In Setting Attributes. The requested operation did not satisfy one or more constraints associated with the class of the object
Reason: You may encounter this type of error when the CSV file you are
using to import values, does not satisfy the conditions associated with
the attribute.
21. Error Code : 80072016 Error In Setting Attributes. The directory service cannot perform the requested operation on the RDN attribute of an object
Reason: You may encounter this type of error if any of the LDAP headers in the CSV file are mentioned inappropriately.
22. Error Code 35 : Error in Creating Terminal Services Home Directory/ Error in Creating Home Directory. The network path was not found.
Reason: The remote server path might not be accessible.
23. Error Code: 800704c3 - Error While accessing User in Setting Account Properties
Reason:Multiple connections to a server or shared resource by the same
user, using more than one username, is not allowed. Disconnect
all previous connections to the server or shared resource and try again.
24. Error Code b7 : Error in Creating Profile Path
Reason: There may be a File/Folder that already exists with the same name.
25. When I delete the Remote Profile folder, it throws "Unable to Delete the profile. The handle is invalid - Error code:6."
Reason : There might not be any inherited permission on the folder. Check whether the particular user has delete permissions on that folder. This can happen even in a condition when the folder is currently in use.
26. When I try to modify users, I get an error message saying, "Unable to modify the user. Error: The specified directory service attribute value does not exist. Error code : 8007200a" What should I do now?
Reason: The following are the possible reasons why this error could occur:
Please check the syntax of the specified attributes and the CSV file for misplaced commas. Also, ensure that the specified attributes are a part of the domain where you would like to use the attribute.
27. While adding user(s), I get the error message: 'License Level Exceeded'. What should I do now?
This message indicates that you have reached the limit for the maximum number of users permitted as per your license. To add more user(s), you should upgrade your license.
28. While creating new user(s) along with Lync Telephony options, either of these error messages is displayed: "Error while enabling Lync services for the user" or "Error occurred while enabling Lync Telephony options". What could be the possible reasons?
Mentioned below are the possible reasons for the above errors. Rectifying them would help you in avoiding these errors:
29. Error Code 78: This function is not supported on this system.
Reason: The remote server path might not be accessible due to insufficient rights.
30. Error Code 80004005: Unspecified Error.
Reason: An object with same name already exists in the restore path.
31.Technician does not have permissions to perform the required operation on this object.
Reason: You may not be authorized to perform the required operation in this OU. Please contact your administrator to get the rights for this OU too.
32. While creating or modifying Room mailboxes with Resource In Policy Request/Resource Out Policy Request, you get these errors: 'The values is already present in the collection' or ' The parameter 'legacyExchangeDN must be a non-empty string'. What could be the possible reasons?
Reason: These errors would occur if the mailboxes selected for the Resource In Policy Request/Reqource Out Policy Request policies are legacy mailboxes. Just remove legacy mailboxes from the selected list, and perform the operation again.
1. When I specify the details and generate the report, it says "No Reports available" or incomplete data
It could be because of any of the following reasons:
2. AD Reports shows an object that does not exist in the Active Directory?
This mismatch could occur when the data is not synchronized with the Active Directory. The data synchronization with the Active Directory happens every day at 1.00 hrs. If ADManager Plus is not running at that time, you can initiate the data synchronization manually by clicking the icon of that domain from the Domain
Settings.
3.Error Code : 80070035- Error in getting Shares. The network path was not found
Reason - The remote server path might not be accessible.
4. Cannot process the argument transformation on the parameter 'Credential'.
Reason: This error occurs when authentication credentials are not specified in the Domain Settings. To resolve this error,
1. When a role is delegated, I get the error as "Permission Denied"/p>
One possible reason could be, the user or system as which the product is started do not have necessary privileges to perform this operation.
Refer to here for starting ADManager Plus in User or System account.
2. I am not able to login through my account!
The following are the possible reasons for that:
3. Reset second factor of authentication for the default admin account
If you have lost your authentication device, or cannot retrieve the verification code required to complete the authentication, you can reset the secondary authentication factor using the following steps.
Note: Authentication factor reset can be done only for the built-in admin account
The reason could be you do not have permissions to alter permissions on that particular folder.
The reason could be you do not have permissions to alter permissions on one of the folders or subfolders.
The reason could be one of the permissions you are trying to apply has already been applied and is currently effective.
The reason could be one of the permissions you are trying to remove has already been denied and is currently effective.
When you delete a namespace using the DFS Management snap-in, sometimes it may not be reflected in the DFS Metadata. To resolve this issue, manually delete the namespaces in DFS metadata too.
To delete a namespace from DFS metadata:
This error occurs due to invalid combination of licenses assigned to an Office 365 user. That is, if you try to assign same license in two or more service plans, you will get this error.
This error could occur if the selected OUs do not contain any users. Click 'refresh', select the desired OUs and try again.
This mismatch could occur when the data is not synchronized with Active Directory. Click the refresh icon to synchronize ADManager Plus database with your AD.
This message is displayed when there is an error in the value being assigned to the parameter. There might be spaces or special characters in the values. Ensure that the parameter is not empty and does not contain any spaces or special characters.
This error occurs when you try to create an Office 365 user directly in a federated domain. To create an Office 365 user in a federated domain, the user must be created in Active Directory first, and then synchronized with Office 365 using DirSync.
Both of the above attributes are mandatory. Ensure that you provide valid values to both the attributes.
This error occurs when a user account with the same user principal name already exists in Office 365. Enter a different user principal name and try again.
This error could occur if the specified password does not meet the password policy requirements. Ensure that the password you provide meets the required password policy settings such as minimum password length, password complexity, and password history requirements.
Solution: Create an empty group called <DomainDNS>$$$ in both the source and target domains, respectively.