Alerts doesnot work for the changes done

February 6, 2009
SYMPTOMS:
Users do not recieve alerts for changes made to items although “Immediate alerts” are enabled in the site collection.
 
POSSIBLE CAUSES:
• The EventData and ACL columns in the SQL Content Database are not written correctly for this specific content database.
• The record is not processed by the timer service job correctly for this specific content database.
• The record is processed correctly. However, the email delivery mechanism is not working fine. For example, the alert templates fail to be picked up by the SharePoint Timer Service.
• Email server is not working.
 
RESOLUTION:
• Open Central Administration
• Click on Operations and then Timer Job Status
• Made sure the two jobs “Change Log “ and “Immediate Alerts” were showing “Success” and 100%
• Open the command window and navigate to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> and run the following command: stsadm -o getproperty -url <http://siteurl> -pn alerts-enabled
• The expected output is <Property Exist=”Yes” Value=”yes” />
• Make sure the account running the SharePoint Timer Service is the account which has the administrator Full Control permission over the site and the full permission
on the content database.
• Restart the SharePoint Timer Service.
• In content database verify the EventData and ACL are not NULL for the specific content database. This seems to be the key to the problem sometimes.
• Check for the following: C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\BIN>stsadm.exe -o getproperty -url <
http://siteurl> -pn job-immediate-alerts
• Expected result is Property Exist=”No” for that specific site
• Use the following command to reset the schedule
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o setproperty -url <http://siteurl> -pn job-immediate-alerts -pv “every 5 minutes between 0 and 59″
 
ADDITIONAL INFORMATION:
The internal working mechanism of how an alert works in Windows Sharepoint Services 3.0:
• The EventCache table records the SQL level events as they occur and the EventData and ACL columns are not NULL for an alert event.
• There is an alerts timer job that runs periodically to process the records in the EventCache. After the alerts timer job runs, it nulls out the EventData and ACL columns.
• It will log an event into the EventLog table.
 
MORE TROUBLESHOOTING STEPS:
• Open SQL Query Analyzer and connect to the content database of concerned site.
• Run the following query in SQL and copy the result out: Select * from timerlock
If the issue persists, collect the following information:
• Run the following query against the content database of concerned site: Select * from eventcache where EventData is not null
This will show all the subscriptions which have not been processed yet. We can see if there are some alerts which are not processed.
• Run the following query: Select * from eventlog where ListID = ‘xxx’. This would give you the ListID from the EventCache table by running Select * from EventCache and check the documents which correspond to the
concerned listor document library.
• If you cannot find any record in the step 1, please perform the following tests: Get a filemon trace on the Sharepoint server and see if the Timer service picks up the alert template during the whole process.
 
How to collect the filemon trace:
• Create a new item in the list or document library where the alerts should work and start Filemon
•  Run the following query: Select * from eventcache order by EventTime DESC
• Check if the latest result is the one corresponds to your uploaded document. Make sure the EventData and ACL columns are not NULL.
•  After some time, check the EventCache table again to see if the EventData and ACL columns are NULL.
•  If yes, stop Filemon after the EventData and ACL columns are NULL.
•  Analyze the Filemon trace for more information

search doenot work with anonymous access

February 6, 2009

CAUSE:
This is a default behavior seen in SharePoint that anonymous users do not get search results.  Security trimming prevents anonymous users from seeing items in search by default.

RESOLUTION:
Enable “Always index all ASPX pages on this site” on the site collection.

Perform the following steps:
• Open the SharePoint Site
• Click on Site Actions, Site Settings and Modify Site Settings
• Click on Search Visibility
• Select the option that says “Always index all ASPX pages on this site”
• Perform a full crawl again
• Log into the site anonymously and perform search and you should get search results now

Unable to Delete Shared Services

February 6, 2009

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.

People picker: Stsadm property (Office SharePoint Server)

September 8, 2008

stsadm -o setproperty -propertyname peoplepicker-searchadforests

   -propertyvalue <valid list of forests or domains>    [-url] <URL>

The syntax for the getproperty operation is:

stsadm -o getproperty  propertyname peoplepicker-searchadforests    [-url] <URL>

 
You can substitute -pn for -propertyname and -pv for -propertyvalue.

Search results for person objects in

September 8, 2008

In the User Profile Properties, the Index check box has been cleared for the Id Property.
(SSP admin site–>User profile and properties–>View Profile properties, click on the Edit button for the ID property)

solution

Browse to SSP admin site–>User profile and properties–>View Profile properties, click on the Edit button for the ID property and select ‘Indexed’

September 8, 2008

Specify user account and password from a one way trust

To specify the user name and password from a one-way trust, so that People Picker can look up this information, use the following syntax:

stsadm -o setproperty -url http://<server:port&gt; -pn peoplepicker-searchadforests -pv “forest:contoso.corp.com;domain:bar.contoso.corp.com”, <LoginName>, <Password>

peoplepicker

September 8, 2008

The syntax for the setproperty operation is:

stsadm -o setproperty

   -propertyname peoplepicker-searchadforests -propertyvalue <valid list of forests or domains> [-url] <URL>
The syntax for the getproperty operation is:

stsadm -o getproperty propertyname peoplepicker-searchadforests [-url] <URL>

Note: 
You can substitute -pn for -propertyname and -pv for -propertyvalue.

Hello world!

August 21, 2008

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!


Follow

Get every new post delivered to your Inbox.