New IE/ActiveX patch breaks PWS Status Reports for us

[Andrew]

The IE patch from yesterday (Tuesday, 4/12/2006) has completely broken
our ability to use PWS Status Reports.

When you log into PWS, and click on your nearly-due Status Report link,
and are taken to the status report page.

At this point, IE seems to have problems drawing the 20-something
editable text boxes, and spikes the processor (IEXPLORE.EXE) to 100%
for ~3 minutes.

Once the processor settles down, if you move your focus to any other of
the editable text boxes, the processor spike begins again for a couple
minutes. This continues forever.

During the spike period, the only way out is to kill IEXPLORE.EXE.

So my questions are:

1. Is this happening to anyone else?

2. Could this be related to the number of text-editors on the status
report page (approx 20)?

3. Is there any work to fix this?

We're basically out of business using project server until this becomes
resolved.

andrew

 

[Gary L. Chefetz [MVP]]

Andrew:

I've made an inquiry on your behalf. I strongly suspect that the malfunction
may be related to an existing code problem on that particular page.

 

[Reid McTaggart]

This temporary patch will revert the ActiveX functionality:

http://www.microsoft.com/downloads/...1b-4fb5-492e-903e-3400abf1d731&DisplayLang=en

Read the documentation carefully, and please let us know how it works out.

Best regards,

--
Reid McTaggart
EPM Architect
Microsoft

 

[Andrew]

Thanks Gary & Reid, I appreciate the help & suggestions.

We probably will apply the compatibility patch this week, but thats
only a temporary solution.

Thanks again,

andrew

 

[Gary L. Chefetz [MVP]]

Reid:

Thanks for posting that.

This temporary patch will revert the ActiveX functionality:

http://www.microsoft.com/downloads/...1b-4fb5-492e-903e-3400abf1d731&DisplayLang=en

Read the documentation carefully, and please let us know how it works out.

Best regards,