/ Forums / Advansys Archive To Go, Advansys PST Creator / Archive To Go / No message properties for Archived items

  • Creator
    Topic
  • #4958
    ab
    Participant

    1.5 beta, exporting using local access. Have tried both with checking off “Include default native Groupwise archive, and uncheking and adding the archive path. In either case I get the same results –
    2007-10-25 11:43:25.408-04:00 Account Name: A Zack
    2007-10-25 11:43:25.408-04:00
    GroupWise Archive: True, U:Gwise_archive
    2007-10-25 11:43:25.689-04:00 [W] Cannot access message properties: 47207EAD.SINAI_D.IS_PO.100.1706D69.1.1C.1.
    2007-10-25 11:43:25.799-04:00 [W] Cannot access message properties: 47207E8F.SINAI_D.IS_PO.100.1706D69.1.19.1.
    2007-10-25 11:43:25.892-04:00 [W] Cannot access message properties: 47207E90.SINAI_D.IS_PO.100.1706D69.1.1A.1.
    2007-10-25 11:43:26.830-04:00 [W] Cannot access message properties: 47207F49.SINAI_D.IS_PO.100.1706D69.1.20.1.
    2007-10-25 11:43:26.908-04:00
    Folder: A ZackMailbox, Messages found: 4, Messages archived: 4
    2007-10-25 11:43:27.127-04:00 [W] Cannot access message properties: 47207E84.SINAI_D.IS_PO.100.1706D69.1.18.1.
    2007-10-25 11:43:27.205-04:00 [W] Cannot access message properties: 472080B0.SINAI_D.IS_PO.100.1706D69.1.21.1.
    2007-10-25 11:43:27.314-04:00
    Folder: A ZackCabinet2nd folder, Messages found: 2, Messages archived: 2
    2007-10-25 11:43:27.923-04:00
    ______________________________________________________________________

  • Author
    Replies
  • #9441
    Support 1
    Participant

    Thanks for this report.

    Which version of GroupWise are you running?

    If you run the Viewer on this export, what text is displayed under the Properties tab for any of these messages?

    You wrote here of using both versions 1.2 and 1.5 with your test account and its native archive. Do you get similar results with 1.2, i.e. when you review the Properties tab for each message – as well as the process log?

    I look forward to your reply.

    Regards,
    Advansys Support

    #9443
    ab
    Participant

    We are running GroupWise 6.5sp4
    Do see the same results using with 1.2 and 1.5, however, I never went back to 1.2 after blowing away and recreating the test account’s archive.
    Sample text displayed when running Viewer:
    ***********************************
    Token failed execution!
    Message Properties
    File Name: R:UsersAzackArchive2Go version 1.5 BETA1.5 all via local using path to archiveAZack Archivemedia-01data0000005472084C7.SINAI_D.IS_PO.100.1706D69.1.26.1.fml
    *************************************
    Thanks

    #9440
    Support 1
    Participant

    We are not sure what might cause this behavior, and are doing various tests in the hope of finding a pattern.

    In the meantime I suggest you upgrade your GroupWise client and try again. We always recommend upgrading to the latest update for a given client version. In the case of 6.5, the appropriate update is 6.5.6 Update 1, also known as 6.5.7. (Note: 6.5.6 Update 2 will not work unless you also upgrade your server.) You can download this update (free) from the Novell website, on this page.

    Regards,
    Advansys Support

    #9442
    Support 1
    Participant

    The preliminary results of our tests indicate that for message properties to be accessible, the relevant account must be logged-in. For a native archive, this means having your GroupWise client switched to the archive prior to starting the export.

    With Archive To Go 1.2 and above you can export a native archive without the corresponding main mailbox. If you switch your client to the relevant archive before exporting, this should avoid the errors you have seen.

    Thus to export a native archive with message properties included, you will need to export it separately from the main account.

    We will look into whether Archive To Go can automate this workaround by reliably switching between GroupWise message databases. In the meantime we have asked Novell to enhance the GroupWise API in order to address this issue.

    Note: It appears that this issue also applies to incoming shared folders. That is, the message properties are not accessible for group (non-personal) items in an incoming shared folder. However in this case we are not aware of a workaround.

    Regards,
    Advansys Support

    [This message was edited by Support 1 on November 05, 2007 at 10:05 PM.]

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.