MOSS DCom Error 8007013d


Do you ever get DCom Error like below when accessing MOSS?

Retrieving the COM class factory for component with CLSID {xxxxxxxxxxxxxxxxxxxxxxxxxxxxx} failed due to the following error: 8007013d

One of my colleague (LJ) having this error in their project. After struggling for few days he manages to find for the solution. It seems like one of the permission for the registry is not given enough access. After adding “Everyone” in the permission for the registry (by default Everyone is given rights to access that reg key), IISRESET and the portal is back to normal.

Visual Round Trip Analyzer - VRTA


I come across this tool from my colleague. It is pretty interesting especially for public internet site or intranet site operating over low bandwidth.

“The Visual Round Trip Analyzer tool helps web developers and testers visualize the download of their page, identify best practices and changes that improve web performance. The network Round-Trip between the client and server(s) is the single biggest impact to web page performance – much greater than server response time. VRTA examines the communications protocol, identifying the causes of excessive round-trips, and recommending solutions. Performance engineers, testers, developers, operations personnel should use VRTA to conduct their web performance analysis”

Download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=119F3477-DCED-41E3-A0E7-D8B5CAE893A3&displaylang=en

This installation required MS Network Monitor 3.2 to capture file for VRTA analysis. (http://www.microsoft.com/downloads/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&displaylang=en)

Here are some screens previews after do some testing on www.bronios.com.


It provides detail performance analysis and overall score rating. The results are more comprehensive compare to firebug in Mozilla FireFox. My www.bronios.com seems get pretty bad rating. Time to change hosting company? :P

An error occurred during printing. (0×8007F303) - MS Reporting Services


Yes, it’s another bug in SSRS. One of my colleagues building a MOSS portal that integrated with SSRS. We are facing a problem when user clicks on print from ‘Action’ button. The first dialog prompted to choose the printer but when press print, the following error message pop up indicate “An error occurred during printing. (0×8007F303)”. If click preview button rather than print, a preview of blank report with the words: “An error occurred trying to render the report (0×8007f303)”. Guess what is the problem???

After hours of searching, debugging and googling, he manage to find out the root cause. This is because we did some customization on the reporting services web.config file. We remove the export “tif” file type in the reporting services web.config file. We do know why this little change is causing the big problem during printing.  Hope this helps!

Web part updatepanel not working in publishing portal – ASP.NET AJAX and SharePoint


Today, I manage to solve this problem after spending hours of googling. During the integration between ASP.NET AJAX and SharePoint, you might found that AJAX does not working in certain type of SharePoint site template.

First, AJAX does not work in publishing site without doing some modification on the master page. It works in other site template such team site. The problem is that, the webpart manager TAG inside the master page“<WebPartPages:SPWebPartManager runat=”server”/>” has been placed before the Form Tag. To resolve this issue, just cut it and paste after the Form Tag as below

Original Code
<body class=”body” onload=”_spBodyOnLoadWrapper();”>
<WebPartPages:SPWebPartManager runat=”server”/>
<form runat=”server” onsubmit=”return _spFormOnSubmitWrapper();”>

….
….
Resolved Code
<body class=”body” onload=”javascript:if (typeof(_spBodyOnLoadWrapper) != ‘undefined’) _spBodyOnLoadWrapper();”>
<form runat=”server” onsubmit=”return _spFormOnSubmitWrapper();”>
<asp:ScriptManager runat=”server” ID=”ScriptManager1″></asp:ScriptManager>
<WebPartPages:SPWebPartManager runat=”server”/>

….
….

* You might found the similar solution in other place. I do a summary and make it easier to search by users with the correct keywords.

403 Forbidden when access SharePoint portal site


After we ran a content deployment job we seem to have this recurring issue where hitting the SharePoint site when one is unauthorized gives the generic 403 Forbidden message. So we found ourselves having to authenticate first (by visiting a backend list or manually going to the _layouts/authenticate.aspx page to bring up the popup to get the credentials…

We don’t know why the site would not ask me to log in to begin with; instead it goes right to the 403 error…
Solution

We added read access to the application pool user on the Inetpub directory to solve this issue. This may have been lost on content deployment or some other way. However it seems to have been the root of the issue all along.

* Thanks to Alexander who share out this issue.

Redirecting User on ItemAdding in SharePoint EventHanlders


Here is an issue from my colleague.

The problem

We got a custom list for which handling ItemAdding Event, in the ItemAdding Event (We are creating a site). We are trying to redirect user to a custom site page, the redirection works fine but the item doesn’t gets added to the list at the same time the site gets created.  On ItemAdded, we are trying the redirection code but HttpContext is null

The Solution

The reason why our item isn’t added is when its redirect, the current thread is aborted and the item is never added to the list. We will have to manually add the item.
HttpContext is null in the ItemAdded because this event is asynchronous – The HttpContext is only available within the constructor when a synchronous event is fired.

The following article explains the same problem and provides a details solution:
http://www.entwicklungsgedanken.de/2008/03/27/redirecting-from-newformaspx-to-dispformaspx-after-creating-a-new-item/

* Thanks to Elin and Akhilesh!

Feature and Content Type to create a web part page library


Here are one good scenario and solution on Feature and Content Type to create a web part page library from my colleague.

The problem

The goal of this exercise is to have a document library act as a store for web part pages and for the “New document” button to create a web part page with my custom content type’s attributes.

Here’s the content type:

<Elements xmlns=”http://schemas.microsoft.com/sharepoint/”>
<ContentType
ID=”0×010109010097431DDCD27A4eedA052535AA74AD98A”
Name=”Content Zone Page Template”
Group=”CMS Content Types”
Description=”Content type for Content Zone Page Templates”
>
<FieldRefs>
<FieldRef ID=”{29B7EF45-7669-4572-A42A-823559212C15}”
Name=”cmsDisplayName”
Required =”TRUE”
/>

</FieldRefs>
</ContentType>

<ContentTypeBinding
ContentTypeId=”0×010109010097431DDCD27A4eedA052535AA74AD98A”
ListUrl=”ContentZoneTemplates”
/>
</Elements>

And the List Instance:

<ListInstance
FeatureId=”00BFEA71-E717-4E80-AA17-D0C71B360101″
Id=”3001″
TemplateType=”101″
Title=”Content Zone Templates”
Url=”ContentZoneTemplates”
Description =”CMS Base: Content Zone Templates”
DocumentTemplate=”106″
/>

Now, I’ve tried the list instance without a document template, but that makes the default “new” item a template.doc.  Using the document template as “106″ brings up a file called “_webpartpage.htm” but asks if you want to open it rather than just opening it.

The default behavior if you create a document library and set it’s content type to web part page (all through the UI) is that it first opens that _webpartpage.htm file which then redirects to the spcf.aspx page, but with knowledge of which document library you came from.

The Solution

In the content type definition, add a document template element pointing to the new web part page form.  So, it looks like this now (the addition for the solution is highlighted in yellow):

<Elements xmlns=”http://schemas.microsoft.com/sharepoint/”>
<ContentType
ID=”0×010109010097431DDCD27A4eedA052535AA74AD98A”
Name=”Content Zone Page Template”
Group=” CMS Content Types”
Description=”Content type for Content Zone Page Templates”
>
<FieldRefs>
<FieldRef ID=”{29B7EF45-7669-4572-A42A-823559212C15}”
Name=”cmsDisplayName”
Required =”TRUE”
/>

</FieldRefs>
<DocumentTemplate TargetName=”/_layouts/spcf.aspx” />

</ContentType>

<ContentTypeBinding
ContentTypeId=”0×010109010097431DDCD27A4eedA052535AA74AD98A”
ListUrl=”ContentZoneTemplates”
/>
</Elements>

* Thanks to Jesicca who share out this KB.

Central Administration is not working- Error File Not Found


Central Administration is not working. When I access central administration, I received the “File Not Found. Troubleshoot issues with Windows SharePoint Services.”  message after I entered my credentials.
Checked the IIS, and the Application Pools for Central Administration as well Central Administration were started. Everything looks fine.  The content web site is working fine. Only the central administration is down.

From what I get from my colleague, in a lot of cases, the easiest way to resolve this issue is to reprovision CA. In other words, unprovision the CA using the config wizard or psconfig.exe and the reprovision it again using the same tools. (This is not the same as disconnect from the farm and if done correctly, will not affect the production of the regular sites).

* This issue happened on one of my colleague and thanks to Jukka who provide this solution.

Error while writing managed code for infopath 2007 forms - InfoPath cannot add the event handler.


I receive some problem from my colleague when designing an infopath-2007 form that uses managed code for custom event handling. Here is the error:

InfoPath cannot add the event handler.

To work with Visual Basic or C# code, Microsoft visual studio tools for Applications (VSTA) is reguired. The Microsoft .Net Framework 2.0 and Microsoft Core XML Services 6.0 must be installed prior to installing VSTA…..

He has installed everything that is required. (MSXML Parser 6.0 / VS-2005 / VSTA) but still facing this error. Here is the solution from “Faithful”:
Read the rest of this entry »

Send notification when someone approve/reject an approval workflow


Is there any form of notification being sent to the submitter of the page?
Yes, default approval workflow does have the following email notification

  1. Requesting approval email notification
  2. Email notification to contributor regarding approved / rejected pages from the approval.

Here are the steps:

  1. Outgoing email settings must be configured at the Central Admin à Operations. Without this, there won’t be any option to send notification email in the list setting.
  2. User profile must be configured and imported, with user email information included.
  3. Please create a new Task list when using default approval workflow, using existing “Workflow Task” list, email notification will not be send out.  If you are using existing workflow task list, on this list setting >  advanced setting > Send e-mail when ownership is assigned ? change it to NO and wait for 5 minutes then change it back to YES then you will be able to see those email notification. The other alternative is DO NOT USE the default “Workflow Tasks”, create a new “Tasks” list

*Special thanks to RC, Abi, SC and LJ.