« Previous Next »

• 12-09-2008, 11:13 AM

  FirstDivision Joined on 07-24-2005, 4:12 PM Posts 3

  FrontPage Server Extensions / SP Designer / Application Upgrade to 2.0 = Broken Reply Contact Hi, We have a development site for our website that users from each office connect to using both FrontPage 2003 and SharePoint Designer.  The website is a mix of an ASP.NET application, and ASPX pages that the users edit.  These changes are then published to production by an admin. We just recently released a new version of the application which has been upgraded to .NET Framework 2.0.  The app runs fine in both production and development, but what we didn't realize was that after upgrading the app to 2.0, users can no longer connect to the development server with FrontPage or SharePoint Designer.  The error provided by SP Designer is: "The server sent a response which SharePoint Designer could not parse.  If you are trying to connect to a Windows SharePoint Services Server, check with the server's administrator to make sure Windows SharePoint Services is installed properly." If we change the ASP.NET Framework version in IIS back to 1.1, users can connect with SP Designer, but (obviously) the application will not run. We have tried removing and reinstalling Server Extensions 2002 on the development site, this had no effect. We have seen some people with that same error where the resolution was editing the web.config to move a key for AJAX (<remove verb="*" path="*.asmx" />).  AJAX for the 2.0 Framework is installed on this server, but not in use for this application.  So there is no key to move. We have not completely uninstalled/reinstalled server extensions 2002 from the server itself yet.  I'd say this is a last resort. The admin CAN connect to the PRODUCTION site with SharePoint Designer, which is weird. This has led to the question: "Is there an update to Server Extensions that provides for framework 2.0 applications?"  Maybe this update has been applied to the server in production and not in dev? Any other ideas (or solutions) are welcome.  :) Thanks, Andrew

  Tags: sharepoint.Net 2.0sharepoint iisasp .netIIS 6

• 12-09-2008, 12:24 PM

  In reply to

  FirstDivision Joined on 07-24-2005, 4:12 PM Posts 3

  Re: FrontPage Server Extensions / SP Designer / Application Upgrade to 2.0 = Broken Reply Contact Hi, As an update, if I create a new virtual application on a new port with the same application code (2.0 framework), and configure Server Extensions 2002 for it, users can connect to it with SharePoint Designer.  So, server extensions are working, there's just some configuration error or something in the original virtual application, and whatever it is it's related to the .NET FrameWork being changed to 2.0.

• 12-09-2008, 2:55 PM

  In reply to

  tomkmvp Joined on 03-20-2003, 6:27 AM Central NJ Posts 6,174	Re: FrontPage Server Extensions / SP Designer / Application Upgrade to 2.0 = Broken Reply Contact Strange.   FWIW, the ASP.NET version should have nothing to do with the FPSE. Tom Kaminski IIS MVP http://mvp.support.microsoft.com/ http://blogs.iis.net/tomkmvp/ http://www.linkedin.com/pub/8/690/408 http://www.bluesrepublic.org/

• 12-09-2008, 3:14 PM

  In reply to

  FirstDivision Joined on 07-24-2005, 4:12 PM Posts 3

  Re: FrontPage Server Extensions / SP Designer / Application Upgrade to 2.0 = Broken Reply Contact Update #2:  I did a full uninstall of server extensions (we had only done the partial uninstall before) from the "All Tasks" context item within IIS..  I was pretty sure, and correct, that this would wipe out the user accounts within FPSE.  It's not a huge deal, there's only 50 or so user accounts that need access.  And anyway, after adding one account back in and testing it, the problem still persists. I'm steadily heading towards rebuilding the website / application from scratch.  Update #3:  Stopped the old application, copied all the files to a new folder, created a new (2.0) application and assigned it the port number of the old application, uninstalled/reinstalled FPSE, re-added all the users.  It seems to be working ok.  I'm kinda curious what the actual problem was, but oh well, it's working.