Wednesday, June 29, 2011

SharePoint:error while accessing SSP

When i tried to go to default SSP it is showing the below error message:
Service Unavailable
HTTP Error 503. The service is unavailable.

And i thought of creating new SSP and routing it to existing web application
But we see the following error message:

An unhandled exception occurred in the user interface. Exception Information: Invalid URI: A port was expected because of there is a colon (':') present but the port could not be parsed

If we want to find the root cause we need to change the web.config file, but it may cause the space issue in the WFE what to do.


If you are facing the current issue, check this steps

If its a 503 error, check the credentials of the application pool whether its matching or not change the identity to Built-In accout or specify the particular accout
you can see this in the right hand side of Application pool Actions-->your app-->identity
change the identity

and if you have corrupted SSP or the secon error message you need to do the following steps:

  1. Create new SSP using STSADM command.


stsadm -o createssp
   -title <SSP name>
   -url <Web application URL>
   -mysiteurl <MySite URL>
   -ssplogin <user name>
   -indexserver <index server>
   -indexlocation <index file path>
   [-ssppassword <password>]
   [-sspdatabaseserver <SSP database server>]
   [-sspdatabasename <SSP database name>]
   [-sspsqlauthlogin <SQL user name>]
   [-sspsqlauthpassword <SQL password>]
   [-searchdatabaseserver <search database server>]
   [-searchdatabasename <search database name>]
   [-searchsqlauthlogin <SQL user name>]
   [-searchsqlauthpassword <SQL password>]
   [-ssl <yes|no>]
  1. route all the exsting webapplications to the new SSP using central admin.
  2. make the new SSP as default one.
  3. Delete the exsting one using STSADM command.


stsadm -o deletessp
   -title <SSP name>

thats it its works fine.

Friday, June 17, 2011

SharePoint:Different types of Content Types in SharePoint 2007

These are the different content types available in Sharepoint 2007
Bussiness Intelligence
Microsoft Project
Page Layouts

Wednesday, June 15, 2011

SharePoint:Creating a Form based authentication(FBA)

check this links

SharePoint: Configuring Indexing Server

In this section I am gonna tell you how to configure index server. Basically index server is required when configuring SSP (Shared Service Provider) in SharePoint. So we need to have index server configured before configuring SSP. Following are the series of steps to configure index server.
  1. Open Central Administration; navigate to Operations--> Topology and Services--> Servers in Farm.
  2. Click server on which you want to run indexer service.
  3.  Click on Office SharePoint Server Search listed in the service list.
  4.  Fill in the details and in Web Front End And Crawling section select Use a dedicated web front end computer for crawling, select server name from dropdown list, and press OK.

Now you have done with configuring index server, it's time to start it. Click on the 'start' link in the action column in front of Office SharePoint Server Search.
  1. Configure Office SharePoint Server Search Service Settings on server creativitybox’ form will be opened, fill in required fields and press Start

SharePoint: Adding content database to Webapplication

  1. Verify that the user account that is being used to perform this operation is a member of the Farm Administrators SharePoint group. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server dbcreator fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have dbcreator permission on the SQL Server instance where the database will be created.
  2. On the SharePoint Central Administration Web site, click Application Management.
  3. In the Databases section, click Manage content databases.
  4. On the Manage Content Databases page, click Add a content database.
  5. On the Add Content Database page:
    1. Specify a Web application for the new database.
    2. Specify a database server to host the new database.
    3. Specify the authentication method that the new database will use and supply an account name and password, if they are necessary.
    4. Specify the name of the failover database server, if one exists.
    5. Specify the number of top-level sites that can be created before a warning is issued. By default, this is 9,000.
    6. Specify the total number of top-level sites that can be created in the database. By default, this is 15,000.
    7. Click OK.

Tuesday, May 24, 2011

SharePoint:Managed properties in Sharepoint

 Here are some examples of managed properties that are available in MOSS 2007,
  • AssignedTo
  • Author
  • ContentType
  • FileExtension
  • SiteTitle
  • etc..

SharePoint:Limits and details in Moss

For SharePoint Portal Server, here's an extract from the Capacity Planning whitepaper:
It is important to understand the ramifications of the different features and functions of the SharePoint Portal Server solutions to size the system so that the performance of the system is good.
The following table lists some of the SharePoint Portal Server objects and describes their recommended use. "Typical" indicates comfortable and well tested; "maximum" indicates that the system can support that number, but not without some performance ramifications or
special configurations.
An asterisk (*) indicates a hard limit; no asterisk indicates a tested or supported limit.
  • Portal sites (full) - typically 2 ... maximum 15 *
  • Portal sites (child) - typically 10 ... maximum 100 *
  • Areas - typically 1,000 ... maximum 10,000
  • Best Bets - typically 1,000 ... maximum 25,000
  • Area depth - typically 5 ... maximum 20 *
  • User profiles - typically 50,000 ... maximum 1,000,000
  • Audiences - typically 500 ... maximum 10,000
  • Audience memberships - typically 500,000 ... maximum 5,000,000
  • SSO credentials - typically 100,00 ... maximum 100,000
  • Search indexes - typically 3 ... maximum 32
  • Content sources -typically 25 ... maximum 250
  • Search scopes - typically 25 ... maximum 250 *
  • Indexed documents per content index - typically 100,000 ... maximum 5,000,000
  • Indexed documents - typically 2,500,000 ... maximum 20,000,000
  • Thesaurus entries - typically 1,000 ... maximum 10,000
  • Alerts - typically 50,000 ... maximum 1,000,000
  • Team sites - typically 10,000 ... maximum 250,000
  • Personal sites - typically 10,000 ... maximum 250,000

SharePoint:Administrations concepts and limits

I frequently get asked for SharePoint scaling limits so I though I would blog an entry I can refer people to.

First an extract from the Capacity Planning section of the Windows SharePoint Services Administration guide which answers general WSS limits questions:

None of these are hard limits enforced by the system. They are guidelines for designing a server that has good overall performance.
  • Site collections (Database scope) 50,000 ... Total throughput degrades as the number of site collections increases.
  • Web sites (Web site scope) 2,000 ... The interface for enumerating subsites of a given Web site does not perform well much
    beyond 2,000 subsites.
  • Web sites (Site collection) 250,000 - You can create a very large total number of Web sites by nesting the subsites. For example, 100
    sites each with 1000 subsites is 100,100 Web sites.
  • Documents (Folder scope) 2,000 ... The interfaces for enumerating documents in a folder do not perform well beyond a thousand entries.
  • Documents (Library scope) 2 million ... You can create very large document libraries by nesting folders.
  • Security principals (Web site scope) 2,000 ... The size of the access control list is limited to a few thousand security principals, in other words users and groups in the Web site.
  • Users ( Web site scope) 2 million ... You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users.
  • Items (List scope) 2,000 ... The interface for enumerating list items does not perform well beyond a few thousand items.
  • Web Parts (Page scope) 100 ... Pages with more than 100 Web Parts are slow to render.
  • Web Part personalization (Page scope) 10,000 ... Pages with more than a few thousand user personalizations are slow to render.
  • Lists (Web site scope) 2,000 ... The interface for enumerating lists and libraries in a Web site does not perform well beyond a few thousand entries.
  • Document size (File scope) 50 MB ... The file save performance degrades as the file size grows. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB (2047 MB) if you have applied Windows SharePoint Services Service Pack 1.

SharePoint:Patch MOSS / WSS with minimal downtime

I have found this perfect article on my friend's blog and as it is absolutely amazing, and very helpfull I decided to link it here.

Original can be found here: Dirk Van den Berghe SharePoint Blog

preparation tasks:
- create a custom App_Offline.htm file for showing a maintenance page  - Copying this file into the root location of each IIS website used by SharePoint Web Applications will show this message instead of the SharePoint content.
- create a batch file that conveniently copies the App_Offline.htm file to all Web Applications (make sure not to copy it to the Central Admin WebApp)
- create a batch file that conveniently deletes the App_Offline.htm file from all Web Applications
- create a batch file that detaches all content databases for all Web applications with the exception of the Central Admin and SSP Web Apps ( add stsadm -o preparetomove command before detach database if you are still running MOSS SP1 pre-Infrastructure Update)
- create a batch file that attaches the content databases

Now you can start with following steps..

Upgrade process:
1.  Make sure that the hardware load balancers stops the services for WFE1 and only uses WFE2 to service user requests. We have an internal procedure that allows for manipulation of the load balancer. Actually we simply need to stop a custom IIS web site on the WFE server which will cause the load balancer to failover to the second WFE automatically.
Availability Result: Users are still able to access SharePoint content through WFE2.
Timing result: this operation took 2 minutes
2. Install the binaries for your SharePoint upgrade on WFE1. In my case WSS SP2 + MOSS SP2 +  all SP2 versions of the WSS and SharePoint Language Packs and finally installing the June Cumulative Update for WSS and MOSS. When installation completes, reboot the server.
Availability Result: Users are still able to access SharePoint content through WFE2.
Timing result: this operation took 50 minutes
3. Simultaneously install the same binaries on the index server. When installation completes, reboot the server.
Availability Result: Users are still able to access SharePoint content through WFE2.
Timing result: this operation took 40 minutes
OK So far so good. So basically, at this point, I have installed the binaries on 2 servers and I still have 1 to go, which is WFE2 that is still serving the SharePoint sites. I have two possibilities to continue:
- option1: install the binaries on WFE2 and reboot
- option2: run the configuration wizard on the upgraded WFE1 or the index server.
Option 1 will take all the sites down, because the installation of new binaries will stop IIS = Downtime and 404 errors. I cannot redirect my users to the upgraded WFE1, because the configuration Wizard has not run yet. So I am working with option 2
4. on WFE2 I launch my script that sets all my sites in maintenance mode (copies the App_Offline.htm file, that is)
Availability Result: Users are not able to access SharePoint content, but they receive a nice page stating that their site is down for maintenance through WFE2.
Timing result: this operation took 1 minute
5. on WFE2 I launch my script for detaching all content databases
- this script launches a stsadm -o preparetomove command for each content database (except Central Admin and SSP databases). This command is no longer required if you have at least SP1 with the Infrastructure Update installed.
- this script launches a stsadm -o deletecontentdb command for each content database (except Central Admin and SSP databases)
Availability Result: Users are still not able to access SharePoint content, but they receive a nice page stating that their site is down for maintenance through WFE2.
Timing result: this operation took 5 minutes ( I had 5 content databases)
6. on WFE1, run the SharePoint Products and Technologies Configuration Wizard.
If the upgrade process fails, investigate the log specified by the wizard, but also check 12-Hive\LOGS\Upgrade.log and the default SharePoint ULS logs. I have already seen that the SharePoint logs are written to the 12-Hive\LOGS folder instead of the location you specified in Central Admin during this upgrade process. After the upgrade your specified Logging location is used again.
Availability Result: Users are still not able to access SharePoint content, but they receive a nice page stating that their site is down for maintenance
Timing result: this operation took 15 minutes
7. Now that the farm configuration databases have been upgraded, your WFE1 is ready to start serving users again as soon as the content databases have been reattached. So, on WFE1 I launch my script to reattach the content databases. If one the operations generate an error, you can find the specific error in the 12-Hive\LOGS\Upgrade.log file.
Availability Result: Users are still not able to access SharePoint content, but they receive a nice page stating that their site is down for maintenance
Timing result: this operation took 10 minutes.
8. Make sure that the hardware load balancers starts the services for WFE1 and stops the services for WFE2 to service user requests.
Availability Result: Users are again able to access SharePoint content through WFE1.
Timing result: this operation took 2 minutes
My upgrade status is now complete with regards to the SharePoint content. My farm is servicing users again through a single Web Frontend Server for the moment, but it is servicing which is my main concern at this point. I no longer have downtime towards my users. If you add up all the minutes, then I have had a downtime towards my users of 33 minutes, which can be considered a small downtime. Now I continue with the rest of the upgrade process.
9. WFE2 is free now to do with whatever I want since it is no longer included in the load balancer pool.
- first, I launch my script to deactivate the site maintenance which simply deletes all App_Offline.htm files
- Next, I Install the binaries for the SharePoint upgrade on WFE2 + Reboot the server
Availability Result: Users are able to access SharePoint content through WFE1.
Timing result: this operation took 50 minutes
10. While WFE2 is installing the new binaries, I can run the SharePoint Products and Configuration Wizard on the index server.
Availability Result: Users are able to access SharePoint content through WFE1.
Timing result: this operation took 6 minutes
11. Run SharePoint Products and Configuration Wizard on WFE2
Availability Result: Users are able to access SharePoint content through WFE1.
Timing result: this operation took 8 minutes
12. Final step: Add WFE2 back into the load balancer pool

Saturday, May 14, 2011

Interview Question in SharePoint

Sharepoint:Stsadm syntax for feature and webpart deployment

For Feature:

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

For Webpart:

Stsadm -o addwppack -filename filename [-globalinstall] [-force]

Monday, May 2, 2011

SharePoint:Create a New Page Layout in SharePoint 2007 - Feature-Based

So the requirement presented to me for a client was to take an existing page layout and change a few of the properties to allow it to use some custom styles implemented at the site collection level. To do this, I needed to create a new page layout based on an existing layout, make this part of a feature and pull in all the bits and pieces necessary to deploy this as a feature. Finally, I had to deploy it to the client's testing environment.
Here is how I did it...
First, I was instructed that the Search Main Page was to be used as the starting point. A developer on my team told me the best way to go would be to load up SharePoint Designer, navigate to the appropriate document library and export the file. This didn't work. My requirement was to have the search web part already on the page, the same as the existing search main page. SharePoint Designer killed this web part tag so it came up empty.
Getting a copy of the page layout
1. Better is to go to the site collection you're starting with
2. Select "Site Actions" -> "Site Settings" -> "Modify All Site Settings"
3. Under "Galleries", select "Master pages and page layouts"
4. Find the page layout from the list and open its context menu, select "Send to" -> "Download a Copy"
5. Save the file to the solution location. We won't be using Visual Studio because its not necessary for this evolution.
6. Once the file is saved, reopen the context menu for the page layout file and select "View Properties".
7. Click on the Preview Image and when it appears, right click and save the image to the same location as the aspx file.
Now you have the basic aspx files you will modify and put back into SharePoint as a feature. Open the aspx page in an appropriate editor. I'm assuming you understand enough about aspx to do what you need to do. Make the appropriate modifications and save the file.
IMPORTANT NOTE: If you are like me, you have a desire to 'clean up' the file declarations so you can see what's going on. Don't do this. I haven't figured out why but when I introduced hard returns in the second line (the really long one) of declarations between <% %> sections, it bombed when I reimported it into SharePoint. A guy on the team here thinks there may be a checksum on that line to head off tampering. Dunno but I know when I leave it it works, when I touch it it bombs.
You can also use any editor (Paint.Net works) to change the page layout to look the way you want it to. Change the folder of this file to your feature folder + "\Images". It's required for the page layouts and master pages.
So you should have two files and a subfolder for your feature ready to go.
Now we need to set up the feature to deploy it.
Create two new files in any editor: "feature.xml" and "layoutfiles.xml"
2. Here are the contents of my feature.xml file:
 <Feature  Id="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
     Title="Custom Formatted Search Page Layout by Jim"
     Description="Search page with customized style inclusions"
   <ElementManifest Location="layoutfiles.xml"/>
2.1. Id is a new GUID you generate from Visual Studio.
2.2. Scope means the level where this will be used, not the level at which it becomes available for items below it. So "Site" scope means it will be installed at the site collection level and used at the site level.
3. Here are the contents of my layoutfiles.xml file:
 <Elements xmlns="">
  <Module Name="CustomSearchMain" Url="_catalogs/masterpage" Path="" RootWebOnly="TRUE">
   <File Url="CustomFormattedSearch.aspx" Type="GhostableInLibrary">
    <Property Name="Title" Value="$Resources:spscore,SearchMainTitle;" />
    <Property Name="MasterPageDescription" Value="$Resources:spscore,SearchMainDescription;" />
    <Property Name="ContentType" Value="$Resources:cmscore,contenttype_pagelayout_name;" />
    <Property Name="PublishingAssociatedContentType" Value=";#$Resources:cmscore,contenttype_welcomepage_name#0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF390064DEA0F50FC8C147B0B6EA0636C4A7D4;#" />
    <Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/Preview Images/customsearchpage.gif,     ~SiteCollection/_catalogs/masterpage/Preview Images/customsearchpage.gif" />
    <AllUsersWebPart WebPartZoneID="TopZone" WebPartOrder="1">
                     <WebPart xmlns="">
                         <Assembly>Microsoft.SharePoint.Portal, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>
                         <GoImageUrl xmlns="urn:schemas-microsoft-com:SearchBoxEx">/_layouts/images/gosearch.gif</GoImageUrl>
                         <GoImageUrlRTL  xmlns="urn:schemas-microsoft-com:SearchBoxEx">/_layouts/images/goRTL.gif</GoImageUrlRTL>
                         <GoImageActiveUrl xmlns="urn:schemas-microsoft-com:SearchBoxEx">/_layouts/images/gosearch.gif</GoImageActiveUrl>
                         <GoImageActiveUrlRTL  xmlns="urn:schemas-microsoft-com:SearchBoxEx">/_layouts/images/goRTL.gif</GoImageActiveUrlRTL>
                         <TextBoxWidth xmlns="urn:schemas-microsoft-com:SearchBoxEx">280</TextBoxWidth>
                         <SearchResultPageURL xmlns="urn:schemas-microsoft-com:SearchBoxEx">results.aspx</SearchResultPageURL>
                         <AdvancedSearchPageURL xmlns="urn:schemas-microsoft-com:SearchBoxEx">~Site/$Resources:cmscore,List_Pages_UrlName;/advanced.aspx</AdvancedSearchPageURL>
                         <ShowAdvancedSearch xmlns="urn:schemas-microsoft-com:SearchBoxEx">true</ShowAdvancedSearch>
                         <DropDownMode xmlns="urn:schemas-microsoft-com:SearchBoxEx">HideScopeDD</DropDownMode>
                         <ShouldTakeFocusIfEmpty xmlns="urn:schemas-microsoft-com:SearchBoxEx">true</ShouldTakeFocusIfEmpty>
  <Module Name="LayoutPreviewImages" Url="_catalogs/masterpage/Preview Images" Path="Images" RootWebOnly="TRUE">
   <File Url="customsearchpage.gif" Type="GhostableInLibrary"/>  
3.1. I took most of this from a coleague and from the net. The CData portion gives you the embedded web part already in the top web part zone.
3.2. Notice the gif image parts of the xml. These are whatever the new name is for the gif you edited earlier.
3.3. Notice also the part that says: "contenttype_welcomepage_name". This means that your layout will appear under the "Welcome Page" templates when you go to use it in your site collection. I haven't found much about this on the web yet but I believe if you search on content types and master page libraries, you may find additional options.
Your feature is complete!
Now its time to deploy.
1. Copy your aspx, gif (in its folder) and 2 xml files to the server where you want to deploy and into a new temporary folder.
2. Copy from the temp location to the 12 hive \Template\Features\ folder.
3. Open a command line and run: stsadm.exe -o installfeature -name MyNewPageLayoutFeature -force
3.1. Use the -force option if you've already installed previously.
3.2. the -name value is the name of the folder where the your feature now exists in the 12 hive.
4. Execute iisreset
5. Browse the the appropriate site collection on your server and back to "Site Actions" -> "Site Settings" -> "Modify All Site Settings"
6. Under "Site Collection Administration" select "Site Collection Features"
7. You should see your new feature/page layout. Click to activate.
Use your new layout.
Now, when you go to create a new page, you should see your additional layout. When you select it, you should get your custom layout gif to show users what it will look like.
I can imagine really intricate uses of this for creating custom CRM dashboards or for magically including SilverLight applications in your system. Good Luck!

SharePoint:Editing page layout in publishing site


  • Browse to the page
  • Click Site Actions, Edit Page
  • From the tool bar click Page
  • In the drop down list click Page Settings
  • Now pick your Page Layout
  • Click OK

Friday, April 29, 2011

SharePoint:hiding quick launch bar

Hi All,

There is a way you can hide a quick launch bar in MOSS 2007.

Here are the steps to follow:

(1)Add content editor webpart on page
(2) Click on Modify shared webpart
(3) Click on source editor button
(4) Copy and paste the following HTML

display: none;

(5)Go to layouts section of that webpart and select Hidden.

That's it. Now no more quick launch bar !!!!!

If you want to get quick launch back, just again edit the page and go to modify shared webpart of content editor webpart. Go to source editor button and remove all HTML content and save it.

That's it. Now you will have your quick launch back in place !!!

Monday, April 25, 2011

SharePoint:To get the size's of the sites

stsadm -o enumsites -url http://site/subsite>File.txt

where file.txt is used to write the data in to a text file
you will get the data in MB's

so how it look like...

<Sites Count="1">
StorageMaxMB="0" /> </Sites> 

Wednesday, April 20, 2011

IIS7:Cannot start service W3SVC on computer '.'


Error while restarting IIS
i.e. after stopping IIS when i start again i hot this error
Cannot start service W3SVC on computer '.'


  1. Run -> appwiz.cpl -> Turn windows features on or off -> Check "Windows Process Activation Service"
  2. That's all.
and also check this

You should check to see that all of the following services are started, or at the very least, not disabled: HTTP, Windows Process Activation Service, DCOM Process Launcher, and RPC Endpoint Mapper.
You should also verify t hat no other process is listening on port 80. The simplest way to do this is to issue the following in a command window:
netstat -a -o|findstr 80

Tuesday, April 12, 2011

SharePoint:Export and Importing of SharePoint Site

To take backup of particular sub site and to make it as sub site to another site collection:

1)      First log in to WFE as admin rights
2)      export needed site into .cab file
stsadm –o export –url “
http://siteA/sub%20site1” –filename –versions 4
3)      Do an import to a required location
stsadm –o import –url “
http://siteB/sub%20site1” –filename

Monday, April 11, 2011

SharePoint:The user does not exists or it's not unique


If you have the above issue "The user does not exists or it's not unique"
in my finidngs i found that this may be due to the change in the active directory domain
if there is some migartion done from one site to other site collection


I saw this problem a few times but when I went to user profile, I can see the user is there and all the information is right. But if you go to WSS_Content db and run
select * from userinfo where tp_title like ‘user%’
I found the tp_login data is different from the user who has problem. The problem with this, is that the tp_Login column in the UserInfo table for every site collection in which Margie has permissions, is cached with her previous NT Login Name. There is also no way to update this information with a SPUser object from the SharePoint object model, and SharePoint does not synchronize this from Active Directory once the users is added to a web in the Site Collection.
The only time that SharePoint will automatically update the tp_Login column, is if the users is completely removed from the site collection. The tp_Deleted column is then set for the user in that site collection. On the next occurrence of the user being added to a web, we gather the current information from the domain. You can however, re-sync SharePoint with the current information without removing them completely from the site collection by using SPUserUtil
For a single user you can use
stsadm.exe -o migrateuser -oldlogin MYDOMAIN\prhranki -newlogin MYDOMAIN\LUHRANKI -ignoresidhistory
If you need to do a batch of users, I personally think WSSUserUtil and SPSUserUtil is the way to go.
See this two references:

SharePoint:Hit counter or stats of SharePoint Site

If you have enabled "Usage Analysis Processing" in SharePoint Central Administration, there is a hidden URL that lets you view the stats for any page/section/area of the Portal (and WSS). Just navigate to the area where you wish to view stats and add
to the URL. Note the string above replaces the filename so if you are in the "News" home page
will become

If you use
instead it will show a summary including Total Hits, Number of Users etc.

SharePoint:Field Lengths in SharePoint Lists


We have a field lent restrictions in SharePoint
Single Line Field : 255 chars
Multi line field (document, forms, picture library) : 255 chars
Multi line field (everywhere else) : no limit

SharePoint:How to change the Maximum File Upload Size


By default SharePoint allows a maximum file size of 50MB that can be uploaded into any document library. This might be too much as you might not want users downloading 50MB files over your LAN/WAN. To change the maximum file size
1. Goto SharePoint Central Administration > Configure Virtual Server Settings from Virtual Server List Page.
2. Select your server
3. Goto Virtual Server General Settings (in Virtual Server Management)
4. Change the value of the Maximum Upload Size in MB's.

If you increase the file size limit, your site might occassionally time out for users while they are uploading files. To accomodate this increase the default time out property for IIS.

Thursday, April 7, 2011

SharePoint:System Center Operations Manager 2007

Hi ,

I have found that there is a tool available for monitoring SharePoint related issues
System Center Operations Manager 2007 is a tool that will help for monitoring the issues in SharePoint but you need to have a addon for this i.e. Microsoft Office SharePoint Server 2007 Management Pack to the above software for more details just look into this links....

Wednesday, April 6, 2011

InfoPath:Excellent site for InfoPath forms with SharePoint

InfoPath:How to create and deploy an InfoPath browser form template to SharePoint

In this InfoPath video, you learned…

  • How to create a SharePoint form library and enable it to display InfoPath browser forms.
  • How to check whether InfoPath Forms Services is correctly configured on SharePoint.
  • How to create a browser-compatible InfoPath form template.
  • How to deploy an InfoPath browser form template to SharePoint.

InfoPath:How to publish an InfoPath 2007 browser form to SharePoint

Learn which actions you have to take both in InfoPath and SharePoint before deploying an InfoPath form template to SharePoint so that it can be opened and/or filled out using a browser.


You have an InfoPath form template, which you want to open and/or fill it out using a browser.


There are several actions you have to take both in InfoPath and SharePoint before deploying a form template to SharePoint so that it can be opened and/or filled out using a browser. The solution described in this article is for InfoPath form templates that do not require administrator approval before deployment, that is, they do not contain .NET managed code.

Prerequisites on the Server

  1. Windows SharePoint Services 3.0 must be installed.
  2. Forms Server 2007 must be installed.
  3. InfoPath Forms Services must be activated.
Refer to the SharePoint documentation for guidance on installing and activating InfoPath Forms Services.

Preparing a form template in InfoPath to become a browser-form

An InfoPath form template must be:
  1. Browser-compatible
  2. Browser-enabled
to be able to be displayed in a browser. You can make a form template browser-compatible by specifying compatibility setting, either up-front, when you first create the form template, or later, when you design the form template.
For more information on InfoPath browser-compatible forms, see
  • Introduction to browser-compatible form templates

Setting browser-compatibility up front

When you first open the InfoPath client application you are presented with the Design a Form Template dialog box. You can check the Enable browser-compatible features only checkbox to make an InfoPath form template browser-compatible.
What this means is that the InfoPath designer will only present you with those features of InfoPath that are supported in both the InfoPath editor as well as the browser.
The benefit of choosing this option so early in the design phase is that you will not run the chance of using options that are not available to browser-forms and then have to change your form's design at a later stage because of this.

Figure 1. Enabling browser-compatible features when creating a new form template.
For more information on setting browser-compatibility, see
  • Specify the compatibility settings for a form template
  • Creating InfoPath Form Templates That Work With Forms Services

Setting browser-compatibility afterwards

You can set browser-compatibility after you have designed your form template by going to the Tools menu, and selecting the Form Options menu item to open the Form Options dialog box, and then clicking on the Compatibility category.
If you created a form template that contains features that are incompatible with InfoPath Forms Services, InfoPath will warn you of this and you will have to modify your form template to satisfy the compability requirements for browser-forms. You will have to fix the incompatibilities before proceeding.
If you don't fix the errors, you can still publish the browser-compatible form template to a server running InfoPath Forms Services. However, the form template may not work as intended/desired.
For a list of the features that are and are not supported in browser-forms, see
  • Web browser compatibility in InfoPath Forms Services
  • InfoPath 2007 features that are unavailable in InfoPath Forms Services
  • View server-generated errors and messages in the Design Checker task pane
Tip: Specify browser-compatibility settings up front to avoid having to adjust your form template afterwards.

                                           Figure 2. Enabling browser-compatible features through the Form Options dialog box.

Browser-enabling a form template

Once you have designed your InfoPath form to be browser-compatible and are ready to publish it to SharePoint, you must make it browser-enabled before doing so.
While you can publish a browser-compatible form template to SharePoint without making it browser-enabled, you will not be able to open or fill out this form in a browser until you browser-enable it. This is an important fact to understand.

So how do you browser-enable an InfoPath form template?

Here is where InfoPath and SharePoint have to work together to make it able for you to browser-enable a form:
  1. In InfoPath: Ensure that the form template does not contain any errors reported by the Design Checker.
  2. In SharePoint: Configure InfoPath Forms Services to Allow users to browser-enable form templates (see figure 3).
  3. In InfoPath: Check the Enable this form to be filled out by a browser checkbox when publishing the form template (see figure 4). 

                            Figure 3. Configuring Forms Services in SharePoint Central Administration Application Management
                                               Figure 4. Browser-enabling a form template in the Publishing Wizard.
If you do not configure InfoPath Forms Services before you try to browser-enable a form template, you will be presented with the following message in the Publishing Wizard:
"This form template is browser-compatible, but it cannot be browser-enabled on the selected site."
                           Figure 5. This form template cannot be browser-enabled message in the Publishing Wizard.
Warning: If you ignore this message and continue to publish the form template, you will not be able to open or fill out the form using a browser, not even if you configure InfoPath Forms Services after you have published the form template. If you configure Forms Services after you have published a browser-compatible form template, you will have to re-publish the form template from within InfoPath and browser-enable it while re-publishing it.

Note: This was taken from the site 


Windows:Event ID 7888(SharePoint AD user profile import error)


When starting a full or incremental import of Active Directory, either manually or scheduled, the import is successful, but there is an error thrown as soon as the import is initiated. My assumption is the AD import kicks off several simulateous jobs such as updating users "My SharePoint Sites" in the MOSS and Office 2007 environments.
For reference, to kick off a manual import of AD: Central Administration > Shared Services > User Profile and Properties

Event ID 7888

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888

Description: A runtime exception was detected. Details follow.

Message: Access Denied! Only site admin can access Data Source object from user profile DB.

Technical Details:
System.UnauthorizedAccessException: Access Denied! Only site admin can access Data Source object from user profile DB.
at Microsoft.Office.Server.UserProfiles.SRPSite.AdminCheck(String message)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(IDataRecord rec)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(String strDSName)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site, Boolean fAllowEveryoneRead)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.GetDataSource()
at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)


  1. Navigate to: Central Administration > Operations > Services on Server > Office SharePoint Server Search.
  2. In the "Configure Office SharePoint Server Search Service Settings" page, locate the account defined for "Farm Search Service Account" and write down the account name.
    1. For reference, the account defined serves as the account for the AD "Configure Profile Account" access account.
    2. For reference, you can get to AD Profile Account page: Central Administration > Shared Services > User Profile and Properties > Configure Profile Import.
  3. Navigate to: Central Administration > Shared Services > Personalization services permissions.
  4. On the "Manage Permissions: Shared Service Rights" page, add the account from before (or edit if already exists). The account needs one of the following permissions; I couldn't figure out which one:
    1. Manage user profiles
    2. Manage permissions
I've tested this resolution several times with success.
For reference, I've updated my Farm Search Service Account with the following permissions since the account in question will most likely be accessing the types of content referenced in the permissions at one point or another:
  • Manage user profiles
  • Manage audiences
  • Manage permissions
  • Manage usage analytics

Other Thoughts

As with Event ID 2424 I wrote about, I noticed that Event ID 7888 began around the time I installed the following WSS/MOSS security patches which came out prior to the SharePoint SP1 patch:
I'm going to make the assumption that this error will occur as soon as you install the SharePoint SP1 patch as well.


Somewhere along the line, the WSS/MOSS and/or SharePoint SP1 update(s) are modifying existing permissions… Shame on the updates.
I've read other posts whose resolution is to add the account in question to the local administrators group. Although their resolution may work, the profile import account should not be a server administrator; the administrator role should be reserved for the global MOSS service account admin (the account used to install MOSS) and the configuration account (the account MOSS uses to provision databases and other content that was defined during the MOSS install).

Tuesday, April 5, 2011

Good site for SharePoint quiries

Check this out...

SharePoint:"Access is denied. Check that the Default Content Access Account has access to this content"

If you have this issue....

Check the steps

The resolution for this was to add the following registry key
1) Click Start, click Run, type regedit, and then click OK.
2) In Registry Editor, locate and then click the following registry key:
3) Right-click Lsa, point to New, and then click DWORD Value.
4) Type DisableLoopbackCheck, and then press ENTER.
5) Right-click DisableLoopbackCheck, and then click Modify.
6) In the Value data box, type 1, and then click OK.
7) Quit Registry Editor, and then restart your computer.

SharePoint:The password for the content access account cannot be decrypted because it was stored with different credentials. Re-type the password for the account used to crawl this content.


Our search is not working. The crawl log indicates following error: "Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)".


ad this problem and solved it by using user@domain.local instead of domain\user when specifying the Default Content Access Account. 

Central Administration --> SSP --> Search Administration | Default Content Access Account.

SharePoint:Alert : Percentage of committed memory in use is too high


Alert Description : The threshold for the memory\committed byte in use performance counter has been exceeded. The value that exceeded the threshold  is 81.35668827192.
I am getting this alert at my SCE Box having 3 GB of RAM. How can i resolve this issue as accourding to the alert description i have checked with the performance counters at system monitor ( perfmon) .

Several Microsoft products including Exchange, SQL Server, and the Operations Manager ROM will use all available memory. This is especially noticeable on 64-bit platforms where memory can scale-out more effectively for the applications.


Configured the server to have a 95% threshold instead of 80%. To do it:

1)    Navigate to authoring pane -> Management Pack Objects -> Monitors.
2)    Find the monitor at "Windows Server 2003 Operating System"  -> Entity Health ->Performance -> "Percentage of committed Memory in Use"
3)    Right click it and select “Overrides” -> "Override the monitor" -> "For all objects of type: Windows Server 2003 Operating System".
4)    Specify the threshold value 95% instead 80% and click to apply.

Hope it helps.

Friday, April 1, 2011

SharePoint:Adding template to the subsites


Some days back i have not seen the Publising site template in the Template selection in the subsite


If you want to see the templates that are available in sitecollection in the subsites you nee to do this:

Check your WEBTEMP.XML file under \12\TEMPLATE\1033\XML folder.
Most probably templates you'd like to see are set to Hidden="TRUE". Make them false.


If your site is a publishing site, go to Page Layout and Site Templates Settings and add the templates that you want your subsites to use.
(Site Actions > Site Settings > Modify All Site Settings > Look and Feel > Page layouts and site templates)

Thursday, March 31, 2011

SharePoint:Adding Webpart to EditForm,DispForm,ViewForm Pages

If you want to edit Edit,Disp,View form aspx page and to add webparts to the following pages


add the above at the end of the url ex: Dispform.aspx?toolpaneview=2

Wednesday, March 30, 2011

SharePoint:WebPart unable to delete from the site


If you are unable to delete the webpart from the sharepoint site and you have any error or displaying blank page while editing the webpart(i.e. to remove the error webpart from your site


http://yoursite/default.aspx?contents=1 will show all the webparts in the site check the error webpart and delete it.

SharePoint:Site Features in SharePoint Site

If you want to see site features in SharePoint Site and in Web

_layouts/managefeatures.aspx?scope=Web for Web
_layouts/managefeatures.aspx?scope=Site for Site

SharePoint:The site is not valid. The 'Pages' document library is missing


When i tried to create a page using Site actions in the site i get the following error
The site is not valid. The 'Pages' document library is missing


It was given that go to site features and activate "Office SharePoint Server Publishing Feature"
but it was already in actived!!!! so what to do now

I have managed to fix this. When you upgrade, the root site needs the site publishing feature deacitvating and reactivating.
Try running this:
stsadm -o deactivatefeature -name PublishingWeb -url https://UrlOfPublishingSite -force
stsadm -o activatefeature -name PublishingWeb -url https://UrlOfPublishingSiteiisreset

Thats it!!!!!!!!!!

Tuesday, March 29, 2011

Excellent blog for SharePoint issues.

Hi i have found an excellent blog with awsome solutions give
check the link below:

SharePoint:Shared Services Error "An indexer is not assigned to the Shared Services Provider 'SharedServices1"

 I was unable to import user profiles, after our development server crashed and fortunately we restored it using the last known back-up of the Virtual machine. All of a sudden our user profiles import and search crawling and indexing services stopped abruptly, throwing a nasty "An indexer is not assigned to the Shared Services Provider 'SharedServices1' error.

Luckily i found a solution for the same:

a. Log in to Central Administration
b. Select your Shared Services provider and choose "Edit Properties" from the drop-down context menu
c. Configure your Index server and it works like a charm...

SharePoint:The search request was unable to connect to the Search Service


There was a SharePoint farm not returning search results. The error it returned was

"The search request was unable to connect to the Search Service"

After looking at it, it was a very simple fix. The server wasn't configure to server search queries. A simple ticking of the box in central admin and it fixed the problem. To fix this:
  • Go to Central Admin

  • Operations

  • Services on Server

  • Office SharePoint Server Search Service Setting

  • Make sure "User this server for serving search queries" is checked.

  • Thats it!!!!!!!!!!

    Another thing that could be causing it is the Account used to search might not have the right access needed or the Search services aren't running. Check that

    • Office SharePoint Server Search and
    • Windows SharePoint Services Search

    Should be both running. If you're still having problems, let me know and I'll try to help you out.

    SharePoint:filtered lookup field

    I have done some investigation for doing a filterd lookup field for SharePoint list/libraries
    got some references check this out hope this will help you....


    Monday, March 28, 2011

    SharePoint:Exception from HRESULT: 0x80040E14


    I got this error when i am updating the item in the list and when i create a new item in the list
    Error:Exception from HRESULT: 0x80040E14,0x80004004


    I have done some investigation and found that the above error message might occur because of SQL transaction logs were full and needed to be truncated. It seems that the SQL Server is running out of the log space.
    so clear the log file you will be out of this error!!!!!!! so simple right.

    Friday, March 25, 2011

    SharePoint:The workbook that you selected cannot be opened.


    When you open document in the document library if you get this error message "The workbook that you selected cannot be opened.

    The workbook may be in an unsupported file format, or it may be corrupt.
    Would you like to try and open this file in Excel? "


    1. From Administrative Tools, open the SharePoint Central Administration Web application.
    2. On the Central Administration home page, click Application Management.
    3. On the Application Management page, in the Office SharePoint Server 2007 Shared Services section, click Create or Configure this Farm's Shared Services.
    4. On the Manage this Farm's Shared Services page, click SharedServices1 (Default). This is the Shared Services Provider (SSP) that you will configure.
    5. On the Shared Services home page, in the Excel Services Settings section, click Trusted file locations.
    6. On the Excel Services Trusted File Locations page, click Add Trusted File Location.
    7. In the Address section, type the location and name of the SharePoint Office SharePoint Server 2007 document library that you want to add as a trusted file location in Excel Services. If the document library is stored in the Windows SharePoint Services 3.0 content database, ensure that Windows SharePoint Services 3.0 is selected as the Location Type.
    8. In the External Data section, select the type of data connections that you will allow workbooks in this trusted file location to contain and click OK.

    SharePoint:Editing Profile in SharePoint Site


    Unable to edit SharePoint Profile


    _layouts/editprofile.aspx add this at the end of the url...

    SharePoint:object not set to an instance of an object with the webpart


    This issue is raised by one of the user who is unable to see a particular webpart in Sharepoint he is getting an error message "object not set to an instance of an object". and this is only happening for a particular users....hmmm god dam..

    Deploying webpart to SharePoint 2007 using  Visual Studio Extensions for Windows SharePoint Services (VSE WSS) and getting error message “Object reference not set to an instance of an object”.


    You need to add the user to the any of the people and groups...simple right.

    This is for the second one:

    1] Copy the built webpart.dll to c:\windows\assembly (GAC)

    2]  In the folder location where webpart VSE solution was created found setup.bat file in bin\Debug, and this is the file which VSE calls when deploying the solution and has instructions to run it. Ran the setup.bat from command prompt as “setup /uninstall” this ran ok, then ran setup /install this ran ok too. Modified the setup.bat file and add the line to remove the webpart.dll from the GAC and add the webpart.dll assembly to GAC as under:

    under :LDeploy section before goto :EOF added the following line:
    "%programfiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" -if webpartTest.dll
    "%programfiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" -uf webpartTest

    Thanks for your time and patience in this matter. 
    Thank You,

    SharePoint:Unable to open doc files from document library


    When i am trying to open a document from document library  i got an error message like a popup showing "Some files can harm your computer, If the file information below looks suspicious, or you do not fully trust the source, do not open the file".


          Follow the steps to rectifiy this issue, add your site to the trusted location in browser
    1)      Open Internet Explorer Options à From your browser Go to “Tools” à then select “Internet Options” àthis will popups Internet Options window
    2)      From the Internet Options window àSelect Security Tab àHere select “Trusted Sites” Icon àClick “Sites” button
    3)      Again Trusted sites window will pop up àHere uncheck
    4)      And add http://yoursitename/  to the web sites list.
    5)      Now try to open the file and let us know the result.

    SharePoint:Outlook sync With Sharepoint calender


    This is one of the major issue i had and striggugeled for long it goes

    When i connect SharePoint calender to outlook i am able to get the events/tasks/items from Sharepoint to Outlook Calender but its not happening viceversa..such an idiatic issue we got ever..


    This is a very simple solution you jus need to remove the redirects from the IIS i.e. you just need to uncheck the redirects from the IIS


    Window(button)+Run-->type inetmgr-->go to redirected site-->check the redirects icons-->uncheck if any redirects are given if so remove them.


    Thursday, March 24, 2011

    SharePoint: Getting script error at my custom page

    In my sharepoint site, at my custome page we are getting script error at the left bottom of the browser:

    probelm: [script error: document.getElementByID(..) ID not found or null]
    here when i check using internet explorer debug option, i found a block of script which is trying to search the sharepoint search text box and renaming its dynamic id to some value(on page load) and also adding event for the sharepoint search text box.

    when i checked master page of the page[where the sharepoint search control exists], it is commented.
    so i uncommented the search_placeholder and added Visible="false" property to the contentholder.
    problem solved


    Wednesday, March 23, 2011

    SharePoint:Page Version History Error

    Today I found a version history “bug” in SharePoint publishing pages:

    The version history system of SharePoint covers only Page Fields, but not Web Parts.

    In detail:

    •Create a new page (e.g. “Blank Web Part Page”) within a publishing web.
    •Now add text and a Web Part. Save changes and check-in.
    •Check out and change the text and some properties of the Web Part.
    •After that, check-in again, and open the “Version History”
    If you now try to recover the first version, it seems to work, but only the page fields are recovered. The Web Part is always the latest version, because the Web Parts are saved in a totally different location, so they are not covered by the version history system.

    Lets have a look on a cool solution:

    Garry Lapointe created a web feature which replaces the version history system and saves a whole page with all Web Parts on every check-in through an Event Receiver on the Pages list.
    The version is Alpha 0.0.1 but it is working very well, so Download from codeplex

    SharePoint:Scope rule for People Search in SharePoint

    If you want to give a scope rule in SharePoint for people search


    The above is the rule that should be given at the scope rule
    Check the image below to see the navigation:

    SharePoint:Unable to see features page in Sharepoint site

    If you are unable to see features page in sharepoint site

    Copy paste this in the url


    SharePoint:Using a Site Template (.stp) from another server results in a File Not Found error

    If you find yourself facing a "File Not Found" error after creating a new web from a custom .stp template file, you might be having master page errors.

    You created and customized a publishing web on Server1. After customization completed, you created a .stp template file through Site Actions/Site Settings/Save Site as Template. After uploading the .stp file to Server2's Site Template Gallery, you create a new site from the site directory, selecting the custom .stp template, but upon completion of site creation, you receive only a "Page Not Found" error such as this:

    The problem could be that the master page did not map properly. To check and correct the problem, you have to "cheat" by directing your browser to the new site's master page settings page. That is done by replacing "default.aspx" in the current URL with "_Layouts/ChangeSiteMasterPage.aspx" e.g. http://site/web/default.aspx becomes http://site/web/_Layouts/ChangeSiteMasterPage.aspx.
    After the page loads, you should see two error messages noting problems with both the site and system master pages.

    *NOTE: If you do not see the same error, you do NOT have the same problem and resetting your master page will probably not solve your problem.

    In the Site Master Page section, ensure that the "Specify as master page to be used by this site and all sites that inherit from it" radio button option is selected. In the drop down below it, ensure that the "default.master" is selected.

    Scroll down to the System Master Page section.

    Ensure that the "Select a system master page for this site and it's subsites to inherit" option is selected and once again set the dropdown below to "default.master".

    Scroll down to locate the "OK" button and click it to reset the site master pages and fix the site.

    Sharepoint:Importent Note while Customizing Master Page in SharePoint

    Dont ever delete any content in master page if you want to some customizations only hide them but dont delete them.
    This is the first basic point if you are starting customizing the master page