PC UI for Leads in CRM 4.0

Question

Is anyone else using PC UI for Leads (CRMD_BUS2000108) or Activities (CRMD_BUS2000126)in CRM 4.0 with EP 5.0? 
A contractor implemented the PC-UI in CRM 3.1.  We currently use EP 5.0 and are in the process of switching over to 6.0.
Both portal versions seem to work with the CRM 3.1 PC-UI, but CRM 4.0 doesn't seem to work anywhere. SAP is trying to help but we don't seem to be getting anywhere.
Also, since the contractor did the work, I don't really know what I'm doing which isn't helping things any.
1)Activities screen displays but nothing happens when I click on the Go button.  The 1st work around was to unclick HTTP compression due to the very long URL but that didn't help.  Has anyone run into anything else that would cause this to hang up? 
2)Leads-Could someone tell me what they are using in the INIT & CREATE_FOLLOWUP event for the search area position?
CRM 3.1 had field group of LEA_SRCH with search group of LEA_GROUP.  SAP says this is not a valid field group or search group and replace the field group with LEA_SRCH_MANAGER and delete the search group, but I am still getting an error.
Please help!

Answer 1

Specifically for using CRM PCUI within EP, there are one (or two) very important notes to keep in mind. We often see random JavaScript errors in CRM that are related to the use of GZIP on JS files. There are just some patches of IE that does not handle GZIP correctly, due to a timing problem. Here below an extract of an email I wrote recently to a colleague on this issue.
There are two main reasons, different but similar, that usually leads to unexplained JavaScript problems.
(1) The first has to do with very long URLs (as we use them in portal) and files that are compressed. The compression is ok, but the decompression with the long URLs fail. For this we recommend note 796354.
(2) There are some browsers out there (we have seen this in both IE 5.50 and 6.00) where decompression just fails. This is a well known problem in IE which we have found references to on MSDN. Usually with very new installed systems it does not happen. It has to do with some .DLL that has a timing problem to other .DLLs. Therefor, our general recommendation once we see these type of "unexplained/random" JavaScript errors, is to recommend that GZIP be disabled (until everyone in the company has browsers that can handle GZIP). The simplest way to do this, is with note 715598. Quick and painless. Thereafter, flush server and browser cache.
There is always the possibility of:
(3) That some ICF nodes are not active over which JavaScript files are loaded. These we usually check, and should not happen for our .JS stuff. For application developed .JS files this is still possible. Use HttpWatch and look for rc=404.
(4) Sometimes there are very obscure errors in the MIME repository, whereby suddenly JS files appear in multiple versions. This can again be seen with HttpWatch, rc=404 or =500.