Friday, October 12, 2012

Content type '0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811' not found

We have a portal server 2007 installation that is working fine except for one frustrating error. We deployed the latest February Cumulative Patches and after this the problem starts.We have one console application that creates a site by using stsadm command.If we try the same activity by using GUI then everything works fine. This Console application runs in 4 steps and we are facing the problem at step 4 and prompts error message "Content type '0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811' not found in web '' "

When i check the content type on the website i was shocked there was nothing means not even single content type.The weird thing is, that the content type ID is the ID from the “PageLayout” Content Type...

After doing lots of googling, i noticed and marked some of the common areas affected by this content type error message.
-If we try to create a new page ("Create Page" command from the "Site Actions" Menu) from any of the sites.
-After a restore from MOSS 2007 Standard to MOSS 2007 Enterprise.
-While creating a new page in a collbartion portal.
-While trying to add a new page.
-After deploying cumulative updates.
-Creating a new Web Site programatically.

Now after countless searched on the internet I turn up basically nothing, TechNet is dry, and no one seems to have had this error (not a first for me sadly). I ask a desperation post on Experts-Exchange and run through the drills. Checking my xml config files, looking at error logs, etc.
There are some resolutions applied for this error message so choose the best one that suites your enviornment.
-Run SharePoint Products and Technologies Configuration Wizard on all the machines.

-Go to Site Central Administration, User Permissions for Web Application and be sure "Use Client Integration Features" and "Use Remote Interfaces" are enabled. That can also work for you.

-This ContentTypeID points to the "PublishingResources" feature.You will need to activate this feature by running STSADM. The command is
-STSADM -o activatefeature -name PublishingResources -url

-Run this commands one by one as follows:-
-stsadm -o activatefeature -filename publishing\feature.xml -url
http://url/ -force

-stsadm -o activatefeature -filename publishingresources\feature.xml -url
http://url/ -force

-stsadm -o activatefeature -filename publishingSite\feature.xml -url
http://url/ -force

-stsadm -o activatefeature -filename publishingweb\feature.xml -url
http://url/ -force

-stsadm -o activatefeature -filename publishinglayouts\feature.xml -url
http://url/ -force

-stsadm -o activatefeature -filename navigation\feature.xml -url
http://url/ -force
I hope the above information helps you to overcome this error message.

Thursday, October 11, 2012

How can you set up RMS-based protection to the documents users store in SharePoint?

You can use Windows Rights Management Services (RMS) to protect SharePoint documents in the two most recent releases of SharePoint; SharePoint Server 2010 and SharePoint Server 2007 both include RMS support. However, there are some restrictions and complexities you should be aware of if you plan to set up RMS with your SharePoint installations.

An important thing to know is that RMS can only encrypt SharePoint documents and subject them to RMS access control restrictions when they are downloaded from a SharePoint 2010 or SharePoint 2007 document library. RMS doesn't leave SharePoint documents encrypted while they're stored on the SharePoint server. This restriction exists so that SharePoint can index and scan the documents on a SharePoint storage provider. RMS applies its restrictions to a document only right before it's downloaded to a client computer. Similarly, when an RMS-protected document is uploaded to a SharePoint site, RMS removes all protection from the document until a new download request is received.

SharePoint-RMS integration ensures that security restrictions are enforced even after a document has left a SharePoint server, which is something that can't be achieved using the standard SharePoint permissions. SharePoint-RMS integration also automatically enforces an organization's RMS document security policies. A SharePoint administrator can centrally define different RMS policies for the document libraries hosted on a SharePoint server. Therefore, individual users don't have to decide what protection they need to apply to documents they post in SharePoint libraries. RMS permissions are defined at the SharePoint document library level: Documents in a library automatically inherit the library's RMS permissions. This protection applies to both existing and new documents in the SharePoint library.

The RMS protection of SharePoint data is, just like the RMS protection that's bundled with Windows and Microsoft Office, only possible for certain file formats. Out of the box, it supports Word, Excel, PowerPoint, InfoPath, and XPS files. Extensions to apply RMS protection to other file formats (e.g., .pdf, .cad) can be added through special software from Microsoft partners such as Liquid Machines (now part of Check Point Software Technologies) and GigaTrust.

RMS support for SharePoint can be set up using either RMS SP2 or RMS V2, which is bundled with Windows Server 2008. Provided you already have a functioning RMS infrastructure, enabling RMS protection in SharePoint is relatively straightforward. The main configuration actions are
  • enabling RMS support on the SharePoint server
  • setting the actual RMS restrictions in the configuration of a given document library
You can enable RMS support in SharePoint by selecting either the Use the default RMS server specified in Active Directory or Use this RMS server option in the Information Rights Management section of the SharePoint Central Administration\Operations configuration section.

To set RMS restrictions on a SharePoint document library you must use the Information Rights Management section in the Permissions and Management configuration section of the document library. When you select the Restrict permission to documents in this library on download check box, you can further refine the RMS protection as follows:
  • Allow users to print documents.
  • Enforce users to verify their credentials every x number of days. This setting can be useful when someone who has access to RMS-protected confidential data leaves your organization; the individual will retain access to the data only for x days after his or her last successful authentication to an RMS server.
  • Reject files that don't support Microsoft Information Rights Management (IRM). Selecting this option results in SharePoint rejecting the upload of document formats that don't support RMS.
  • Remove RMS protection on a particular date. This setting is useful for publishing company financial results, for instance. After the quarterly results are published, the RMS protection policy on the quarterly results SharePoint library automatically changes -- meaning that the RMS restrictions are removed.
Microsoft provides more detailed guidance on how to set up SharePoint-RMS integration in the article "Deploying Windows Rights Management Services with Microsoft Office SharePoint Server 2007 Step-By-Step Guide," which is available from Microsoft's website.


Monday, October 8, 2012

Error: Spdesign.exe has been denied access to or there is no server on port 443 at .

Today one of my client reported with an issue while browseing some of the SharePoint sites using designer. Accessing sites using SharePoint gives the below error messages. 

Error: Spdesign.exe has been denied access to

Clicking Ok produces another error message as below.

Error: There is no server on port 443 at . You have selected the Connect using SSL Option. This connections problem may indicate that the server does not support Secure Socket Layer (SSL) communications, or that it uses SSL communications on a different port number.

I was clue less for the issue at the start since the sites were browseable using https//….. Protocol. So I started the troubleshooting based on the troubleshooting related to NIC card, VPN connection suspicion, SSL port disability (prompting for making calls server at 443 ports) from windows firewall. 

Tried to compare the SPD versions on the different machine where it was working not working and didn’t found any issue.

Tried to clear SPD Cache clearance by using the following steps:

1. Close SharePoint Designer.

2. Open My Computer.

3. Go to %System Drive%\Documents and Settings\%user%\Local Settings\Application Data\Microsoft\WebSiteCache. 

4. Delete all folders and files there.

5. Open the site using SPD and we still has the issue. 

On further checking for proxy used by SharePoint designer I noticed that actual issue was related to the wrong proxy usage with Designer.

The proxy was not configuring to make connection to the server using Secure Socket Layer at port 443. By changing the proxy settings in Designer we were able to access all of the sites using designer.

Steps to change Proxy using Designer. 

1. Open SharePoint Designer. 

2. Go to tools -> Application Options.

3.On General tab choose to click Proxy Settings. And change the proxy with is configured to use the SSL over http protocol. 

By changing the proxy for the client, we were able to open the sites from the SharePoint Designer. 

Note: This Proxy settings can also be configured via IE and you may be prompted to provide credentials to open the site for the first time in Designer. 

If you have any issue or query please do let me know, I would be more happy to help you answer.


snow flakes

blogger widgets Blogspot Tutorial


Related Posts Plugin for WordPress, Blogger...