Support 2

[Support 2]

Thanks for the update. As Archive To Go Viewer is a read-only application, it is not possible for the Viewer to remove or corrupt its own files. As a result, it is almost certain to be a workstation related issue.

Kind Regards,

Advansys Support

[Support 2]

The problem you describe appears to be very unusual. Was it confirmed that the Archive To Go archive was AOK after it was initially created?

The symptom suggests that the Viewer does not have access to the data folder, which resides under the media-01 (or media-NN where NN is the volume number) folder. The data folder contains all the message folders, that you mention do exist.

Could it be that the viewer may not to have access rights to the data folder and/or its subfolders?

Does the archive reside on a local workstation drive or a shared/network drive? If it resides on a network share, what happens if you copy the complete archive to the local workstation drive and run the viewer from there?

Kind Regards,

Advansys Support

[Support 2]

Our pleasure, thanks for letting us know!

Kind Regards,

Advansys Support

[Support 2]

Hi Mickey,

Every message in the GroupWise message store is allocated a unique ID that never changes during the life of the message. Items that have not been saved , and therefore have not yet been allocated an ID, can be accessed using the special ID “X00”.

A workaround might be to check for a composing message (ID=”X00″) before checking BoxType. Alternatively, it may be worth saving as a draft and then using the ObjectAPI to access the BoxType using Message.BoxType.

Here is some code from our applet source library, which checks the ID and boxtype.

  if (GroupWise.ItemMessageIDFromView <> "X00") then
    Set oMsg = Client.ClientState.CommandMessage

    if ((oMsg.boxtype = fgwIncoming) or (oMsg.boxtype = fgwOutgoing)) then
      msgbox "Incoming or outgoing message"
      set oMsg = nothing
      exit sub
    end if
  end if

  msgbox "Draft message..."

Hope this helps.

Kind Regards,

Advansys Support

[Support 2]

Hi Matthew,

Thanks for your question. Earlier testing of A2Go during the GroupWise 2012 beta did reveal a problem which the Novell GroupWise team resolved promptly. Our testing so far with the GroupWise 2012 release code looks good and, while it is still early with respect to broader testing of GroupWise 2012 in the field, we are hoping that no other issues will surface for our current codebase.

quote:

---

Or indeed what’s next on the horizon?

---

This is being reviewed soon once we assess the take-up of GroupWise 2012. Our customers use Archive To Go in many different scenarios. Do you have any specific features you would like to see in the product? If you do, can you provide some background on the business case behind your requirements? If you would like to take this type of feedback offline, please feel free to send an email to supportATadvansyscorp.com.

Kind regards,

Advansys Support

[Support 2]

Hi Michael,

Thanks for your question. At this stage we are not planning to develop a viewer for a non-Windows platform. Any future decision to develop beyond Windows would be based on customer demand and, since the launch of the product, we’ve had very few requests for this capability.

Kind regards,

Advansys Support

[Support 2]

Hi Jason,

There may be a couple of approaches to consider. First is the language construct Utilities.ExecutionSource/ExecutionSourceInfo as documented the Formativ Language Guide. This command enables you to determine the type of control which initiated the applet. The problem with it for your needs is that it will identify applet execution from the toolbar but won’t distinguish between the GroupWise client’s main toolbar and a message view’s toolbar.

The other option is to use the Applet Chaining feature along with Utilities.TransferData as a parameter. You can write a separate stub applet for each view integration you wish to identify then, using TransferData, pass the desired context and any other information to a separate main applet, whose behavior changes according to the applet which initiated it.

Hope this helps and provides some avenues for investigation.

Kind Regards,

Advansys Support

[Support 2]

Thanks Jason, we very much appreciate your feedback.

[Support 2]

Hi Jason,

Thanks for the feedback. Your work-around is correct and we’ll be finalising a formal update after tests with the GroupWise release code are completed, which should be within 6 to 8 weeks. There is likely to be a beta download during this period. It is correct that GW 2012 is not yet officially supported for Formativ until this update is released. We’ll be updating the information our site soon to reflect these plans.

Kind Regards,

Advansys Support

[Support 2]

Oops, sorry the link contained a comma, which I’ve fixed now. Glad we could help.

kind regards,

Advansys Support

[Support 2]

Hi Jason,

Thanks for the heads up on the dead links, which I have updated in http://www.advansyscorp.com/forums/topic/3971028821/.

Try this link: http://www.torry.net/docs/inprise/help/d6pro.zip which is a link from http://www.torry.net/pages.php?id=62.

Kind regards,

Advansys Support

[This message was edited by Support 2 on January 29, 2012 at 11:23 PM.]

[Support 2]

quote:

---

By different results I mean, the number of sub-folders that are archived each time are different. In the first attempt, 10 of the existing 20 folders under the cabinet folder were archived and the second time, none of the folders were archived.

---

This sounds like a data sensitive issue. It could be due to a range of reasons, corrupted data or a message(s) with a huge attachment, which may be causing a memory issue. As requested earlier, we would need to see the logs to gain further insight.

quote:

---

Also if you would also confirm whether the 5000 message limit applies to all the GroupWise folders – including archives.

---

With the more recent GroupWise clients, there is not a 5000 message limit. We suggest 5000 for problem cases which seem to be data related because it used to be a limitation. Resolution may be as simple as moving some messages to different folders in order to update the GroupWise database files, which in some cases rectifies data related problems impacting the GroupWise API.

Kind regards,

Advansys Support

[Support 2]

Hi Gopal,

Thanks for your post. The problem you describe is unusual and we don’t have a ready explanation, apart from the suggestions mentioned here:

Troubleshooting Export Problems
http://www.advansyscorp.com/forums/topic/2021043902/

quote:

---

…and the archived results are different each time we run it.

---

Can you elaborate on the nature of the unexpected results?

quote:

---

…is there a way to expedite archival of mailboxes?

---

Performance depends on a range of factors, such as server and local workstation capabilities and speed. As you are dealing with a large number of mailboxes, probably Enterprise mode is fastest. You can install Archive To Go Creator on as many workstations as desired and, combined with batch mode Enterprise operation, you could split the batch jobs across multiple workstations.

If the suggestions above in the Troubleshooting Export Problems post do not assist solve your problem, in order for us to get a better picture of what is happening, please send the Archive To Go Creator logs, along with a detailed description of the problem, to supportATadvansyscorp.com.

Kind regards,

Advansys Support

[Support 2]

Thanks for your enquiry. Enterprise Proxy has not been designed for nor tested on Windows 2008 Server. While it probably would work with the appropriate configuration, it is designed to run on a workstation OS such as Windows 7 or Windows XP. Can you run it from one of your workstations instead?

Kind regards,

Advansys Support

[Support 2]

Thanks for your feedback.

Kind regards,

Advansys Support

[Author]

Replies