Stsadm Technical Reference for SharePoint Server 2007
Stsadm Technical Reference for SharePoint Server 2007
Microsoft Office SharePoint Server 2007 includes the Stsadm tool for command-line administration of SharePoint Server 2007 servers and sites. Stsadm is located at the following path on the drive where SharePoint Products and Technologies is installed: %COMMONPROGRAMFILES%\microsoft shared\web server extensions\12\bin. You must be an administrator on the local computer to use Stsadm.
Use the interactive application on this page to learn about the commands available. For more information, see Index for Stsadm operations and properties in the technical library.
For information about using the Stsadm tool with Windows SharePoint Services 3.0, see the Stsadm Technical Reference for Windows SharePoint Services 3.0.
http://technet.microsoft.com/en-us/office/sharepointserver/cc948709.aspx
Sharepoint Administrative Tasks
I have been asked many a times what is the role of Sharepoint Administrator. In my opinion the Sharepoint Administrator primary job would be to monitor and check the Sharepoint Servers and Sharepoint Access, Build up the Physical Architecture, Logical Architecture and creation of SIte Collections and Sites and Management of Content Databases as per the best practices suggested by Microsoft.
- Some of the Routine SharePoint administrative tasks would be:
- Daily checks to test and monitor the SharePoint Status, health, and the Performance (SharePoint sites Response time, status of host server, SharePoint Server and the IIS Server)
- Daily check of Front-end and Back-end backups for business continuity.(Check the last date of your backups)
- Daily Check of the profile import.
- Daily check of the Search and Indexing features.
- Daily check and installation of Security Updates.
- Daily check the SharePoint Site Access
- Daily Monitoring and Reporting of SharePoint Sites.
- Daily Monitor and analyze SharePoint usage and activity.
- Daily Monitor and analyze SharePoint content and storage.
- Daily Monitor SharePoint Trends and Governance Violations.
- Daily monitor event logs for any errors or warnings. Make sure the number of warnings and errors were minimum and health check of the Sharepoint environment.
Excel 2002 and SharePoint- Unable to open and edit the spreadsheet and save
Today one of the SharePoint Users called me for help with Sharepoint. The User was trying to open the Excel Spreadsheet from Sharepoint and was not able to make any changes or edits to the document and also could not save any changes. when he tries to open the Excel Spreadsheet(.xslx). the spreadsheet opens up in the web browser but will not allow the user to make any changes and the option to save it is not available.
I remoted in to his machine and found that the user had Office 2002 installed on his machine. Once we upgraded the current version of office 2002 to office 2007, everything worked like charm....
Event ID-7043 Error on SharePoint Server
I found these 7043 errors in my application event log on the SharePoint web front end server
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Web Controls
Event ID: 7043
Date: 5/24/2010
Time: 2:04:13 AM
User: N/A
Computer: MOSSSERVER
Description:
Load control template file /_controltemplates/LookupFieldEditor.ascx failed: Thread was being aborted.
Event ID: 7043
Date: 5/24/2010
Time: 2:03:52 AM
Description:
Load control template file /_controltemplates/EditPreview.ascx failed: Thread was being aborted.
Resolution:
Re-run the SharePoint configuration wizard, once the configuration is complete you should get rid of these 7043 packaged errors.
Event ID-4354- EventSystem- SharePoint Servers
This is the event that is seen almost once or twice a week in the event log:
Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354
Date: 5/17/2010
Time: 8:34:57 AM
User: N/A
Computer: MOSSSERVER
Description:
The COM+ Event System failed to fire the PostShell method on subscription {80F9D260-A86A-4EAE-BDF8-543B9461A63E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 80004001.
Resolution:
After a bit of research related to this issue, it was found to be from McAfee AntiVirus Agent and the VES version installed on the machine. A hot fix was eleased to fix this.I noticed this warning every time after 3 to 4 minutes a user logged in.
The KB on this has been published (KB67381):
https://kc.mcafee.com/corporate/index?page=content&id=KB67381
Event ID-2003 Performance Library Information-Windows 2003 SP2 Ent x64
These four errors realted to Performance Library information were reported in the event log.
Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 2003
Date: 5/17/2010
Time: 9:14:14 AM
User: N/A
Computer: MOSSSERVER
Description:
The configuration information of the performance library "C:\WINDOWS\system32\inetsrv\w3ctrs.dll" for the "W3SVC" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
Event ID-2442 Windows SharePoint Services 3 Search
Lately I noticed an event ID 2442 logged in the application log.
Event Type: Warning
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2442
Date: 5/14/2010
Time: 5:18:03 PM
User: N/A
Computer: MOSSSERVER
Description:
The index was paused.
Context: Application 'Search', Catalog 'index file on the search server Search'
The cause of this warnings was due to the scheduled backups that were running at these times. When SharePoint backup jobs were running the indexing or all the crawler jobs were stopped temporarily untill the backups were completed.
Hopefully these issues should be resolved with SharePoint 2010 as the Indexing and Search Architecture was completed changed with partioning of Index in Palce and Search being made more felxible.
Award Winning SharePoint Administration Tool-Control Point New Release
Many a times people keep asking what were the responsibilities of a SharePoint Administrator.
Some of the important jobs performed by any Share Point Administrator would be
- Manage SharePoint Permissions
- Analyze SharePoint Usage and Activity
- Move / Copy Sites
- Clean Up, Manage and Configure SharePoint accounts and sites
- Analyze SharePoint content and storage
- Monitor SharePoint trends
- Set up alerts and Enforce policies
- Audit your SharePoint environment
- Identify governance violations
- And More!!!!
SharePoint Error:Task Update was Not Accepted
Today I ran into a situation where one of the SharePoint Powers users got the message when updating a SharePoint Task Status or completing a workflow assigned to ..
Error:
Task update was not accepted.
Also the user received an email below:
I started to investigate the cause of this unusual behaviour and one thing that came to my mind was to check whether the user is a vaild user or any of his permissions changed. Everything looks good and all the permissions were retained as defined.
After a bit of search I was able to figure out that the User who logged in has a change in the AD account due to various reasons. They changed the User account in AD, created a new account and tied it to the same email account. We use Windows authentication for Sharepoint.
After adding the respective user's new account to the assigned to task, the user was able to update the Sharepoint tasks assigned to him.
Bridging SharePoint’s Faults
SharePoint is a woman-Absolutely!!!
SharePoint is a woman
Yes.. I’ve said it before and I’ll say it again. SharePoint is all woman. Here is why:
“If you don't know why I'm mad, I'm not going to tell you!”
MOSS Installation Pitfalls
The Office SharePoint Server 2007 administrators now have three years of experience in installing MOSS in various environments. I thought to gather here all the common errors faced in MOSS installation process. Most of these are now luckily documented in MS KB articles. This was not case a year or two ago.
Backing up SharePoint-related SQL Server databases
Backing up SharePoint-related SQL Server databases

I recently came across this artice by Ross very nicely explained about the backup of SharePoint related to SQL Server Databases.
SharePoint administrators often make good use of the included tools when backing up and restoring SharePoint-related SQL Server databases. However, these tools cannot be used to restore a full SQL Server installation to the point of failure. To overcome this obstacle, SharePoint administrators should be aware of the following SQL Server elements:
|




