SharePoint

Failed to retrieve the AzMan Scope

2010-02-20T13:57:00.001+05:30

Hi Fellows,Yesterday, I was creating a Commerce Server environment which was to co-exist in a existing MOSS installation on the same box.NOTE: Bare in mind folks, if you have DC and MOSS on the same box, I would not recommend installing Commerce Server on to the same box. DC makes Commerce Server impossible to work. My recommendation keep DC separate and then you may install Commerce and

Commerce Server 2007 - Fetch Product Catalog

2009-11-02T11:47:00.009+05:30

Hi Fellows,Been quiet a while since I blogged last. These days am understanding nuts and bolts of another Microsoft Product i.e. Microsoft Commerce Server 2007/2009 and how they sync with Microsoft SharePoint Server 2009. Watch out for my up-coming blogs on Commerce Server.Just to give you guys a Sneak Peak of what I have done so far, take a look at the code below which gets you Product Catalog

SharePoint: Move Site Collection / Database Resizing

2009-08-23T15:34:00.008+05:30

In SharePoint world, content databases can grow to huge numbers, which in-turn result in multiple (performance, archival, consolidation of Sites, etc...) issues. Solution is either to bring automation in place which is smart enough to allocate content db's for Sites, based on the mapped logical architecture or another way would be to re-size your content databases as per your needs on regular

STSADM - Object reference not set to an instance of an object

2009-07-24T17:32:00.008+05:30

Its been nearly 2 days am struggling to deploy a wsp solution in my farm by not using system account credentials. Am running a small farm locally on my system comprising of DC, SQL, Indexer and WFE. It all started with a issue where I was not able to activate a feature on my site using System Account, as activating feature would trigger a functionality in the code where it will check the user and

SharePoint: Version Table (Service Packs/Hot Fixes)

2009-07-12T23:39:00.003+05:30

MOSS 20071 or WSS 3.0 SP2 + Cumulative update (June 09) 12.0.0. 6510MOSS 20071 or WSS 3.0 SP2 + Cumulative update (April 09) 12.0.0. 6504MOSS 20071 or WSS 3.0 SP2 12.0.0.6421MOSS 20071 or WSS 3.0 Cumulative update (Feb 09) 12.0.0. 6341MOSS 20071 or WSS 3.0 Cumulative update (Dec 08) 12.0.0. 6335MOSS 20071 or WSS 3.0 Cumulative update (KB956056 & KB956057)

Event ID : 6398 - WSS (IndexingScheduleJobDefinition - Access Denied)

2009-02-21T16:37:00.008+05:30

It’s been three days I have been struggling with rectifying an insane error which keeps popping up in Windows Event Viewer under application category. I checked everything starting from permission settings on DCOM Component Services (OSearch) to recreating entire index and resetting all crawl rules and scopes, even creating new SSP. Steps as suggested in some Microsoft TechNet Posts are specified

Event ID 10016 and Event ID 6398

2009-02-20T17:04:00.006+05:30

Recently, I am working on to build a SharePoint environment for my team. This is a brand new environment. So I created the AD accounts and did all those steps, account delegation stuff. Created the sites/site collections following our build docs. Everything was working out fine to a point where things started falling apart. I narrowed down the problem to following errors, which I dug up from

Requirements for SharePoint VPC or VM

2009-01-19T14:40:00.008+05:30

Hi All,My apologies for being away so long, did not get much time to update my blog regularly. Anyhow, now as am back, I will keep you updated on stuff happening at my end in SharePoint World.Let's talk a little about what can get us up and running to do development on SharePoint 2007. There are two possible options. 1. Use a common development environment. 2. Use a personal development

SharePoint: Best Practices

2008-11-15T21:24:00.002+05:30

"Several of the Windows SharePoint Services objects, primarily the SPSite class and SPWeb class objects, are created as managed objects. However, these objects use unmanaged code and memory to perform the majority of their work. The managed part of the object is small; the unmanaged part of the object is much larger. Because the smaller managed part of the object does not put memory pressure on

SharePoint: Creating Timer Jobs

2008-10-20T09:49:00.015+05:30

Its been quiet some time since my last post. Been hectic at work lately, finally some relief. Today, I want to discuss how to create timer jobs in SharePoint. A timer job is a schedule of when to run a service by using the SharePoint Timer service.SharePoint Service Timer service is a service that runs other services according to schedules specified in timer jobs. Many features in MOSS/Windows

SharePoint: Creating a Web Part with a Custom Tool Part

2008-10-13T09:18:00.010+05:30

Today, I want to talk on, how to add multiple toolparts in a webpart property window. In one of my earlier post, I did mention a quick and dirty way as how one can add simple textbox in webpart property window without needing any toolparts for that matter. But when it comes to implementing reusable/pluggable collection of controls, using toolparts is best possible option. Now, the question is,

SharePoint: All webparts appear as ErrorWebParts when using SPLimitedWebPartManager

2008-10-01T14:27:00.009+05:30

Hi! recently I was given a task to update properties of multiple webparts(custom developed webparts created by extending existing SharePoint OTB webparts). Now the trick was to fetch those webparts across pages multiple pages and update their properties and UI formatting instructions based on a configuration file which is provided at run time on feature activation. Seems a simple enough task,

SharePoint : WSS 3.0/MOSS feature list

2008-09-29T09:57:00.005+05:30

.style1 { color: rgb(255, 255, 255); background-color: #000000; } .style2 { border-width: 0; } Windows SharePoint Services v3 Features:33 Features in WSS v3 AdminLinks AnnouncementsList BasicWebParts ContactsList ContentLightup ContentTypeSettings ctypes CustomList DataSourceLibrary DiscussionsList SiteSettings SPSearchFeature SurveysList TasksList TeamCollab

SharePoint: Deploying WebPart/Feature as SharePoint Solution Package (.wsp file) - Part 4

2008-09-23T17:28:00.008+05:30

Link to Part 1 : Creating Skeleton.Link to Part 2 : Creating Features/WebpartsLink to Part 3 : Creating .ddf and Manifest.xmlLink to Part 4 : Using STSADM and Centeral Admin to add and deploy solution (current post)Upon successfull completion of build, you will se two additional folder, in bin\debug directory. Namely:cab: contains cab filewsp: contains wsp filereason for creating cab file is:to

SharePoint: Deploying WebPart/Feature as SharePoint Solution Package (.wsp file) - Part 3

2008-09-23T16:44:00.005+05:30

Link to Part 1 : Creating Skeleton.Link to Part 2 : Creating Features/WebpartsLink to Part 3 : Creating .ddf and Manifest.xml (current post)Link to Part 4 : Using STSADM and Centeral Admin to add and deploy solutionOnce we have all our feature and webparts ready its not time to create Manifest.xml file and .ddf file.Manifest.xml[code]

SharePoint - using SPLimitedWebPartManager to create WebPart Connections

2008-09-15T12:15:00.012+05:30

Scenario: A .wsp solution is deployed on SharePoint Server, which has publishing feature running on it. A new site is created based on a "site definition" as defined by Onet.xml (deployed in 12 hive directory by .wsp file). Doing so, number of new webparts available in WebPart gallery and hundereds of publishing pages based on different layout pages. Problem Statement: What I want is, weparts

Microsoft Certified Technology Specialist - Wss 3.0

2008-09-07T23:35:00.011+05:30

To take MCTS exam had been a lingering task in my To-Do list. Finally, I caught up with it this weekend. I was being a lazy numb-nut, post-poning exam every weekend for one or the other reason. Upon post-poning, planning out study-schedule for upcomming week. I said to myself, this ae'nt going to work. Reasons will keep on popping up and I 'll never gonna get time to sit down in peace and prepare

XSLT - Keys implementation

2008-08-26T10:39:00.011+05:30

XSLT Keys - xsl:key is used to declare keys. If I were to define xsl:key in my lanuage, I would say, key represents a collection of nodes (as specified in use attribute) which is filterd by specific pattern as defined by "match" attribute.SyntaxAttributes AttributeValue Description name name Required. Specifies the name

XSLT - Modes In Templates

2008-08-22T14:53:00.026+05:30

"Modes allow an element to be processed multiple times, each time producing a different result." - [As defined by W3C] Another way of interpreting modes can be, a mechanism which allows us to process same XML data island(by this I mean XML Node Set) in multiple ways. To understand modes let us look at example below:xml fragment[code]

SharePoint : HttpContext in synchronous / asynchronous events

2008-08-22T10:36:00.014+05:30

In my previous post we discussed how one can register/unregister event receivers and what are the various events which SharePoint exposes in its Object Model. Let us focus our attention on how one can add custom business logic alongside these events and how to handle page redirects using HttpContext when these events are triggered.To start with, let me differentiate between synchronous and

SharePoint: Register / Unregister Event Receivers

2008-08-20T11:59:00.017+05:30

"Event Receivers" in SharePoint is one topic, I always wanted to discuss and today seems to be a good day to do so.Event Receivers allow you to add your custom/specific business logic/needs into the default functionality of SharePoint. As in, item Added, item Deleted, item Updated, site Created, site Deleted, etc... are few events SharePoint raises and carry out actions based on those events.

Sharepoint Document Property Promotion and Demotion

2008-08-18T11:08:00.023+05:30

I have been playing around with XML document, its meta data and property promotion/demotion lately. I was able to integrate XML meta data with SharePoint parser to promote/demote meta data automatically in a SharePoint Document Library.As in, consider a scenario:I want, when values of M1 and M2 are changed in XML document, metadata in columns (“Metadata 1” and “Metadata 2”) should be

Constructing Pages with User Controls in SharePoint

2008-08-12T10:49:00.016+05:30

In my previous post I discussed how one can create "Custom Controls" in SharePoint. However, Custom Control have certain limitations. Custom Controls limits developer to build rich web UI quickly also, for any minute UI change, code needs to re-compiled and new dll needs to be deployed. This is where User Controls come in.User controls provide a more productive alternative to custom controls.

Constructing Pages with Custom Controls in SharePoint

2008-08-12T10:25:00.005+05:30

The groundwork needed to create a custom control in SharePoint is somewhat similar to what is required in a custom ASP.NET application.Let’s begin with a simple example of a custom control. A server-side control in ASP.NET is defined as a class that inherits from the Control class. Following is a simple code which, which displays "site title" and "site id" based on SPWeb object which is fetched

Generate C# file from XML Schema

2008-08-07T09:44:00.010+05:30

To write a serializable C# class file based on an XML Schema is a pain, in case of a complex schema implementation. What if we can have C# class file generated for us? Visual Studio provides us with a tool (XSD.exe) which can do the needful.Step 1: Go to run and type:Visual Studio 2005: %comspec% /k ""C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat"" x86Visual Studio 2008: %comspec% /

XML Schema (element with optional integer value and mandatory attribute)

2008-08-06T19:24:00.012+05:30

I was working through XML schema today and stumble upon an unusual but relevant problem. I wanted schema to validate an element having a mandatory attribute and optional integer text node.For example :Code snippet in green should validate, where as code snippet in red should result in validation failure.[VALID]23[/

.Net c# traverse XML Schema (XSD)

2008-08-01T14:49:00.011+05:30

Traversing an XML schema using the Schema Object Model (SOM) API provides access to the elements, attributes, and types stored in the SOM.The following properties of the XmlSchema class provide access to the collection of all global items added to the XML schema. PropertyObject type stored in the collection or

Life is what happens to you when you are busy making plans

2008-07-31T20:59:00.005+05:30

"Life is what happens to you when you are busy making plans" - something I stole off a friend's gtalk title. This I believe defines Symphony of life we live. Numerous occasions, it so happens, you anxiously wait for something to come by and make future plans based on it. Turns out, when it's in your grasp, life plays you like a toy and everything you prepared for, looses relevance.This not only

DataForm WebPart [escape from hardcoded List GUIDs]

2008-07-31T12:12:00.005+05:30

SharePoint Designer is undoubtedly, an impeccable tool when it comes to quick and dirty UI creation. Quick drag and drop approach of Lists/Libraries allow easy readable access at UI level. However it has certain limitations. For say, we created a new page and added new DataForm webpart using drag and drop in our development environment. Once our development is complete, it is required to move

Disposing SharePoint site and web objects

2008-07-31T11:45:00.007+05:30

There are several different ways of retrieving an SPWeb object. Take the following 3 examples: 1) SPContextSPWeb web = SPContext.Current.Web 2) OpenWebSPSite site = new Site("http://myserver/");SPWeb web = site.OpenWeb(""); 3) Site "RootWeb"SPSite site = new Site("http://myserver/");SPWeb web = site.RootWeb; Thumb rule:Never dispose SPContext.Current.Web or SPSite.RootWeb Make sure you dispose

Customising Sharepoint Alerts (SPAlert)

2008-07-31T09:42:00.017+05:30

Have you ever wanted to modify "Alert" Setting in SharePoint 2007 based on certain criteria. We had a requirement recently, from a client, to modify alert filters in a very specific way. They wanted to change not the functioning but the filters, and they wanted the filters to be generated at run time based on the content type.Alerts[Info: MSDN SPAlert] can be created based on context of a SPWeb

Custom WebPart connections and Custom WebPart Properties

2008-07-30T21:52:00.009+05:30

Custom Properties does not seem to work any longer the way described in article below. Seems like new patches and SP's from Microsoft makes certain changes. Try inheriting webpart from Microsoft.SharePoint.WebPartPages.WebPart. Note: Do not forget to include System.Web.UI.WebControls.WebParts in your using statements. Updated properties are as follows:[WebBrowsable(true)][Personalizable(false)][