Nidhi's Blog

A Site owner of a Sub site cannot save any list as Template gets Access Denied.

2010-05-12T15:50:00.000+05:30

I am working with a new organization now and we deal more in the user interface then the server side and you know what its definitely a learning experience when you stand at the other side, we truly ignore what would an action on the server result at the users end and it a great learning curve here.

From now on my posts will me more of client specific rather then server because not everyone using SharePoint has an access to server but they do have issues
Most of the users face “Access Issue” we as administrators inherit and break permissions, play with the item and list levels and it some times does impact the customers the issue I had recently was

A Site owner of a Sub site cannot save any list as Template gets Access Denied.

Here we have a site collection with site admins and we have some sub sites under it, every sub site is governed by different site owners (and admin’s as well but they do not step into another territory)

When a site owner tries to save any list as template he gets AcceSS denied

The issue lies with the List template gallery in the Main site o look at that logon to main site > site actions > site settings > Galleries > List template gallery

We saw that the Site collection admin was running it with unique permissions and the site owner for the sub site was given Read access out there

We then added him as contribute on list template gallery and it fixed the issue for us

2010-03-26T23:34:00.002+05:30

1. On windows 2008 servers we installed the Desktop experience feature and started the web client service

2. Then we went to the IIS 7.0 manager page

3. On the Module section we removed the WebDav module

4. Explorer view started working on the windows Integrated sites

5. but not on FBA , we noticed via fiddler that site was running into authentication loops when browsed with FBA

6. while signing in the browser on FBA we checked the Checkbox ""sign me in automatically "

Explorer view gives "Internet Explorer Cannot dispal this webpage" on Server 2008

2010-03-26T23:26:00.000+05:30

Search does not work for me since I splitted the indexer and the query server

2009-09-09T19:34:00.001+05:30

I came across a rather interesting problem yesterday,
I came to know that we were not able to search the portal site since we decided to have a dedicated Search server in the farm.

The environment was
1 Application server 32 BIT Windows Server 2008 also running search query service
1 Search server 32 BIT Windows Server 2008 running Search Indexing Service
1 Database server which was SQL 2005
Interesting catch was that everything was running under FQDN

The search started getting rude to us since we added a search server to the farm and gave it an Indexer role. also the search was set crawl all the Dedicated WFE (which might not be a good idea)

First thing you have to check is the Crawl logs, which might give you a better direction, mine gave me error as - could not access the url
The site was browse able on the client and the application server
we RDP'd to the Index server and tried browsing the site & it did not show up
Tried pinging, tracert, nslookup; no response- by this time we were sure that it was a network problem

What's the catch ?

The Domain Controller was running on Windows Server 2003, which means IPv4 we saw that Sharepoint was running on Server 2008 which is IPv6.
when you give role to a server as Indexer it writes entries to the host file with the url of the sites and from there we saw that it was IPv6
we disabled the IPV6 networking layer on Sharepoint and the sites were now browseable and searchable
checkout the following links to support that :

http://support.microsoft.com/kb/215383
http://technet.microsoft.com/en-us/library/cc748826.aspx

Golden Point to remember:

Incase you have separate Query and Index server in the farm make sure that the site should be up and browse able on the Indexer server

"The path for the index location is not valid"

2009-09-02T03:12:00.002+05:30

"The path for the index location is not valid"

I recently faced this issue with the Sharepoint on the Central administration page that gives "The path for the index location is not valid" error message on the Manage search settings page on Application management

Reason:
================
The problem occurs when you have changed the default location of the index file path

Resolution:
================

+ Either you can try bringing the index location back to where it was
+ Try stopping and starting the Osearch service give it the new location, and start it again, to do this make command line your friend.
+ To stop and start WSS search with command line use http://technet.microsoft.com/en-us/library/cc288507.aspx
+ To stop and start Office search with command line use http://technet.microsoft.com/en-us/library/cc262920.aspx
+ Try giving WPG group as full permissions on the index file location folder
+ Also give permissions to the C:\windows\tasks folder
+ As its a system folder and it will not give you permissions to edit the attributes on the command prompt run attrib -s C:\windows\tasks the go to security tab and add permissions and then again on command prompt run attrib +s C:\windows\tasks, to get the system folder attributes in place

Assume that the new index location you have provided is Drive D,
so go to the D drive and add the network service and the Worker Process Group (WPG) group as the following permissions listed

Permissions:

Traverse Folder / Execute File, List Folder / Read Data, Read Attributes, Read Extended Attributes, and Read Permissions

And I bet it going to work, if you are wondering why, this is because O search is controlled by a service named Office server web services and this service runs with the service account as Network service.

you can determine this from the IIS

I cannot open my sharepoint site on server, but works on clients

2009-08-19T04:57:00.001+05:30

Suppose you run into problems with your machine that you can never open the SharePoint site on your server
There might be several reasons why you may run into this

First question: do you have a Host header on the site?
Second: did you configure the site in a Host header mode?
Third : Is the site browse able on the server with servername ?

If you answer yes to all three I guess I know what to do, also even if you answer no to the third one we are still good….

Follow the magical KB http://support.microsoft.com/kb/896861 and disabled loopback check
Steps to do that are as follows:

Disable the loopback check

Follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
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.

Now it is okay if you do not restart the machine, sometimes it just takes it and the site should be then browse able on the server

Setting full anonymous access for a document library

2009-06-25T04:38:00.001+05:30

If you have a SharePoint site which is running on full anonymous access and you want a document library to run on anonymous access too, that will not be possible because by design SharePoint will only allow the anonymous users to only view the contents of a document library and not add anything to it

If you want the anonymous users to be able to add the documents as well to the library you will have to perform an additional task

SPD workflow Failed on start (retrying)

2009-06-19T21:07:00.000+05:30

I have been wrestling with this issue for about 60 days, the issue occurs when you create a simple OOB SPD workflow or even a Nintex workflow.

The solution to this is two parts

PART I

=================

The service account should be a part of

1. Looked at the groups in the local machine

· WSS_WPG

· WSS_ Restricted

· WSS_Admin_WPG

· IIS_WPG

2. Checked on the SQL management studio > security > logins > Service account > properties > server roles were given as dbcreator > security & system admin > public

Looked in user mappings the service account was set db owner

3. >> Looked in the application content database in SQL

service account should be is a db owner

4. In Central Admin page > policy for web application > add service account as full control

5. CA > operations tab > update farm administrators group > service account is added there

6. looked in the site > site settings > site collection administrator

7. looked in the component services > dcom config > IIS admin service > security > added the service account to launch and activation > access permissions > and Configuration permissions .

After doing all these settings the service account must have all the require permissions

PART II

===============

Second part of the solution is change the service account from the central admin page & run an IIS reset

this is the main key and you will have to compulsorily do this to resolve the issue

hope it works for you

Every thing you can do to make WSS search work !!!

2009-05-14T04:20:00.002+05:30

If like me you are haunted by Event IDs 2424 and 2436 on your SharePoint server and you have no clue of what needs to be done join the club, WSS has least relation with the search configurations and if you get a search error you can do anything and everything mentioned in this article to get the error away ….

Taking reference from my earlier article WSS search does not work after service account password changes here are the additions

If this issue occurs when you have site running in the Host Header and the search stops working after the Infrastructure update is applied, apply the post infrastructure update or the Service pack 2, this is because the infrastructure update is know to break your AAM mappings check this: http://blogs.msdn.com/alimaz/archive/2008/07/27/known-issue-with-infrastructure-update-for-windows-sharepoint-services-3-0.aspx and http://support.microsoft.com/kb/951297
Use KB 934838 which can update your credentials to use the updates account
Try to make the content access account as the farm administrator
Add the service account to the following groups

Administrators
IIS_WPG
WSS_WPG
WSS_ADMIN_WPG

5. On database server, configure the account as:

"dbcreator" and "securityadmin" role of the database server
"dbowner" of all SharePoint databases including configuration database, content database and search database

6. The alternate Access mappings should have the default running with http://servername:portnumber and in IIS host header should be configured with http port number and second entry as with host header of your site and port 80

7. In web.config set the <identity impersonate = “true”/>, this should help

8. The timer service account must be same as the search services account in the services console and should have permissions in the task folder locate this on c:\windows\task now this is a system folder and will not let you assign permissions, so you can run the following command from start > run > cmd > type the following attrib –s <folder name> this will remove the system attributes from the folder, after your done with giving the permissions you can run attrib +s

9. On Site Actions > site settings > Search Visibility > index all aspx pages

10. Look at the kb http://support.microsoft.com/kb/952172/

11. go to start > admin tools > component services > component services > My computer > computer > DCOM config > give permissions to the IISadmin and SPSearch components

Go to properties > security tab > edit all the 3 frames and add the service account

12. Now run the command stsadm –o enumservices and note down the output, especially for WSS search

13. Now run the provision the search follow tech net http://technet.microsoft.com/en-us/library/cc262031.aspx first stop and then start, you will have to provide a new database

14. To check if the search works, run the command stsadm –o spsearch –action fullcrawlstart

10 Free SharePoint Themes full configuration for Dummies

2009-05-04T16:16:00.005+05:30

As we know that share point does provide you some set of themes to work with you can locate them in at your site, go to site actions > site settings > under the look and feel category hit the site themes to go there, if you are working with MOSS you have an option to apply the master pages to your site as well, master pages are predefined pages which gives your site a uniform look and feel,

The difference between Themes and master pages is that themes needs to be applied on a site level and in master page you can set up an option to inherit to the sub sites, but if you use the sushi 3.4 you can set themes on all you sub sites in one go.

Incase you are still wondering how do we go about these you can refer a superb article by Heather Solomon difference between master pages and Themes difference between master pages and Themes, and you will know which one to implement,

As mentioned in my earlier posts I did discover some hidden themes in SharePoint packed with the product but they were not released because of there non uniform CSS, now Microsoft has released free themes which will work with you MOSS site these are available as free download here, you can checkout the preview this looks super cool on site but the implementation is not that simple

Pre requisites:

You need Visual Studio 2008 installed on your machine

You need Visual Studio 2008 extensions for SharePoint – available here:

o V1.2 http://www.microsoft.com/downloads/details.aspx?familyid=7BF65B28-06E2-4E87-9BAD-086E32185E68&displaylang=en

· V1.3 CTP http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fb9d4b85-da2a-432e-91fb-d505199c49f6

Now after you are done with the pre-requisite you can install the new cool themes for SharePoint from here http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0a87658f-20b8-4dcc-ad7a-09ad22641f3a

and enjoy a new look to your portal site, I am in a process of implementing these but will surely comment about the look and feel as soon as I am done :)

Alright addition to my earlier post today on 5/5/2009 why? not because the SharePoint themes were tough but because I had jus too much work

Okies now everywhere we see that the ten themes are just given with the links to understand the complete configuration you must refer to my older post at SharePoint Hidden themes; here I talk about Editing the SPthemes.xml file

so if you go step by step

1. Download and install the ten themes for SharePoint

2. Install Visual studio 2008 on the server

3. Download visual studio extensions for SharePoint

4. Then locate the Ten themes folder

5. Select any theme folder eg SportingsiteTheme folder

6. double click on the folder go to > Sporting site theme > Template > themes > SPORTING

7. copy this folder and paste it into c:\program files\common files\Microsoft shared\web server extensions'\12\template\themes

8. Also copy sporting_preview.jpg to the c:\program files\common files\Microsoft shared\web server extensions'\12\template\images folder

9. Now Modify the SPthemes.xml (Take tips from SharePoint Hidden themes;) located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033

just add a chunk of code in between as:

“<Templates>
<TemplateID>sporting</TemplateID>
<DisplayName>sporting</DisplayName>
<Description>sporting</Description>
<Thumbnail>images/sporting_Preview.jpg</Thumbnail>
<Preview>images/sporting_Preview.jpg</Preview>
</Templates>”

this makes the theme available on site actions> site settings > site themes. so its easy to apply, save the file and close it.

10. now if you try applying this theme it will be applied to your site but will show something as this

11. Now comes the visual studio part, you have to go back to the place where you original Ten Themes for SharePoint are located and sportingsitetheme > double click and run the file SportingSiteTheme.sln, it will load and run the project in Visual studio 2008

12. Once that is done click on Debug button (green start button) the project will take its own sweet time to compile

then it gives you message as Activating feature sporting site template, and succeeded

13. you can check the featured being deployed at the Central admin > Operations tab > Solution Management > sportingtheme.wsp incase this is not deployed you can use the command prompt to do that, catch the links here http://technet.microsoft.com/en-us/library/cc263231.aspx

14. now try to refresh the site or apply the same thing… it works !!!!

Here’s the new look

My recommendation try the Construction site theme its awesome

WSS search does not work after service account password changes

2009-04-15T03:12:00.002+05:30

If you have a SharePoint 2003 version referred to as WSS, and you run into an scenario that search does not work reason being that the service account password expired on Active Directory.

First things first always remember to set the service account a condition to be on password never expires, Incase you miss it by mistake

Now as this happen you should

shoot for KB http://support.microsoft.com/kb/934838 which works most of the time

stop the Windows SharePoint search service from Central admin page > Operations tab > services on server and start it again proving the new username and password

you can try the same from command line, follow article on http://technet.microsoft.com/en-us/library/cc287997.aspx

The last step to try is rebuilding your configuration data base and providing the same service account

because earlier when password was changed WSS config database was not updated of the change and it did not recognize the account so no search results appeared

After you do the new config database you should run the stsadm –o spsearch –action fullcrawlstart

And this will not start immediately you need to give it maximum and hour and then check the performance

I am 100% sure this will work !!!!

Working with Sushi 3.4

2009-04-11T02:20:00.003+05:30

Sushi is good to eat and great to work with !!! yes that's true I am talking about the sushi tool available from Codeplex, just to be on record I love Codeplex!! and the tools they are neat and work absolutely gorgeous. ...

Alrighty back to sushi, you can have a look at this little piece at the link http://www.codeplex.com/sushi pretty much info there, but just to list

sushi gives you and option to

Get reports from the site
save your profile images
Perform an stsadm backup with a GUI option to provide the location
Perform an stsadm restore
Send a test email

It also lets you work with lists, like copying view, metadata, bulk list creation, bulk site and column creation

It also lets you apply themes to the site as well as sub sites in one go, now isn't that just awesome...

Sushi is a good took when working with a large creation and deployment on Sharepoint sites and servers good for the view feature.

STSADM by default in My Command prompt

2009-04-09T01:31:00.003+05:30

SharePoint has a lot of programs to be performed on the command prompt as in the GUI in fact after so much interaction with SharePoint product I believe that stsadm is more reliable and faster then the UI, so when ever you have to perform an action on the SharePoint site you open the command prompt and type the command that world knows about

c:\Program Files\common files\Microsoft shared\web server extensions\12\bin

and then you proceed with you list of stsadm commands, but is there an easier way to do it ????.

well of course there is we can add the stsadm path to the hive for command prompt so you can just hit command prompt and run the stsadm commands

>> Copy the path for 12\bin

>> On the SharePoint server(s), go to my computer > Properties and the Advanced Tab

>> Here hit on the button Environment Variables > here you see two frames user variables and system variables, go to system variables

>> Here go to the “PATH” variables and say Edit

>> Here paste the copied url which is c:\Program Files\common files\Microsoft shared\web server extensions\12\bin

>> Say OK and Apply and close

>> Now open command prompt and run stsadm –o help

>> you should be able to see a list of stsadm commands

>> Congrats you just made your life a little easier with SharePoint which is as unusual as pigs got wings ….

Traces of portal 2003 on my MOSS site

2009-04-07T19:10:00.002+05:30

I just ran into an issue yesterday where,

we have upgraded the environment from Portal 2003 to MOSS 2007 with Gradual upgrade everything is running just fine, but when we try to go into a sub site which has some lists inside it I try to browse through the lists and i find that the lists contain and interface of portal 2003

Just a little background here, the portal 2003 SharePoint site was heavily customized with banner and bread crumbs and quick launch bar, we took out all the customizations before we run the prescan which was successful. then we run the gradual upgrade and this bought the default pages of the site

The issue is I am running into is that the some document libraries still show the SPS2003 Interface. Initially you might think that this is a result of incorrect upgrade, you can try running the command

stsadm –o –upgrade –inplace –url <url of the site> –forceupgrade

If this does not help try resetting site to site definition from the top level site this works in 90% scenarios

I was able to get over the issue with creating a new view on my document libraries and which helped me get rid of the portal 2003 interface

That means when the upgrade was performed the Views did not get updated and sustained the old SPS 2003 look and feel so in short the default views got corrupt and so we have to work around it by creating a new view and replacing the default view.

Issue: Cannot spot My Site & My links on home page of Sharepoint website

2009-03-11T04:40:00.001+05:30

Issue: Cannot spot My Site & My links on home page of Sharepoint website

Before we proceed lets check if the SSP is created and its working good

Then check if there is a different application created for My site and My links and check the site collection created in the Central admin page, if there are collections present with /username.

Now start investigating the SSP, here in SSP you have some features to check the status of these two links

Look into Personalization service permissions > edited permissions for NTAuthority\AllAuthenticatedUsers > it should have permissions to create my site & personalize settings

Look into My site settings
Look into My site host permissions, you should be able see the authenticated users there
Check the personalization site permissions, but you will have to work with audience in this way
Also check is use personal permissions is enabled there

When you complete doing all this you have to start thinking on isolation of this issue, Isolation of the issue is very very important as when you troubleshoot as it gives you the right direction
Create a new web application ‘Test’ and check if you can spot the links there, if not there then you might have to check with a new SSP

If you can, either the web application is corrupt or there is a redirection setup on the Application Pool
The point is that if you have a redirection setup on the app pool level it prevents the My sites and My links from appearing on the application

Suppose your site url is http://hotmail and you set the redirection to http://hotmail.dsc.net so that whenever your user opens browser and types http://hotmail and gets redirect to http://hotmail.dsc.net , this keeps away the my sites & my links.

To workaround remove the redirection from Application Pool, and use it through the Alternate Access mappings on the Central Administration page

February Cumulative Update for Sharepoint Server

2009-03-05T23:56:00.003+05:30

February Cumulative Update

There are lots of known issue that are fixed [such as orphaned entries for site collection/subsites, SSP Index backup/restore issues]

Please take a look at the following articles and get to know the issues that we have encountered and the ones which are fixed in the update.

Knowledge base articles:WSS 961750 GlobalDescription of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): February 24, 2009http://support.microsoft.com/kb/961750

967703 Language specificDescription of the Windows SharePoint Services 3.0 hotfix package (Wssmui-en-us.msp): February 24, 2009http://support.microsoft.com/kb/967703

MOSS & Search Server 2008 961749 Global Description of the Office SharePoint Server 2007 hotfix package (Coreserver.msp): February 24, 2009http://support.microsoft.com/kb/961749

961754 Language specific Description of the Microsoft Office SharePoint Server 2007 hotfix package (Coreservermui.msp): February 24, 2009http://support.microsoft.com/kb/961754

Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): January 27, 2009http://support.microsoft.com/kb/963023/

Download locations:WSS 961750 Global http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961750&kbln=en-us

967703 Language specific http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=967703&kbln=en-us

MOSS & Search Server 2008 961749 Global http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961749&kbln=en-us

961754 Language specific http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961754&kbln=en-us

A little update on this …..

You cannot install the February Cumulative update on you server unless you have the December CU installed the dilemma is that the Feb CU unlike Dec CU does not contain all the previous updates, or a better option is to wait for the “Uber” package which will contain all the previous updates, this package should be out in few weeks from now but no ETA defined .

SQL databases created by SharePoint

2009-02-26T06:24:00.002+05:30

When we install SharePoint we have the databases created in SQL, SQL is the backbone of the SharePoint server, whenever you upload any data or any document to the site its actually uploaded to the SQL database associated with that application, the documents gets stored in SQL and they have only the reference link

Let’s look at the databases created in SQL when you install SharePoint and configure stuff like search My Sites and SSP, also when you make your very first application
Installing SharePoint on your server

When you install SharePoint on your farm, irrespective of the type of installation you choose that’s Basic or Advanced (I mean using SSEE or Full SQL version) you get two databases created on your specified SQL instance they are:

Sharepoint_Config : This is the configuration Database for the site this database holds information on farm configuration, patches and updates applied to the server, versions of sites and databases, users, custom templates, Features, etc to be specific it contains 24 tables and each tables has its own significance

1> dbo.antivirusvendors – contains 3 columns
Vendor Id
Vendor Product
Vendor Version
As you would guess it will be talking about the Antivirus properties applied on the server obviously this table has to be present on the Config database as Antivirus is a portal level application and not an application level

2> dbo.Binaries - Contains 2 columns
Object ID
File Image
I am not really sure what this table is doing here its maybe used for some customization references

1> dbo.classes- contains 3 columns
Id –
BaseClassId-
FullName
It contains the classes used to create the SharePoint dll
So the next time you face an error of a particular class not working you can check the entry here
2> dbo.customtemplates – contains 6 columns
ID
Title
Description
LCID
Content
Template ID
This table would contain the information of the custom templates applied to the site, when you run the stsadm –o addtemplate command the attributes are added to the site as well as the dbo.customtemplates
just comparing these columns with the attributes of stsadm –o addtemplate, they are filename, title, description,
so we can troubleshoot issues with the custom templates not getting updated or the custom templates not being applied to the site from these

3> dbo.databases – contains 15 columns
DatabaseID
VirtualserverID
Name
UserID
Password
SiteCount
SiteCountWarning
SiteCountLimit
DatabaseServiceID
LastModified
LastModifiedUser
LastModifiedServer
Status
Version
Properties
As seen its used to get all the details of the databases used in the SharePoint site, It also contains the warnings and limitations of the site, status their version and properties

4> dbo.dependencies – contains 2 columns
ObjectID
DependentID
Generally a list of object ID and Dependent ID mapped together

5> dbo.EmailenabledLists- contains 5 columns
Alias
SiteID
WebID
ListID
Deleted
Whenever you create an email enabled document library you can see the attributes being listed here, we configure this library on a particular site collection and have to provide ‘Alias’ of the library while creating the library, the ‘SiteId’ of the site holinding the email enabled list, Web ID of that site, ListID of the List, and status as deleted or not

6> dbo.globals- Contains 14 columns
GlobalID
SchemaVersion
UseHostHeader
UseNTAuthfordatabase
smtpserviceID
Mailcodepage
FromAddress
Replytoaddress
LastModified
LastModifiedUser
LastModifiedServer
Status
Version
Properties
These all are the global settings for the site which can be done via several links on the central administration page like Web application general settings, AAM etc

7> dbo.InstalledWebpartPackages- contains 5 columns
WPPID
url
IISInstance
ServerID
Globalinstall
It talks about the third party web parts added to the site or the custom webpart solution deployed to the server, can be a good medium to troubleshoot the issues with Out of the Box web part solutions

8> dbo.LastUpdate – contains 2 columns
Value
Version
This is an interesting thingy to look at cause it contains the information of the last update applied to the server, so In case you feel that something happened to your server because of the automatic update applied or you want to check on the last update you can check this table

9> dbo.Objects- contains 7 columns
ID
ClassID
ParentIDName
Status
Version
Properties
Contains information of the objects

10> dbo.pendingDistributionList- contains 5 columns
SiteID
WebID
GroupName
ModifiedBY
Version
Contains list of pending DL’s and some information

11> dbo.Servers- contains 9 columns
ServerID
Name
Address
LastModified
LastModifiedUser
LastModifiedServer
Status
Contains information of the servers in the farm and there details

12> dbo.services- contains 10 columns
ServiceId
ClassId
ServerID
Instance
LastModified
LastModifiedUser
LastModifiedServer
Status
Version
Properties
Contains information of the services

13> dbo.SiteCounts- contains 2 columns
DatabaseID
NumSites
It contains the count of sites in each Database

14> dbo.SiteMap- contains 9 columns
ID
ApplicationID
DatabaseID
Path
Pairing
Status
Version
Redirecturl
HostheaderIssiteName
This also gives information about the sites

15> dbo.sites- contains 9 columns
SiteId
DatabaseID
URLpath
LastModified
LastModifiedUser
LastModifiedServer
Status
Version
Properties
This one is supposed to contain the number of sites and its attributes with respect to each application

16> dbo.Timerlocks- contains 9 columns
JobID
LockedByServerName
LockedTime
This contains all the jobs Locked by the timer job

17> dbo.TImerRunningJobs - contains 10 columns
ServiceID
VirtualServerID
JobID
JobTitle
ServerName
Status
StartTime
CurrentStatus
TargetCount
CurrentTargetPageDone
Shows time and status of all the timer jobs

18> dboTimerTargetInstances- contains 2 columns
JobID
TargetInstanceID
Will contain Timer Target Instances and there list with the Job ID

19> dbo.tombstones- - contains 2 columns
ID
Version

20> dbo.Versions - contains 10 columns
VersionID
Version
ID
Username
Timestamp
Finaltimestamp
Mode
ModeStack
Updates
Notes
Contains previous versions of the site and the version History, also account that changed it the newer version (by applying updates)

21> dbo.Virtualservers- contains 12 columns
Virtualserver ID
Name
smtpserviceID
Mailcodepage
Fromaddress
Replytoaddress
LastModified
LastModifiedUser
LastModifiedServer
Status
Version
Properties
Shows the entries and attributes of virtual servers added to the farm

22> dbo.webpartpackages- contains 3 columns
WPPID
Title
Content
Similar to dbo.InstalledWebpartPackages contains information of the OOB or custom web part packages

Admin_Content : This database is created when you complete running the PS Config wizard for SharePoint, this wizard launches the Central administration application, actually in background the wizard creates an application for the Central admin page

The central admin database is names as admin_content database, this is by default and you cannot rename or edit it.

It is just like any other normal content database, but it has the Central Admin site, which is the most important site.

You receive “cannot complete this action” error message whenever you try to do anything on your site

2009-02-10T06:30:00.001+05:30

This situation basically occurs when you try to backup restore or migrate the sites between two server farms, usually the biggest problem you may face while migration site between two farms is that the user SID gets Screwed for good and then the hell breaks loose when you cannot get users log in to the site the permissions are messed up,

Check these few things before your land up to a conclusion.

Symptoms Faced:
Cannot backup restore or Delete a site collection, you face “Cannot complete this action” error message from Both GUI and Command prompt (I mean stsadm, of course)

This error message sounds a permission problem to you so there you go … start checking these

Run the command stsadm -o migrateuser with the problem account, if its successful you are done otherwise try

stsadm -o updatefarmcredentials

Remember you will have to hit IIS reset after this

Check if the account is available on WSS_WPG; WSS_ADMIN_WPG; IIS_ADMIN_WPG

If the migrate user command fails because you use the same accounts both times then create a temporary account that you create in AD and run the command as

Stsadm –o migrateuser –oldlogin domain\problem account –new login domain\temporary account –ignoresidhistory
Then run
Stsadm –o migrateuser –oldlogin domain\ temporary account –new login domain\ problem account –ignoresidhistory

Make some other account as a site collection administrator, remove the problem account from site collection admin and re-add it
From the link http://susandoreydesigns.com/software/AboutSharePoint.pdf

When permissions are established by NT/XP network ID, problems can arise when an ID is stopped and restarted. When a network user ID is (re)established and there are pre-existing permissions for that ID in a SharePoint site by virtue of membership in site groups by user name (as opposed to domain group membership) and/or as the owner of a site, the person will not be able to access the site. Instead they will get an error message like “Cannot complete this action. Please try again”.
In this case the ID must be removed from the site. This may be easier said than done.

􀂃 Change the site owner to somebody else. This is done by the server administrator on page “siteusrs.aspx.”

􀂃 Remove the ID as a site user by removing it from membership in site groups, including any custom list permissions.

This is complicated because SharePoint does not use the text of the user’s ID but a SID, which is different each time the network ID is re-established.

· Finally when you are convinced that this is not a permission problem run the hot fix 956994, which can be obtained from the Support professional also you can try running a very generic KB 936867, which is included in Service pack 1 for MOSS
This fixes the issue for the site with broken permissions problems

Playing with the Sample master pages for Sharepoint

2009-01-10T03:57:00.000+05:30

I have been concentrating on the master pages and the look and the feel for quite some time no, let me tell you creating a custom theme or a master page is not easy work at all, I am a BIGGG fan of heather Solomon, I am referring to the link http://www.heathersolomon.com/content/sp07cssreference.htm#LeftNav for the CSS reference and believe me even TechNet cannot provide such details.
That was when I was trying to create a custom theme, i got success to some point but some cases kept me busy, then my VHD crashed, so every thing is gone :( but as said 'A busy bee has no time for sorrow' I will be re doing it again ...

How as I told you that creating a custom site theme and Master page is a Verrrrry big task (believe me). so let checkout the available resources. I came across the a link that contains some sample master pages (how cool is that) so lets explore. (like every one I like things that I get for free ;) )

so the link to download free cool master pages to your site is http://www.microsoft.com/downloads/details.aspx?familyid=7C05CA44-869A-463B-84D7-57B053711A96&displaylang=en

Here it gives you a MasterPage.exe file, Save that file on your desktop, Run that .exe extension and save it to a folder, this contains 4 folders that means 4 master pages those are
1. Block
2. Clarity
3. Horizon
4. Reverse
Each type of the master page is made in different colors like blue, purple, red, green, orange

the Big question is how do you make this work which is actually quite simple to do the download has a very easy to understand and read Readme.txt with it.

· Create a Sharepoint site collection
· Open this Sharepoint site from the Sharepoint Designer, for that Open Sharepoint Designer in the File menu, click Open Site. In the Open Site dialog box, type the URL of the site that you want to open in the Site name box, and then click Open.
· Import the master page files into your site.
On the File menu, select Import > File...In the Import dialog box, select Add Folder... Browse to location of the extracted master page files, and then browse to a specific master page, lets suppose you select 'Clarity' Select the "_catalogs" folder and click open. Repeat steps for the "images" folder and the "styles" folder. Click ok to finish importing the files.
That means now you have attached the files necessary for the master page to the Sharepoint site.

· Select the folder _catalogs under the master page menu, open the folder master page now you will see a new list of master pages
1. Clarity_lay1 blue.master
2. Clarity_lay1 green.master
3. Clarity_lay1 orange.master
4. Clarity_lay1 purple.master
5. Clarity_lay1 red.master

so you can select any one of them and set it as Default masterpage from the designer

· Then log in to the site and just go to site actions > site settings > Master pages under Look and feel category and hit the Drop down button select from the master pages and there you go

Some things that I noticed while working with the master pages

· I tried using a Team site template but it just screwed up my master page so use collaboration site template if you are using MOSS
· When you set a master page as default to your site you cannot delete that master page from your site template gallery if you try to do taht it gives you an error this is a known issue with the master pages

Sharepoint Hidden themes.

2008-12-30T02:20:00.000+05:30

Sharepoint Hidden themes.

I am from the Admin background of Sharepoint but I will always love to design my Sharepoint site and there is a big world out there, I mean just open up your browser go to Google or Live and just type "customizing Sharepoint sites". Bang !!! there you go. and there are millions of articles, blogs, TechNet , KB's, Designer videos and lot of them. but as you I am very confused where to start with. I got a link where it talks about creating your own theme which will be available through Site actions > Site settings > Site theme.
how cool is that, something that's your theme your choice of color and images and available so easily that you can apply it to any site you want, well I will talk about this on my next post because that's still in the pipeline.
ok now, while trying to create my own theme I noticed something for that you will first have to go through the article http://sharepoint.microsoft.com/blogs/GetThePoint/Lists/Posts/Post.aspx?ID=122 which talks about making your own custom theme, so all the themes are located in the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\THEMES and the list is available at the Sharepoint site
so whenever you have to change the theme of your Sharepoint site simply log into the Sharepoint site go to Site actions > Site settings > Site theme select a theme and change it
let us list the available themes (shown on the page)
1. Belltown
2. Breeze
3. Cardinal
4. Citrus
5. Classic
6. Default theme
7. Granite
8. Jet
9. Lacquer
10. Lichen
11. Obsidian
12. Petal
13. Plastic
14. Reflector
15. Simple
16. Verdant
17. Vintage
18. Wheat

that means total 18 themes that you can play with but if you check on the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\THEMES. there are some additional folders that you can spot such as
1. Centrlad
2. Club
3. Fresh
4. Sharedservice
5. Spsky

that means we can actually play with 23 themes but these 5 are hidden and hence cannot be applied to the site from GUI, however if you make a little change in a file you can get these themes as well
ok now, follow the steps to get the hidden themes

Go to the XML file located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033
· Locate SPTHEMES.XML
· Open it in a notepad
· add the following code

( here we are trying to apply the Club theme)

Now open the Sharepoint site and go to site actions > site settings > site theme, amongst other entries you can spot Club as a theme, click on that it will show a broken image as preview; we will fix that in a minute
click apply Tadaaaa.....

you can see a new theme applied to your site, i would suggest you to try the Spsky theme as its beautiful with color combination of sea blue and green colors

Now fixing the broken image preview, as soon as you apply the theme take a screenshot of that theme and edit it in paint making the size smaller you can add the image to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES and name it Club.bmp or whatever theme you choose
and you are done.
now you can play with the themes that are new and fresh :)

Installing Sharepoint on Server 2008

2008-11-18T03:35:00.000+05:30

So all of us waited to see and know how working with Windows Server 2008 would be, So did I, I wanted to install Sharepoint 2007 (MOSS) on Windows Server 2008, and use the client as vista, Thought that the task might be quite simple, to its time to get working !!!

> My first Step : Installing Windows Server 2008

To be really honest I used a vhd that had the pre-installed software, but I would really like to explore that too.

the first thing I notice that Server 2008 has the interface totally different to 2003, it had the vista look which was quite pleasing to the eye also that there were different names for the similar things like suppose you have to configure the TCP/IP settings, I had to wander around the whole server to get it right. you can locate it at Control panel > Network and Internet > Network connections and configure the IP

> My second Step : Installing IIS 7.0

To install Share point my first step was to install IIS (which was a very, very painful task, trust me) well it is located at the Administrative Tools > Server Manger > Then you choose the IIS service and proceed with the installation. This was simple!!!

> My third Step : Installing .net framework 3.0

In server 2003 days you had to download the software from the site, here .net framework 3.0 is bundled with the server 2008, you will have to pull it from the Administrative Tools > Server manager > Features > add features > Check on .net framework 3.0 services, and you're done.
Positive point as the software is included with the OS it works for you even if you don't have an internet connection

> Fourth Step : Installing MOSS

Ok now its SHOWTIME, one thing that you must note before you install MOSS RTM on Server 2008 is that Server does not proceed with the installation unless you have the slipstream version of Sharepoint (Incase you are wondering what that is all about, it means MOSS + Service pack 1), to make your RTM CD a slipstream simply download the SP1 for MOSS setup file and place it on you upgrade folder (for MOSS), then proceed,

For this you will have to copy the entire CD on your Local disk, then add the KB on the upgrade Folder then hit the setup file. Here I am performing the Basic install of the product that it with SSEE.

One little thing that frustrated me was that after placing the WSS SP1 and MOSS SP1 on the upgrade folder the installation did not proceed to resolve this you will have to extract the KB articles on the upgrade folder via command line which will be something like 'c:\wssv3sp1-kb936988-x86-fullfile-en-us.exe /extract:c:\wsssp1'
After the struggle I was finally able to install MOSS on Server 2008, so In the end success matters, I would love to experiment more on the new IIS version "version 7.0", and Sharepoint site, keep an eye on my future posts.

Installation of O.S. Windows Server 2003 R2:-

2008-11-13T22:23:00.000+05:30

Installation Process Types:-
1. BASIC
2. RIS (Remote Installation Services)
3. NETWORK

BASIC:-
Normal Installation Type, through Product Installation CD.

The Normal install consists of two types Attended and Unattended install.

Attended install is where you sit in front of the machines and install the whole operating system , this process may not be feasible if you are working with more than one machine, suppose you want to install OS on 15 machines you will be using the method called Unattended install where you will be creating an answer file, for the setup

• The answer file will be provided by the floppy drive, so the OS Compact Disk works on the Data provided by it

• To create answer file copy the file at drive \setup\support\tools\Deploy.cab\setup.manager.exe

• Copy it to another location on network then run the wizard and add the information like the CD key, regional settings, machine names to be given, organization name etc. then save it, the file will be saved anywhere like C:\setup\unattended.

• This will create 3 files
Unattended.bat
Unattended.txt
Unattended.udc

• Now to make sure the process runs successfully you will have to perform some changes as
Rename Unattended.bat to “winnt.bat”
Rename Unattended.txt to “winnt.sif”

• Now this will only work if you have the Boot priorities set to
I – CD ROM
II – Floppy Drive
III – HDD

RIS (Remote Installation Services)

RIS supports two types of operating system images:
 CD-based images (images created by using RISetup)
 Remote Installation Preparation (RIPrep) images.

The CD-based option is similar to setting up a server operating system directly from the Windows Server 2003 product CD, except that the source files reside on a RIS server.
You can create a RIPrep image from a server that is running Windows Server 2003 with SP2, and you can then deploy this image to other similar servers that are connected to the network.

Creating a CD-based (RIS setup) image to add to a RIS server
After you install RIS, perform the following steps to create the image and then add the image to your RIS server.

To create an image of Windows Server 2003 with SP2 and add it to your RIS server
1. Create an integrated version of the operating system with SP2.
2. To create an image, click Start, click Run, and then type: risetup.exe /add
3. The Remote Installation Services Setup Wizard appears. Follow the instructions in the wizard. When the Installation Source Files Location page prompts you for the image source, enter the path to the shared folder that contains the integrated version that you created in Step 1.
4. A box appears showing the progress of the installation. After the RISetup image is complete, you can install the image on each server as described in Remote Installation Services on the Microsoft TechCenter Web site.

Creating a Remote Installation Preparation (RIPrep) image to deploy to other servers

If you want to add additional programs or settings to your integrated installation image, you must have a CD–based image of Windows Server 2003 with SP2 on your RIS server. Note that you cannot use the /integrate option to integrate SP2 directly into an existing CD-based image or a RIPrep image.

To update existing RIPrep images
1. Use RIS to install the RISetup image on your computer.
2. Add the additional programs and settings that you want to include in the image.
3. Run RIPrep to create an image on the RIS server. For instructions on how to run RIPrep on RIS servers running Windows Server 2003, see:
• Remote Installation Services (http://go.microsoft.com/fwlink/?LinkId=36940 )

• Automating and Customizing Installations (http://go.microsoft.com/fwlink/?LinkId=44324 )

4. You can now deploy your RIPrep image to other servers.

NETWORK:-

Installing SP2 using source files that are located on a network share
To install SP2 from the network, first extract the installation files to a shared distribution folder. Then install SP2 on each computer using these files.
To install the service pack using a network share

1 Connect to the network or computer where you want to create the distribution folder.

2 In the shared folder, create a distribution folder.
For example, to create a distribution folder named WS2003SP2, type mkdir Drive:\WS2003SP2 at the command prompt (Drive: represents the drive where you want to store the distribution folder).

3 To extract the files to the distribution folder, type the following at the command prompt, where Path is the location of the distribution folder:
WindowsServer2003-KB914961-SP2-XXX-LLL.exe /X:Path

4 For each computer that you plan to update, back up the files and close programs before you continue (unless you plan to force programs to close during the installation).

5 To install the service pack from the shared distribution folder, run Update.exe. For example, to install from a distribution folder named WS2003SP2, type the following at the command prompt using the desired command-line options :
Drive:\WS2003SP2\i386\Update\Update.exe

6 Follow the instructions in the Setup Wizard.

7 After Update.exe has completed, restart the computer to complete the installation. SP2 will not be fully installed until you restart your computer.

8 If you disabled your antivirus software, enable it after you restart the computer.

THE NETWORKING CLASS

2008-11-13T06:09:00.000+05:30

1. TCP / IP is a suit of the protocols, TCP works on port 6

2. You can communicate to another machine by PING-ing to it using its IP address

3. The full form of PING is Packet Inter Net Groper,
The PING command can be defined as a computer network tool used to test whether a particular host is reachable across an IP network; it is also used to self test the network interface card of the computer, or as a speed test.

4. You can also use the command called Address Resolution Protocol to determine the who and what of your machine, i.e you can get a list of all the machines that spoke to your machine by typing the command arp –a
Address Resolution Protocol (ARP) is the method for finding a host's hardware address when only its Network Layer address is known.
As soon as you fire this command it gets a list of all the machines talking to your machines
Arp works in two formats arp request and arp acknowledgement. Both request and acknowledgement makes a reply

5. IP addresses : An Internet Protocol (IP) address is a numerical identification (logical address) that is assigned to devices participating in a computer network

There are 5 classes of this address

CLASS A 1-126
CLASS B 128-191
CLASS C 192-223
CLASS D 229-239
CLASS E 240-256

127 is reserved for Loop back, checks the position of NIC and NOS – Network Operating System

6. Subnet mask- it is actually the number of bit that can be used by the machine,

For example: 192.168.10.1/ 24
8.8.8.0 Bits
Equals 255x255x255x0

172.16.0.0
8.8.0.0
Equals 255x255x0x0 = 165025 bits

255 x 255 x 255 = 16521375
7. Private IP : The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets (local networks):

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

These IP’s must not be used in Internet
In a IP address first 24 Bits is the Company ID and last 25 bits is Unique ID

8. Difference Between HUB and Switches :

HUB :
Hub is a common connecting device that connects the machines in network or LAN. Hub has a tendency to broadcast the data every time so if it needs to send data to Mac1 to will broadcast to all the machines in network, Hackers can make god use of it so its Insecure and because of the broadcasting technique its slower..

SWITCHES: :

This is again a device that connects Computer devices however it broadcasts the information only once, and then it creates the IP – MAC table and remembers the IP address of the machines to deliver the data correctly next time, also its quite evident that this method is more secure & Faster

9. LAN :

Local area network (LAN) supplies networking capability to a group of computers in close proximity to each other such as in an office building, a school, or a home. A LAN is useful for sharing resources like files, printers, games or other applications. A LAN in turn often connects to other LANs, and to the Internet or other WAN.

LAN works on two things basically, Physical MAC and Logical IP

10. Network Topology :

Four types of network topology
a. Bus : Linear setup
b. Star : One central switch or Hub connection to computers
c. Ring : each packet is send round ring until it reaches destination
d. Mesh : All the machines are connected to one another
I got the best explanation on the site http://www.firewall.cx/topologies.php

11. Difference Between FAT and NTFS
Refer to my post on link http://alliknw.blogspot.com/2008/05/diffrence-between-ntfs-and-fat-file.html

12. Operating system and versions :
NT 4.0 works on FAT 16
NT 5.2 is renamed as server 2003

• Windows server Web edition Does not support ADS
• Active Directory cannot be installed on FAT

Search server 2008 Express edition gives Error message as “Your License for Microsoft search server has expired”

2008-11-06T02:07:00.000+05:30

Troubleshooting Search server 2008:

Search server 2008 Express edition gives Error message as “Your License for Microsoft search server has expired”

Search server 2008 can also be used at your Organization even if you are not using Sharepoint at all, in this scenario you can crawl your File share, Search server 2008 indexes the files then you can use the search center to insert the key words.
Now if you are using the Search server 2008 express edition and you face a problem while search as an error message as “Your License for Microsoft search server has expired”

You will have to check the following
 Check if the Help search that us Windows Sharepoint Help search service and Office Sharepoint search is running with same account
 Check the content access account
 Check if the help search is working
 Incase its not or the accounts configured for both the services is different Stop and start the services using Services on server link under operations tab
 Then you are sure that the new databases are at work
 Then you will have to migrate to Add remove programs and locate the Search server Express and run a repair
 Then reboot the machine
 Then run the PS config wizard again
 Let it finish
 Launch the Search dashboard
 The search will not show any license errors now. 

Excel web access web part gives error message as “Access Denied”

2008-10-25T02:57:00.000+05:30

Excel web access web part gives error message as “Access Denied”

Now suppose you wish to look at your workbook in sharepoint site you will have to take care of some things, first and the foremost is that your Excel calculation services needs to be turned on,
>>Then you need to make sure that the excel file you save is in xlsx format as the excel calculation services is not compatible with xls files.
>> Then make sure the location which can be UNC path or a sharepoint site is added to the trusted file location in SSP
>> Also choose Trusted children and Trusted data connection in Libraries and Embedded
>> Enabled user defined functionalities allowed

Then you add the Excel web Access web part to the site. Try adding the path in the configurable section, try accessing the page if you still get Access Denied Error message then maybe the culprit is your authentication provider which might be Kerberos, so you will have to run these 3 commands to make sure it is activated

stsadm -o set-ecssecurity -accessmodel delegation -ssp SharedServices1 (here escsecurity means excel calculation security)

stsadm -o setsharedwebserviceauthn -negotiate

stsadm -o execadmsvcjobs

Ran an IIS Reset

Then try accessing the webpart the workbook will render just fine.

List of all stsadm commands with attributes

2008-10-16T04:44:00.001+05:30

here is a list of all possible stsadm commands used in sharepoint site, this list was passed to me by a friend, thanks amzi
====================================================================

1. stsadm -o activatefeature {-filename -name -id } [-url ] [-force]
2. stsadm -o activateformtemplate -url [-formid -filename ]
3. stsadm -o addalternatedomain -url -incomingurl -urlzone -resourcename
4. stsadm -o addcontentdb -url -databasename [-databaseserver ] [-databaseuser ] [-databasepassword ] [-sitewarning ] [-sitemax ]
5. stsadm -o adddataconnectionfile -filename [-webaccessible ] [-overwrite ] [-category ]
6. stsadm -o add-ecsfiletrustedlocation -Ssp -Location -LocationType SharePointUncHttp -IncludeChildren TrueFalse [-SessionTimeout ] [-ShortSessionTimeout ] [-MaxRequestDuration ] [-MaxWorkbookSize ] [-MaxChartSize ] [-VolatileFunctionCacheLifetime ] [-DefaultWorkbookCalcMode FileManualAutoAutoDataTables] [-AllowExternalData NoneDclDclAndEmbedded] [-WarnOnDataRefresh TrueFalse] [-StopOpenOnRefreshFailure TrueFalse] [-PeriodicCacheLifetime ] [-ManualCacheLifetime ] [-MaxConcurrentRequestsPerSession ] [-AllowUdfs TrueFalse] [-Description ]
7. stsadm -o add-ecssafedataprovider -Ssp -ID -Type OledbOdbcOdbcDsn [-Description ]
8. stsadm -o add-ecstrusteddataconnectionlibrary -Ssp -Location [-Description ]
9. stsadm -o add-ecsuserdefinedfunction -Ssp -Assembly (strong) -AssemblyLocation GACFile [-Enable TrueFalse] [-Description ]
10. stsadm -o addexemptuseragent -name
11. stsadm -o addpath -url -type
12. stsadm -o addpermissionpolicy -url -userlogin -permissionlevel [-zone ] [-username ]
13. stsadm -o addsolution -filename [-lcid ]
14. stsadm -o addtemplate -filename

Nidhi's Blog

A Site owner of a Sub site cannot save any list as Template gets Access Denied.

Explorer view gives "Internet Explorer Cannot dispal this webpage" on Server 2008

Search does not work for me since I splitted the indexer and the query server

"The path for the index location is not valid"

I cannot open my sharepoint site on server, but works on clients

Setting full anonymous access for a document library

SPD workflow Failed on start (retrying)

Every thing you can do to make WSS search work !!!

10 Free SharePoint Themes full configuration for Dummies

WSS search does not work after service account password changes

Working with Sushi 3.4

STSADM by default in My Command prompt

Traces of portal 2003 on my MOSS site

Issue: Cannot spot My Site & My links on home page of Sharepoint website

February Cumulative Update for Sharepoint Server

SQL databases created by SharePoint

You receive “cannot complete this action” error message whenever you try to do anything on your site

Playing with the Sample master pages for Sharepoint

Sharepoint Hidden themes.

Installing Sharepoint on Server 2008

Installation of O.S. Windows Server 2003 R2:-

THE NETWORKING CLASS

Search server 2008 Express edition gives Error message as “Your License for Microsoft search server has expired”

Excel web access web part gives error message as “Access Denied”

List of all stsadm commands with attributes

Search service stuck at stopping or starting

Infrastructure Update for MOSS

Configuring Search Server 2008

Search Server 2008

Branding sharepoint site III

Branding sharepoint site Part II

Branding the sharepoint site Part I

Central Administration Backup

Restoring Single Site in Sharepoint

Restoring single Item in Sharepoint

Installing Exchange Server 2003

Installing Types of Windows Server 2003

Diffrence Between Windows Server 2000 and Windows 2003 server with advantages

Backup Windows 2003 Server

Global Address List in Exchange Server 2003

Groups In Active Directory

Clustering

Diffrence between NTFS and FAT file system

Internet Information Services (details)

WMSDE and SSEE

As we Start .........................