Support 2

[Support 2]

Yes, Formativ only uses the first configuration object found when checking certain eDirectory objects for the See Also field entry. It checks backwards up the tree for a Formativ Configuration Object entry, starting from the User Object, in the following order:

1. User Object
2. Group Object (only if Group search is enabled in the Formativ Windows Control Panel Applet)
3. Organization Unit Object
4. Organization Object

I hope this helps.

Kind Regards,

Advansys Support

[Support 2]

Just prior to the end of the year we managed to track down and reproduce this error with a basic test C3PO. Our research confirms it is a GroupWise C3PO issue and not specific to Formativ. The D107 error will occur when forwarding or replying to an embedded message with any C3PO which traps the Forward or Reply events.

We provided the test code and results to the GroupWise engineering team, who have documented this issue as GroupWise bug #461686.

At this stage we do not know when a resolution will be available, although hopefully it will be addressed in the next GroupWise service pack for 7.x and 8.x.

Unfortunately, for technical reasons, we are cannot provide a work-around.

Kind Regards,

Advansys Support

[This message was edited by Support 2 on January 05, 2009 at 06:23 PM.]

[Support 2]

Thanks for the confirmation. We will write to you direct via email to continue troubleshooting and report back the results to this thread.

Kind Regards,

Advansys Support

[Support 2]

Thanks for your reply, which is interesting. If you unregister or uninstall Formativ, presumably the problem does not occur?

Regards,

Advansys Support

[Support 2]

Hi André,

Sorry for the delay. We are still investigating the exact cause of the problem but we now believe it is not related to problematic registry entries but potentially a low level GroupWise code change which has impacted our Third Party Handler DLLs.

To help verify our initial problem tracing results within your environment, on a workstation with the problem, could you please try the following steps, which will unregister the Formativ TPH Dlls. Formativ will still continue to operate normally but any custom applets using low level token integration features will not (most solutions do not normally use this feature).

• Close the GroupWise Client.
• Open the Formativ Control Panel Applet.
• Select the General Tab (it should be showing by default).
• Under the Enable/Disable group, if selected, unselect both Applet Recorder and Command Blocker (for Formativ Runtime, only Command Blocker is relevant).
• Press OK.
• Restart the GroupWise client and test the Forward/Reply functions on an embedded message.

Once we receive your results we will review the next course of action.

Thank you in advance for your assistance.

Kind Regards,

Advansys Support

[Support 2]

Hi,

We just received information that this issue is being tracked by Novell as bug #206743 (originally reported in 2006). We have not been advised when it will be addressed.

Regards,

Advansys Support

[Support 2]

This is a non-trivial change but we will log your request and reason for consideration when these features are reviewed. When this feature was initially designed and developed, we spent considerable time consulting with Novell eDirectory engineers before settling on the choice of attribute usage.

Kind Regards,

Advansys Support

[Support 2]

Thank you for the additional details and feedback. We can confirm that in addition to core search engine enhancements, we are certainly intending to add relevant GUI search extensions for the next major release, 2.0. We would like to do it earlier but our focus has been on fundamental export quality and also adapting to/testing minor GroupWise updates and of course, the major QA testing required for Bonsai, which is a timetable controlled by Novell.

With regard to the search issue you are experiencing, from your last post, the search function appears to be working as outlined in our previous post, where you need to enter first characters of the whole word you are looking for and then the wildcard, in other words, firstname* is the first part of the email address character string firstname.lastname@xyz.com with the wildcard * appended. From your post it appears that this syntax is returning the results you expect.

quote:

---

If I search for lastname, the same email is not returned. If I search for xyz.com, the email is NOT returned. In my mind, all 3 searches should produce the email I am looking for.

---

As these character strings, lastname and xyz.com are not the first characters of the email address string firstname.lastname@xyz.com, then the search engine cannnot return the results you seek. If you don’t restrict your search to a specific field, like [b]from:[b], in other words you do a general search for lastname or xyz.com and they appear anywhere in other parts of a message as whole words, then these results would be returned.

You can also use other approaches to do the search with a combination of search operators, including specific field(s), for example:

Example 1: from:(firstname OR lastname AND @xyz.com~)
Example 2: from:((firstname AND lastname) or @xyz.com~)
Example 3: from:(firstname OR lastname or @xyz.com~)
Example 4: firstname AND lastname AND @xyz.com~
Example 5: from:(firstname OR lastname or @xyz.com~) AND (firstname AND lastname)

The brackets in the examples help refine the search results. The first three examples are confined to the from field, the fourth example is an unrestricted field search and the fifth example uses a combination of techniques.

The next version of the search engine technology will have extended capabilities and will be able to have wildcards prefixed to text, like *xyz.com. This enhancement combined with the GUI extensions will offer more flexible searching. To take advantage of the new search technology, it is planned that you will be able to reindex your existing Archive To Go archives.

Kind Regards,

Advansys Support

[This message was edited by Support 2 on July 29, 2008 at 06:04 PM.]

[Support 2]

Thank you very much for your feedback and questions. We will certainly be enhancing the search engine capabilities in version 2.0. Originally we had planned to expose a more advanced GUI for the search facility but as we had very few requests for it beyond the existing simplified interface, we decided to coordinate it with enhancing the core engine, which will offer additional end-user search options.

The way search works at present is that you need to put in the first characters of the whole word you are looking for and then the wildcard. If additional characters immediately precede the search text string robles* without a space, such as grobleston, the wildcard search would not find grobleston but rather it would find matches like robleston, robleskin, roblesse etc. In the case where you don’t know the beginning of the word or text string for which you are searching, you can try the Fuzzy search operator (~), which will find words with similar spelling, for example: from:robles~ (using address field search) or just robles~. While the Fuzzy search operator may return more results than you need it should also include the one you want.

I hope this helps and please let us know if you have any further questions.

Kind Regards,

Advansys Support

[Support 2]

We are not aware of any feature which existed to export a corrupted GroupWise personal archive. Unfortunately, if the GroupWise archive is corrupt, it is unlikely the GroupWise APIs we use would be able to access some or all of the archive. What we have continued to do since the inception of Archive To Go is to increase the robust nature of our use of the GroupWise APIs to try and cope with all known potential failure conditions due to corrupted data within the GroupWise data store, whether it is exported from the server, cache or personal archive.

It depends on what type of corruption to which you are referring. There were some parameters introduced which tried to cope with inaccurate messages dates within an archive and you may be able to add a ‘start folder’ parameter to enable you to skip some folders which you know are causing problems during the export.

Can you provide more information on what you are experiencing or trying to achieve for a particular GroupWise personal archive export?

Kind Regards,

Advansys Support

[Support 2]

Thanks for your feedback and question. As you have noticed, the underlying technologies we have selected are suitable for this application and web enabling is certainly on our futures roadmap, although we cannot provide a specific time-frame yet.

The other question about local mode and enterprise mode has been answered by direct mail.

Kind regards,

Advansys Support

[Support 2]

Novell have created bug #363742 to track this issue.

Kind Regards,

Advansys Support

[Support 2]

Thank you for your post and enquiry. While the underlying technologies used within Archive To Go will allow this functionality in a future release, our current versions do not offer search across multiple archives. This is on our enhancement list and, as it is a major development, we are targeting a 2.0 release which will not be until Q3 or Q4 this year.

Another thought is that we are in the final development stages of HTML and PST converters, which will take an Archive To Go archive and convert it to HTML/separate attachments or Outlook PST format. This would only help in the interim if you have access to another search product that will index either HTML/file attachments or PST. If you wish to pursue this path, please send an email to support@advansyscorp.com.

Kind regards,

Advansys Support

[Support 2]

Thanks for your enquiry. The Formativ Portal technology, which took significant resources to develop, is classed as Advansys internal IP. Unfortunately this means we cannot provide information on how it works. Sorry we could not be of assistance in this case.

Kind Regards,

Advansys Support

[Support 2]

Thanks for your reply. Sorry, 1.2 was a typo, it should have been 1.5, which is released. The engineers will look at the information you sent and get back to you.

Kind Regards,

Advansys Support

[Author]

Replies