DB60 The LDAP server is being used for eDirectory synchronization
Source:
GroupWise engine; administration engine.
Explanation:
An MTA that performs eDirectory user synchronization obtains its eDirectory information from a server that is also being used in your GroupWise system as an LDAP server.
Possible Cause:
You are trying to delete an LDAP server that is being used for eDirectory user synchronization as well as for LDAP.
DB61 The signature information is too large
Source:
GroupWise engine; administration engine.
Explanation:
ConsoleOne cannot save the global signature you have created because it exceeds 2.43 MB.
Possible Cause:
You have tried to create a global signature that is larger than 2.43 MB.
Action:
Remove some text or objects from the global signature.
DB62 The software area is being referenced
Source:
GroupWise engine; administration engine.
Explanation:
The software distribution area is still in use by one or more post offices.
Possible Cause:
You are trying to delete a software distribution area that is still in use.
Action:
Configure the post offices to use other software distribution directories. In ConsoleOne, display the Post Office Settings property page of each Post Office object, then select a different software distribution directory. When no post offices reference the software distribution directory, it can be deleted.
DB63 Following a database rebuild the ownership of the target file has been changed. The file uid.run must be deleted manually.
Source:
GroupWise engine; administration engine.
Explanation:
After it rebuilds a domain or post office database, ConsoleOne tries to delete the
uid.run file that specifies the user that the agent runs as, so that user information can be reestablished from the
uid.conf file.
Possible Cause:
ConsoleOne was unable to delete the
uid.run file.
Action:
Delete the
uid.run file from the domain or post office directory. The agent generates a new one based on the
uid.conf file when it starts running against the rebuilt database.