Remote portlet failing after upgrading to 6.5 and SQL Server to 2005

Question

we are upgrading our environment from 6.1 mp1 to 6.5 in the process we upgraded our sql server from 2000 version to 2005.After the database upgrade all our remote custom portlet developed using API's to query the database to get user properties or documents name in KD is failing at the point where it try’s to make the call to the database.
We are getting following error on all the portlets result page “The underlying connection was closed: The server committed an HTTP protocol violation. “
For example for user search portlet its fails at this line
IPortalSearchRequest searchRequest = searchFactory.CreatePortalSearchRequest();
Any Ideas??
Edited by spinto at 06/11/2008 7:02 AM
Edited by spinto at 06/11/2008 11:59 AM

Answer 1

You had 6.1 MP1 running on SQL 2000? If you pulled off that sql magic, this issue should be peanuts. ;-)
Seriously, though, when we went from 6.1 to 6.1 MP1, all of our apps using the native API's IPTSearchRequest broke. Notice I said 'IPT' not just 'I' - again, I'm talking about the native api, not the remote. Though come to think of it, the remote search api calls may have broken, too. That was the whole reason we put off the MP1 upgrade - it broke the search in all our tests. I don't think it was until the patch 1 for MP1 came out that we moved forward.
Enough of my yapping, our fix for the native api apps - those using IPTSearchRequest - was to simply recompile the apps using the MP1 assemblies. Whatever the handful of assemblies you may have referenced in your project to get the native api working, just change their ref path to the newer MP1 assemblies - or in your case the new 6.5 versions. That fixed us right up.
Edited by tjannotta at 06/12/2008 7:36 AM