Forum Discussion
MeAndMyBIGIP_60
Nimbostratus
Jun 29, 2009Sharepoint Content Editor Webpart dies behind F5
We made the move to put an existing Sharepoint 2007 site behind an LTM 6400 running 10.0.1, and using SSL Offloading.
The move went great, the Application Template made it super-easy... EXCEPT:
Now, when the site admins log in and try to edit pages using the Content Editor Webpart in IE8, they get:
"Cannot retrieve properties at this time"
If we take the F5 back out from in front of the site, we're good.
Recommendations I've seen say to either restart IIS (no change), or to re-extend the site (sounds messy), but all assume and point to ISA being the problem, which I only mention as it sounds like there's a problem with the SSL to HTTP traffic translation
Did I miss something?
--MeAndMyBIGIP
- hoolio
Cirrostratus
Does the error occur only with IE8? What about IE7 or IE6 or FF? Can you use a browser plugin like Fiddler to compare a working browser versus a failing one? - MeAndMyBIGIP_60
Nimbostratus
Hi Aaron -- thanks for the reply and the link. - MeAndMyBIGIP_60
Nimbostratus
Okay... so newbie to Fiddler, but made sure to get the version that can see HTPPS traffic. Here's what we got when we repro'd the error:ResultProtocolHostURLBodyCachingContent-TypeProcessComments 130401HTTPSwebsiteURL /Programs/BetaMobile/_vti_bin/WebPartPages.asmx341text/html; charset=us-asciiiexplore:4588 131500HTTPSwebsiteURL /Programs/BetaMobile/_vti_bin/WebPartPages.asmx534private text/xml; charset=utf-8iexplore:4588 132304HTTPSwebsiteURL /Programs/BetaMobile/_themes/Lacquer/siteactionsmenugrad_lacquer.gif0private,max-age=0 iexplore:4588
- MeAndMyBIGIP_60
Nimbostratus
Update:datetimes-ipcs-methodcs-uri-stemcs-uri-querys-portcs-usernamec-ipcs(User-Agent)sc-statussc-substatussc-win32-statustime-taken 6/30/200916:04:14WFE Node1 IPPOST/Programs/BetaMobile/_vti_bin/WebPartPages.asmx-80domain\admin.userF5 IPMozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+GTB5;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2;+MS-RTC+LM+8)50000546
datetimes-ipcs-methodcs-uri-stemcs-uri-querys-portcs-usernamec-ipcs(User-Agent)sc-statussc-substatussc-win32-statustime-taken 6/30/200915:57:36FQDN IPPOST/Programs/BetaMobile/_vti_bin/WebPartPages.asmx-443domain\admin.userClient Workstation IPMozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+GTB5;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2;+MS-RTC+LM+8)20000156
- MeAndMyBIGIP_60
Nimbostratus
hope this isn't bad form, but wanted to bump this up to get a little more airplay, and see if anyone else has seen this issue... thanks! - hoolio
Cirrostratus
You might try opening a case with F5 Support. They could help you compare the browser recordings from a successful request with a failing request. You might also be able to enable verbose errors or some kind of debug on Sharepoint to get a better idea of what Sharepoint doesn't like about the requests from IE clients via LTM versus direct. - naladar_65658
Altostratus
Hello MeAndMyBIGIP, - MeAndMyBIGIP_60
Nimbostratus
Right...datetimes-ipcs-methodcs-uri-stemcs-uri-querys-portcs-usernamec-ipcs(User-Agent)sc-statussc-substatussc-win32-statustime-taken 6/30/200916:04:14WFE Node1 IPPOST/Programs/BetaMobile/_vti_bin/WebPartPages.asmx-80domain\admin.userF5 IPMozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+GTB5;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2;+MS-RTC+LM+8)50000546
datetimes-ipcs-methodcs-uri-stemcs-uri-querys-portcs-usernamec-ipcs(User-Agent)sc-statussc-substatussc-win32-statustime-taken 6/30/200915:57:36FQDN IPPOST/Programs/BetaMobile/_vti_bin/WebPartPages.asmx-443domain\admin.userClient Workstation IPMozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+GTB5;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729;+InfoPath.2;+MS-RTC+LM+8)20000156
- naladar_65658
Altostratus
I forgot to mention. We had problems with some of the admin functions calling HTTP pages even though we were logged in via HTTPS... until we set the AAM's up like I mentioned. - Rudi_95802
Nimbostratus
We had the same problem thanks a stack naladar, this problem caused me to age a couple years, There are still numerous users out there that have exactly the same issue, i'll post some more detail with regards to the AAMs. MeandMyBigIP I see you struggled with this for months, hope you came right eventually. It would be great if we can have a note somewhere in the deployment guide RE. the AAM's.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects