IE Crash when using TeamSite

Has anyone experienced any IE crashes when attempting to submit a DCR to a workflow? After answering OK to "Would you like to submit this file for approval?", the Submit Files dialog is displayed, but almost immediately a dialog opens saying "Microsoft Internet Explorer has encountered a problem and needs to close". The detail of the fault seems to indicate a fault within oleaut32.dll (we have version 2.40.4514.1).

Has anyone else experience of this? FYI we are running IE5.5 SP2 against TeamSite 5.5.2 SP1.

Any help appreciated.

Find more posts tagged with

Comments

Gregg Faus

Yes. This occurs with us if there are a large number of Visual Format fields that are inline. There are many posts about this same issue. The only solution in 5.5 is to make the VF fields callout.

KeithL

Thanks gfaus for the suggestion. When you say a large number of inline VF fields, all our templates have one inline VF field; the remainder of the template are just standard fields e.g. text fields, radio buttons etc. This issue has always lurked in the background but was very, very occassional; recently we are seeing a more frequent failure, having made no changes to our templates!!
Anyway we'll try call out VF fields and see how we go :-)

KeithL

We set the external-editor-inline='f'.
This puts a VisualFormat... button next to the text field and opens VF in a new window. All changes are written back to the TextArea in HTML format. This is not very author friendly when just viewing the template. What approach do others use to make this a better experience for users?.

Any views welcome!

Adam Stoller

FWIW - it works better in TS6 ... you don't need the callout button, and the text shows up formatted in the textarea

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

KeithL

Thanks fish.
Unfortunately we are not in a position to upgrade currently, although by all the reports we have heard, TS6 looks a better and more flexible release.

Gregg Faus

I was just suggesting an alternative that may have fixed the crashes you mentioned. By calling the VF field out did it resolve your crashing problem?

Although the external VF field is not as user friendly it is quite necessary if you have multiple instances of the editor. I usually call it out if I have over 7 or more instances. That seems to be the threshold for a lot of my users.

KeithL

Your suggestion was appreciated. Since I reported the issue we have had real difficulty reproducing it, so applying any fix at this time is not ideal. What we have noticed however that running against 5.5.2 SP4, the problem so far has not occurred, while running against 5.5.2 SP1, it seems a lot more reproducable. I'll try again tomorrow ... we're early evening in the UK, and I like to think I have some sort of life :-)
Kind Regards !