Support 1

[Support 1]

Thanks for reporting this problem.

quote:

---

“Retrieving the COM class factory for component with CLSID {99C5B7D2-8CF7-40C1-A8E0-0EE54FF92AB9} failed due to the following error: 80040154”

---

This error relates to the GroupWise API used by A2G. I suggest you reinstall GroupWise on the affected machine before trying again.

Please let me know how you go.

Kind regards,
Advansys Support

[Support 1]

Thanks for your question.

Yes, you can search an archive for multiple terms.

By default the results will be limited to all search terms, so with Example 1 only items containing all three terms will be listed. This is the same as entering any of the following:

• David AND Peter AND Mary
• +David +Peter +Mary

With Example 2 the results will include items containing any of the three search terms.

You can find detailed information about search terms on page 21 of the Viewer manual for Archive To Go 2.x.

At present it is not possible to search across multiple individual archives. To search the 15 archives you will need to view each one in turn, start Finder, then enter the 20 terms to search the archive. You may find it faster to use File Explorer to navigate into the _viewer folder of each archive and start a2gofinder.exe directly.

Regards,
Advansys Support

[Support 1]

Great news – thanks for letting me know.

Kind regards,
Advansys Support

[Support 1]

Thanks for reporting this problem, which we have not seen before.

I suggest you try the workaround described by the steps below:

• On the Folders screen choose All folders which makes the Options group visible.
• In the Options group, choose Include incoming shared folders.
• Click Next > which goes to the next screen.
• Click < Back which returns to the Folders screen.
• Switch to Selected folders and choose the folders you require.

We have confirmed the problem you found applies also to the Trash folder, and to newsgroup and RSS folders, which are also set in the Options group. You can use the same workaround for these folders.

If you are using GroupWise 7.x I recommend you upgrade to the 2.0.0.6 beta which is not yet formally released:
Archive To Go 2.0.0.6 (beta)

I will update the enhancements list for Archive To Go to record this problem.

Please let me know how you go.

Kind regards,
Advansys Support

[Support 1]

Correction: the log shows only 9 items were archived from the Checklist folder. The Trial version will report only up to 10 items found per folder – it will not report the actual number found if it is greater than 10.

Kind regards,
Advansys Support

[Support 1]

Thanks for reporting these problems.

> On a PC of my colleague, the trial version converted the Groupwise folder structure,
> but only the inbox contained 10 messages, the other folders were left empty.

The trial version will archive up to 10 items from each folder in the GroupWise mailbox. The log shows 10 items were archived from each of the following folders:

• Postbus
• Verzonden items
• Agenda
• Contactpersonen
• Checklist

> The log says: “The given key was not present in the dictionary”.

This warning relates to a defect in archiving of personal address books, where Archive To Go expects to find a specific address book field that is missing. This occurs with GroupWise 7 but not with GroupWise 8; your log shows you are using 7.0.2. A fix is available and a new beta installer is available for download:

Archive To Go 2.0.0.6 (beta)

Note that the selected GroupWise native archive was not found:

GroupWise native archive folder not found: "C:Documents and SettingsXXXXXXXXMy DocumentsGroupWise Archiefofw05arc"

I suggest you select the following folder for this archive:

"C:Documents and SettingsXXXXXXXXMy DocumentsGroupWise Archief"

We always recommend upgrading to the latest release for any GroupWise version; for GroupWise 7 the latest release is 7.0.4. You may find the Novell Patch Finder useful for this.

Please let me know if you have any questions or comments. I look forward to your reply.

Kind regards,
Advansys Support

[This message was edited by Support 1 on May 03, 2011 at 06:26 PM.]

[Support 1]

Thanks for confirming the log results.

From your later post in this forum I think you have been able to proceed with your testing.

Kind regards,
Advansys Support

[Support 1]

Thank you for reporting this problem. Please note that I have edited your post to remove the IP address included in the log. This is the summary log; there is also a detail log, mentioned below.

The most likely cause of this problem is that the target location for audit files is read-only, which means Archive To Go cannot write audit information as it archives data. If you look at the detail log (‘pcannaer.log’ in the archive folder), you may find it contains something like this:

2011-04-12 14:30:57.848+02:00 [E] Advansys.Arctic.Auditing.TextFileAuditWriter:
 
Directory is read-only: C:UserspcannaerDocuments

If so, it may be due to a Windows Vista default setting which can be changed for that folder, or you could avoid this problem by choosing a location that you know the user has read/write access to, for example:

C:UserspannaerDocumentsMy Audits

If you do not see the above error in the detail log, please post it (with IP address removed).

I hope this helps.

Kind regards,
Advansys Support

[Support 1]

Thank you for these questions.

1) Sender column: this feature is in our enhancements database for Message Viewer. Unfortunately no information is available about when it may become available.

2) To search for a specific first or last name, or email address, enter the required text at the box Containing Text on the Message Search dialog, which you can open from the main menu (Search) or press F3.

Kind regards,
Advansys Support

[Support 1]

Thank you for the clarification. The Token API online documentation indicates that ItemAddMimeXField() was added in GroupWise 8.0. I would say you are correct: this new token probably is not yet supported in Formativ. You can use the following workaround:

Dim oMsgItem
Set oMsgItem = Groupwise.ComposingItem
if oMsgItem is Nothing then
  call Groupwise.NewMail
end if
set oMsgItem = Nothing
Dim iMsgID
iMsgID = Groupwise.ItemMessageIDfromView
Dim iSyntax
iSyntax = "ItemAddMimeXField(""" & iMsgID & """, ""X-WDRCrypt"", ""yes"")"
MsgBox GroupWise.ThrowToken(iSyntax, iReturnVal)

I hope this helps.

Kind regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

While I have not used this token previously, I think the following code sample might be helpful to get you started. It assumes you have a GroupWise message view open and that it is the active window. Therefore, if you create a Formativ applet based on this code, you will need to integrate the applet so an icon for it appears on the message view.

  iMsgID = GroupWise.ItemMessageIDFromView
  call GroupWise.ItemAddMimeXField(iMsgID, "X-Kingdom", "Animalia")
  call GroupWise.ItemAddMimeXField(iMsgID, "X-Phylum", "Arthropoda")
  call GroupWise.ItemAddMimeXField(iMsgID, "X-Class", "Insecta")
  call GroupWise.ItemAddMimeXField(iMsgID, "X-Order", "Lepidoptera")

The X-fields in this sample represent the butterfly’s scientific classification.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

It sounds like you are referring to a GroupWise secondary/native (not default) personal archive that must be identified explicitly by its folder with Archive To Go.

The problem may be due to selecting the incorrect folder. Have you looked at the featured topic in the Hints & Tips forum Specifying additional native GroupWise Archives?

Are you able to use the GroupWise client to view the contents of the required archive? If so it should be possible for Archive To Go to access this archive.

It may be helpful to send screen shots of the error and archive folder contents to support@advansyscorp.com.

I look forward to your reply.

Kind regards,
Advansys Support

[Support 1]

Novell informed us in May 2009 that this defect had been fixed in GroupWise client 8.0.0 HP2. I would expect you should not encounter this error with GroupWise 8.0.2.

This issue was logged by Novell against the following defect numbers:

Defect #: 461686
Defect #: 486173

If you need to contact Novell about this issue, it may be best to quote both defect numbers.

Kind regards,
Advansys Support

[Support 1]

Many thanks for your confirmation.

The featured topic mentioned above has been updated and the next update Archive To Go will include this in its documentation.

Kind regards,
Advansys Support

[Support 1]

This message has been replied to by direct email.

Regards,
Advansys Support

[Author]

Replies