Following Text from: http://technet.microsoft.com/en-us/library/ff730261.aspx
Friday, February 24, 2012
MySites orphaned / old memberships not updated
Run the command stsadm -o sync -listolddatabases 1 You should then get a list of database GUID
Run the command stsadm -o sync -deleteolddatabases 1 This will remove the record from the SSP database but will not touch the actual Content Database.
(Run this commands as a User which has Full Control to the User Profile Service Application!)
Run the command stsadm -o sync -deleteolddatabases 1 This will remove the record from the SSP database but will not touch the actual Content Database.
(Run this commands as a User which has Full Control to the User Profile Service Application!)
Wednesday, February 22, 2012
“Object not found” error in search service crawl Logs
My problem was that the crawler jobs "Content Source" was the "Default Zone" without alternate access mapping.
As soon I've modified the Content Source to the AAM Zone, the error was gone.
eg for my Content Source:
Not working: http://intranet (Default Zone)
Working: http://intranet.domain.lcl (AAM)
As soon I've modified the Content Source to the AAM Zone, the error was gone.
eg for my Content Source:
Not working: http://intranet (Default Zone)
Working: http://intranet.domain.lcl (AAM)
Monday, February 20, 2012
Necessary Firewallports if SharePoint is in a DMZ using a One-Way-Trust
Direction: ALL SharePoint Servers --> Domain Controllers in Trusted Domain
53/TCP/UDP --> DNS
88/TCP/UDP --> Kerberos
135/TCP --> RPC
389/TCP/UDP --> LDAP
3286/TCP --> LDAP GC
Direction: ALL SharePoint Servers --> SMTP Servers in Trusted Domain
25/TCP --> SMTP
Direction: Clients --> ALL SharePoint FrontEnd Servers
80 or 443 /TCP
Direction: Admin Clients --> ALL SharePoint Application Servers
e.g.:9090/TCP for Central Administration
53/TCP/UDP --> DNS
88/TCP/UDP --> Kerberos
135/TCP --> RPC
389/TCP/UDP --> LDAP
3286/TCP --> LDAP GC
Direction: ALL SharePoint Servers --> SMTP Servers in Trusted Domain
25/TCP --> SMTP
Direction: Clients --> ALL SharePoint FrontEnd Servers
80 or 443 /TCP
Direction: Admin Clients --> ALL SharePoint Application Servers
e.g.:9090/TCP for Central Administration
First Query after Crawl takes up to 60 seconds
You have SharePoint 2010 SP1 CU12:
Every time you are performing a search query on any web application the first query always takes about 60 seconds.
When you are performing the second search query for the same term or another term the query response time is under 3 seconds.
Every time you are performing a search query on any web application the first query always takes about 60 seconds.
When you are performing the second search query for the same term or another term the query response time is under 3 seconds.
Thursday, February 16, 2012
Activate a Feature on all SiteCollections
$FeatureId = $(Get-SPFeature -limit all | where {$_.displayname -eq "OfficeWebApps"}).Id
Get-SPSite -limit ALL |foreach{Enable-SPFeature $FeatureId -url $_.URL }
Get-SPSite -limit ALL |foreach{Enable-SPFeature $FeatureId -url $_.URL }
Wednesday, February 15, 2012
Search service is not able to connect to Administration component server
$AdminComponentServer = "ServerName"
$varInstance = Get-SPEnterpriseSearchServiceInstance -local
Start-SPEnterpriseSearchServiceInstance -Identity $AdminComponentServer
$varSearchApp = get-spenterprisesearchserviceapplication
set-spenterprisesearchadministrationcomponent –searchapplication $varSearchApp –searchserviceinstance $varInstance
...Wait a few minutes.....
(http://blogs.technet.com/b/poojk/archive/2011/11/28/sharepoint-2010-search-service-is-not-able-to-connect-to-administration-component-server.aspx)
$varInstance = Get-SPEnterpriseSearchServiceInstance -local
Start-SPEnterpriseSearchServiceInstance -Identity $AdminComponentServer
$varSearchApp = get-spenterprisesearchserviceapplication
set-spenterprisesearchadministrationcomponent –searchapplication $varSearchApp –searchserviceinstance $varInstance
...Wait a few minutes.....
(http://blogs.technet.com/b/poojk/archive/2011/11/28/sharepoint-2010-search-service-is-not-able-to-connect-to-administration-component-server.aspx)
Monday, February 13, 2012
Subscribe to:
Posts (Atom)