Please note that this solution is also a guide, requirement and troubleshooting method when having issues with the trusted application.
You receive the following error when trying to login using the GroupWise Trusted Application:
=====
11:59:31 DEBUG: SetTrustedApplicationCredentials(, )
11:59:31 DEBUG: Login with MultiLogin(UserName, /ph-\\cs-novell65-01\sys\mail\poa, , ...)
11:59:32 DEBUG: Login failed for user UserName.
11:59:32 MultiLogin:
11:59:32 [80004005] Unspecified error
11:59:32 Source: Account.Object
11:59:32 Description: Login unsuccessful
=====
GroupWise Trusted Application has not been generated correctly.
The GroupWise Trusted Application is created from the last wizard screen of the Quest GroupWise Migrator for Exchange tool (running under the credentials of a GroupWise Administrator).
- Upon a successful run, the GroupWise Trusted Application will return and add a line within the C:\Program Files\Quest Software\GroupWise Migrator for Exchange\gwmigapp.ini file starting with TK= specifying the GroupWise Trusted Application key value similar to the following example:
...begin gwmigapp.ini file snippet..
[GroupWise]
DomainPath=\\cs-novell65-01\SYS\MAIL\DOMAIN
TK=
...end gwmigapp.ini file snippet.
Note: This value is returned from the GroupWise server as part of the GroupWise Trusted Application process.
- The GroupWise Trusted Application process then generates the hostname of the machine within the Tools | GroupWise System Operations -> | Trusted Applications... window of ConsoleOne that looks similar to the following:
QUESTGWMIGAPP-COMPUTERNAME
First, please confirm the following requirements for the trusted application key creation are met:
- An admin account must be defined with administrator rights to the GroupWise server.
For more information on this requirement, please see Quest solution SOL40629 - What permissions are required to use Quest GroupWise Migrator for Exchange against the source GroupWise Server?
- The GroupWise Trusted Application key can only be used with GroupWise Server/Client 6.5 or higher.
- Quest GroupWise Migrator for Exchange 3.5 or higher (please download the latest version from the Downloads and Updates section of the Quest Support website found at http://support.quest.com
Please try resetting and re-create the trusted application as follows:
- Add the following line below to the gwmigapp.ini file in order to force the application to use the trusted application key function. Add this line specified below under the [GroupWise] section:
UseTrustedAPI=1
Note: For more information on adding/modifying the gwmigapp.ini file, please refer to the current Quest GroupWise Migrator for Exchange - Program Parameters Reference Guide.
- If the GroupWise Trusted Application key exists within ConsoleOne please remove it. You can do this via highlighting the GroupWise Post Office Name, then select Tools | GroupWise System Operations -> | Trusted Applications... from the ConsoleOne menu. The name of the application will be that of the computers hostname, similar to QUESTGWMIGAPP-COMPUTERNAME as an example. Highlight this value and click Delete from the Configure Trusted Applications dialog.
- Delete the TK= from the gwmigapp.ini file located from within the install directory. Only delete the number generated number, NOT the TK= text. So the line only reads TK=.
- Re-run the Administrative Driven Batch Migration tool. Once complete, give it time to propagate through the GroupWise Domain to the Post Office if it is a large environment. Confirm the QUESTGWMIGAPP-COMPUTERNAME has been created in Console Ones Trusted Applications... area. Also verify that the TK= value has been re-populated. If so, please re-run the migration to test, otherwise, see below for further troubleshooting methods.
Troubleshooting GroupWise Trusted Application Key
- Upgrade to the latest GME release
- Confirm *all* of the requirements and Quests application requirements are fully met. Please review the current Quest GroupWise Migrator for Exchange System Requirements for further details.
- Please be aware that the GroupWise Trusted Application key may need time to propagate in a large environment.
- Confirm that all domains are communicating and the MTAs are in an open status.
- The single-sign on setting for the client has been known to cause issue with Novell. Please disable this.
- Novell and GroupWise passwords are separate. Please verify that the GroupWise Administrator account has a GroupWise mailbox password set (and test it by typing the password into the GroupWise Login dialog).
- Please obtain the Post Office Agent log files. These should give information regarding the creation of the GroupWise Trusted Application key.
- Confirm there are no duplicate hostname on the network and if the machine was cloned, confirm DNS resolution is working for this hostname.
For more information on the GroupWise Trusted Application and possible returned error codes, please refer to the following Novell article titled CreateTrustedAppObject found at the following link:
When there are issues with eDirectory we see the following error within the PO logs:
Error: Directory Services Data missing [D105] User:QuestMigAdmin App( QUESTGWMIGAPP-SERVERNAME )
This error from Novell is stating that the link between objects in Novell and their association is down. A database and post office build is recommended from Novell. Please confirm this with Novell first.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center