Support 2

[Support 2]

Is it a custom applet? What does the applet do and how is it integrated with the GroupWise client (toolbars, events etc.)?

From experience and although rare, we’ve seen that it is possible for an applet’s operation to be sensitive to the state of a GroupWise user’s account. This can vary according to how the applet uses the GroupWise APIs and events and to the GroupWise Client version. A thorough GWCheck of a user’s account may help.

For at least on of the workstations with the problem, it is recommended that you upgrade to GroupWise 6.5.4 or later (6.5.6 is the latest).

Regards,

Advansys Support

[Support 2]

You should be able to use the /quiet command line switch, for example,

archive2go.msi /quiet

Let us know if this does not address your need.

Regards,

Advansys Support

[Support 2]

You should only need system level admin rights to create the Trusted Application, which I note was successful. Using the Trusted Application from the same workstation should in theory need only standard GroupWise domain access.

When you mention that you are logging in as a different user on the same workstation, do you mean a different Windows user or network user? For example, as you would be aware, you can log onto a different eDirectory user while not changing the workstation’s Windows user.

If you are changing the Windows User, therein may lie the problem. Archive to Go saves its system settings on a Windows user basis, for example, in C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To Go. Logging into another Windows user will make these settings unavailable, including the encrypted Trusted Application Key. A work-around would be to copy the systems.xml file from the ‘admin’ user to the target Windows user’s Archive To Go folder.

I hope this helps.

Regards,

Advansys Support

[This message was edited by Support 2 on March 17, 2006 at 05:30 PM.]

[Support 2]

From past experience, attempting to close GroupWise from a C3PO (i.e. Formativ) either did not work or resulted in unpredictable behavior. It is not recommended.

What are trying to achieve?

Regards,

Advansys Support

[Support 2]

Thanks Todd, we have received your files. It is likely we will need to write a test application to try and identify specifics of your environment.

Regards,

Advansys Support

[Support 2]

Thank you for your enquiry. Could it be possible that the target machine has only Microsoft .NET Framework 2.0 installed?

Microsoft .NET Framework 1.1 must be installed prior to installing Archive To Go. As the Microsoft .NET Framework 2.0 was released recently, Advansys will migrate Archive To Go to use it in a future version.

You can obtain the .NET Framework 1.1 Redistributable from here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en

Please install this redistributable before installing Archive To Go.

This and other installation requirements (listed below) are described at http://www.archive2go.com and in the readme document (which is installed with Archive To Go).

• Novell GroupWise 32-bit Windows Client, Version 6.5.3 or later. GroupWise is required for archive creation only and is not needed afterwards to access or search an Archive To Go portable archive.
• Microsoft .NET Framework 1.1 Redistributable.
• Microsoft Windows Installer.
• Adobe Acrobat Reader to access documentation

I hope this helps.

Regards,
Advansys Support

[This message was edited by Support 2 on March 10, 2006 at 04:43 PM.]

[Support 2]

Thanks Dat, your contribution is appreciated.

Regards,

Advansys Support

[Support 2]

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

[Support 2]

Great news, thanks for letting us know!

Regards,

Advansys Support

[Support 2]

Thanks for the feedback. Great to hear that the information was helpful.

Regards,

Advansys Support

[Support 2]

This should not happen because Message Saver uses the subject plus date/time of the message as part of determining a unique file name.

Are you able to forward to us a couple of GWIA accounting messages which cause the file exists message when saved?

If so, please send the GWIA accounting messages as mail attachments to another email (not flat-forwarded) to support@advansyscorp.com. We will try and replicate the problem in-house.

Regards,

Advansys Support

[Support 2]

We will need to review the Formativ GroupWise.SendOptions operation to see if a problem exists with the Formativ call. In the meantime, you can use the Formativ GroupWise.ThrowToken call as an alternative method for executing a GroupWise token.

The GroupWise.ThowToken method calls the native GroupWise token directly, and returns a boolean indicating if the token execution success status.

For example:

iSyntax = “SendOptions(2;0;276)”
msgbox groupwise.throwtoken(iSyntax, iReturnVal)

Note: The operation of the above syntax has not been checked but it provides the general idea of how to use it.

You also need to be aware that some GroupWise tokens perform different functions depending on whether a composing (draft) message has the focus or if the main GroupWise Client has the focus.

Please see the Formativ Language Guide for more information.

Hope this helps.

Regards,

Advansys Support

[Support 2]

Upon further review, there was a known issue with the initial release of the GroupWise 6.0 client, 6.5.0.

Could it be that you are using the initial relase of the 6.5 client?

Please refer to this post from 2005:

http://www.advansyscorp.com/forums/topic/113109079/

quote:

---

Upon review, the problem is very likely due to using the GW Client 6.5.0. As a ‘.0’ release, it had some serious issues we had to try and work around. Upon review of the code, the work-around had to use some clipboard functions and probably explains the problem you are seeing.

---

If you are using the 6.5.0 client, updating to 6.5.5 or 6.5.6 (which has just been released) will resolve the Stationery and many other GroupWise Client issues.

Regards,

Advansys Support

[Support 2]

Sure, we have replied by email.

Regards,

Advansys Support

[Support 2]

Hi,

We are not aware of a similar problem. How are you creating your stationery, for example, are you creating stationery from existing GroupWise messages or creating it from scratch using the internal or an external HTML editor?

Does this problem happen every time you use Stationery?

Does it happen on any other workstation?

Which version of the GroupWise Client are you using?

What is the version of Stationery (see About on the Stationery dialog)?

Regards,

Advansys Support

[Author]

Replies