Recently they added a new Win2003 server. Once this server was added, it started introducing referrals into the Active Directory structure, and then replicated these updates to the rest of the LDAP servers. Hence, Dimensions authentication stopped working because Dimensions LDAP implementation will not work with referrals.
Please gather any applicable information from the list below and contact Dimensions Support for help with this error message. What you need to troubleshoot:
When making changes with the Customized Menu Sets or Tools within the Desktop Client, the changes are saved into the local workstation registry and are only available on the workstation where the changes are made. Below is a list of where the items are stored in the registry for the various versions of Dimensions . For Dimensions 9.1.x:
By default, Pulse uses a user in the database with a name of pulse and the default password is pulse. In some cases, you may need to change the password to adhere to your security restrictions.
The workset permissions will need to be modified in order for regular users to create worksets or update their structure, (e.g. create workset directories). For Dimensions 8 and 9 this is done with the SWSP command. SWSP <product id> /WS_PERM=<n>
KM-Dim9: 1330-Error cannot route change document 'change_doc' as there are no users with next roles. Ensure in Process Modeller that a Change Mgmt Role does not have a workset assigned. Version Mgmt Roles may have an assigned workset.
In some situations, the problem may have been caused by upgrading or moving the database without adhering to Serena documentation that states that the database should always be imported into a database that uses the same characterset as the database where the export was performed. The Oracle export/import utilities will do a great deal to convert from one characterset to another, but the Oracle utilities cannot properly convert some of the multi-byte characters that Dimensions utilized in previous versions of Oracle and Dimensions .
