Skip to main content

Document Property disabled under Quick Parts in Word 2010

Document Property under Quick Parts sometimes appears grayed out or disabled in Word client and we can see that Compatibility mode written on the Word client on the top part.


This happens because Word disables certain features to make our document compatible with previous versions of Office. To workaround we have to change the compatibility feature. To do that click File on the Word ribbon and select Info.


Click on Convert button and click OK on the pop up message.


This enables the disabled features and now we can access the Document Properties under Quick Part.


Labels:

Comments

JohnC said…
Thanks, quickly solved my issue thanks to your post.
March 25, 2014 at 12:16 AM
AK said…
Great, saved me heaps of time with this answer. Thank you!!
December 23, 2014 at 8:07 AM
Anonymous said…
This was most definitely a compatabilty issue - but becuase it was stored on SharePoint I had to save as a newer version, so it was 97/2003 and now is 2010 format. All works perfectly now.
Thanks
July 22, 2015 at 4:04 PM
Anonymous said…
Thank you! Not a lot of information on the web for this issue and this solved it perfectly.
July 31, 2015 at 6:18 PM
Khushi said…
Thanks you! You saved me!
March 5, 2018 at 10:46 PM
Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more