Teddy's Tech Blog

Wednesday, December 17, 2008

Update the Theme CSS immediately.

Once you are doing change css for a page redering to see, you will find it doesn't work immediately if you change something in theme.css or mossExtension.css.

The way to make it works is doing iisreset, it's a permanent change.
You can use SharePoint Designer to open another temporary file named like Xxxx1011-65001.css which is merged by both of theme.css and mossExtension.css. This file is under _themes\yourthemefolder.

It will be available immediately.

RegistrationId List Template Type IDs

RegistrationId List Template Type IDs
InvalidType = -1
GenericList = 100
DocumentLibrary = 101
Survey = 102Links = 103
Announcements = 104
Contacts = 105
Events = 106
Tasks = 107
DiscussionBoard = 108
PictureLibrary = 109
DataSources = 110
WebTemplateCatalog = 111
UserInformation = 112
WebPartCatalog = 113
ListTemplateCatalog = 114
XMLForm = 115 (InfoPath Forms Library)
MasterPageCatalog = 116
NoCodeWorkflows = 117
WorkflowProcess = 118
WebPageLibrary = 119
CustomGrid = 120
DataConnectionLibrary = 130
WorkflowHistory = 140
GanttTasks = 150
Meetings = 200
Agenda = 201
MeetingUser = 202
Decision = 204
MeetingObjective = 207
TextBox = 210
ThingsToBring = 211
HomePageLibrary = 212
Posts = 301
Comments = 302
Categories = 303
Pages = 850
IssueTracking = 1100
AdminTasks = 1200
Translation Management Library = 1300
Languages & Translations = 1301

Monday, December 8, 2008

How to remove the site theme from site settings

After you deployed custom theme by STSDEV and then retract and delete the solution.

You will find it will still exist on site settings-site theme (http://mysharepoint/_layouts/themeweb.aspx)

To remove it, open the file C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\SPTHEMES.XML , find the corresponding templates and delete it.

You will see it disappear from the theme management after iisreset.

STSDEV with Theme function error handle

When you first time to create a solution for theme definition by STSDEV theme version. You might be see the error message when do a deployment as following:
The 'ReceiverAssembly' attribute is invalid.

The steps to fix this issue:

Install Reflector and running it. ( If there's not already, you are going to download it from http://www.red-gate.com/products/reflector/)
Run reflector and open the directory which host solution dll file. (Your solution folder\bin\Debug) And drag the dll into the reflector panel and then click the new added one.
Copy the name string from bottle panel of reflector and paste into "ReceiveAssembly item" of file feature.xml.

Tuesday, November 25, 2008

Most simple site definition master page. (Fix error)

When edit a most simple webpart page, you got error as following desc:

The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

You will find the page element is right AuthoringContainer, remove the corresponding item in masterpage as following:

<PublishingWebControls:AuthoringContainer id="authoringcontrols" runat="server" >
<PublishingConsole:Console runat="server" / > </PublishingWebControls:AuthoringContainer>

The final most simple masterpage will be :

<%-- Identifies this page as a .master page written in Microsoft Visual C# and registers tag prefixes, namespaces, assemblies, and controls. --%>
<%@ Master language="C#" %><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>
<%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %>
<%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %>
<%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %>
<%-- Uses the Microsoft Office namespace and schema. --%>
<html>
<WebPartPages:SPWebPartManager runat="server"/> <SharePoint:RobotsMetaTag runat="server"/>
<%-- The head section includes a content placeholder for the page title and links to CSS and ECMAScript (JScript, JavaScript) files that run on the server. --%>
<head runat="server">
<asp:ContentPlaceHolder runat="server" id="head">
<title>
<asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server" />
</title> </asp:ContentPlaceHolder> <Sharepoint:CssLink runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server" />
</head>
<%-- When loading the body of the .master page, SharePoint Server 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. --%>
<body onload="javascript:_spBodyOnLoadWrapper();">
<%-- The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. --%>
<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
<wssuc:Welcome id="explitLogout" runat="server"/>
<PublishingSiteAction:SiteActionMenu runat="server"/>
<%-- The PlaceHolderMain content placeholder defines where to place the page content for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. --%> <asp:ContentPlaceHolder id="PlaceHolderMain" runat="server" />
<asp:Panel visible="false" runat="server">
<%-- These ContentPlaceHolders ensure all default SharePoint Server pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. --%>
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/>
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server"/>
<asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/>
<asp:ContentPlaceHolder id="PlaceHolderBodyRightMargin" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleRightMargin" runat="server" />
</asp:Panel>
</form>
</body>
</html>

Thursday, November 20, 2008

Fix DocAve Granular Backup error

Got the error when using AvePoint DocAve v5 to granular backup the full moss sites as following description from the report log.
Feature 'a0e5a010-1329-49d4-9e09-f280cdbed37d' for list template '10102' is not installed in this farm. The operation could not be completed.
11/20/2008 15:11:13=Backup Statistic Before List(http://mysharepoint/Documents):14 MB data, 7(0) sites, 19(0) webs, 154(1) lists, 1801(0) items.

After searching the feature id from 12 hive\TEMPLATE\FEATURES, it belongs to IPFSWebFeatures. Check the corresponding list, it's documents which can't be deleted as a list.
Hence open command line, and input following command to install this feature.
stsadm -o installfeature -filename IPFSWebFeatures\feature.xml
iisreset -noforce

Then it works.

Tuesday, November 11, 2008

The trial period for this product has expired

After restart prod server. All other site collection features working fine except Office SharePoint Server Publishing Infrastructure .It show me web page message "The trial period for this product has expired."

The MOSS is working on a 6 boxes load balance environment. I tried to upgrade to Enterprise license, change the app pool's running account to local administrators group, also added into Distributed COM Users group. Still doesn't work.

Detailed message:Feature receiver assembly 'Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c', class 'Microsoft.SharePoint.Publishing.PublishingFeatureHandler', method 'FeatureActivated' for feature '22a9ef51-737b-4ff2-9346-694633fe4416' threw an exception: Microsoft.SharePoint.SPException: The trial period for this product has expired. at Microsoft.SharePoint.Publishing.CmsSecurityUtilities.EnsureEvaluationNotExpired() at Microsoft.SharePoint.Publishing.PublishingFeatureHandler.FeatureActivated(SPFeatureReceiverProperties receiverProperties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) Feature Activation: Threw an exception, attempting to roll back. Feature 'Publishing' (ID: '22a9ef51-737b-4ff2-9346-694633fe4416'). Exception: Microsoft.SharePoint.SPException: The trial period for this product has expired. at Microsoft.SharePoint.Publishing.CmsSecurityUtilities.EnsureEvaluationNotExpired() at Microsoft.SharePoint.Publishing.PublishingFeatureHandler.FeatureActivated(SPFeatureReceiverProperties receiverProperties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)

Finally, fixed the error. The entire process here:

You will find this error from not enough rights to read registry from internet.

The IIS application pool running account need to read DCOM and registry table for getting the production information.

By checking local group administrators and Distributed COM Users, I found the running accounts there. And then checking DCOM rights by command "dcomcnfg.exe" , still looks fine. So exclude this possibility.

Now open "regedit" to checking registry table. Open \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0

It show me several item's path has inexistent driver. This is right the reason.

After found back the missing drivers, it does work.

What a tricky error message.