locked
Trouble connecting to a SharePoint site with SharePoint Designer RRS feed

  • Question

  • I am trying to connect to a SharePoint site using SharePoint Designer, but it seems to just hang when I try to login.  It will eventually (about 15 minutes later) ask me to login after hitting Open when doing "Open Site...".  I input the correct User Name and Password and then it asks again another 15 minutes later.  After inputting the User Name and Password correctly the second time, a long while later, an error comes back:

    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 WSS is installed properly.

    There is one thing I have found that makes me think is why this error comes about (but I do not know how to fix it!).  In the Central Administration it shows an Administrator Task titled "Central Administration application pool account should be unique.".  When I click on the Title, it has me "Change service accounts", but I am not sure what to do on this form.  There is one section called "Credential Management".  The Windows Service drop-down list has nothing in it, but switching to Web application pool gives me options.  When I look through the Application pools though, I do not see a pool for the Central Administration to change to.  Also, this is our Live server so I need to be extra careful!  If it is possible to test on another server first, I would love to be able to replicate this issue.  Does anyone have any ideas?   Thanks!!!

    I am able to connect to SharePoint sites on a different server.  It does not seem to be any sort of Firewall issue. 
    • Changed type Mike Walsh FIN Friday, July 10, 2009 3:18 AM always use the question type so people get credit for their replies to you
    • Moved by Mike Walsh FIN Friday, July 10, 2009 3:19 AM spd q (From:SharePoint - Setup, Upgrade, Administration and Operation)
    Thursday, July 9, 2009 9:01 PM

All replies

  • You have not only access to Central Admin, but you have the permissions to make farm-level changes like that, yet you are not the one who architected and built it?  This is also a LIVE system?  I'm very curious how all of that is possible.  Let me start by saying that you should _not_ be touching the app pool for Central Admin or any other service account like that without a deep and full understanding of what that is and how to mess with it.  I would have expected that you were the one who built the system if you have this access, and even if you didn't build it, you would be overseen or taught directly by the person who did.  Or, at the very least, there would be detailed documentation on how it was built and a policy written for what must be done before making farm-level changes to the production environment.

    Anyway, what do you mean when you say "sites on a different server"?  Sites aren't specific to servers really.  All "sites" (web applications) get replicated across all web-front-end servers in the farm.  So, what do you mean by that last statement.  What servers or sites can you access successfuly and which one can you not access?
    SharePoint Architect || My Blog
    Thursday, July 9, 2009 10:43 PM
  • SPD questions go to Design/Customize.

    Moving this.

    WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
    Friday, July 10, 2009 3:18 AM
  • Clayton,

    First of all, I do not know how you came to the conclusion that I was not the one who architected and built it; I did not say anything about that.  I was in fact (a long time ago, when I knew much, much less about SharePoint) the one who installed Windows SharePoint Services on the server (the farm consists of just that server and a mail server - the content databases and applications are on the same server) a long time ago when I apparently did not know as much as I should have to have installed it.  But, I still am getting this issue and I am not sure how to fix it.

    When I say "sites on a different server", I mean "sites on a whole separate instance of Windows SharePoint Services".  Let's call the "sites on a different server" our test environment.

    I can successfully connect to a WSS Site in the Test Environment using SPD.  I can NOT successfully connect to a WSS Site in our Live Environment using SPD.  Do you have any idea why that is happening?  Also, do you know anything about the "Change Service Accounts" issue that Central Administration is giving me?  Thanks a lot!

    Cardi
    Friday, July 10, 2009 12:56 PM
  • That message would likely be due to not using least privileges with your service accounts when building it.
    SharePoint Architect || My Blog
    Friday, July 10, 2009 2:08 PM
  • Hi

     

    It seems that the failure of connecting to SharePoint Service server is due to web.config file. Find the httpHandlers section of your web.config file:

    <httpHandlers>
          <remove verb="GET,HEAD,POST" path="*" />
          <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint
          <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,
          <add verb="*" path="Reserved.ReportViewerWebControl.axd" type
          <add verb="*" path="*.asmx" validate="false" type="System.Web
          <add verb="*" path="*_AppService.axd" validate="false" type="
          <add verb="GET,HEAD" path="ScriptResource.axd" type="System.W
          <remove verb="*" path="*.asmx" />
        </httpHandlers>

     

    Then move the last line to the position as follows:

        <httpHandlers>
          <remove verb="GET,HEAD,POST" path="*" />
          <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint
          <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,
          <add verb="*" path="Reserved.ReportViewerWebControl.axd" type
          <remove verb="*" path="*.asmx" />
          <add verb="*" path="*.asmx" validate="false" type="System.Web
          <add verb="*" path="*_AppService.axd" validate="false" type="
          <add verb="GET,HEAD" path="ScriptResource.axd" type="System.W
        </httpHandlers>

     

    Now try to see if you can open site in SPD.

    Regarding the task titled "Central Administration application pool account should be unique", you can go to IIS to check if you use unique application pool account for Central Administration application pool. If not, change the account in IIS.

    PS: Please change the account by using command line instead in IIS, see my post below for detailed steps. 

    Hope this helps.

     

    Lu Zou

    Monday, July 13, 2009 2:31 AM
  • Better to change service accounts in Central Admin so that it gets written to the Config DB and propagates to IIS, right?
    SharePoint Architect || My Blog
    Monday, July 13, 2009 2:37 AM
  • Hi Clayton,

     

    Thanks for your reminding. In SharePoint, when go to “Operations” à “Services account”, there is no option to change the account of central administration application pool. However, I agree with you that change the account in IIS is not a good way. It should be changed through stsadm command line as below:

    1.         Open a command prompt.  

    2.         Run: stsadm -o updatefarmcredentials -userlogin domain\username -password password

    4.         To restart the application pool, either open IIS and recycle the application pool, or open a command prompt and type iisreset –noforce

     

    For more information, please refer to:

    http://technet.microsoft.com/en-us/library/cc288300.aspx

     

    Hope this helps.

     

    Lu Zou

    Monday, July 13, 2009 3:14 AM
  • Clayton,

    What do you mean by "not using least privileges with your service accounts when building it"?

    Thanks!
    Cardi
    Tuesday, July 14, 2009 1:15 PM
  • Lu Zou,

    Can you please re-post the web.config XML.  It looks like some of it got cut off and there are some of those lines of code that I do not actually have in my web.config file.  I added the <remove> line but that did not work.  I think I may need to add the rest.

    Thanks!
    Cardi
    Tuesday, July 14, 2009 1:16 PM
  • Clayton,

    What do you mean by "not using least privileges with your service accounts when building it"?

    Thanks!
    Cardi

    I mean the Microsoft best practice for building SharePoint.  You use the principle of least privileges, which includes using different service accounts for each service and only giving those service accounts the least possible privileges needed to run that service.
    SharePoint Architect || My Blog
    Tuesday, July 14, 2009 2:01 PM