Download SharePoint Designer 2010

By -
SharePoint Designer 2010

- Download 32 bit version

- Download 64 bit version

Notes:
- WSS3/MOSS 2007 only works with SharePoint designer 2007

- WSS4/SP SERVER 2010 only works with SharePoint designer 2010

- You must use a build of SPD2010 equal or earlier than the build of Foundation/Server (4006.1010 conflicts with 4514.1007)

- Data transfer uses client's dinamic TCP ports (2400, 2579, etc). Make sure SPD is added to firewall exceptions. Enable some of these ports if nothing else works.

- If your system has 32 bit versions of Office apps installed, you need 32bit version of SPDesigner 2010 or you'll get an error saying "you have these XXX 32bit office apps. please uninstall them in order to install 64bit app version or download 32 bit version"

- It IS possible to have both 2007 and 2010 installed side-by-side (if same 32/64 bit version)

If you try to open a WSS3/MOSS 2007 website with SPD 2010, you will get:
"This web site has been configured to disallow editing with SharePoint Designer. Contact your web site administrator for more information."
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/c23c9d1a-7038-4a13-9342-62300c828d5d/

Comments

  1. Indian PatrioticSeptember 25, 2010 at 7:47 AM

    good article,

    My network has been blocking working on SP Designer 2010, it is keep asking to enter Credentials and keep showing me message"You do not have permission to do this operation and etc."

    Where this is working absolutely fine in other system at home.

    How can i make access Designer.

    ReplyDelete
  2. Tiago DuarteSeptember 26, 2010 at 8:11 AM

    I haven't runned into this issue before, but I think you may not have enough permissions to open that specific site.
    You should make sure the site is SPD-enabled, by checking all options in "SharePoint Designer settings" under Site Collection Administration. You can also do this in Central Admin, http://sharepointbind:CAPORT/_admin/SharePointDesignerAdmin.aspx

    If you can access SPD from other computers, with the same credentials, you should check firewall settings, such as ISA rules.

    You can also use Fiddler 2 to find out what page/resource is being blocked.

    Tiago.

    ReplyDelete

Post a Comment

Popular posts from this blog

Breaking down document locking in SharePoint

By -
Image
This is a topic I've been meaning to discuss in a while. We open, change and close documents almost every day, and sometimes we collaborate with other people at the same time on those documents. SharePoint brings all co-authoring features we need, straight out-of-the-box, but sometimes, there are problems. While things are starting to look better on the cloud side, the concept of document locking is still very much up-to-date and understanding how it works and what to do when things go wrong is crucial. In an article that has since disappeared the Microsoft Knowledge Base (but still available here ), Microsoft explains it best: When a document is opened by a client program, Windows SharePoint Services puts a write lock on the document on the server. The write lock times out after 10 minutes. Users cannot modify the document during the time when the document is locked. In a scenario where the program that opens the document unexpectedly quits or crashes and you try to open the do
Read more

Working around X-Frame-Options for iframes

By -
Image
The problem: One of the first things we noticed after migrating to SharePoint 2013 was that our iframes have stopped working, giving the error: "Refused to display 'http://contoso/pages/home.aspx' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'." Quickly we could see that this is in fact a security mechanism to prevent click-jacking and others: "The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a frame or iframe. Sites can use this to avoid Clickjacking attacks, by ensuring that their content is not embedded into other sites." Soon we realized that, starting SharePoint 2013, an HTTP Module is adding the header " X-Frame-Options " by default, with the value " SAMEORIGIN ". This is effectively preventing the rendering of pages outside the scope of the current web application. The (attempted) solution: So what to do?
Read more

Document ID not being generated

By -
Image
Problem In a scenario where we have many document Content Types, we may want to enable Document ID - aka "Permanent Links" - which is a feature in SharePoint that assigns a specific ID for each document. That ID never changes even if the document is renamed or moved to another location. In this scenario, the Document ID field was being generated for some libraries/content types, but not others, which is a surprisingly common problem. Background There are several stages we need to go through to enable use this mechanism. Stage 1 We enable the feature in the Site Collection Features. Stage 2 Under Site Collection Administration > Document ID Settings, we need to enable the assignment and pick a prefix. The IDs use the format: PREFIX-LISTID-LISTITEMID ( ref ) Where: PREFIX: the preconfigured prefix for the site collection, which can be any set of numbers and letters between 4-12 characters LISTID: the property docid_msft_hier_listid of the list
Read more