Support 2

[Support 2]

The current release of Archive To Go (A2Go) is not designed for multi-mailbox search and iterative discovery export. While we were aware of these needs during the design of A2Go 1.x, we had to schedule their inclusion in a future release.

You can use advanced search within a single mailbox archive. The advanced logic search capabilties are documented in the help manual.

While we cannot address your main requirements now, if you write directly to support@advansyscorp.com, we would be happy to consider what may be possible, if anything, in the interim.

Just as background, GWAVA Reveal enables cross-mailbox search on mailboxes within the live GroupWise system. GWAVA Reveal integrates with Archive To Go to provide off-line export capabilities. However, I realize that this is not useful in your situation because you already have multiple export DVDs.

Regards,

Advansys Support

[Support 2]

Yes. Archive To Go is licensed on an organization basis (i.e. per legally registered corporate/company/trading entity). This means that you can install and run the software on as many workstations, separately or concurrently, as you like within the licensed organization.

Where a company is comprised of a group of corporate entities, each registered corporate/company/trading entity within the group would need to purchase an Archive To Go license.

I hope this helps.

Regards,

Advansys Support

[Support 2]

Thanks for your post. This is a known issue which will be addressed in the next point release. The problem occurs because the display name field is empty in the GroupWise message being exported.

Regards,

Advansys Support

[Support 2]

The most common causes for this failure are:

• in the System Definition, Post Office IP/Port or path information is either not specified at all or not specified correctly;
• the optional trusted application workstation IP address is specified incorrectly. This option is not required for operation and if specified incorrectly it will cause process failure.

Assuming that the issues above are not the cause, to help us identify the cause, could you please send us (to support@advansyscorp.com) the systems.xml and settings.xml files from the following folder:

C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To Go

The Windows User Name needs to be the Windows User which is logged in when you run Archive To Go.

Could you also send the partial log file which is produced in the export output folder and a screen shot of the error dialog which displays when it fails.

Regards,

Advansys Support

[Support 2]

This request will be handled by direct email.

Regards,

Advansys Support

[Support 2]

As a first step we recommend that you upgrade to the GroupWise 7 SP1 (7.0.1) client. While we do not know the cause of this problem, we know there were a range of issues fixed in SP1.

Regards,

Advansy Support

[Support 2]

Not with the current version. A batch export feature is scheduled for the next main release, which is anticipated to be around the BrainShare 2007 time-frame.

With the answer above, it is presumed you don’t mean that you want all selected GroupWise mailboxes to be merged into a single exported archive. This would not be practical due to the size of the final archive.

Regards,

Advansys Support

[Support 2]

Hi Steve,

Thanks very much for the update and the detailed explanation.

We will certainly be investigating the options to avoid the write permissions after an initial system cache is created. Even so, if you change your system topology or add users, the system cache would need be refreshed by a user who has write rights (unless the GW API requirements change).

Regards,

Advansys Support

[Support 2]

Thanks for the additional information and the files.

quote:

---

After we run the program, we can no longer logout/login via C32… Windows will then not restart or shutdown – we keep getting popups about “dummy window not responding”

---

We are not familiar with this problem. To avoid assumptions on our part, can you confirm what C32 is and what the login/logout process is?

Has this problem occurred ever since you started using Archive To Go or did it just manifest recently?

If you review the process list in Task Manager, is a2goengine.exe still listed?

As this has not been reported previously, we do not know the cause. To solve the issue we need to know how to replicate the problem. If you cannot readily determine the environmental factor which precipitates these symptoms, we will need to discuss a troubleshooting action plan with the developers.

quote:

---

but this time with two identical EPSID-ADMIN entries.

---

This is usually because two definitions now exist in the systems.xml file because another has been added at some point. You can check the systems.xml file to confirm.

quote:

---

2006-10-19 08:46:47.156-06:00 User ID: aapoklud
2006-10-19 08:46:47.156-06:00 [I] Command Line:

---

The blank command line in the log entry above and the [i]”Will the command line arguments “ text in the error dialog indicates that the Post Office definitions do not have the IP address or Port numbers specified. While you did send a systems.xml file with these completed, it does not seem to correlate with the log/error information. Can you confirm that the system definition you are using has all Post Office properties completed? Not completing this information is the most common cause of trusted login failure. While you may already seen this information, a quick reference can be found here: a2g_poa_settings.pdf

As a benchmark, could you also confirm that if you have system admin rights, you can export successfully?

Regards,

Advansys Support

[Support 2]

quote:

---

We deleted the Reveal trusted app via Console One.

---

No problem, just gathering all information. A2Go integrates with Reveal 1.5. There are no conflicts with any other versions of Reveal.

quote:

---

…does that not expose the entire system to the danger of someone accidentally opening up any of the critical files such as wpdomain.db and altering them?

---

It will increase risk but to what extent really depends on your staff. It would probably have to be intentional rather than accidental. Unfortunately, due to the Admin API requirements, A2Go requires this for Enterprise mode. For the next version we will look at caching techniques which may mean these rights will be required only the first time system discovery is performed.

quote:

---

Is that the correct method? Also, where exactly is the trusted key stored on the workstation, and where is the object in the tree?

---

It is the correct method but it depends on what you mean by login: login to the network or login to Windows workstation. The difference is relevant to the second part of your question.

The Trusted Application key information and the system settings are stored in XML files within the current user’s application data folder:

C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To Go

This means that you can login to the Windows User who will be using A2Go, login separately to the network as administrator (i.e. a NetWare login), create the tapp key, then login to the network as the ‘user’. This means all A2Go information is available in the appropriate user’s Windows application data folder.

Alternatively, just copy the XML files above from one Windows user’s app data folder (the Windows user which created the tapp key) to the equivalent Windows user’s app data folder (the user who will use A2Go).

The Trusted Application key is stored within the GroupWise domain database. There is a function to list and manage them in ConsoleOne.

I hope this helps.

Regards,

Advansys Support

[Support 2]

Upon further review, to enable Archive To Go (A2Go) to perform initial system discovery, for Enterprise Mode you will need to provide each A2Go user with Read, Filescan and Write rights to the primary domain directory.

The advice above assumes that the A2Go trusted app key has already been created for that user on the worksation being used.

Please let us know if this does not solve your problem.

Regards,

Advansys Support

[Support 2]

Thanks for the information. At this stage we don’t know the cause of the problem, which appears to be that the GroupWise APIs we use in Archive To Go cannot ‘see’ or recognize your system domain.

Just for our reference, are you able to perform Archive To Go exports in Enterprise mode when a user has admin rights to the domain?

To help gather further information, it may be worthwhile using a utility to troubleshoot this problem. The utility is available from:

http://www.advansyscorp.com/utilities/groupwise-system-discovery.msi

After downloading, double-click the MSI file to install GroupWise System Discovery. Operation should be straightforward. Given the appropriate connection information and access rights, it will attempt to connect to your GroupWise system and identify the Domain and Post Office objects. It will not attempt to list or access User objects. It should create a log file which you can return to us via email (click the “Create email…” button).

Just as additional background information, are you using Reveal 1.5 with Archive To Go 1.1?

In addition, from a couple of the workstations with the problem, could you please send us (support@advansyscorp.com) the systems.xml and settings.xml files from the following folder:

C:Documents and Settings[Windows User Name]Application DataAdvansysArchive To Go

Regards,

Advansys Support

[Support 2]

This will be a basic system component which is not on your desktop PC. Have you tried reinstalling the latest version of MS Internet Explorer?

As you are already running 1.0.0.6, you should not need the work-around listed in this post below, although I’ll put the link here just in case.

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

Regards,

Advansys Support

[Support 2]

We have replied via direct email with the Registry setting.

Regards,

Advansys Support

[Support 2]

In Formativ versions prior to 2.0.1, the Formativ installer would disable the association between VBS/VBE files and the Windows Script Host. However, we changed that operation in 2.0.1 and it should not do that any more.

As you know already, you can re-assign the association from the Formativ Windows Control Panel applet – press the ‘restore association’ button under the additional security section (and ensure the ‘disable association…’ option is unchecked).

If this is not solving your problem, it would appear that the Registry entry controlling this setting is being rewritten by Citrix for some reason. Perhaps a master(?) Registry entry is not set correctly and is propagating when a Citrix user logs in?

Regards,

Advansys Support

[Author]

Replies