Forum Replies Created
January 12, 2021 at 8:53 pm in reply to: System.ArgumentException: The path is not of a legal form. #10692
This post has been replied to directly and should a solution be found, it will be documented here.April 7, 2020 at 4:18 pm in reply to: Invalid Image Size error with GroupWise 18.2, display scaling greater than 100% #10649
Thanks for your reply. Can you please send to support[AT]advansyscorp.com your Formativ Configuration information and the steps to reproduce, including which applet you are executing and how the applet is initiated, such as manual, upon startup etc.. Does the error happen with any applet?
The Formativ configuration information can be accessed by selecting the GroupWise client’s Help menu, select About Formativ, select the Configuration tab and use the Copy to Clipboard button, then paste the config info into an email reply to support[AT]advansyscorp.com.
Advansys SupportApril 6, 2020 at 2:55 pm in reply to: Invalid Image Size error with GroupWise 18.2, display scaling greater than 100% #10644
Thanks for your post. Can you confirm you still get the Invalid Image Size error even though you have disabled Formativ Portals?
Advansys SupportApril 11, 2019 at 7:19 pm in reply to: Exchange groupwise migration quick config does not show app #10563
Thank you for your post. Can you please confirm you mean the Personal Outlook Migration Pack Applet (https://www.advansyscorp.com/products/extend/fv-solutions/personal-outlook-migration-pack/) which you are trying to use with Formativ Express?
Did you restart the GroupWise client after installing the Personal Outlook Migration Pack?
Advansys SupportMarch 12, 2019 at 10:23 am in reply to: How do I get applets to be active in the GroupWise client without eDirectory? #10554
Thank you for the additional information and please see responses below.
when the ZENworks guy distributes the encoded version, it’s going to stomp on my source code version
Yes, this is true if your Applets folder is the same as every other user within the organization and is automated by ZENworks. This risk can be mitigated by changing your default Applets folder for your workstation, so that your source code applets load from a different folder than other users. Change the default folder locations by using the Formativ Windows Control Panel Applet, which will update an associated registry entry.
This approach should not substitute for having an alternative, secure backup of your source code. 🙂 We use a source code control system to store our Applet source code.
While the use of eDirectory automated the encryption of the applets during distribution, moving to a ZENworks approach means the applet developer/distributor needs to Flexalock the applet prior to ZENworks distribution to GroupWise clients running Formativ Runtime.
Is there a corresponding File, Open operation that I just don’t see?
No, you are not missing these options, they do not exist. The reason is that it is assumed any applet to be loaded will be stored in either the local My Applets folder or the public user (shared) folder on the workstation. The applet must be physically copied into one of these locations before it will appear in the Creator IDE and accessible via the GroupWise client interface.
I’d like to import the saved file back in
Copy the original applet source vbf into the workstation’s Applets folder and restart the GroupWise client.
The saved version of the source code has the form data encoded in it. Is it reasonable that I can open the saved off source file, copy all to the clipboard, and paste all into the applet in the library, and the form imports as well?
The applet source XML file does include form data although you cannot import forms by pasting them into the IDE’s applet source code editor. When the applet XML file loads, only parts of the XML are loaded into the visible area of the IDE’s editor.
To achieve your objective, simply copy the applet source vbf into the Applets folder, restart the GroupWise client and open the Formativ Creator IDE.
Should you have the need in future, to Export/Import forms, click on the Forms button on the IDE when an applet is loaded and choose EXPORT or IMPORT. To import you will already need to have previously exported one or more forms (.frm files).
Please let us know if you have any further questions.
Advansys SupportMarch 9, 2019 at 5:35 pm in reply to: Formativ runtime appears to hang on GroupWise client shut down #10549
Hi, thank you for the issue report.
This is not an issue we’ve come across previously and don’t have an idea of the cause, particularly as it works on some workstations and not on others within your environment. There is no known way to check if Formativ is still trying to contact eDirectory in the context you mention, apart from having a look for clues in the Formativ Config information (GroupWise Help | About Formativ – Configuration Tab).
Is it possible some registry entries were not written correctly or the same between all workstations? Could it be related to different anti-virus behavior on the workstations which hang? These are simply brainstorming suggestions.
Feel free to send a copy of the Formativ Configuration from a working workstation and one which hangs to support(AT)advansyscorp.com.
Advansys SupportMarch 9, 2019 at 5:22 pm in reply to: How do I get applets to be active in the GroupWise client without eDirectory? #10548
Hi, thank you for your post. Just to check some assumptions, are the applets Flexalocked or are they the original source code version?
As you are migrating from eDirectory distribution where the GroupWise client integrations are handled automatically, you need to copy the Flexalocked version of the original source code applets into the Applets folder on the workstation, which is usually the D:\Users\[user_name]\Documents\Advansys\Formativ\Applets folder. Formativ Runtime can only load Flexalocked or Encoded Applets.
As long as the client integrations have been preset in Creator, when you copy the Flexalocked applet into the correct location on the workstation, when the GroupWise client starts the applets should be integrated correctly.
Great news, thank you for the update. For flexible workstation security configuration, Archive To Go has a hierarchical search order for a2go-config.bin files to allow for locking down the configuration on a workstation or leaving it accessible in a User folder.
Upon startup, the a2go-config.bin search priority is as follows:
– Override folder (if provided)
– Program Files installation folder
– Local Application Data folder
– Common Application Data folder
Thank you for your post. Can you please check there isn’t an a2go-config.bin file in the C:\Program Files (x86)\Advansys\Archive To Go folder? If not, can you please search the local PC to see if any other a2go-config.bin files exist apart from the one you copied into the C:\ProgramData\Advansys\Archive To Go folder?
Hi and thanks for your message. Yes, it should be possible, although we don’t have a pre-written Formativ solution which matches your exact requirements. There is an example written many years ago and the general approach should still be valid. The source code will be sent to you via direct email and hopefully it will be of some assistance.
Thanks for the update. For future reference, creating or updating a search index for the archive with Archive To Go 4.0 Indexer will also invoke the message cleaner during the indexing process.
Thank you for your message. You do require the Outlook Client installed because the Advansys PST Creator utilises the Outlook APIs, which are made available when Outlook is installed.
Advansys SupportJuly 20, 2017 at 6:49 pm in reply to: Error: Archive To Go Creator stopped working on partial sync #10143
No problem Grant, please let us know if you have further questions.
Advansys SupportJuly 19, 2017 at 10:38 am in reply to: Error: Archive To Go Creator stopped working on partial sync #10140
Thank you for the additional background. It is disappointing to learn partial sync is not working for you, particularly as it is intended to be a core feature of 4.0. Indeed, if it was working on your workstation, it would ignore in the archive any previously exported items subsequently deleted from your GroupWise mailbox or personal archive. Even so, Full Sync should achieve your objective by placing any previously exported items, subsequently deleted from GroupWise, into the Deleted Items Archive folder. While they will not exist in their previous GroupWise folder structure, they remain searchable and accessible within the target Archive To Go archive.
But that I understand that means I need to maintain a GroupWise archive, too, rather than just delete emails otherwise delete emails will also be deleted from my A2Go archive (yes?)
Wen you use Full Sync (default setting), previously exported items permanently deleted (not in the Trash) from GroupWise are preserved by the export moving them to the Deleted Items folder in the target Archive To Go archive. The Deleted Items Archive folder is searchable using the high-speed full text index feature. Partial Sync uses different GroupWise APIs to provide a faster comparison process and part of the performance gain is the trade-off that this approach ignores items deleted from GroupWise and thus cannot support the use of the Deleted Items Archive folder.
Using a GroupWise Personal archive to preserve the items may not be a bad idea in terms of additional backup, even if Partial Sync can be made operational again.
If you have any questions about the above information, which for clarity and accuracy was edited since the first post, please let us know.
The logs will be reviewed to see if they help identify a possible cause. It may be necessary to isolate workstation environmental factors by running a control test on another computer with a new installation of Archive To Go.
Advansys SupportJuly 11, 2017 at 8:26 am in reply to: Error: Archive To Go Creator stopped working on partial sync #10133
Sorry to hear about the problem, which is not normal and indicates something fundamental is wrong. Unfortunately the nature of the error documented provides no indication of the potential cause. For troubleshooting purposes, please send the export log(s) to support(AT)advansyscorp.com for review. The main log is found under the archive’s main folder and update (partial sync) logs are found in the update sub-folder.
Does your message mean you have always exported your account once only rather than using the update feature, ever since you first installed the release version of Archive To Go 4 (around November 2016 according to our records)?
Does the “Archive To Go has stopped working” message appear every time you attempt an update, no matter how many times you attempt it?