So I did the following;
1. Download the latest version of Adobe iFilter
or Adobe iFilter 9 for 64bit platforms
2. Or make sure you download Adobe Reader 9.0 using the Internet access of the WFE or a similar PC with same OS configurations. http://get.adobe.com/uk/reader/
3. Stop IIS Manager from the services console.
4. Install both the Adobe iFilter and Adobe Reader 9.0 (Well I had to install both to get the results).
5. Then follow the Microsoft resolutions here.. to point 7. Stop. Make sure you take note of this info
6. Follow this document and do points 2 - 5
7. Also you might want to take note of this PDF file
8. Restart your server.
Also note that PDF files are crawled after the installation of Adobe iFilter
- Configuration of Adobe iFilter 9 for 64bit Platforms of MOSS 2007
I was looking at one of my test environment today and I found this error (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND))
And also the site it self http://webserver:418 was not crawled or the crawl log under Hostname Summary... Http://webserver:418 (successfully crawled = 0). That didnt look good!.
So I did a search for similar issues online and came across this solution. http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/6b204093-4e30-4e6a-b829-1bbede2602a1/ which I applied and it worked.
So my steps were;
1. Go to the IIS Manager check the account under which the sharepoint central admin appool is running (say it is running under com\user1)
2.go to administrative tools -->component services--> drill down to DCOM config
3.Osearch and spsearch properties -->identity--> this user put (com\user1) account there
4. Then perform Full/Incremental crawl on the sites. Voila it worked!
Solution: The problem is caused by the local wss_wpg server account not having write access to the %windir%\tasks folder, usually c:\windows\tasks folder. This folder is used by Windows Task Scheduler. So to fix the problem the wss_wpg account needs to be given write access to the c:\windows\tasks folder on the index server.
Note: The c:\windows\tasks folder is a hidden folder by default.
- On Index Server or all server in farm
- Open a command prompt and type attrib -s %windir%\tasks
- Browse to %windir%\tasks, right click and select properties. Add the WSS_WPG group and grant Read & Write permissions on the tasks folder.
- Open a command prompt and type attrib +s %windir% \tasks
Event Type: Warning
Event Source: Office SharePoint Server
Event Category: Publishing
Event ID: 7352
Error occured while processing a Content Query Web Part. Performing the following query '
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
1. Visited the URL and deleted the Content Query Webpart
After the last disaster recovery i started to receive this error from the Web Front End.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
The Execute method of job definition
dfe5d15e-4a9e-4d4e-8e58-26ca0d11e2fa) threw an exception. More
information is included below.
An update conflict has occurred, and you must re-try this action. The
object SPSearchDataAccessServiceInstance Parent=SPServer Name=VC-SPCR0
is being updated by QUINCY\spconfigacct, in the OWSTIMER process, on
machine VC-SPCR0. View the tracing log for more information about the
For more information, see Help and Support Center at
This error was populating the Event Log every 5 minutes. Then I found this solution
I found that this issue is caused by a disaster recovery. The file-system cache on the front end is newer than the contents of the configuration database. After a disaster recovery, it may be necessary to manually clear the file system cache on the local machine.
1. Clear the file system cache on all servers in the farm running the timer service manually. To do this, stop the timer service, delete (or move) the contents of the folder at
%ALLUSERSPROFILE% \Application Data\Microsoft\SharePoint\Config\<someGuid>
2. Then, simply restart the timer service. The cache will be rebuilt and the issue should disappear. This should be done on every machine in the farm running the timer service
Hope this helps!
Microsoft Online Community Support
So what did I do?
- Stopped/Disabled the Timer jobs that run in minutes on the Central Admin Server VC-SPCR0 Deleted the <guid> from every server in the farm at this location C:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
- Then I restarted all the Timer jobs I disabled.
This was a solution that I came across when this client of mine needed to free up some space on his SharePoint test environment.
He was running a VM Ware setup and he had run out of space on the C: drive wherein his SQL server was holding his DB files.
I was able to create new drives on the VMWare SQL server wherein the DB files will be kept. Then I created an empty DB (stats_db). This was an “insurance policy” that I wanted to use just in case I loose the site collections if I had to move the content database.
- Create a new drive or identify your new storage media.
- In the SQL database create a new database from the Microsfot SQL Server Management Studio.
Right click on Database and select New Database, name it “New_db”
- Goto the SharePoint Central Admin >Application Management > Content Databases> and add this database as a content database to the web application you will be moving its content database.
Add the “New_Db” to the Database name and click OK
- Remove the old/previous content database.
- Then detach the old/previous content database from the SQL server.
- Copy the detached Db files (LDF & MDF)to the new media storage.
- Reattach the Content database from the new location
Browse to the new location and attach the copied database.
- Add the newly attached Db to the web application just like you added the “New_Db”.
- Do iisreset.
- Test the web application and voila! – this works
Then I also had this
run stsadm -o sync -DeleteOldDatabases 0
Simple enough it can help to export your sites and you can do an import unto the live site.
Now the panic started..Where is the problem? Why did MSSQL go down?
Well I took the following steps;
1. Perform a farm reset. Restarted all the servers in the farm.
When all servers came up, it helped abit as the errors cleared out.
Now I faced the MSSQL server.
During this period, I had been faced with another dreaded issue which started as a result of one of my consultants deleting a Shared Services Provider which he created in a bid to fix another issue. So the DB created was still hanging around in the MSSQL brains..but needed to be cleared out.
Solution was... from this link.
Phew! what a relief. now let me watch the servers for a while..
His problem was that after recent setup of a SharePoint installation he was having problems with Site User Authentication. So whenever a signed in user tries to access the Team site/ Collaboration then he/she gets a prompt to login to the sharepoint site.
His intial plan was that users will be authenticated with thier Windows logon.
The simple solution was to add the intranet site to the Local Intranet Settings.
1. Open IE, click Tools, Internet Options, Security, Local Intranet, Sites, Advanced
2. Type in the local intranet address and press Add.
Voila! Your sites would load as planned
I hope you find it useful
Planning and Architecture for Office SharePoint Server 2007 (TechNet)
Plan for Performance and Capacity (TechNet)
Scale, Performance, and Capacity Planning (Microsoft SharePoint Products and Technologies Team Blog)
SharePoint Test Data Load Tool
SharePoint Asset Inventory Tool
Microsoft Forefront Security for SharePoint
Database Management Concepts
I embarked on this because, for a while now, I have encountered different installations of SP. And this has created a load of different trouble scenarios. Then I thought, whats if you had a "magic wand" you could wave at that server.. Then it would tell you whats wrong and where..
I came across Eamon Barker's blog here. Its a good compilation, but my search continues.
Besides the Microsoft SharePoint Administration Toolkit which you can find here . It can only add the Batch Site Manager.
Which is added under the Apps Mgmt can only be used for Site Collection. I will rate this tool 30%.
- SharePoint is the fastest-growing product in the history of Microsoft
- More than 100 million licenses sold
- Has attracted over 17,000 user companies
- Over $1 billion in sales for Microsoft
- 3/4 of the Fortune 100 companies use SharePoint
- SharePoint is positioned as a leader within the Gartner Magic Quadrant for Horizontal Portals products
- Six focus areas : Collaboration, Portal, Search, Enterprise ontent management , Business process management and Business intelligence
The problem was a site collection was deleted by the site administrator without doing this via Central Admin.
This infact affected the upgrade of this SharePoint installation to SP1. It was pain as you could see it under Site Collections List but it reports this site collection cant be deleted.
The simple solution was;
1. Goto Central Admin > Application Management
2. Select Content Databses under SharePoint Web Application Management
3. Click on the Top Level DB > scroll down and remove database
4. Do not delete DB or contents
5. Go back to Content DBs and add DB, Type the name of the one your removed to attach it again.
Voila! all orphan sites have disappeared
I suggest using SharePoint Designer 2007
How can i get access back to my sub-site.
- Go to the Central Admin
- Click Apps Management
- Click Site Collection Administrators
- Add yourself as a site collection administrator.
- Go back to your site and you will be able to modify site settings
How do i change the icon (left side of the title 'Internal Project Group' on top left)..
Do I need sharepoint designer to change it?
- Move your mouse over the image, right-click on it and view the properties
- Note its name down
- Goto your Front End Server, wherein the site is hosted. Perform a search for the file name.
- Pronto you will find it among your search results.
Else, Use SharePoint Designer to change it!
Event Type: Error
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2424
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'
For more information, see Help and Support Center
The Staging Environment of WebWox is a replica of the Live environment.
This SharePoint Installation includes a Server Farm of 5 servers + and IIS server as follows;
- IIS-Stage-WFE01 – Hosts the HomePage
- SP-Stage-APP01 – Runs Excel Services
- SP-Stage-Search01 – Runs Office Search Services
- SP-Stage-WFE01 – Hosts the Central Administration
- SP-Stage-WFECr01 – Acts as a Front End Web Crawler
- SP-Stage-SQL01 – Hosts the Staging Database
webwox-stage.webwox.com and mysites.webwox.com are subdomains used to hosting the Web Applications and Site Collections. These 2 are SSL enabled and obtains the SSL certificate from the domain controller
The following steps were implemented;
- Perform a backup job of the entire farm – to \srv-pencil\serverbackups$\stage.
- Ensure that the backup is successful (Incomplete backup cannot be used)
- Disconnect from farm SP-Stage-APP01, SP-Stage-WFECr01, SP-Stage-Search01.
- Uninstall SharePoint from all servers that have been disconnected from the farm.
- Reinstall SharePoint on all the servers that have been disconnected from the farm
- Run Configuration Wizard on WFECr01 setup a new farm – WXSPConfig
Connect Search01, APP01 for the new farm
- Assign Services to these servers. – Office Search Server and Windows Search setup on SEARCH01 using (WSS_Search_SPSTSCH) as DB
- Point webwox-stage & mysites to WFECr01. Add the xxx.16.xxx.163 to WFECr01.
- Run restore job to restore the backup taken from WFE01.
- Select New Configuration
Databases used for restore;
- Ensure that restore was successful
- Setup SSL on the Websites mysites-stage and magellan2-stage by assigning a new SSL certificate using the DNS names webwox-stage.webwoxd.com & mysites-stage.webwox.com
- Perform tests to ensure staging environment is functional
- Perform the upgrade to SP1 by installing all the files on the servers APP01, Search01, WFECr01 following the Microsoft Documentation on upgrading MOSS 2007 to SP1.
- Perform Testing after the farm has been upgraded.
- Turn on the Firewall on all servers and click Office Web Servers, Secure HTTPS and HTTP access. Add Secure MySite Connection 8083. Allow this traffic
- After SP1
Go to search setting from the SSP, click Crawl Rules and Apply new Crawl Rule to https://mysite-stage.webwox.com and uncheck
"Follow links on the URL without crawling the URL itself".
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10034
Could not access the Search service configuration database.
Context: Application '76d822a2-1c3c-4cc8-aa02-5c16fe104138'
The filename or extension is too long. (0x800700ce)
For more information, see Help and Support Center
Simple solution restart the search service on the Office SharePoint Search Server.
Make sure that you confirm that the service account is given permission on the SQL database and also the WSS_Content Search DB.
To ensure DBs dont grow beyond a certain size is to limit the number of sites and employ site collection quotas. By using these 2 elements togther you can ensure your content DBs dont grow beyond a pre-determined size.
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
to the user test\SPConfigAcct SID (S-1-5-21-1430212151-832525293-1231754661-36867). This security permission can be modified using the Component Services administrative tool.
For more information, see Help and Support Center at
Here lies the solution
View the above to resolve the problem
- Copy the apps to a folder on the CA WFE server
- Open cmd and dir to C:\Program Files\Common Files\Microsoft Shared\Web Server Connections\12\Bin\
- Add Solution to SharePoint - use the command stsadm -o addsolution -filename
\application.wsp press Enter
- After Successful addsolution. goto CA>Operations>Solution Management
- Select the application name and click, once it opens click deploy solution.
- Once its successful, it can now be used
The context of the problem is as follows;
A particular web part was added to a site, this webpart was expected to display the names and photos of staff in a particular group that was selected for the web part.
The web part worked but did not display so particular profiles photos. Also when you click on the user profile it takes you to a user profile display page "userdisp.aspx" which does not display updated profile.
The fix is a simple one and would require adding some settings to all the site collections.
1. Login to any Site Collection as Admin
2. Click Site Actions >Site Settings>Modify All Site Settings
3. Click Profile Site Connection under Site Collection Administration
4. Select Connect to a portal Site and add https://mysite.domain.com
5. Ok and exit
I have been thinking of writing procedures of Server Monitoring and Maintenance. I decided to put together some write-up for this. It is not an exhaustive document but it will help if you are fairly new to SharePoint Administration.
Server Monitoring and Maintenance Procedures
This document explains daily procedures that should be performed in order to monitor and manage the SharePoint 2007 Server. Moreover, daily and monthly procedures are outlined to help you maintain the SharePoint Installation.
Daily Monitoring Procedures
The following system monitoring procedures should be performed daily.
- Check that all relevant services are operational on all the servers in the farm using the Services Snap.
- Check that ample space is left in the C: Drive in order to free-up disk space for applications to run properly.
- Verify that the previous night's backup has run.
- Search for unusual entries in the Event log Snap, this task should be done every 6 hours.
- Check for all Timer Jobs definitions and resolve all jobs that failed or did not complete.
In the Event of an Emergency Downtime,
The following has to be restored back as quickly as possible;
- SQL Database
- Front End Server
- Search Server
- All Solutions/modifications applied
The functionality of the SharePoint different functions should be checked after every downtime.
In order to seamlessly administer and manage the SharePoint 2007. Some tools are needed as follows;
- Microsoft Office SharePoint Server 2007 MP for MOM 2005
- SharePoint Administration Toolkit
These tools would help to detect any errors and problems that may arise which might not be easily detected.
Event Log Resolution Procedure
Once an error log is detected in the Event log, this should activate the quick resolution process be aware that a resolution might take the whole day and sometimes it might be a quick fix or an after close of work fix.
- Log this Error/Fault in the Daily Resolution KB on the SharePoint Administration Site.
- Diagnose and detect the problem, propose a solution to this error/fault.
- Perform a google search for similar problems, document the results, make sure the results obtained from the google search reflect the same problems occurring on the server.
- Discuss with Teksys and if necessary raise a call ticket
- Copy the URL from the search and add it to your entry on the Daily Faults Resolution KB.
- Test resolution on the test environment, then staging environment.
- Discuss possibility of a change with Project Manager and/or Infrastructure Team leader in order to resolve this fault.
- Determine length of time for resolution to take place, time it would start and any extent of downtime/effect on the entire farm.
- Have a Rollback plan
- Raise an RFC for the change.
- Inform the CAB about the change and time.
- Effect the change, perform testing and confirm the functionality of the entire farm.
- Update the Issues Log.
I have been thinking of how to put together a wealth of experience I keep gaining from an extremely versatile tool - Microsoft Office SharePoint.
This blog will document my day-to-day activities in resolving some of the complex problems I face with several installations.