Forum Replies Created
-
AuthorReplies
-
Hi Martin,
ItemAddMimeField was not added to the language as a separate call. This is primarily because Formativ inherently supports the generic “GroupWise.ThrowToken” function, which enables any GroupWise token to be executed, regardless whether it is overtly exposed as a unique command within the Formativ language.
ItemAddMimeField is not a command we use in our solutions nor have we had any requests about it since our last support post above in 2011.
Does the work-around listed above not work in your case?
Kind Regards,
Advansys Support
June 7, 2017 at 11:45 am in reply to: Question: Is there a way to "merge" or join multiple A2Go archives into one? #10127Hi Grant,
Thank you for your question, although unfortunately Archive To Go archives cannot be merged and there are no plans to add this capability.
Kind Regards,
Greg
Advansys SupportAdded reply to correct activity date following forum migration.
Added reply to correct activity date following forum migration.
Added reply to correct activity date following forum migration.
Hi Grant,
Thank you very much for your feedback, which means a lot to us!
Kind Regards,
Advansys Support
September 19, 2016 at 1:23 pm in reply to: Archive to Go 4.0 Beta – crash after deleting folders #10018Hi Grant,
Thank you for the problem report and you should definitely be able to perform an update after deleting folders and moving messages. It may be a beta software bug you’ve uncovered, an issue related to environment, GroupWise version or perhaps a combination of factors.
We would like to determine the cause and resolve the issue. Are you able to send via email the logs from the crashed attempts to support(at)advansyscorp.com?
While it is probably evident, when sending email to Support, in the support email address shown above, please replace the character sequence “(at)” with a single “@” character.
The original log is in the archive’s top level folder and update logs are found in the [archive folder]updatelogs folder.
When Archive To Go crashed, how did this present? Were there an error message dialogs?
How many times did you attempt to re-run the update process and if multiple times, did it fail at the same point?
Our first step will be to attempt to reproduce the error and knowing the exact error you are experiencing will help in this process.
Thank you again for your report and any assistance you can provide in helping us to replicate the problem.
Kind Regards,
Advansys Support
Hi Grant,
Thank you very much for your feedback and for advising us of the positive outcome.
As you progress to performing archive updates or using other features, please let us know if you have further questions, suggestions or comments.
Kind Regards,
Advansys Support
September 16, 2016 at 2:42 am in reply to: Question: splitting a local archive into smaller archives? #10015Hi Grant,
quote:Is it possible to create an Archive to Go archive from ONLY a local GroupWise archive (not the online mailbox)Yes. The way to do this is to select your primary or secondary archive(s) and on the General Options Wizard page, uncheck the “Include the main account” option.
quote:and using dates to segment the massive archive into smaller archives by date, i.e. effectively splitting it into a 2007, 2008, 2009, 2010, etc. set of archives?Yes. Probably the best way to do this is by creating an initial export template with a date range, the copy and edit it:
- change the name of the template and description to match what it does, i.e. 2007-GW-archive, 2008-GW-archive;
- change the date range to the appropriate settings; and
- change the output location so that this date range export creates a new archive.
The advantage you will have is that the archives will be smaller. The disadvantage is you will not be able to search across all archives simultaneously and instead you would need to search each year separately because they would be in separate archives.
An alternative with version 4.0 is to create your complete export of the full GroupWise archive, then create an export template which updates only a specific date range of the archive, for example 2016. This will keep the archive in a monolithic format which can be searched in full and yet updates will be restricted to a specific date range, making updates much faster.
It really depends on how you update your GroupWise personal archive, for example, if you tend to only archive this year’s items rather than randomly from older years. Of course you can always choose to do a full update at any time, which is now possible in 4.0 and can be very fast, particularly if you use SSDs or other fast storage media.
Experimenting with 4.0 archive updates may make your decision more clear. Hopefully this addresses your questions and, if not, please post further questions.
Kind Regards,
Advansys Support
Hi Grant,
Thank you for your feedback and we look forward to learning of your test results.
Kind Regards,
Advansys Support
Hi Grant, thank you for your post and sorry to hear about the frustrating problem. This is an unusual issue which appears to be related to the _viewer folder support files not being copied across correctly during archive creation, indicating that the archive process may not have completed successfully. Finder relies on a range of files to support the main program, a2gofinder.exe and this is likely why you are seeing this error after copying only this file.
The key to solving this issue is to identify what went wrong during the creation process, which can sometimes be related to GroupWise data corruption issues. Can you please send your archive log, which can be found in the top level folder of the archive, to support(AT)advansyscorp.com and after reviewing we will correspond with you about it by direct email.
While the log file may reveal the clue needed to isolate the cause, it would be useful to know in your email to support what actions you took after registering, for example, as the trial is limited to 10 items per folder, did you create a new archive?
Were there any messages showing on the Wizard completion page when it completed?
Kind Regards,
Advansys Support
Thank you for your report. This is an unusual disk access problem which can be caused by real-time anti-virus scanners. If there happens to be a virus attached to an email, sometimes the anti-virus (such as Microsoft Security Essentials) can lock the file as it is saved out during the conversion process to XML. This is one reason we recommend disabling real-time malware checking during an export, which not only makes the process faster, it can also avoid this potential issue. Any GroupWise message attachment containing a malware cannot be executed during the export process. You can always run a manual scan after the process is completed.
There can be many other reasons for file system issues, although according to your history of successful exports, this would be a good place to start because the error appears to be specific to this GroupWise archive and hence may be data related.
Another suggestion, which will be relayed to you by direct email, is if further troubleshooting is necessary you may wish to try with Archive To Go 4.0 (currently in private beta). 4.0 introduces a new updatable archive format, which enables the resumption of the export after stopping or a failure. This makes it ideal for easier troubleshooting of data related issues and prevents the need to re-export data already exported successfully.
Kind Regards,
Advansys Support
Thank you for your post. In case it assists other customers, Advansys Support was advised by direct email that the problem was resolved by accessing the Formativ Control Panel Applet from the Windows Control Panel, disabling and re-enabling “Command Blocker”, then restarting GroupWise.
Kind Regards,
Advansys Support
Thank you for your post. The server is the GroupWise server’s primary domain IP address and the port is the default REST Administration port.
As with 2012 and earlier, you need to have System Administration rights to be able to create a Trusted Application key.
It is possible to configure multiple master accounts and you can choose one for synchronization during a specific session.
Apart from creating a system definition using the REST API, the process is the same for 2014 as it was for previous versions.
We will send you some documentation via direct email.
Kind Regards,
Advansys Support
Great news, thank you for the update.
Kind Regards,
Advansys Support
-
AuthorReplies