Support 1

[Support 1]

Thanks for reporting this problem.

Which version of Archive To Go are you using?

Are the shared mailboxes GroupWise Resource objects?

How many eDirectory Trees are in your GroupWise system? If you have not authenticated to the Tree that contains a given mailbox, the mailbox (and its containing post office and domain) will not be listed.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

You are welcome. I hope my suggestions will help.

Regards,
Advansys Support

[Support 1]

Thanks for the clarification.

Yes, the problem is clearly environmental, ie. it is associated with specific GroupWise accounts.

I hope that archiving messages helps to fix this issue.

Regards,
Advansys Support

[Support 1]

Thanks for your question.

The log summary, the section at the end of the log, includes the total number of items found and the number processed. This will give some idea of how many items could not be processed.

The message ‘An error occurred in allocating memory’ is sometimes associated with a document or attachment that Archive To Go was unable to extract from GroupWise. If you have not already done so, please do a thorough GWCheck (Fix Structure and Contents) before trying again. You could try to change the mailbox contents slightly before running GWCheck, eg. move some folders or messages; this can force a database rewrite to fix any corrupt data.

If you like, please send the log file (zipped) for us to analyze. You will find it in the archive folder. If you are referring to the Indexer, you will find its log file in the following location in the archive:

media-XX_indexinfindex.log

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

I have edited your post only to change the format, because some lines were very long.

It looks like you have used GWCheck on the user’s machine to obtain the mailbox stats. If you have not done a thorough GWCheck (Fix Structure and Contents), please try that.

It looks like you have a Formativ applet that executes on start-up, and fails while attempting to access a folder in the GroupWise mailbox. Either there is no matching folder or the mailbox is corrupt. Perhaps GWCheck will fix this. You may need to determine which applet is involved – your Formativ configuration shows that 6 applets are in the eDirectory cache. This may help to find out which folder is not found.

Finally, we recommend using the latest point release of any GroupWise version. For GroupWise 7 the latest patch is 7.0.4; for more information see Novell Patch Finder.

I hope this helps and please let me know how you go.

Regards,
Advansys Support

[Support 1]

Thank you for reporting these problems.

> XP installs, but in running, the splash screen comes up and then nothing…

Unfortunately the only known workaround is to restart the machine. During shutdown, you may see the following error pop up:

quote:

---

CSC.exe
The application failed to initialize properly (0x0000142)

---

This seems to happen immediately after upgrading from an earlier version, but does not recur after a system restart.

> a large error screen comes up referencing system application exceptions, config files, license files, etc.

We have a new 64-bit-compatible beta available. Please write to support@advansyscorp.com if you wish to test the beta.

Regards,
Advansys Support

[Support 1]

Thanks for letting us know.

We have confirmed this is caused by a defect in Creator 2.0. For the moment the available workarounds are:

– Log into all eDirectory Trees.
– Migrate the system definition created with Creator 1.5 as described in my post on June 30th.

We are in the final stage of testing an update that fixes this defect; the update will be available within a few days.

Regards,
Advansys Support

[Support 1]

Thanks for reporting these errors.

> “21,417 contain one attachement which is not available”.
> …
> So when the user calls up any one of those attachements, they will not be available?

Yes. Note that the log entry states ‘at least one attachment… is not available’. Other attachments in a single message may be available. It is possible that for some of these 21,417 messages, the unavailable attachments are not important, eg. Mime.822 or some other ‘system’ attachment.

An attachment may be unavailable because it is very large and cannot be loaded into the machine’s available memory, or for some other reason.

[I] [Warning] Cannot load file “TEXT.htm”: 231 Byte(s)

The next log entry should show the related error. This attachment is very small, so it is probably not a machine memory error.

Unfortunately, without looking at the complete log, it is difficult to say what has caused this problem. You may wish to send the log (zipped) to support@advansyscorp.com for us to analyze.

> [I] 1,165 message(s) contain at least one attachment which could not be saved.

This means that Archive To Go requested GroupWise to save these attachments but GroupWise was unable to do so. It could be due to some data corruption in the GroupWise message database, or due to some other reason.

We tend to see more problem reports with GroupWise personal archives.

In general we recommend running a thorough GWCheck (Fix Structure and Contents) on the GroupWise mailbox and personal archives prior to commencing an export. Also, we recommend updating your GroupWise client to the latest patch; for 8.0.1 I believe the release date is 8 January 2010.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Your enquiry has been replied to by direct email.

Regards,
Advansys Support

[Support 1]

Your enquiry has been replied to by direct email.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

>I Try to switch to GW 8.0.0 => Bug

Do you get an error message with GroupWise 8.0.0? If so, what is the message text?

We recommend using the latest update to any major version of GroupWise. For version 8.0 the latest update is 8.0.1, January 8 2010.

Regards,
Advansys Support

[Support 1]

Thank you for reporting this problem, which is not familiar to me.

If there is an error message when Finder crashes, what is the text of the message? It’s possible that this is due to the .NET security mechanism which must be configured to allow execution of an application from a remote location. This would be relevant if your DVD reader is on a different machine. Please review this featured topic: Running Archive To Go from a Network drive.

I am not aware of size limitations that apply to searching an archive. Assuming a valid index exists, Finder only reads the index data. Please send the index log (zipped) to support@advansyscorp.com; you will find this file in the archive sub-folder media-NN_indexinf (where ‘media-NN’ is the last volume in the archive).

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Tedd,

Many thanks for your detailed description; this is very helpful. Our engineers are now investigating this behavior with A2G v2.0.

In the meantime, please test your environment by using our stand-alone GroupWise System Discovery utility, which attempts an administrative GroupWise system login and discovery of all domain and post office objects. If there is a rights issue or folder access problem, the utility should still log a similar error because it uses the same technique as Archive To Go. Like A2G v1.x, the utility was built for .NET 1.1; if the utility fails to reproduce the problem we may need to provide you with a .NET 2.0 build for comparison.

The utility is available from:

http://support.advansyscorp.com/utilities/groupwise-system-discovery.zip

After downloading, double-click the MSI file to install. 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 and use support@advansyscorp.com).

In addition, you may be able to get v2.0 to use the system defined with v1.5, as follows:

• Ensure that ‘systems.xml’ is available and not renamed to something else. This is the cache file for system definitions created by Creator 1.x.
• Navigate to the folder below:

  C:Documents and SettingsAll UsersApplication DataAdvansysArchive To Go

• If this folder contains the file ‘a2go‑config.bin’, rename it as something else, eg. ‘a2go‑config.bak’.
• If Archive To Go 2.0 is installed, re‑run the installer for it and choose the Repair option. If it is not installed, run it as a normal installation.

  This should replace ‘a2go‑config.bin’ by a copy with the default settings.

• Run Archive To Go Creator 2.0, which should migrate the settings in your ‘systems.xml’ and ‘settings.xml’ files. You should see the system defined using Creator 1.5. Try to archive one or multiple accounts. What results do you get?

Regards,
Advansys Support

[This message was edited by Support 1 on June 30, 2010 at 08:44 PM.]

[Support 1]

Thanks for reporting this.

Please provide a description of your eDirectory topology, eg. total Trees, total Domains, total external Domains. Are any Domains distributed across multiple Trees? If you prefer, send your response to support@advansyscorp.com.

After successful creation of a system definition, Archive To Go Creator caches the definition. This is important because it avoids the need to do system discovery every time you use Creator. Both versions 1.5 and 2.0 will cache any system definitions.

Please follow the directions below, for doing a ‘clean’ test with Creator 1.5.

• Use Windows File Explorer to navigate to the folder below:

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

• If this folder contains the file ‘systems.xml’, rename it as something else, eg. ‘systems.bak’.
• If 2.0 is installed, uninstall it. Install Archive To Go 1.5.
• Run Archive To Go Creator 1.5. You should see that no system is defined. Try to create a new system definition. What results do you
  get?
• If you do not wish to retain the test system definition created at step 4, delete ‘systems.xml’ and restore the original name of ‘systems.bak’ (steps 1 and 2). Otherwise, you may delete ‘systems.bak’.

I look forward to your reply.

Regards,
Advansys Support

[This message was edited by Support 1 on June 29, 2010 at 07:18 PM.]

[Support 1]

Thanks for reporting this problem.

Please send the process log file (zipped) which you should find in the archive folder, to support@advansyscorp.com. Our engineers may be able to recommend a specific solution based on the log contents.

Regards,
Advansys Support

[Author]

Replies