Support 1

[Support 1]

The error relates to GroupWise failing to save the message properties envelope (or message Properties) to a file. The following is a list of known conditions that lead to this of error:

• The installed version of GroupWise is 7.0.2 HP or below.
• Archive To Go is processing a GroupWise native/personal archive, and GroupWise is running but not switched/proxied to that archive.
• Archive To Go is processing a shared incoming folder within the native/personal archive.

To avoid this problem when using GroupWise 7.0.2 HP or below, you would need to run GroupWise and switch to the required native/personal archive, then set Archive To Go to include only that archive (not the main account). In other words, if message properties are required, GroupWise must be switched/proxied to the mailbox/archive of interest, and no other mailbox/archive can be included during that Archive To Go session.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

Which version of Archive To Go Viewer is on the CD-ROM archive? You can see the version by going to the main menu and choosing Help | About.

If you use Windows File Explorer to view the contents of the first CD, what folders are listed? The top-level folder should be “media-01”, and it should contain these folders:

_metadata
_viewer
data

You may need to compare the folders and files on the CD with those in the original location.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem. Most reports of this error involve a GroupWise native/personal archive, or a folder that contains more than 4,960 items, or both.

If a thorough GWCheck has been done already on the affected message store, I suggest dividing a large folder (4,960 or more messages) into several smaller folders (eg. Mailbox-2009, Mailbox-2008, etc.) before running Creator again.

Please let me know how you go.

Regards,
Advansys Support

[Support 1]

Which edition of Windows (XP, Vista) are you using?

Are you using a thin client served by Citrix or Windows Terminal Services?

Please reinstall Message Saver; it should install the Formativ Framework for .NET. After that, please confirm whether the Formativ Framework for .NET was installed.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

I think one or more XML files used by A2Go have become corrupted, perhaps because of a forced reset of the machine. Which files are affected depends on the A2Go module that displays the error: Creator, Indexer or Viewer. Please send the appropriate files, as indicated below, to support@advansyscorp.com.

Creator

• a2goengine.exe.config in the installation folder (usually C:Program FilesAdvansysArchive To Go).
• The following files in C:Documents and Settings[/i][Windows User Name][/i]Application DataAdvansysArchive To Go:
  settings.xml
  systems.xml

Indexer or Viewer

The _metadata folder (zipped) within the archive. The exported metadata contains only Sender, Recipients, Subject and Date for each message; it contains only Display Name and Email Address for each contact.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

TOpenDialog is a wrapper class for the Windows File Open common dialog. Unfortunately this class does not provide a way to set the screen position of the dialog. I believe the position is specified in the Windows Registry, and will change if the dialog is dragged away from its default position.

This may explain why it appears off the screen – someone has, at some point, dragged a File Open dialog to that position. Otherwise, the default position is the screen center.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for trying the other installers.

Could you send the following file (zipped) to support@advansyscorp.com, please?

C:Documents and SettingsAll UsersApplication DataAdvansysFormativ1.0AppletsMessage Saver_Flexalock.vbf

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for your report.

Can you confirm that .NET 1.1 is installed, please?

Could you try uninstalling the Formativ Framework for .NET before you reinstall Message Saver?

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

If these products were working previously on your computer, something must have changed to cause this “trial expired.” Can you describe what has led you to reinstall them, please?

You will need to re-enter the registration codes that were sent to you for these products at the time of purchase. Use the Registration Utility for this; you will find it on the GroupWise Help menu.

Please let me know how you go.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

An email has been sent to you with details of how to obtain the updated solution.

I hope this helps.

Regards,
Advansys Support

[Support 1]

We have received your files by email, thank you. A reply containing a fixed file has been sent to you.

Regards,
Advansys Support

[Support 1]

Thank you for the clarifications.

We have received your email, thank you.

I think the Message Saver solution has become corrupted. What is the name and version (see file properties) of the installer file that you used for reinstalling? If this is a different installer file than that used for installation on other machines, could you try using a different copy? If no other installer is available, please copy the solution file from another machine where it is working (you should find it in a similar folder to that listed in your initial post above).

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

I think it is possible to do this in VB, using one of the Novell APIs for developing to eDirectory. Unfortunately I cannot advise you on a specific API, but the ActiveX controls (NDAP/LDAP) do make it possible to develop an eDirectory application quite rapidly. You might find this sample helpful.

I hope this helps.

Regards,
Advansys Support

[This message was edited by Support 1 on February 04, 2009 at 05:25 PM.]

[Support 1]

Thanks for your enquiry.

The behavior your describe is by design: Stationery will not overwrite an existing subject because the user may want to include that subject.

How important is it for you that Stationery overwrite the subject, or is it simple enough to clear the subject before applying stationery? It is possible to add a setting/hotkey that makes Stationery behave this way.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem. Does it occur when attempting to save all or only some messages?

It sounds like the Message Saver solution has become corrupted. Has it been working on the affected machine, or has it just been installed there? I suggest reinstalling the solution before trying again. If there is no improvement, please obtain another copy of the installer – either from a different machine, or download it again.

I hope this helps.

Regards,
Advansys Support

[Author]

Replies