Stop SharePoint Completely or stopping the farm

19/03/2013 Leave a comment

For Wss 3.0:

Stop the farm by following these steps:

1. in the Services snap-in, stop the following services:

  • Windows SharePoint Services Administration service
  • Windows SharePoint Services Search service
  • Windows SharePoint Services Timer service
  • Windows SharePoint Services Tracing service
  • Windows SharePoint Services VSS Writer service

2.    at the command prompt, type iisreset /stop.

Do it for all SharePoint installed servers in your farm.
http://technet.microsoft.com/en-us/library/cc512723(v=office.12).aspx

For Moss 2007

Stop the farm by following these steps:

1.  in the Services snap-in, stop the following services:

  • Microsoft Single Sign-On service
  • Office Document Conversions Launcher service
  • Office Document Conversions Load Balancer service
  • Office SharePoint Server Search service
  • Windows SharePoint Services Administration service
  • Windows SharePoint Services Search service
  • Windows SharePoint Services Timer service
  • Windows SharePoint Services Tracing service
  • Windows SharePoint Services VSS Writer service

2. On the server that is running the Central Administration Web site, at the command prompt, type iisreset /stop.
Do it for all SharePoint installed servers in your farm.
http://technet.microsoft.com/en-us/library/cc512725(v=office.12).aspx

For SharePoint Foundation 2010

1. in the Services snap-in, stop the following services:

  • SharePoint 2010 Administration
  • SharePoint 2010 Timer
  • SharePoint 2010 Tracing
  • SharePoint 2010 User Code Host
  • SharePoint 2010 VSS Writer
  • SharePoint Foundation Search V4
  • SharePoint Server Search v4
  • World Wide Web Publishing Service

2. at the command prompt, type iisreset /stop.
Do it for all SharePoint installed servers in your farm.
http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx

For SharePoint Server 2010

1.  in the Services snap-in, stop the following services:

  • SharePoint 2010 Administration
  • SharePoint 2010 Timer
  • SharePoint 2010 Tracing
  • SharePoint 2010 User Code Host
  • SharePoint 2010 VSS Writer
  • SharePoint Foundation Search V4
  • World Wide Web Publishing Service
  • SharePoint Server Search 14
  • Web Analytics Data Processing Service
  • Web Analytics Web Service

Not:  The final two services are part of the Web Analytics service application. If you are running the Web Analytics service application and choose to rename your server, you must also reconfigure the Web Analytics database locations. For details, see To reconfigure Web Analytics database locations .

2. On the server at the command prompt, type iisreset /stop.
Do it for all SharePoint installed servers in your farm.
http://technet.microsoft.com/en-us/library/cc512725(v=office.14).aspx

For SharePoint 2013

1. in the Services snap-in, stop the following services:

  • SharePoint 2013 Administration
  • SharePoint 2013 Timer
  • SharePoint 2013 Tracing
  • SharePoint 2013 User Code Host
  • SharePoint 2013 VSS Writer
  • World Wide Web Publishing Service
  • SharePoint Server Search

2. On the server that is running the SharePoint Central Administration website, at a command prompt, type iisreset /stop.
Do it for all SharePoint installed servers in your farm
http://technet.microsoft.com/en-us/library/cc512725(v=office.15).aspx

Advertisement

Filed under Sharepoint Tagged with , , , , , , , , ,

How to delete the Default SSP in SharePoint 2007

01/02/2012 Leave a comment

There is no way to delete default SSP from Sharepoint Central Administration site via using this gui.
So stsadm command has help us for removing Default SSP

1) Open a command prompt
2)change your path to drive:\program files\common files\microsoft shared\web server extentions\12\BIN
3) Run fallowing command:
stsadm -o deletessp -title SharedServices1 -force

Have a nice Tips&Tricks

Filed under Sharepoint Tips & Tricks Tagged with , , , , , ,

MOSS2007 + SP2 (Turkish) Calculated Column not accepting METİN formula

13/01/2012 Leave a comment

Hi Everyone,

if you try suggested formula  for Sharepoint Calculated Column (MOSS2007 with Turkish Language Pack)  on fallowing official article http://office.microsoft.com/tr-tr/sharepoint-foundation-help/HA010379915.aspx and the help document of wss like
=”Ekstre tarihi: “&METİN([Sütun2], “gg-aa-yyyy”)

is not working  and getting error of “Söz dizimi hatası”

Cause :Should be a documentation error .

The formula should be “METNEÇEVİR” instead of “METİN” and the splitter should be “;” instead of “,”

Here is the correct version of formula:
=”Ekstre tarihi: “&METNEÇEVİR([Sütun2];”gg-aa-yyyy”)

You may getting some errors for other formulas please read fallowing warning and always keep in mind:

“All example formulas in this topic use commas “,” as the parameter delimiter character. In some countries, the comma is reserved for use as the decimal mark. In such countries, users creating a calculated field must use semi-colons “;” as the delimiter character. Regardless of which character is used when the field is created, the formula works on lists in SharePoint websites anywhere in the world. SharePoint automatically changes the delimiter character to the one that is appropriate for the language/culture of the current page. For example, suppose the following formula is created on a website whose culture setting is fr-fr (France): =IF(Number1>Number2;5;10). If the website’s culture is then changed to en-us (United States), the formula changes automatically to: =IF(Number1>Number2,5,10).”
http://msdn.microsoft.com/en-us/library/bb862071.aspx

Filed under Sharepoint Tagged with , , , , , ,

MOSS2007 viewlsts.aspx reports that item count mismatch with document library item count.

11/10/2011 Leave a comment

This is very common misunderstanding of sharepoint libraries. Draft files can be counted as viewlsts.aspx reports. This meas documents count in document library can be different than actual count also item level security can provide this difference. But the real problem is even if System Admin or Site Administrator somehow can not able to see that documents in document library.

In our scenario we have 14 files that reported by viewlsts.aspx page , but when we login as system admin and browse the library the total file count which is same visible file count , is 13.And this problem is related with Sharepoint 2007 Sp1 which is currently not supported state. (So please upgrade your system as soon as possible to SP2) .So some of files should be check out to a user(s) . Ok than we checked the Document Library Settings->Manage Checked Out files and see nothing ? that’s wierd.

I am sure that the problem checkout to user so How could we find the users ? For troubleshooting issue we have to connect sharepoint db just for select. Don’t forget that  do not change anything in Sharepoint DB this kind of operations are not supported.

First We select all lists for finding Guid of the issued list.

select * from lists where  tp_Title  like ‘%Network Trainings%’
we noted the ListId Guid and SiteId guid from query results :

ListId: B08577CD-A418-4E08-8F6D-33365082FF05
SiteId: E39EF3B7-5679-45DE-8565-97D9C6F9CAB3

Than Getting all files for this list from AllDocs table:

select LeafName,DocLibRowId,[Type],Version,UIVersion,Dirty,IsCurrentVersion,[Level],DraftOwnerId from alldocs where listid=‘B08577CD-A418-4E08-8F6D-33365082FF05’

On results we compre the files for defining which file can not be able to seen by System Admin account:

“BGP  trainings.doc” ‘s DraftOwenerId is set to 960

The userid has changed by site collection so query userinfo table like this.

select * from userinfo where tp_SiteID=‘E39EF3B7-5679-45DE-8565-97D9C6F9CAB3’ and  tp_id=960
Resutls say : Domain****\a90003342 is draftowner

Now you can find the user account from results. we could not find the cause why the system admin account cant see the documents in “Manage Checked out files” also i don’t intend to find reason for unsupported version. We loged in with this user account and able to see all documents.So this is not a common scenario , i always suggest that use latest version of sharepoint sp and cu.

Filed under Sharepoint Tagged with , , , , ,

Moss 2007 – Troubleshooting incoming email problems

15/07/2011 Leave a comment

Windows SharePoint Services 3.0 uses e-mail handlers to route incoming e-mail from virtually any e-mail client to a list in your SharePoint site. Each e-mail-enabled list is associated with a unique e-mail address, and each e-mail handler is associated with a particular list type.

For troubleshooting incoming e-mails

1) Check Central Administration ->  Operations -> Incoming E-Mail Settings  is correctly configured.

2) Check your library – Settings-> Incoming E-mail settings is correctly configured.

If you correctly enable Incoming emails settings, you should have also an installed smtp server feature (for Windows server 2008 r2)
At this point i want to tell about the process of an incoming email distribution. When you send an email to a sharepoint list first your mail is delivered by your mail server and pass through the your sharepoint machine smtp server. It stored c:\inetpub\mailroot\drop folder with a file format of eml. The timer job of “Windows SharePoint Services Incoming E-Mail” is monitoring your mailroot\drop folder and when it find an email it process this mail and deliver the attachments to destination document library.

3) Check your Mailroot/drop folders stores eml files.

Incoming e-mail uses the Microsoft SharePoint Directory Management Service to connect SharePoint sites to the directory services used by your organization. If you enable the Microsoft SharePoint Directory Management Service, users can create and manage distribution groups from SharePoint sites. SharePoint lists that use e-mail can then be found in directory services, such as the Address Book. You must also select which distribution group requests from SharePoint lists require approval. The Microsoft SharePoint Directory Management Service can be installed on a server in the farm, or you can use a remote Microsoft SharePoint Directory Management Service.

4) If you are using Microsoft SharePoint Directory Management Service  Check Microsoft SharePoint Directory Management Service is running.

5) Check your sharepoint timer service identity has correct rights on mailroot folders. (you can check it from services.msc)

6) Trace the log messages using ULSViewer program with a filter of “category equals E-Mail”

For more information of Configuring Incoming E-Mail Settings:
http://technet.microsoft.com/en-us/library/cc287879(office.12).aspx

 

Filed under Sharepoint Tagged with , , , ,