Webpart Chrome type is not working or Webpart Title is not working: SharePoint

Webpart Chrome type is not working or  Webpart Title is not working: SharePoint

Issue:

Today one of my user complained that she was not able to set the title of her web parts on various pages on her site.  When setting the chrome type to ‘Title’ it set it back to none, when we hit apply and Ok o the web part page. Hence leading to a problem of Webpart Chrome type is not working as expected.

Troubleshooting:

- We tried setting chrome type to other types. No luck.

- We tried changing the various properties of the Webpart, but no luck.

- While researching on the internet I came across an article which says that forcibly changing the

we implemented the same on the effected page and it doesn’t correct the problem.

- One of the article talks about the problem with the webpart zone, when comparing the webpart zone of the webpart with other webpart on the other sites, it was showing only one webpart zone= main.

Resolution:

This article talks about the resolution but doesn’t show how to do it. http://www.novolocus.com/2009/05/29/webpart-titles-not-shown-in-webpartzone

To do this, Open the site in SPD, go to faulty page, and open the page in the coding mode. Look for the webpart page main property.

Change the ID of the webpart to anything other than “Main”. It would bring back the tittles on the webpart. I am not sure why this issue problem had occurred but now it has corrected the problem.

Another Post which talks about the same issue: http://stackoverflow.com/questions/5455893/override-chrome-type-webpart

If you have questions/queries, do let me know. I would be more happy to help you.

SharePoint Help - http 403 forbidden Error / hiding SharePoint help Icon.

Today one of my client stated that he could not open the ‘Set Blog Permissions’ link on one of this Blogs and got the error message. 

I checked the same on my test site and see the same behavior. Now question is why this is happening?

To give you background: We have SharePoint Help disallowed in our environment due to loop whole for the vulnerability attach with the Help.aspx page as per the MS security Bulletin release.   http://technet.microsoft.com/en-us/security/bulletin/MS10-039. 

Just going a bit out of track from here, to suggest some other methods to disallow the help in SharePoint.  To Disallowing access to the help content page can be manually done need to run a small SharePoint farm. Follow the steps.

• open up IIS management console
• find the web application responsible for the public portal
• find the _layouts virtual folder
• find the file help.aspx and open the Properties window for that file
• Change the access permissions for that file.
• repeat these steps for "HelpSearch.aspx", too

You'll have to repeat these steps on all servers in your web farm.

If you even don’t want the users to see the Help icon on the site then commenting out the following lines in the master pages does the trick for the icon.

The MS Security Bulletin given above also suggests the automated workaround for this. 

You can easily test whether or not your site is prone to the breach, by using below url on your site:

“http:///_layouts/help.aspx?cid0=MS.WSS.manifest.xml%3Cscript%3Ealert%28%27XSS%27%29%3C/script%3E&tid=X”

If your site is prone, you will see a JavaScript popup stating your site is hacked.

Hot fixes to resolve the vulnerabilities: WSS 3.0 hotfix: KB983444, MOSS hotfix: KB979445

Coming back to original question why ‘Set Blog Permissions’ link was not working for the client is that when we click the Set blog permissions link in the Admin web art page of the blog site. It tried to call the java script method/functions 

“javascript:HelpWindowsKey(%27MS_WSS_SetBlogPermissions%27)”. 

This script tries to call the Help.aspx, helpcontent.aspx page using HelpWindowsKey function. Since the Help doesn’t work so does this window.

 

Error: Cannot complete this action.

Error:  Cannot complete this action.
          Please try again.
          Troubleshoot issues with Windows SharePoint Services. 

      

What is the cause of this error? 

The short answer is that the page is trying to access something that doesn’t exist, or thinks does not exist.

Resolution:

1). To check which webpart is having the issue, open the site with SharePoint Designer  and double click on the page. The webpart which shows the ‘server error’ is the culprit one.

2). Right click on the webpart to visit its properties and to find its name.

3). Go to web part maintenance page by using http://xyz.com/sites/default.aspx?contents=1  and

4). Closed the offending web part.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issue. Thank you

Unable to search users profile in people picker.

Issue: Unable to search users profile in people picker. You may see.

Troubleshooting done:
- You have validated the user has a valid domain account in Active directory.
- You tried to type the first name and the last name of the user, but no results.
- You tried to resolve the user Alias in Active directory, no results found.

Resolution:
In active directory console, check the account information console for the account and is must be set to disable state.

If the user account is set to disable, It will not appear in the SharePoint people picker and you will get no match found also you will not be able to resolve the name of the user in the outlook.

Mark the user account to active in Active directory, will have it appear in the SharePoint people picker.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues. Thank you.