I got following question from Chris Polek who happen to stumble upon my blog. I tried to answer it best of my knowledge but I am sure there can be multiple ways to achieve this. If you find a better solution, do comment!

Question:
I would like to create a column in a custom list that will sequentially assign the number 1, 2 or 3 to an item created in the list. After assigning a ’3′, it will start over at ’1′. Optionally, this could be a name as well, but a number will work just fine.

Would you be able to help me with this request?

Answer:
Interesting! You can do this by using a calculated column or by using a workflow.

Calculated column method:
You can base your logic with the help of ID column.
For e.g. If the id of the list item is 3 or 6 or 9 or if the sum of the digits is 3/6/9 then put the column value as 3
For e.g. If id =12 then 1+2= 3 hence you will print 3
If all above is false then if the id is even number then print 2 else print 1

If above logic seems complicated then try this
Workflow method:
Create another list, create one list item where Title = 1
Now on your original list write a workflow which will read this value and print in your custom column. Once this is done the workflow will also increment the value into another list by one or reset it to one if it has reached to 3

Removing all HTML tags from a string

<xsl:template name="removeHtmlTags">
<xsl:param name="html"/>
<xsl:choose>
    <xsl:when test="contains($html, ‘&lt;’)">
        <xsl:value-of select="substring-before($html, ‘&lt;’)"/>
        <!– Recurse through HTML –>
        <xsl:call-template name="removeHtmlTags">
        <xsl:with-param name="html" select="substring-after($html, ‘&gt;’)"/>
        </xsl:call-template>
    </xsl:when>
    <xsl:otherwise>
        <xsl:value-of select="$html"/>
    </xsl:otherwise>
</xsl:choose>
</xsl:template>

Thanks.

We often need to configure Office Server Search while working on MOSS 2007 infrastructure projects. Microsoft Filter Pack is efficient as long as it only comes to indexing the metadata documents or metadata and content of file types.

As a large volume of documentation often exist in PDF format and there is always a requirement to index those .pdf files. As you know for every other file type, a so called iFilter indexing is needed. In case of .pdf files, you need to aquire third party iFilters.

The most common iFilters available for .pdf files are:

Adobe PDF iFilter 9 for 64-bit platforms

Foxit PDF IFilter

PDFlib TET PDF IFilter

Here, most common are Adobe PDF iFilter and Foxit PDF iFilter. While Adobe iFilter is available free of charge, for the other two you will need to pay license fees.

With respect to the performance, these two IFilters differ. Microsoft bloggers have already done various testings on Adobe PDF iFilter and Foxit PDF iFilter. As a result of various testings done by Microsoft bloggers, Foxit iFilter (32 bit) is around 4 times as fast as the Adobe Filter. And Foxit iFilter (64 bit) is about 5 times, as fast as the Adobe Filter.

In addition we found PDFlib TET PDF IFilter, for which there were no performance records found.

This was a enough reason to test all these three iFilters for their performance.

The Test Setup:

All three iFilters were tested on same hardware environment.

We used a virtual Hyper-V with two virtual processors and 4 GB RAM. OS used was Windows Server 2008 (Standard Edition) with Service Pack 1.

MOSS 2007 SP 1 (Cumulative update Feb 2009)

Here we indexed 1022 documents (both German and English) of volume of 1.8GB.

The default settings of the current IFilter were used. The duration of indexing was collected in two runs and considered the best result.

The Test Result:

Sharepoint ifilter comparison

License costs compared

Sharepoint ifilter comparisons

Status: 11.05.2009, all data without guarantee.

Rating:

Alrough the Adobe iFilter comes free, its indexing performance has lot of scope for improvement. While the performance of  iFilter Foxit and PDFlib are at par. Initial review cannot comment on difference in the quality of indexing. You can therefore reduce the decision criteria for an iFilter on other factors like volume, cost and personal preferences.

If a large volume of PDF documents are to be indexed the one of the paid options are recommended.
If the index server is not a dedicated server, then this task is preferably preformed by a Web Frontend Server. Because the indexing requires much CPU time, it should be exploited as efficiently as possible.

In case of multi-core the PDFlib IFilter is more cost effective than other peers.

Resources:

Original blog post

Download:

2007 Office System Converter: Microsoft Filter Pack

Adobe PDF iFilter 9 for 64-bit platforms

Foxit PDF IFilter

PDFlib TET PDF IFilter

Learn:

How to register Microsoft Filter Pack with SharePoint Server 2007 and with Search Server 2008

While doing so I recognized that on my machine the datasheet view doesn’t work. Then I started blaming my IE6 and upgraded to IE7 which didn’t helped and finally I landed up with IE8 which also didn’t worked.

It gives following error.
“The Standard View of your list is being displayed because your browser does not support running ActiveX controls.”

While I tried to search for some solution, I found that lot of people are facing this problem.

There are many solutions that worked for them and there are many of them for who nothing worked actually.

————————————————————————————–

See Also: MCTS: MOSS 2007 Configuration (70-630) all you need to know to clear this exam

————————————————————————————–

So I came to a conclusion that there is no perfect solution available.

Here are some possible solutions that work.

All of these are not found by me. I’m just trying to put them at one place.

1.
Microsoft says:
A datasheet component that is compatible with Windows SharePoint Services is not installed.
AND/OR
A Microsoft Office 2003 Professional edition is not installed on the computer.
AND/OR
The Web browser does not support ActiveX controls.
AND/OR
Support for ActiveX controls is disabled

If you are using Office 2003, then try the first solution first. Install Office 2003 web components.

Make sure that you have installed Office 2003 or higher on your client machine.

Unfortunately there are no Office 2007 web components available and I am using Office 2007. Still I tried to install those which didn’t worked too.

I also tried my ActiveX settings for IE8 but that didn’t helped.

As I tried all of them. Still it didn’t worked. Then I carried on my R&D.

2.
On your client machine run, “Microsoft Office Diagnostics”.

This one worked for me. And datasheet view started working normally.

But this too doesn’t work for everyone.

3.
Try putting the site in the trusted sites list. This may solve the problem if it is related to activeX.

4.
Based on my exprience, this kind of problems (a ActiveX component doesn’t work on a particualr client) mostly is caused by a corrupted registry entry or file. So, a complete reinstallation may be the most prompt way to resolve such an issue. While this is not a good advice.

5.
Open the file ows.js in your favorite editor. It can be found here.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\LAYOUTS\1033

Put following javascript code
function RenderActiveX(str)
{

document.write(str);
}

and reset your app pool.

while if the problem is only with a perticular client then I wont suggest this.

6.

If you are working on as WSS 2.0 site then this hotfix might help you.

http://support.microsoft.com/kb/948919/en-us

This is a post SP3 hotfix.

7.

The Office Service Pack team has announced that Service Pack 2 for the 2007 Microsoft Office System due to ship April 28th. This is a good news and we hope they solve this problem for all users.

Even I found some people who has tried all of these and still the datasheet view doesn’t work for them.

So I said earlier, there isn’t a perfect solution for this.
If you know some more then please comment!

If you found the article useful, please re-tweet it and help others too.

This exam seems to be easy as compared to its sister exam 70-542.

I’ll suggest that you complete the study from e-book or hard copy and then before going to exam give 5-6 hours for revision.

Books I used:

Sybex publication: MCTS: Microsoft Office SharePoint Server 2007 Configuration Study Guide: Exam 70-630

by James Pyles

In the following book, you will also get sample questions for practice after each chapter.

After each chapter ends, there are also provided “Exam Essentials” which highlights vital things you should put more emphasis on.

The book also contains a “Assessment tests” which are helpful too.

If you are already working on MOSS 2007 and have gone through the initial setup stages at your workplace, then you can skip first 3 chapters as they are too basic. But from exam perspective do not skip the sample questions.

At end I’ll say enough work experience plays a vital role when you start answering exam.

These are few links you can refer to get some more info.
MCTS: Microsoft Office SharePoint Server 2007 – Configuration
Preparation Guide for Exam 70-630

Some more books (recommended on Microsoft Learning site)

Microsoft® Office SharePoint® Server 2007 Administrator’s Companion

Inside Microsoft Office SharePoint Server 2007

Some more sample tests (from Microsoft Certified Test providers)
MeasureUp - they have practice tests, online courses and exam vouchers.
SelfTest Software – they have practice exams, study guides, online learning and virtual labs too.

If you have any queries then comment with your email id. I’ll try to reply.

1. Disabling mysite/mylinks on MOSS 2007

Step 1.
Visit “Central Administration”
Select “SharedServices” under “Shared Services Administration”
Step 2:
Under “User Profiles and My Sites”, select “Personalization services permissions”

Step 3:
This will open “Manage Permissions”.

Select appropriate user for which you want to disable “mysite” option.

In most cases you will have to use “NT AUTHORITY\Authenticated Users”. This will apply to all authenticated users. In my case I was using windows integrated security so I used this one.

Step 4:

Clicking the user will take you to the following screen.

Un-check the “Create personal site” option.

This should work for you. You may additionally un select the “Use personal feature” option as per your needs.

2. Disabling mysite / mylinks on SharePoint 2003 Server

Check following detailed link for 2003 server.

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B887921

But again there are 2 types.
1. Turning off My Site personal site and turn off views for members of a site group
2. Turning off My Site personal sites without affecting views for a site group

So first confirm which option you want to go first. Then only make changes.

Enjoy..

Unfortunately you cannot adjust the width of this control properly. Sometimes the toolbar get streatched but the inside frame doesn’t.

I have tried various approach. Also tried to correct the width using JavaScript. But it doesn’t work

People have tried many things link setting number columns etc.

But someone has posted on a forum thread that this is a known Microsoft bug (Bug ID: 37846)

I don’t know where I can recheck if this id is true or not.

But probably this will be patched in next service pack.

You must be looking for a control which will allow you to create formatted text as shown in below given image.

InputFormTextBox is the correct control you will ever need. This is available under Microsoft.SharePoint.WebControls namespace. (Only MOSS 2007)

How to use it? Very simple.

InputFormTextBox richMessage = new InputFormTextBox();
richMessage.RichText = true;
richMessage.RichTextMode = SPRichTextMode.FullHtml;

You may also use following useful properties:

richMessage.AllowHyperlink = true;
richMessage.TextMode = TextBoxMode.MultiLine;
richMessage.Wrap = true;
richMessage.Rows = 10;
richMessage.Width = System.Web.UI.WebControls.Unit.Percentage(100);

Check another thread for known issues with InputFormTextBox Control.
InputFormTextBox width, Enabled, ReadOnly Properties not working properly



If you found this post helpful then please share it.

My command line was like below:

STSADM -o InstallFeature -filename FeatureName\feature.xml -force

Before doing this I had already copied necessary feature files to “Features” directory.

Solution:

1.
This happens when you do not have permissions on the database server. Make sure you have the necessary permissions.

2.
If you have recently updated your MOSS version to 12.0.0.6318 i.e. MOSS 2007 or WSS 3.0 Infrastructure Update (KB951695 & KB951297) then you might need to restart the PC/DB services.

3.
If you have updated SQL Server Express Edition to SQL Server then you need to restart the PC/DB services.

In my case just restarting machine helped. But in some cases you cannot restart server machine just like that. So in that case restarting the services might do well.

Let me know if this helped. Also let me know if there are better ways to do this. Or in case if you have faced different issues.