Dooly's Domain: Publishing InfoPath Forms - Updating Content Type Failed

I'm also getting the same issue. Can u help me, how to fix this issue.

Configure MOSS 2007 Site Usage Reports

Three Quick Steps to Configure Site Usage Reporting

Enable Usage Logging in Central Administration
A. On the Central Administration home page, click Operations.
B. On the Operations page, in the Logging and Reporting section, click Usage analysis processing.
C. On the Usage Analysis Processing page, in the Logging Settings section, select Enable logging.
D. Type a log file location and number of log files to create.
E. In the Processing Settings section, select Enable usage analysis processing, and then select a time to run usage processing.

Enable Usage Reporting on SSP Admin Page
A. On the SSP home page, in the Portal Usage Reporting section, click Usage reporting.
B. On the Configure Advanced Usage Analysis Processing page, in the Processing Settings section, click Enable advanced usage analysis processing.
C. In the Search Query Logging section, select Enable search query logging.

Activate the Reporting Feature for the Site Collection
A. On the Site Actions menu, click Site Settings.
B. On the Site Settings page, in the Site Collection Administration section, click Site collection features.
C. On the Site Collection Features page, click the Activate button for the Reporting feature.

After site usage reporting is enabled the site administrators and site collection administrators will be able to view reports detailing:

Requests and queries in the last day and the last 30 days
Average number of requests per day over the last 30 days
Requests per day over the last 30 days
Top page requests over the last 30 days
Top users over the last 30 days
Top referring hosts over the last 30 days
Top referring pages over the last 30 days
Top destination pages over the last 30 days
Top search queries for the last 30 days
Search results top destination pages
Number of search queries per day over the previous 30 days
Number of search queries per month over the previous 12 months
Top search queries over the previous 30 days
Search Queries per search scope over the previous 30 days
Site collection administrators will be able to view reports detailing:

Total amount of storage used by the site collection
Percent of storage space used by Web Discussions
Maximum storage space allowed
Number of users for all sites in the hierarchy
Total hits and recent bandwidth usage across all sites

Adding a 'Save site as template' Link to Site Settings in WSS v3/MOSS 2007 using a CustomAction Feature

The SaveSiteAsTemplate feature will consist of a Feature.xml and an Elements.xml file.
Feature.xml declares the Feature itself, and Elements.xml further defines the CustomAction for the Look and Feel menu on a Site Settings page.
To get started, create a folder named SaveSiteAsTemplate below the Features folder located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES on your WSS v3 server. Create Feature.xml and Elements.xml from the code below and place each file in the SaveSiteAsTemplate folder you just created.

Feature.xml



Note the Scope attribute in the Feature element of Feature.xml. Scope can be set to either Farm, WebApplication, Site or Web. Also notice that the ElementManifest element points to Elements.xml.

Elements.xml







Setting the Location of the CustomAction to Microsoft.SharePoint.Settings and the GroupId to Customization is what decides where the link will be render in the UI.
Next, install the feature into WSS v3 by using the stsadm tool. Stsadm.exe is located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN on your WSS v3 server.
stsadm -o installfeature -name SaveSiteAsTemplate


Finally, activate the new feature on your WSS Site by going to Site Settings > Site Features and clicking the Activate button for the new Save Site As Template feature.

You should now see a “Save site as template” link under the Look and Feel menu of the Site Settings page.

Reference: http://sharepointsolutions.blogspot.com/2006/07/adding-save-site-as-template-link-to.html

Apply top level site UI to all the Sub sites

1. Create the Top Level Sites as per the requirement

2. Change the UI as per the requirement

3. Save the Changed UI as Custom Template

Site Action --> Site Settings --> Save “Site as Template”

A) Enter the FileName: CustomTemplate (Change the file name as per the requirement)
B) Template Name: CustomTemplate (Change the template name as per the requirement)
C) Template Description: CustomTemplate (Change the Description as per the requirement)
D) Finally click ok

4. Active on "Office SharePoint Server Publishing Infrastructure" features.

Site Action --> Site Settings --> Site Collection Administration --> Site Collection Features --> Activate "Office SharePoint Server Publishing Infrastructure" features

5. Activate "Office SharePoint Server Publishing" features

Site Action --> Site Settings --> Site Administration --> Site Features --> Activate "Office SharePoint Server Publishing" features

6. Create the Sub site and inherit the UI from Top Level Site

Site Action --> Create or Create Site

A) Title: As per the requirement
B) Description: As per the requirement
C) URL name: As per the requirement
D) Select a Template: Click the Custom Tab --> Must Select the "CustomTemplate".
E) User Permission: As per the requirement
F) Finally click "Create" option.

7. Apply Top Level site header to sub site

Go to Top Level Site --> Site Action --> Modify All Site Settings --> Look and feel --> Master Page

A) Site Master Page --> Select Default.master --> Check "Reset all sub sites to inherit this Site Master Page setting" check box

B) System Master Page --> Select Default.master --> Check "Reset all sub sites to inherit this system master page setting" check box

C) Finally click ok

Create a Managed Path Embedded Site Collection

Create a Managed Path Embedded Site Collection

Have you ever want to create a site collection in the root of a managed path?
For example, create a site collection at http://portal.foo.bar/sitecollection.
It can be done and is particularly useful on publishing sites when you don't
want a managed path like sites in the URL. It can also be used for division
portals like http://portal.foo.bat/HR and http://portal.foo.bar/IT

To create an embedded managed path site collection, do the following:

1. Open Central Administration > Application Management > SharePoint Web Application Management > Define Managed Paths.

2. Select the Web application in which you wish to create the managed path.

3. In the Add A New Path field, enter the name you wish for the embedded managed path site collection.
In the earlier example, the name is accounting.

4. You must select Explicit Inclusion as the Type .

5. Open Central Administration > Application Management > SharePoint Site Management > Create Site Collection.
This action must be performed from Central Administration.
You cannot create an embedded managed path site collection using self-service site management.

6. Select the correct Web application from the list.

7. Select the Explicit Inclusion you created earlier as the URL path.

Custom Advanced Search Code

1. Add code to Button Click Event
Microsoft.Office.Server.Search.Query.FullTextSqlQuery kwQuery = new Microsoft.Office.Server.Search.Query.FullTextSqlQuery(new SPSite("Top Level Site Name"));
kwQuery.QueryText = "SELECT Title, URL FROM Scope() WHERE FREETEXT(Contents, '" + Custom Text Values + "') and Competitor='"+Custom Values+"'";
kwQuery.ResultTypes = Microsoft.Office.Server.Search.Query.ResultType.RelevantResults; Microsoft.Office.Server.Search.Query.ResultTableCollection results = kwQuery.Execute(); Microsoft.Office.Server.Search.Query.ResultTable tblResult = results[Microsoft.Office.Server.Search.Query.ResultType.RelevantResults];
if (tblResult.TotalRows == 0)
{
lblQueryResult.Text = "No Search Results Returned.";
}
else
{
ReadResultTable(tblResult);
}


2.
public void ReadResultTable(Microsoft.Office.Server.Search.Query.ResultTable rt)
{
#region Create a DataSet and load the returned ResultTable into it
DataTable relResultsTbl = new DataTable();
relResultsTbl.TableName = "Relevant Results";
DataSet ds = new DataSet("resultsset");
ds.Tables.Add(relResultsTbl);
ds.Load(rt, LoadOption.OverwriteChanges, relResultsTbl);
#endregion
#region Add the results to the DataGrid
fillResultsGrid(ds);
#endregion
}

Icons are not displayed for Adobe PDF documents that are listed in the search results when you search your portal site in SharePoint Server 2007

Step 1: Download Adobe PDF IFilter 5.0 from the following Adobe Web site:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=1276

Step 2: Stop the IIS Admin service. To do this, follow these steps:

a. Click Start, point to Administrative Tools, and then click Services.
b. Right-click IIS Admin Service, and then click Stop.

Step 3: Run the Adobe PDF IFilter 5.0 Setup program to install the filter on the server.
(For MOSS 2007, install the PDF iFilter on the Index servers)
After installing the iFilter, perform Steps 5, 6, and 7 on all the Web Front End servers in the farm.

Step 4: Register the Adobe PDF IFilter. To do this, follow these steps:

a. Click Start, and then click Run.
b. In the Open box, type cmd, and then click OK.
c. Switch to the folder that contains the Adobe PDF Filter 5.0 files. For example, switch to the following folder:
Drive:\Program Files\Adobe\PDF IFilter 5.0
d. Type regsvr32.exe pdffilt.dll, and then press ENTER.
e. If you receive a message that states that the operation was successful, click OK .
f. Type exit, and then press ENTER to exit the command prompt.

Step 5: Copy the .gif file that you want to use for the icon to the following folder on the server, as appropriate for your situation: Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images

Step 6: Edit the Docicon.xml file to include the .pdf extension. To do this, follow these steps:

a. Start Notepad, and then open the Docicon.xml file. The Docicon.xml file is located in one of the following folders on the server: Drive:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml
b. Add an entry for the .pdf extension.
For example, add a line that is similar to the following to the Docicon.xml file, where NameofIconFile is the name of the .gif file:
c. On the File menu, click Save, and then quit Notepad.

Step 7: Restart the server.

Step 8. Add the .pdf file type to the content index. To do this, follow these steps:

a. Connect to the portal site, and then click Site Settings.
b. On the Site Settings page, click Configure search and indexing under Search Settings and Indexed Content.
c. On the Configure Search and Indexing page, click Include file types under General Content Settings and Indexing Status.
d. On the Specify File Types to Include page, click New File Type.
e. On the Add File Type page, type pdf in the File extension box, and then click OK.

Step 9. Update the context indexes for portal content and for non-portal content. To do this, follow these steps:

a. On the Site Settings page of the portal site, click Configure search and indexing under Search Settings and Indexed Content.
b. On the Configure search and indexing page, click Manage content indexes under Content Indexes.
c. On the Manage Content Indexes page, click the down arrow next to the name of the index that you want to update, and then click Start Full Update.