/ Forums / Advansys Formativ / Commercial Formativ Solutions by Advansys / Filing Assitant crashes with GW 2012

  • Creator
    Topic
  • #4816
    mawim
    Participant

    Hello,

    some days ago my company changed to GW 2012. Since that the filing Assistant doesn’t work anymore.

    It simly crashes after selecting the folder where the message should be moved to.

    My configuration ist:
    – Win XP
    – GW 2012 (Build 97039; Languages DE EN)
    – Fomrativ Runtime 2.5.0.0
    – Calendar Pack 2.0
    – Filing Assistant 1.0

    Is there a solution for this problem?

    Best
    Martin

  • Author
    Replies
  • #9099
    Support 2
    Moderator

    Dear Martin,

    Thank you for your report. As GW 2012 is still in beta phase, we are still working on compatibility testing and your feedback is most helpful. At this stage we do not know the problem and will need to investigate.

    We cannot reproduce the problem with the lastest GW 2012 beta update (not the public beta), although we tested it initially using the English language setting.

    Does it crash on all folder types you select, such as personal and shared?

    Which version of the GW 2012 client are you using? Can you send us the Formativ configuration information from the Help | About Formativ dialog (please send to support(AT)advansyscorp.com … replace the [AT] with @)?

    Kind regards,

    Advansys Support

    [This message was edited by Support 2 on November 07, 2011 at 05:55 PM.]

    #9104
    mawim
    Participant

    Hello,

    I sent the request information to the email address mentioned.

    Latestly I found another issue where Formative crashes with GW2012.

    In “Import dates into your calendar” from the Calendar Pack nearly everything works fine, one problem is that using roll-back also leads to a crashing GW-client.

    Best
    Martin

    #9100
    Support 3
    Participant

    Thanks for the information.

    Our concern is that these solutions has not changed, and it was working for you before you upgraded, something is likely to be broken in the GW 2012 client or different with your environment. If this assumption is correct, we may or may not be able to work-around it. This will mean identifying the cause and, if it is a GroupWise issue, notifying Novell.

    Once we have more information, will let you know.

    Regards,

    Advansys Support

    #9105
    Support 3
    Participant
    quote:
    Latestly I found another issue where Formative crashes with GW2012.

    In “Import dates into your calendar” from the Calendar Pack nearly everything works fine, one problem is that using roll-back also leads to a crashing GW-client.

    Our engineers unable to reproduce this behaviour with GroupWise 2012 SP1 (Version: 12.0.1, Build date: 07/09/2012, Installed Language: EN).

    Roll-back option removed imported items and no crash of the GroupWise client. However, during testing we have noticed once after roll-back, imported items remain but disappear after pressing F5 (refresh) on the GroupWise client. There is a known behaviour of the GroupWise client on refreshing items.

    Please make sure you are running the latest point release of the GroupWise 2012 client, you can find latest point release from here: http://download.novell.com/patch/finder/

    Do you see the same behaviour with GroupWise 2012 SP1?

    Regards,

    Advansys Support

    #9106
    Support 3
    Participant
    quote:
    some days ago my company changed to GW 2012. Since that the filing Assistant doesn’t work anymore.

    It simly crashes after selecting the folder where the message should be moved to.

    As we said earlier in this thread that we could not reproduce this issue with beta client.

    We also could not reproduce the issue with GroupWise 2012 SP1 (Version: 12.0.1, Build date: 07/09/2012, Installed Language: EN). Filling Assistant appear to work fine, including Undo, select folder after move, etc.

    Regards,

    Advansys Support

    #9103
    mawim
    Participant

    Hello,

    indeed with GW2012SP1 most of the problems seem to be solved. With GW2012 w/o SP1 I still can reproduce all the crashes I encountered before.

    One issue is remaining. With Calendar Dates Importer (V. 2.0.9) if I checked the box “All day (24hours)” in the Day definition dialog I’d expect the items to be imported as an all day appointment an not as an appointment taking from 00:00 to 23:59.

    But the upgrade seems to cause a new bug. Also with Calendar Dates Importer it is not possible any more to assign a category to the impoted items.

    So finally the most importand issues are solved, but there is still some work to be done.

    My configuration:
    GW2012SP1 12.0.0 Bulid 101769 (EN DE)
    Windows 7 Professional (DE)
    Formative Runtime 2.6.0.0

    With best regards
    Martin

    #9102
    Support 2
    Moderator

    Hi Martin,

    Thanks very much for the feedback and we’ll look into the issues you are reporting above.

    Kind regards,

    Advansys Support

    #9101
    Support 3
    Participant

    Thanks for your post.

    Our engineering team has updated the “Calendar Dates Importer” solution (version 2.0.10) to fix the issue of AllDay and category in GroupWise 2012.

    We have emailed you the updated applet. Please let us know whether the updated solution fix the issue.

    Regards,

    Advansys Support

    #9098
    mawim
    Participant

    Hello,

    thank you for your post and the email with the updated “Calendar Dates Importer 2.0.10”.

    Up to now it seems that nearly all issues are solved.

    Assigning categories to appointment is working again.
    And if the all day box is checked the appointments will be imported correctly.

    There is only one minor bug remaining. Importing an all day appointment works fine, but if you try to roll back this action by using the roll back function of the applet the appoint will not be removed. It will be converted to an appoint taking from midnight to 11 pm or so.

    Best regards
    Martin

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.