Support 1

[Support 1]

I’m sorry to hear of this frustrating experience for you. Actually this forum is moderated though usually not on a weekend (your original post was on Friday 10:53pm local time for us in Sydney, Australia). The alternative to this forum is to write directly to support@advansyscorp.com, however once again our support staff usually do not work on a weekend.

You wrote:

>I had to unarchive all his emails

I’m curious about this. If the emails were in a GroupWise native/personal archive, why not simply copy the archive to another machine and run ATG against the copy? With ATG Creator you can select the default and/or secondary native archive, and opt to exclude the main account (if you only want to export the native archive).

Unfortunately we do not yet know of a foolproof workaround for this problem, other than the options mentioned in earlier posts. It may help to reinstall/update the Microsoft Framework for .NET.

Additional information may assist our engineers to prevent the problem; please provide the following:

• Your installed version of ATG.
• Your installed version of Microsoft Framework for .NET.

Regards,
Advansys Support

[This message was edited by Support 2 on July 11, 2009 at 08:57 PM.]

[Support 1]

The latest point release for GroupWise 7 is 7.0.3 (13 May 2009). You can download it from:

http://www.novell.com/communities/node/8363/novell-info-groupwise-security-alert

Please send your Formativ configuration to support@advansyscorp.com. You can obtain the configuration by selecting Help | About Formativ… from the GroupWise main menu. When the About Formativ dialog appears, go to the Configuration tab and click the button Copy to clipboard. Then paste the text into your reply email (or save it to a plain-text file and include it as an attachment).

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

Were there any other error messages associated with either of the following?

• ‘Archive to go has encountered a problem and needs to close’
• ‘a runtime debug error’

It’s possible that this behavior is caused by running certain Archive To Go modules from a network location. You may find this featured topic helpful.

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

Which version of Archive To Go are you using?

Does the log file list any warnings/errors? You can find the log in the archive folder; its file extension is ‘.log’. It may help if you send this file (zipped) to support@advansyscorp.com

If you want to export the default native/personal archive, all you need to do is check the box at Include default native GroupWise archive. If you want to export secondary native/personal archives then you also need to add the path for each of them.

If “C:My Documentsgwarchiveof393arc” represents a secondary native/personal archive, I suspect the correct path to enter is “C:My Documentsgwarchive”. See this featured topic for more information.

Regards,
Advansys Support

[Support 1]

Thank you for letting us know.

Could you describe how the Windows installation was damaged, please? This information may help us to resolve problems like this more speedily.

Regards,
Advansys Support

[Support 1]

Thank you for the additional details.

There is probably something about the computer environment that causes this problem:

• Is the user running Windows as a limited user, ie. does the problem occur for an administrator on the same computer?
• Does the problem occur on any other computer?
• Are there any special security restrictions associated with the .NET Framework?

We may need to send you a special ‘debug’ build of the solution to help identify the cause of the problem.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

Please provide the following details:

• The version of Advansys Message Saver Pack (open the Properties of the installer file and go to the Version tab).
• The Windows version.
• Is VFU using thin clients with Citrix or Windows Terminal Services?
• Is the following key defined in the Windows Registry?

  HKEY_CLASSES_ROOTCLSID{E75C1463-2311-4C65-AE84-71B846B54BAF}InprocServer32

  If so, what are the values at Assembly and CodeBase?

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

We have received your email, thank you.

Unfortunately the metadata you sent does not reveal an obvious explanation for the Viewer failing to find the file.

It’s possible that sometimes an application cannot find files that are on the Windows Desktop (or a sub-folder of it). Could you move/copy the archive, please, to a folder like “C:Archives” and try again?

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for reporting your latest finding.

Please send the contents of the _metadata folder (zipped) to support@advansyscorp.com for our engineers to analyze. The exported metadata contains only Sender, Recipients, Subject and Date for each message; it contains only Display Name and Email Address for each contact.

What is the size of the file as displayed in File Explorer?

What is the total number of files in this folder, ie:

C:Documents and SettingslpollardDesktopLPollard Archivemedia-01data0000037

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Thanks for letting me know.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

>I want to transfer the complete site with all data to the body text.

By ‘body text’, do you mean the body text of a composing message?

What do you mean by ‘the complete site’?

To clarify, the fields (ie. <INPUT> elements) in your HTML code can be acessed using the FormVariables property, as described in the Formativ Developers Guide. For example, if your HTML includes the field ‘Address’, its value would be retrieved as follows:

  dim iAddress

  iAddress = aDlg.FormVariables.ItemByName("Address")

If you want to copy this value to a message body text, use the GroupWise Token API as follows:

  ' Append the value of iAddress to the composing message ("X00") body text. 
  call GroupWise.ItemSetText("X00", 10, iAddress, 1)

Please refer to the Developers Guide and the Token API documentation. I hope this helps you.

Regards,
Advansys Support

[Support 1]

We have received your email, thank you. We will reply by direct email.

Regards,
Advansys Support

[Support 1]

Thanks for your question, and my apologies for the delay.

Yes, this is normal – the behavior is by design: Archive To Go does not export the Address Book groups, only the group members.

How useful would it be for you/your organization if the groups were included in the export?

Regards,
Advansys Support

[Support 1]

Thanks for the additional information.

This is the first external report of the “CSC.exe” error. The reason I asked about an upgrade is because we have seen this error during testing, usually after replacing the Creator executable by a newer/older version. This executable is a2goengine.exe.

Technically, the problem seems to be that ‘just in time’ (JIT) compilation of a2goengine.exe by the Microsoft Framework for .NET is failing. This may be due to a conflict between the executed file and a previously-cached copy of another version.

The only workaround we know of is to restart the machine, which has always fixed the problem.

If this does not help, you could try reinstalling Archive To Go; it may be best to uninstall manually beforehand (use Add or Remove Programs in the Windows Control Panel).

Finally, it’s possible that your Archive To Go settings have become corrupted (especially if you’ve had to reset your machine while Creator was running). You can also try the following:

• Rename the folder:

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

  to something else, like:

  C:Documents and Settings[Windows Username]Application DataAdvansysArchive To Go.bak

  .
  This folder contains the configuration files for Archive To Go.

• Start Creator. Note that you may need to reconfigure certain settings, eg. for Enterprise Access.

Please let me know how you go.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

Which version of GroupWise are you running?

The SmartField Assistant should have been bundled with Multiple Signatures. It might be helpful to obtain a diagnostic trace of SmartField Assistant’s progress. In order to gather such diagnostic information, you will require a debug event viewer. If you do not already have one, I suggest you download and install DebugView from http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx, and follow the steps set out below:

[Author]

Replies