MCTS Finally - End of issues with MCP ID

Long time ago..actually 2 years back, during TechEd 2009, I knew I was on my way to becoming a Microsoft Certified Technology Specialist (MCTS) as I had cleared the required certifications-

1. Microsoft Office SharePoint Server 2007, Configuring (70-630) &
2. Microsoft Office SharePoint Server 2007 - Application Development (70-542)

However, as it happens, the person who was filling-in data on the computer for my certification accidentally created another MCP ID rather than continuing with my previous ID. I was unaware of this during and even after the exam for a long time.

When I realized this, I lost all the joy of clearing my 3rd MS certification and I let it be then. Also, I dumbly provided my then organization email address which was later discontinued by Windows Live services.

Fortunately, today things had to take a different turn, when I saw from one of my colleague the UX for the new MCP site. I decided I got to fix this stuff and earn my MCTS badge. So I looked up the Microsoft site and found the helpline numbers here:
http://www.microsoft.com/learning/en/us/help/service-asia-pacific.aspx#tab2 (for India)

The helpdesk executive was patient and she understood my issue. She was able to rectify my problem by keeping my older MCP ID and merging the result from the newer one to this. She was polite to update all contact details and replaced my old organization ID.

Voila, there I have it now.. :)

I really hope this helps someone who might have faced a similar issue with MCP ID.

Planning to write MS Certification 70-576

Designing and Developing Microsoft SharePoint 2010 Applications

It has been quite sometime since I last wrote any MS certification. I am planning to write the 70-576 on the latest SP 2010 soon. Lets see how it goes..

Some helpful items could be found at the below links for preparations:

http://channel9.msdn.com/learn/courses/SharePoint2010Developer/

http://joelblogs.co.uk/2010/09/01/top-tips-for-passing-sharepoint-exams-70-667-70-668-70-573-and-70-576/

Bye, I gtg now..studies ;)

SharePoint 2010 SP1 released and Office Sept CU available

SharePoint 2010 SP1 was released on 28th June 2011 and it is available for download. 


It is important to have your systems updated with the latest service packs and subsequently with the cumulative updates (CU) which MS typically releases each month.


Some important points to note before going ahead with the installation: 

1. Do read the known issues published on the TechNet: http://support.microsoft.com/kb/2532126 
2. Be aware about the order to follow in case of these updates: 
• Update SharePoint Foundation first with SP1 and then install the CU 
• Then SharePoint Server with SP1 and then install June CU 
3. If you have a farm installation, then run “psconfig –cmd upgrade –inplace b2b -wait” on every server in the farm following the final update installed else run the same command on your standalone box
4. To verify if the updates have been installed properly, check the Central Administration à System Settings à Manage Servers In Farm
   Or, in PowerShell, write (get-spfarm).buildversion

It should display 14.0.6029.1000 after SharePoint Server 2010 SP1. Hope this helps folks trying to keep their SP2010 boxes up-to-date.

For any other assistance, go through SharePoint 2010 Team Blog here

Fix Configuration of the Document ID feature

With SP2010, Microsoft has tried to provide an excellent and helpful feature for uniquely identifying a document within a site collection called DocumentID.
Well, you might ask the rationale behind this tiny change from MS side..right?

Basically, with the previous version of SharePoint product i.e. MOSS 2007, if the user moved a document within a site collection, lets say from one document library to another or the folder containing the file has been renamed or your site URL has been modified in someway, then you would typically face a situation which in IT is called a Broken Link or simply put a bad url :(.

Hence, in the site collection features, you would typically get an option to activate/deactivate the Document ID Service


Document ID Service

Once you have this activated, you would expect the Document ID column to show up when you try to add a new document to a library, unfortunately there is another catch here. You might see this message, "Configuration of the Document ID feature is scheduled to be completed by an automated process." as highlighted in the image below:

This message is shown because the timer job called Document ID enable/disable job has been activated. Once the job completes at the scheduled time, the message will go away or else you may run the timer job and put it to completion forcibly by clicking "Run Now". However, I can assure you that even after the previous step, there is no certain time when the Document ID would show up if you go for a new document upload.


Document ID enable/disable Job

One v.important note that if your doc lib was already having some documents, you would need to explicitly perform some action for this new column of Document ID to show up..for example Check-in/Check-out of docs.

Do try this out and explore this cool stuff from SharePoint 2010!

ASP.net WebParts Vs SharePoint WebParts - Which one to choose?

And we are back! Well, it has been a very busy time for me over the last 8 months, anyhow moving on.

Well, this might be a question which should have popped-up in the head of any beginner in SharePoint probably with some .net background.

Well, an interesting point is that SharePoint 2007 is based on top on ASP.net 2.0 framework. Hence, for folks who are well versed with ASP.Net 2.0 and plan to move on to MOSS/SPS should definitely start with "HelloWorld" kind of webparts using System.Web.UI.WebControls.WebParts.WebPart as a reference.

This enables:

• Usage on websites developed on ASP.net 2.0 and also on SharePoint based portals
• Getting familiarized with Windows SharePoint Services 3.0 classes as a starting point

However, the hard truth remains that sooner or later, developers working on MOSS or SPS would need to move on to Microsoft.SharePoint.WebPartPages.WebPart in their code.

It obviously has it's own advantages:

• Enables cross-page connections
• Enables connections between webparts placed in different webpart zones on the same SharePoint page
• Helps in migrating webpart code to WSS 3.0 based webparts
• Utilize the SharePoint offerred data caching mechanism

Signing off here..enjoy coding!