Thursday, December 18, 2008

Upload Mulitple Documents - .zip files not visible

Environment :- Only Vista Machines.

Note :- Before making any registry changes, take Reg back up

Resolution :- Delete the follow registry keys and reboot is a MUST
HKEY_CLASSES_ROOT\CLSID\{E88DCCE0-B7B3-11D1-A9F0-00AA0060FA31}
HKEY_CLASSES_ROOT\CLSID\{0CD7A5C0-9F37-11CE-AE65-08002B2E1262}

Thursday, December 11, 2008

Files opens as Read Only after Check-out

Note:- Please take precautionary steps before applying the below steps. Backup your registry.

Issue:- Files will open as Read-Only after checking Out a document in SharePoint and trying to Edit it.

Environment:- XP + Office 2003 or Vista + Office 2007

Follow the below steps to resolve the issue.
---------------------------------------------------
1.) Search for oledb32.dll on the workstation and make sure it exists in this location. The default location is c:\program files\common files\system\ole db\oledb32.dll

2) Copy and paste the information below to Notepad and save as a .reg file. This will correct the entries in the Registry that are probably missing.

===========================================================
REGEDIT4
[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}]@="Microsoft OLE DB Root Binder for Internet Publishing"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\InprocServer32]@="C:\\Program Files\\Common Files\\system\\ole db\\oledb32.dll""ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\OLE DB Binder]@="Microsoft OLE DB Root Binder"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\ProgID]@="MSDAURL.Binder.1"

[HKEY_CLASSES_ROOT\CLSID\{FF151822-B0BF-11D1-A80D-000000000000}\VersionIndependentProgID]@="MSDAURL.Binder"

[HKEY_CLASSES_ROOT\MSDAURL.Binder.1]@="Microsoft OLE DB Root Binder for Internet Publishing"

[HKEY_CLASSES_ROOT\MSDAURL.Binder.1\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"

[HKEY_CLASSES_ROOT\MSDAURL.Binder]@="Microsoft OLE DB Root Binder for Internet Publishing"

[HKEY_CLASSES_ROOT\MSDAURL.Binder\CLSID]@="{FF151822-B0BF-11D1-A80D-000000000000}"

[HKEY_CLASSES_ROOT\MSDAURL.Binder\CurVer]@="MSDAURL.Binder.1"

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

3) From Start->Run, type Regsvr32.exe "[Drive]:\Program Files\Common Files\System\OLE DB\MSDAIPP.DLL"

4) Test and see if the issue is resolved.

Wednesday, December 3, 2008

Windows SharePoint Services Search (SPSearch) Errors File Not Found / 'start' action failed

Disclaimer: Take all possible backups, Since you have decided to troubleshoot on your own we hold no responsibility if anything goes wrong.

Note: After every troubleshooting step run following command
stsadm -o spsearch -action fullcrawlstart
& monitor Eventviewer>Application log for Success or Failures related to Windows SharePoint Services Search Service

On Failures try next step.

1. Open a Command prompt
Browse to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN

stsadm -o provisionservice -action stop -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"stsadm -o provisionservice -action start -servicetype "Microsoft.SharePoint.Search.Administration.SPSearchService, Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" -servicename "SPSearch"

stsadm -o spsearch -action stop

From SQL Server Management Studio backup & remove Old WSS_Search databases

stsadm -o spsearch -action start -farmserviceaccount [Domain\user]-farmservicepassword [Password] -databaseserver [SQL Server\Instance] -databasename [New WSS_Search DatabaseName]
Note: Replace above parameters with proper values

2. Run following from command prompt Before Reboot
net stop sptimerv3
net stop spsearch
sc config sptimerv3 start= disabled
sc config spsearch start= disabled

Run following from command prompt After Reboot
sc config spsearch start= demand
sc config sptimerv3 start= auto
net start sptimerv3
net start spsearch

3. From Windows Explorer go to backup cache.ini file from following location
C:\Documents and Settings\All Users\Application Data\ Microsoft\ SharePoint\ Config\

Change the contents of cache.ini to 1

From command promptnet stop spsearch net start spsearchstsadm -o execadmsvcjobs

4. psconfig -cmd secureresources
attrib -s %windir%\tasks.

Go to Properties of windows\tasks folder and add wss_wpg and wss_admin_wpg groups and give the full control permissions.

5. Repair MOSS from Add/Remove programs
Reboot server
Run PSCONFIG without changing any settings

NOTE: Do not perform following step if you want to use Network Service as SharePoint Service Account on SingleServer Installation with SQL Internal Engine

6. Central Admin>Operations>Servers in Farm
Note down the Configuration Database name

Run PSCONFIG Disconnect from Configuration Database

Run PSCONFIG Reconnect to same Configuration Database disconnected above.

Friday, October 24, 2008

Workflow "Error" System Account An error has occurred after workflow completed MOSS 2007

Problem: If you have a "built in" or custom approval workflow setup for your document library. The workflow runs correctly, however when sometimes you look at the workflow status, you may receive an error after the task has been approved and completed such as, Event Type: Error User ID: System Account Description: An error has occurred in [name of workflow].
Resolution: When you define your workflow, there is a section "Post-completion Workflow Activities", where you can check "Update the approval status (use this workflow to control content approval)". If you check this option, and you do NOT have content approval enabled on the library level, you get the system account error message. If you do not check it, everything works fine.
Reason for occurrences: The account listed in the "User ID" column does not have permission to "something" that is being requested in the workflow code. Workflow usually running as the "system account" within SharePoint and should have access to all the objects within SharePoint. However, the system account may not have access to some resources that are outside of SharePoint and needed by the workflow code. Accessing outside resources is usually done via the .NET worker process account (e.g. NETWORK SERVICE).

Tuesday, October 14, 2008

Move WSS3.0 databases from one SQL Server to another?

How to move WSS3.0 databases from one SQL Server to another?

Configuration:
WSS3.0 Server
Source SQL Server: Win 2003 Server SP2 SQL Server 2000 + SP4
Destination SQL Server: Win 2003 Server SP2 SQL Server 2000 + SP4

STEP1: BACKUP:

1] On Source SQL Server: Backup SharePoint Content databases.
Open SQL Server Enterprise manger
Right Click a database (For ex: WSS_Content)>All Tasks>Backup Database>Database Complete>Backup to disk>Add>Filename>Provide a path & filename>Ok>Ok
Repeat above procedure for all SharePoint databases however we will not restore all of them.
(Do not restore COnfiguraion & WSS_AdminContent... database on new SQL Server)
How to find name of Content databases:
Central Admin>Application Management>Content databases>Select web application from Right Hand Side Top drop down list
Database name will be displayed

-------------

2] On SharePoint Server: Take screenshots of all configured setting on Central administration page
For example:
Central Admin>Operations>Global Configuration>Alternate access mappings
Central Admin>Operations>Outgoing email settings
Central admin>Application management>Define managed paths
etc.

--------------

STEP 2: PREPARE DESTINATION SQL SERVER
We must install either same or Better version than Source SQL Server
Open SQL Server Enterprise manger
Security>Logins>Right Click>New Login
Add SharePoint Service Account in Domain\user format
This account must be either Domain admin or Domain user with Local admin rights on SharePoint server.
Security>Logins>Right Click Service Account>Properties>Server Roles Tab
Check Security Administrators & Database Creators
Click Ok

STEP 3: RESTORE CONTENT DATABASE TO DESTINATION SERVER
Copy backup Content database files to Destination SQL Server
Open SQL Server Enterprise manger
Databases>Right Click>All Tasks>Restore database>Restore as Database>Type name of Content Database>From device>Select device>disk>Add>Browse to backup files>Ok>Ok
Similarly restore all Content databases from backup
Security>Logins>Service Account>Database Access Tab>In upper pane select Content database>In lower pane check DB_OWNER checkbox>Click Ok

STEP 4: DISCONNECT FROM SOURCE SQL SERVER
On WSS3.0 Server
Run SharePoint Products and Technologies Configuration (PSCONFIG ) Wizard
-Select Disconnect from this server farm

-We should get configuration successful message.

STEP 5: CONNECT TO DESTINATION SQL SERVER
Run SharePoint Products and Technologies Configuration (PSCONFIG ) Wizard
-Select No, I want to create a new server farm

-Database Server: Give Destination SQL Server name
-Database Name: Type new Config Database Name
-Username: Use same Service account as used in existing old server
-Password: Password for that account

-We should get configuration successful message.
-After PSCONFIG finishes successfully Central admin page will open automatically.

STEP 6: RESTORING SITES FROM DATABASES

3.Create a new web application http://app on port 80 with content database name WSS_Content_TEST

1] Go to V3 Central Administration Page>Application Management>Create or extend Web Application

2] Click on Create a new web application

3] Choose any unused port no

4] Enter Database Server Name and enter Database name as WSS_Content_TEST

7] Wait for operation to complete

8]After application is created create a site collection

9] Fill the details and select Team site template click Ok

11] Browse to test site http://app

12] Check if it is working

To remove dummy_content_db from a web application

1] Click on Content Databases

2] On right hand side select the newly created web application if not already present
3] Click on Database name WSS_Content_TEST


4] Check remove content database checkbox and click OK

To attach restored content database to a new web application:
Open a command prompt and browse to
c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin>
Run following command
stsadm -o addcontentdb -url -databaseserver -databasename

Now browse to http://app and check if it is working
Similarly add content databases for other web applications.

STEP 7: POST MIGRATION TASKS

From the screenshots taken earlier we need to reconfigure central admin.
If site was using SSL we need to reapply it & change AAM.
We need to redo any customizations if lost after creating new configuration database.
If 3rd party web parts stop working we need to reinstall them.
Integration with other products needs to be reconfigured.
We need to assign the indexer to the sites from Central Admin>Application Management>Content databases>Select web application from Right Hand Side Top drop down list>Click on Database name>Select Search server from drop down list>Click Ok
Use "stsadm -o spsearch -action fullcrawlstart" to force instant crawling of sites.

NOTE:
=====
Do NOT discard Source SQL Server & Databases until the functionality of New SQL Server & WSS3.0 is tested & confirmed.

There are alternatives to above procedure but are quite tricky. :-)

Wednesday, October 8, 2008

500 Internal Error

Error:- 500 Internal Error

Description:- This error comes only for subsites and subsite administrators can browse the subsite without any issues. The parent site collection is also browsable without any issues. Only member or visitors of the subsite get the error "500 Internal Error"

Resolution:
1. Go to the subsite settings page by adding /_layouts/settings.aspx at the end.
2. Select Advanced permissions -> Settings -> Permissions Level
3. Click "Edit Permissions level"
4. Click "Inherit Permissions from parent"

Now the subsite should be browsable by all without any issues.

Friday, August 15, 2008

Unable to delete Shared Services

DESCRIPTION: Unable to Delete Shared Services when it's database is deleted from SQL server.

SYMPTOMS: Unable to delete Shared Services. There are still some objects which are dependent on configuration database and on project serve, due to which users are unable to delete SSP. Manually deleting of SSP using stsadm -o deletessp -title "ssp_name" command also shows same error.

ERROR MESSAGE: “An object in the SharePoint administrative framework, "SharedResourceProvider Name=SSP Parent=SPFarm Name=MOSS", could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation. The dependant objects are as follows: ProjectPSISharedApplicationTimerJob Name=Project Server Synchronizing Job for 'SSP' Parent=ProjectApplicationService Name=ProjectApplicationService”

RESOLUTION: ° Identify the GUID for the problem SSP. ° Use STSADM -o deleteconfigurationobject -id "id retrieved from object table" to remove these items from the configuration database.

Use the following procedure to identify the Shared Services GUID:

Login to SQL server. ° Open SQL Management Studio and expend Databases. ° Expand Configuration Database & Tables. ° Opened table for dbo.object. ° Executed following query in query analyzer: SELECT * FROM [MOSS_CFG_CA_01].[dbo].[Objects]where name like 'Name of the Shared Services'. ° Copy the ID of object referenced in objects table of configuration database. ° Open command prompt and changed directory to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> and executed following command to delete the Shared Services using the ID which was copied: Stsadm -o deleteconfigurationobject -id "id retrieved from object table"


Shared Services should be deleted from the Cenral Administration.

Wednesday, August 13, 2008

Step by Step Guide on Publishing InfoPath Forms to SharePoint Site.

1. Creating and Configuring Forms Library in SharePoint.
2. Configuring InfoPath Form 2007. 3. Configure Form Submit Options.
4. Publishing InfoPath Form to SharePoint 2007.
5. Adding the Published form as Content type to the Forms Library.

Note: There are 2 types of InfoPath Forms.
a) User Form:- Only fields to be entered, where there is no Active code or programming added to the Form. These forms can be directly published to SharePoint Site. To Publish this Form, the user should be an Owner or Administrator of the Site Collection.
b) Admin Form:- These Forms have .net coding or Programming with the code which should run in the background once the Form is submitted. These Forms should be uploaded on the Central Administration and Activated for the Web Application to be used with. To publish this Form, the user should be a Farm Administrator.
Creating and Configuring Forms Library in SharePoint.
1. Browse to the SharePoint site you need to create the Forms Library.
2. Click in Site Actions -> Create -> Select “Form Library” under Libraries Section.
3. Enter the Name and the Description for the Form, Click on “Create
4. Once the Form Library is created -> Select Settings -> Form Library Settings
5. Select “Advanced Settings” .
6. Select “Yes” for Allow Management of Content Types.
7. For “Browse-enabled Documents” -> Select “Display as Web Page”. This option is beneficial when users do not have InfoPath 2007 installed on their local machine. The Form will open in the browse if this option is selected.
8. Click Ok.


Configuring InfoPath Form 2007

1. Once the Form is Designed and Created, we have to perform some pre-requisite tasks to be able to successfully publish to the SharePoint Site.
2. From the Tasks pane -> Select “Design Checker


3. Select “Change Compatibility Settings”. Enter the data as in below screenshot.
Note:- The URL to be entered should be of the “Site Collection”. Not of a Subsite or Form Library URL. The user publishing this Form should be the Owner/Administrator of the Site Collection URL specified.


Note:- If you select “Backward Compatibility” option for Office 2003, some of the controls that are not support in InfoPath 2003 will not function as expected. Select it at your own risk. If you have configured the Form Library to open the Form as a Web Page, this option will not be required to be selected.
4. Click Ok.


Configuring Form Submit Options

1. Select “Tools” Menu -> “Submit Options”. You will get the below dialog box.
2. After entering the details as required, click “Add” button for “Choose a data connection for Submit
3. You will get “Data Connection Wizard” -> Copy the Form Library URL Link (created during 1st step) and paste it.
4. When you click on “fx” button you will get the “Insert Formula” dialog box. Click on “Insert Field or Group” button you will get “Select a Field or Group” dialog box.
5. Select the Field, whose data should be taken as the file name, once the Form is submitted.
6. Select “Allow overwrite if file exists” as per your requirement and the data you will be entering in the Form. If you select this option you can also Enable Versioning on the library.
7. Click “Next”. Enter a Friendly name for the Data Connection. Click “Finish”. It will again come back to the Submit Options dialog box, Click OK.

Publishing InfoPath Form to SharePoint 2007.
1. Click File Menu -> Publish. Publishing Wizard will open up.
2. Select the option to publish to SharePoint server and click on “Next
3. Now again enter the URL of the “Site Collection” and click on “Next
4. Make sure that the Check box is selected as the screen shot. It is recommended to select “ Site Content Type (advanced)” to avoid manual creation of the content type. Click on “Next”.
Note:- The 3rd option “Administrator-approved Form Template (advanced)” is to be selected when the Form has Active code or any .net Programming added to the form.
5. Select “Create a new Content Type”, so that we don’t overwrite the default content type of SharePoint. Click on “Next
6. Enter a Friendly Name and Description for the Content Type. Click on “Next
7. You will need the URL of a Document Library. You can copy the shortcut as shown in the screen shot. Then paste it in the Publishing Wizard and click on “Next

8. Add Columns to your Form Library. Click on “Next
9. At the end it will give the summary of the options selected and Click on “Publish” button. Once you get the Message “Your Form template was Published Successfully” Click on the “Close” button.

Adding the Published form as Content type to the Forms Library.
1. Browse to the Forms Library -> Select Settings -> Form Library Settings. You will Content Types as below. “Form” is the default content type. We have to add the new InfoPath Content type that got created while publishing the InfoPath form.
2. Click on “Add from existing site content Types”. From the drop down list select “Microsoft Office InfoPath”. Add the “Content Type”. Click on OK.
3. You will now see 2 Content types, the default (Form) and the one you just added. You can delete the default content type if required.

Now you can go ahead and create a New Form, the published Form should open up in Web browser.

Not able to Export Survey list with more than 100 responses to Excel Spreadsheet

Issue:- While Exporting a Survey List, only 100 responses are exported.

No Error is logged or generated.

Resolution:- Open the Sharepoint Survey List in Sharepoint Designer. For both Overview.aspx and Allitems.aspx do the following.

Change the RowLimit element Paged property set to FALSE.
RowLimit Paged="FALSE">100</RowLimit
Change the value to True (using SP Designer 2007), otherwise it will limit the items display and export to excel.
RowLimit Paged="TRUE">100</RowLimit

Thursday, July 31, 2008

Not able to Create a New Document in Document Library

Issue:- Not able to create a New Document in Document Library.

Error:- "The exception unknown software exception (0xc06d007f) occured in the application at location 0x7c812a5b."

Environment:- Office 2003 and Office 2007 product together.

Resolution:- http://support.microsoft.com/kb/938888

Wednesday, July 30, 2008

Export to Spreadsheet

Issue / Error:- “Cannot get the list Schema column property from the SharePoint List”
When does is occur? :– While exporting a list to Excel Spreadsheet.
Environment :- Office 2003
Resolution :- Known bug. Can be resolved by Post Service Pack 1 release http://support.microsoft.com/kb/941422/en-us

Workaround:-
Upgrade to office 2007 OR
a. Change all the Date columns in the List to use “Date Only” format.

b. Using a machine which has Office 2007 installed, Export the list to Spreadsheet.
c. Create a new Blank “Import Spreadsheet” List.
d. Import the old Exported List back.
e. Now you will be able to export the list to spreadsheet in Office 2003 also.

Note: Do not change the format back to “Date & Time”

How to Re-produce the issue?

1. Create a SharePoint List with “Date and Time” Column keeping the format as “Date Only”
2. On Office 2003 machine Export the list to Spreadsheet, it will work without any issues.
3. Change the Date Column Format to “Date & Time”
4. Now again try to export the list to spreadsheet, it will not work, you will get the error “Cannot get the list Schema column property from the SharePoint List”, but the same list will get exported without any issues in Office 2007 setup.

Note: Even if you change the Date format back to “Date Only”, the issue will still persist; it does not resolve the error.

Tuesday, May 20, 2008

Error while creating a new page in MOSS.

Getting the below error while creating a new page in Moss 2007 while using publishing or collaboration portal template.



List does not exist The page you selected contains a list that does not exist.

It may have been deleted by another user.



In ULS Logs the error listed is as below.

05/16/2008 13:13:34.51 w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 8kh7 High List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user. 05/16/2008 13:13:34.51 w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 8nca Verbose Application error when access /_layouts/AccessDenied.aspx, Error=List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user. at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount) at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt... 05/16/2008 13:13:34.51* w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 8nca Verbose ...32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount) 05/16/2008 13:13:34.51 w3wp.exe (0x1AF8) 0x148C Windows SharePoint Services General 0 Verbose Releasing SPRequest with allocation Id {BD5F0900-38A4-40AB-BC1F-E78319A3DD70}



Resolution
=========
Go to Site Settings -> Master page Gallery -> Add Authenticated Users group and give Read Restricted Access rights.


Add the same group in Style Library and give the same permissions.

Sunday, February 24, 2008

Microsoft Search Server 2008

Search Server is one of the other major Enterprise servers of Microsoft which is growing Fast with Sharepoint 2007. With the new release of Search Server 2008 in March, it is expected to take Search functionality and Search Experience to the next level for Microsoft's Customer's.

There are better features than Google's Onebox Search Server Appliance, though I would say both have their own pro's and con's.

Search Server 2008
It's RTM version's are getting released in Express and Full Edition. Express Edition will be downloadable for free whereas Full version is a licensed product. There will be support provided for both these versions from Microsoft.

Express Edition's limitation is that it can be installed only on a SingleServer WSS 3.0 environment, whereas, Full Edition can be installed in a Farm WSS 3.0 enviroment.

Search Server 2008 MOSS patch is expected to be released later this year. When you install Search Server 2008, WSS 3.0 will be installed along with it, with some more cool features of Search which is not available with only WSS 3.0 Another new and cool feature of Search Server is the Federated Search which allows you to render the index of the Search engines on the internet, except for Google Search, Google blocks any search engine to crawl its content.

Search Server needs to get the results returned in XML formart to display those results in the Search query, for any Search engine that cannot return the results in XML format to Search Server, we have Federated Search custom connectors that can be created to re-format the results in XML format and store it locally. Those custom connectors is something that Shareopoint Developers will have to do. There are many 3rd party custom search connectors already available and can be used with Search Server 2008.

Google's Enterprise Search products have limitations of crawling data, depending on the product you buy, the limitations differ. In Microsoft Search Server 2008 there is no limitation to the no of files that be crawled. Also, Google's product expire in 2 years and so will their email support, they do not have any on call support. If you want to renew the support you will have to buy a new license for that to get support. (Email)

More information on the Installation and new features of Search Server 2008 will be posted soon.

Sunday, February 10, 2008

Email Enabled Document Library [Error in Application]

'Error in Application' is the error we get when configuring Email Enabled Document library.

There is one most common scenario when you will get this error.

WSS 3.0 or MOSS 2007 installed as a Basic Installation [SINGLESERVER]

By Design when you install sharepoint using Basic intallation, the Central Admin site and any other new Web Apps that you create will use 'Network Service' as the service account for the Application Pools in IIS. For a contact to be created for a Document Library, the Application Pools of both Central Admin and the Web App should be using a domain user account and not Network Service.

Steps to Perform to resolve this error.

1. Create a Service Account in Active Directory who is also a member of the Domain Admins group. Delegate all rights to this service account to the Organizational Unit created for Sharepoint, where contacts will be created.

2. On the Sharepoint server, Open Computer Management -> Local Groups and Users -> Groups. you will find 3 WSS_WPG groups, make the service account a member of all these 3 groups and also the member of the IIS_WPG group.

3. On the Sharepoint server, open IIS console and make sure that the Application pools running for Central Admin site and the Web Application are running using the service account created in step 1. Perform an IISRESET and then make sure the Central Admin and the website are up and running after changing the Application Pools.

4. Now configure the Incoming Email settings for the Document Library. You should not get the 'Error in Application' error.

5. Now create a new Web Application and a Site Collection using the service account and not 'Network Service'. Take a backup of the old Site Collection using stsadm -o backup command and restore that backup on the new one just created using stsadm -o restore

Note: We have to do the 5th step because once changing the service accounts in many cases the site will not open from Client machines, it will open only on the Server or after configuring the Incoming email settings for the Doc Library, the emails will not be visible in the document library.

These above steps will resolve the issue and also the sites up and running. In many cases where the installation is not Basic, you will find the same error message, that purely due to the service account not being a member of the 'Domain Admins' group.

Thursday, January 10, 2008

Search Does not work with Basic Authentication, only WSS 3.0

WSS 3.0 Only with Basic Authentication to Search the Sites

Only WSS 3.0 is installed and Basic Authentication is configured so that while logging to the site domain\username and password is not required, only username and password should work.


But by design Search in WSS 3.0 with Basic Authentication will not work. So there is a work around for the same which can be followed by using the following article.


http://technet2.microsoft.com/windowsserver/WSS/en/library/8208d71e-7c41-4845-bc06-95429de02cf11033.mspx?mfr=true

But this above article is misleading many times as every network has various scenarios.

Step by Step to configure this setup

1. Open Central Administration Site ->Application Management -> Create or Extend Web Application -> Extend an Existing Web Application.

a. Select the main Web application
b. In IIS Web Site select ‘Create a new IIS Website’
c. Give port no. 81 or any random port you want.
d. Enter a hostheader if desired.
e. Select NTLM as Authentication Provider.
f. In Load Balanced URL select ‘Intranet’ Zone. Click on OK.

2. In Central Administration -> Application Management -> Authentication Providers.

a. You will see the Default Zone and the Intranet Zone where we extended the new site.
b. Click on Default zone; make sure that only Basic Authentiation is selected. Click on OK.
c. Click on Intranet zone; make sure that Windows Integrated is selected. Click on OK.

3. Open IIS console -> Web Sites.

a. Go to the properties of the Main site -> Directory Security
b. Click Edit in Authentication and access control.
c. You should see only ‘Basic Authentication’ selected over there.
d. In Default Domain type \ (backslash)
e. Click on OK. Click on OK.

4. Open Central Administration -> Operations -> Alternate Access Mappings -> Select the Main Web Application.

a. You will see 2 zones having URL’s specified. In default zone your primary URL. In Intranet zone the URL and port no. which you extended the main site with.
b. We have to now swap these 2 zone URL’s Put the Default URL in the Intranet zone and the Intranet zone URL in the Default zone.

5. Perform an IISRESET.

6. Check the Eventviewer App Log and verify that we should NOT get the event id 2436 gatherer which is a warning. This warning will come after every 5 mins if Search will not work, otherwise it will not come.

We have to swap the URL’s in AAM purely because Search always renders the page which is mentioned in the Default Zone and then crawls it. After the Swap of the URL’s in AAM, as the default zone URL will be of Windows Integrated, Search will be able to render it, crawl and we will be able to see the search results after 5 mins. In App log you will stop seeing event id 2436 warning and event ID 10044 information event which means that search should work fine.

Wednesday, January 9, 2008

Installation Windows Sharepoint Services [WSS] 3.0

Installing Only WSS 3.0


Windows Sharepoint Services 3.0 Installation is farely easy but very complicated to resolve if it errors out. There are 2 types of Installations which are described in detail below. WSS 3.0 is freely downloadable from Microsoft site. [ http://www.microsoft.com/downloads/details.aspx?FamilyID=d51730b5-48fc-4ca2-b454-8dc2caf93951&DisplayLang=en ]



Pre-requisites before Installing Windows Sharepoint Services.

  1. Windows 2003 OS with ASP.net + IIS 6.0. SMTP is required if you are deciding to use Email Enabled Document Libraries, not otherwise.
  2. Service Pack 1 or higher.
  3. ASP.net 3.0 framework.
  4. Service account created in Active Directory, recommended to be a member of Domain Admins groups. This service account should not change the password according to group policies, otherwise everytime the password is required to change, Sharepoint sites will go down once the password is changed. If you dont want the Service account to be a member of Domain Admins group, it has to be the member of the local administrators group on the server you will be installing Sharepoint.

Types of Installation of WSS 3.0

  1. Basic
  2. Advanced

Basic Installation Detail Description

  1. You run the sharepoint.exe file which you can download from the above link. You will get the License agreement page. Accept it and Click on Next.
  2. On next Page It will give you 2 buttons 'Basic' and 'Advanced'. We are going to select 'Basic'
  3. After selecting Basic it will continue with the installation process and at the end it will stop at 'Run the Sharepoint Products and Technologies Configuration Wizard now'. This is inshort referred as 'PSConfig' wizard.
  4. Make sure that the checkbox is selected and click on the Close button. PSConfig Wizard will start.
  5. Click on Next, it will give a warning of restartint the IIS Services -> click on Yes. It will run 1 to 10 steps in PSConfig wizard.
  6. Once all the steps are completed Click on the Finish button and default page http://servername/ site will open automatically.


Description of above steps

  1. Step 1:- Log on to the server using the Service account created. If the pre-requisites of IIS and ASP.net 3.0 framework is not met, it will error out and you will not get the EULA page. Before coming to the EULA page, pre-requisites are checked.
  2. Step 2:- Basic Installation will not prompt for any configuration settings. Using Basic installation SQL Express Edition is installed and Sharepoint Databases are created in SQL Express Edition. By Default there is not GUI mode to manage those databases, you will have to separately install SQL Management Studio Express [ http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796&DisplayLang=en ] and once installed connect to the database using "\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query" (without quotes).
    In this step only the binaries and some registry keys are installed and configured.

    Binary files are located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin

    SQL Express Databases .mdf and .ldf files are located at C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

    Registry Key location is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS. Important Registry keys are 'Server Role' and 'Setup Type'. If Basic Installation is done, "Server Role" will be mentioned as "SINGLESERVER" and "Setup Type" will be mentioned as "CLEAN_INSTALL"
  3. Step 3:- PSConfig wizard is when Sharepoint is Basically configured. Untill you run this wizard, Sharepoint Administration site or any functionality related to Sharepoint will not be possible. Description of the PSConfig Steps, I will Post it Separately.

Once the Installation and PSConfig Config wizard is completed successfully, Open up IIS console and you will find that the 'Default Web Site' will be stopped and the default Sharepoint Site created is also at port 80 [ Sharepoint - 80 ]. So if you have Exchang running on the same server, OWA will stop working as OWA is extended on the 'Default Web Site' in IIS. Exchange and WSS 3.0 only is supported by Microsoft but Exchange and MOSS 2007 on the same server is not Supported.

You will also find the Sharepoint Central Administration V3 site, which is the Sharepoint Central Administration Site IIS Virtual site. This Site will be created at a random port no. which will be taken during PSConfig wizard. From the above registy path, you can also get the 'CentralAdministrationURL' which specifies the Central Admin site URL with the Port no.

There will be 3 Default groups created 'WSS_WPG', 'WSS_RESTRICTED_WPG', 'WSS_ADMIN_WPG'. The user account using which you installed Sharepoint will be the member of these groups by default. It is recommended you log-on to the server as the service account first and then proceed with the Installation.

By Default at the database location you will find 4 Sharepoint Databases created in Basic Installation.

1. Sharepoint_Config_bigGUID [ Sharepoint Farm's Configuration database].
2. Sharepoint_AdminContent_bigGUID [ Sharepoint Central Administration database].
3. WSS_CONTENT [ Sharepoint - 80 sites database].
4. WSS_Search [ Windows Sharepoint Search Service Database, By default Search Service will be started in Basic Installation.]

Sharepoint Search not working. Event ID 2424

Search not working, Application Log filled with Event ID 2424

Event Type: Error Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2424
User: N/A
Computer: ComputerName
Description: The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application 'Search', Catalog 'index file on the search server Search'

Resolution
Central Administration -> Operations -> Services on server -> Click on the Windows Sharepoint Services Search service and make sure that the 'Service Account' and 'Content Access Account' service account specified are the same. They should not be working with two separate accounts. If it still does not work, Stop the service and while starting it again specify a common service account and create a new Search Database.

Sharepoint Backup

Types of Backup in Sharepoint V3.

As Every product or any business Disaster Recovery is very importand and in similar way, Sharepoint has some very good options for the same. Below are the methods that can be used in WSS 3.0 only or also for MOSS 2007.


1. GUI mode from Sharepoint Central Administration.

This Method is very common and most of the Administrators use this Method.

Go to Sharepoint Central Administration page -> Operations Tab -> Backup Operations.

This method will need a UNC path to store the back. It automatically creates a folder starting which will have various files in it and the most important file is the .xml file which get created, which has all the information about the backup.

The .xml file will contain data about the backup ID, The type of Backup, the Components selected during the backup.

GUI Backup is the same like the stsadm -o backup [catostrophic]. Both work the same way and the backrgound process is the same. Only difference here is the GUI interface.

By Default this backup will take the entire Sharepoint Farm backup

2. STSADM -o backup

This method is a command line backup which needs to be run from the BIN folder of Sharepoint.

This method can backup any top level sites or site collections of a Web application.
You will need to specify the URL address of the site to be backed up.

By default in this method the security or permissions are also backed up.

stsadm -o backup -filename c:\back.bak -url http://siteurl/

This is the standard command. It is not necessary to give the backup file extension as .bak, it can be anything or you may not even give any extension. Using this command you can backup only 1 top site at a time within the Web Application. If you want you can create a batch file which will include the commands having different URL's and schedule te batch file to run accordingly. It also includes other parameters for which you can use

stsadm -help backup

3. STSADM -o backup [catostrophic]

This method is similar to GUI Central Adminstration backup, its only Command line interface. You will need to manually specify the parameters and components to be backed up using this command. By default if the component is not specified, Enter Farm level backup is taken. Using this command as well a UNC path is to be given, where again and .xml file will be created.

stsadm -o backup -directory
\\server\backup -backupmethod full [This will take the default Farm level backup]
You can use stsadm -o backup -showtree to see the list of the items in the Farm and then use stsadm -o backup -directory \\server\backup -backupmethod full -item
4. STSADM -o export

This method will help you to take backups of subsites separately which is not possible in any of the above backups. Using this method, subsites and top level sites backup can be taken but by default User permissions are not exported, you have to manually specific to export User permissions.

stsadm -o export -filename c:\exp.back -url http://siteURL -includeusersecurity

If you do not use -includeusersecurity, User permissions will not be exported by default.

5. SQL Database backup.

This method is the usuall maintenance method from SQL Management Studio. It is recommended to have the Sharepoint Content Databases backup from SQL as well, just in case Sharepoint Backup's don't work.