If we assume that there is no problem with Archive To Go ‘seeing’ your Primary Domain path and primary domain database (wpdomain.db), it leaves us at the problem of authentication or access rights. Nothing in the GroupWise APIs enable us to preset any security or authentication settings and, without debug DLLs when possible, there is very little information returned upon authentication failure.
Apart from obvious causes which result in authentication problems, such as correct user access rights, the only other problem of which we are aware involves a multiple eDirectory Tree topology. Generally customers experiencing an authentication problem have only a couple of Trees and logging into the ones which provide the appropriate level of access for the GroupWise APIs solved the problem.
The APIs used are client based. Which version of the GroupWise Client are you using?
Have you tried running Archive To Go in Enterprise Mode from another workstation?
Have you tried reinstalling the GroupWise Client?
If the authentication failure is occurring during the Trusted Application process, sometimes it is possible to get additional information about the problem by installing the GroupWise debug version of the Trusted API DLL. However, from your description, the process appears to be failing before this step, in fact during the very first step when the solution is attempting to connect to the primary domain.
What may help is if you could ZIP and send to support@advansyscorp.com all files from the following folder:
C:Documents and SettingsApplication DataAdvansysArchive To Go
If you are not successful in finding the cause of the authentication problem and we can’t glean anything from the files above, it may be worth trying the Trusted API debug DLL, although as mentioned above it may not assist, in which case we’d need to consider another troubleshooting approach.
Regards,
Advansys Support
