23 May, 2012

The SOAP message cannot be parsed

Guys

I am back again to share some valuable information with all of you. This time the issue was with InfoPath forms.

Problem Description: I was getting the following error message while trying to publish the InfoPath form to a SharePoint site.

Error Message: The SOAP message cannot be parsed.

Started research on this and found important article that resolved my issueJ. That article is published by Microsoft and we (my complete team) wants to thanks Microsoft for sharing this vital information.

Troubleshooting done:
·         Checked the compatibility by means of form options
·         Checked the trust level by means of form options
·         Checked the VB scripting and deprecated code
·         Checked the submit options and browser compatibility

Resolution: 


References:


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 J

21 May, 2012

The document could not be opened for editing. A Windows SharePoint Services compatible application could not be found to edit the document.


We are all aware of this generic error message. If we are getting this message while editing office documents then we all know what kind of troubleshooting we need to do but….if we gets such error message while editing PDF document then what need to do ? Few mins before I worked on this issue and resolved it successfully

What things we need to consider for the troubleshooting:
·         Save the PDF document to your local desktop make the changes and save it. If you are able to save it then it means that proper editor is installed on the machine.
·         Is this problem specific to the document library? Will there be any URL character exceeds limitation? Upload the document to different library and check the results.
·         Try changing the view from “All documents” to “Explorer view” then try to edit the documents & check the results.
·         Same scenario we can check with windows explorer (document library-actions-open with windows explorer)
·         Check out the document, make the changes and save it. check in the document and check the results.

If you have any queries/questions regarding the above mentioned info then please let me know. Thank you

If you are looking for something else then please refer this:
Still some different problem then please convey me so that i can get back to you and guide you in right directions. Thanks again for visitng my blog.

20 May, 2012

Sharepoint Menus rendering Problems with IE 8

Guys-Hope all are doing well J I was Out of office from last few days and come back to office now and as usual started working on incident tickets that comes on daily basis J
Okay, coming back to the topic now. Today I am going concentrate on problems with customizations and their effects with supported browsers.
We all know that SharePoint Designer 2007 is a well know tool which is used to customized SharePoint sites. When we do any customizations then it’s quite obvious that we do some testing before releasing it to production. While doing some customizations on SharePoint sites, the important thing we need to test is support with multiple browsers as we don’t know “which browser is going to use by user”
After doing some customizations, I was testing with IE7, Google chrome as well as with IE8. Customizations works well in IE7 as well as with chrome but problems with IE8
What are these problems?
-Custom menus i.e. dynamic fly outs are not rendering properly in IE8
-white spaces coming instead of menu text and this problem occur only with IE 8
Started my research on this and found this:
As per the above mentioned Microsoft forum, it seems that the problem is with Meta tags which are present in IE7 and missing in IE8
I haven’t tried this keep the above mentioned information handy just as knowledge add-on.
Final resolution which resolved my issue:
Please refer the above mentioned article and your all queries/questions will be answered.
Exact description behind this problem:
Some OOB master pages (like default.master ) do not have a DocType declared so they are rendered in Quirks mode OR IE 7 rendering mode. But some OOB Master pages
(like BlueBand.master) do have DocTypes declared. So for these master pages IE8 will automatically attempt to render them in IE8 Standards Mode. The OOB
SharePoint menu’s cannot show dynamic menu items/fly-outs in IE8 Standards Mode and sometimes appear as just white spaces without a text or link.
Recommended Solution:
This tag should be added to all custom SharePoint master pages if they are to be rendered in IE 8.
Add this in the <head> </head> tags
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
After the tag is added, check-in a major version / publish and approve the master page. Also, restart IE8 before the change will be picked up, inorder to clear the cache.
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 issuesJ J

13 May, 2012

SP 2010 - Loading the Document Information Panel in MS Word throws a warning when 'Run ActiveX controls & PlugIns' for internet zone is set to 'Administrator Approved'

While working on document panel recently, I came across the strange error:

If a site falls in the intranet zone and the internet security setting “Run ActiveX controls and plug-ins” for the internet zone is configured to “Administrator Approved” and a user tries to create a new document within a document library, they gets the following warning

Microsoft InfoPath
One or more ActiveX controls could not be displayed because either:

1) Your current security settings prohibit running ActiveX controls on this page, or
2) You have blocked a publisher of one of the controls.

As a result, the page might not display correctly.

Not able to find out the root cause behind this but wanted to share the step that leads to resolve this issue:

Note: before making any changes to the registry, I can suggest you to take the backup so that in case anything goes wrong then we can restore t easily.

Roll out the following registry modification to all users:
-HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\AllowedControls

- Create a new DWORD value that is the GUID for the Managed Metadata control, which is: {64247C52-5C34-4597-B2A3-17BF5617F17F}

- Set this value to: 0

That’s it and your issue will be resolved J J

Please let me know in case of any queries/questions regarding the above mentioned information. I am providing some links to all of you relates to same as how to take the registry backup.

Microsoft has published a document on this:

How to take registry backup in windows 7

How to take registry backup in windows XP

10 May, 2012

Incoming Emails .msg attachments missing/not coming

Recently I worked on one issue which was very interesting, in fact easy to troubleshoot but difficult to believe/conclude the results.
One of our users raised an incident ticket with my team and it came to me for research and debugs the issue. The issue based on ‘incoming email settings’. More than 10-20 users send an email with attachments to SharePoint document library in which incoming email functionality is enabled.
What exactly the issue is?
If I send an email with an .msg file as attachment then the attachment goes missing. If I send an email by attaching word document, excel document or PDF document then it works properly i.e. email goes to the document library as per the expected behavior.
Note: One think I would like to highlight is “.msg is not a blocked file type” in any blocked extensions which are provided by MS list.
Troubleshooting done:
-block file types already checked in central administration: no difference
-if the settings in the incoming email document library are set as per unique permissions then we can change it to “any sender” settings for the troubleshooting purpose
-tried changing the settings “save all attachments in folders” to “save all attachments in the root folder: didn’t make any difference
-tried changing the mime type by means of outlook (to be specific: from MIME to UUEncode or BinHex): didn’t make any difference
Note: this issue is not machine/user specific. This is complete farm issue in which you can cross verify on any portal/web application.
Conclusion: this seems to be a by design behavior/Product limitation of the SharePoint.
If anybody has a perfect resolution for this then please shares the same here so that it would be very helpful for all the SharePoint communities. Thank you