THIS IS NOT SUPPORTED AND ONLY FOR DEV-ENVIRONMENTS TO TROUBLESHOOT PROBLEMS:
– get overview ——————–
select
msscrawlurllog.lasttouchstart as Time
, msscrawlurllog.displayurl as URL
, DocName = REPLACE ( RIGHT(msscrawlurllog.displayurl, CHARINDEX(‘/’, REVERSE(msscrawlurllog.displayurl))-1 ) , ‘%20′, ‘ ‘)
, msscrawlurllog.errorid as Error
, msscrawlerrorlist.errormsg as Description
FROM dbo.msscrawlurllog with (nolock)
inner join dbo.msscrawlerrorlist with (nolock) on msscrawlurllog.errorid = msscrawlerrorlist.errorid
order by msscrawlurllog.lasttouchstart
– show latest crawler stats———————
SELECT [HostID]
,[HostName]
,[SuccessCount]
,[ErrorCount]
,[WarningCount]
FROM [dbo].[MSSCrawlHostList] with (nolock)
In my case i found following error through above TSQL:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (The item was deleted because it was either not found or the crawler was denied access to it.)
Solution:
Solution was to set following registry-key in windows 2008 :
Disable the loopback check
Follow these steps:
|
1.
|
Click Start, click Run, type regedit, and then click OK.
|
|
2.
|
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
|
|
3.
|
Right-click Lsa, point to New, and then click DWORD Value.
|
|
4.
|
Type DisableLoopbackCheck, and then press ENTER.
|
|
5.
|
Right-click DisableLoopbackCheck, and then click Modify.
|
|
6.
|
In the Value data box, type 1, and then click OK.
|
|
7.
|
Quit Registry Editor, and then restart your computer.
|
http://svengillis.blogspot.com/2008/10/access-denied-when-crawling-moss.html
After setting the registry key start Crawler with stsadm.exe manually:

If you need to troubleshoot kerberos problems with SharePoint, Reporting Services… you need an overview of all defined HTTP SPNs in Active Directory.
You can use the the following command in a dos-box to quickly output all SPNs to a textfile with the windows tool “LDIFDE.EXE”:
ldifde.exe -f check_spn.txt -t 3268 –d “” -l serviceprincipalname -r “(servicePrincipalName=HTTP*)” -p subtree
Here’s a sample output:

If ldifde.exe i not installed on your server:
Windows 2008
–> Add Remote AD Management Tools (RSAT-ADDS) Feature with Servermanager or:
- Click Start, Run, and in the Open field run ‘ServerManagerCmd -i RSAT-ADDS‘
Windows 2003 –> Install Support Tools from windows server CD or download:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&displaylang=en
Bei DB-Applikationen ist es eine gute Praxis den Namen des SQLServer grundsätzlich nicht direkt im Connectionstring/Config zu hinterlegen sondern über einen „SQL Alias“ zu arbeiten!Muss der SQLServer irgendwann umgezogen werden oder im Disaster/Ausfallszenario auf einen anderen SQL Server umgeleitet werden kann man, für die Anwendung transparent, dann einfach den SQL Alias anpassen. Ein SQL Alias ist übrigens NICHT zu Verwechseln mit einem DNS-Alias(Host/CNAME Eintrag)!
Microsoft empfiehlt in folgendem Artikel auch explizit das Anlegen von SQL Aliasen vor dem eigentlichen SharePoint Setup:
Storage and SQL Server capacity planning and configuration (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/cc298801.aspx
Achtung:
Ein SQL Alias kann entweder über das, auf jedem Windows Client/Server vorhandene, Tool CLICONFG.EXE eingerichtet werden oder über „SQL Server Configuration Manager“ (wenn SQL Client explizit installiert wurde).
In beiden Fällen sollte man folgendes zu beachten: Auf 64Bit Systemen muss der Alias für 64BIT UND 32BIT separat konfiguriert werden sonst funktionieren nicht alle Anwendungen (in Abhängigkeit davon ob die Anwendung 32bit oder 64bit SQL-Provider verwendet)!
Auf Systemen ohne SQL Installation findet man die Tools hier:
32Bit -> C:\WINDOWS\System32\cliconfg.exe
64Bit -> C:\WINDOWS\SysWOW64\cliconfg.exe
Auf Systemen mit SQL Installation geht es etwas komfortabler über den “SQL Server Configuration Manager“ (Start>Programme>SQL Server>Config Tools..):

Weitere Infos:
http://www.eggheadcafe.com/software/aspnet/31792482/alias-not-working-on-some-machines.aspx
http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/#
SharePoint Outlook Connector makes it easier for outlook users to upload emails to SP and attach SP documents to an email message . You’ll no longer have to save your email to desktop and upload from SP UI or download SP documents to your drive and attach them to your email.
- Saving email meta data to SharePoint document item (title, to, from etc) functionality has been added
- SharePoint 2010 support has been added
- Saving email message as list item and attachments as attachment of the list item functionality has been added
CodePlex:SharePoint Task List Email Reminders (WSS 3.0, MOSS2007, SharePoint 2010)
Similar to OOTB Alerts; but emails are triggered by task due date.
Allows task list owners to automatically send email reminders when tasks are due.
One email is sent per list, per assignee each day, if tasks meet this criteria:
1) task status is open
2) it is assigned and assignee has an email address
Emails are sent out daily and only when assignee has tasks in the list that are:
1) due today
2) due in two days
3) two days past due
AD User Editor is a Webpart for MOSS 2007 that allows to easily modify any profile property of any person in Active Directory. Il can also be configured as "self-service" for a user to be able to modify his properties only.
- 6 different types of properties fields: ReadOnly, Simple TextBox, DropDownList/ListBox (with predefined values), People Picker, Date Picker with calendar.
- Multi-domain compatible.
- Nearly Any Active Directory property can be easily added or removed of the edit form, directly trough the webpart configuration (nothing "hard-coded").
- SharePoint "look & feel"
- Available in English, Spanish and French
Zur Einführung hier ein paar Links zum Thema:
SharePoint Logging Database Exposed
SharePoint Tagging Exposed
Über TSQL Abfrage auf die MMS DB anzeigen wer wann welche Tags erstellt hat:
SELECT
[ObjectUniqueId]
,[ObjectId]
,[Label]
,[Owner]
,[CreatedTime]
,[LastModifiedTime]
FROM [ECMChangeLog] ecl, ECMTerm t, ECMTermLabel etl
where
ChangeType = 1
and
ecl.ObjectUniqueId = t.UniqueId
and
ecl.ObjectId = etl.TermId

to be continued…
TSQL Experten lieben SharePoint 2010. Dort gibt es viel mehr Datenbanken als in 2007 mit jeder menge nützlichen Informationen..so auch in der SSS Datenbank
Was ist SSS:
The Secure Store Service replaces the Microsoft Office SharePoint Server 2007 Single Sign On feature. Secure Store Service is a shared service that provides storage and mapping of credentials such as account names and passwords. It enables you to securely store data that provides credentials required for connecting to external systems and associating those credentials to a specific identity or group of identities. The SSS Database provides storage and mapping of credentials such as account names and passwords.
DB Schema of Secure Store Service DB
Additional Information for the DB can be found here: [MS-SSDPS]: Secure Store Database Protocol Specification
The DB can log informations for troubleshooting and compliance purposes. THIS IS NOT SUPPORTED AND ONLY FOR DEV-ENVIRONMENTS.
HowTo enable DB-Auditing:
1. Connect with SQL Server Management Studio (SSMS) to Secure_Store_Service….DB
2. Run following command: UPDATE dbo.SSSConfig SET EnableAudit = 1
3. Open DOS-Box and run: IISRESET /NOFORCE
4. Audit Data should now be logged to table dbo.SSSAudit
5. You can run following query or create as VIEW for easier analysis of this table:
SELECT TOP 1000
[AuditDateTime]
,[UserIdentityClaimType]
,[UserIdentityClaimValue]
,[UserIdentityClaimIssuer]
– ,[ActionType]
,[ActionTypeText] = CASE [ActionType]
WHEN 101 THEN ‘A target application has been created.’
WHEN 103 THEN ‘A target application has been updated.’
WHEN 105 THEN ‘A target application has been deleted.’
WHEN 107 THEN ‘The user claim (2) for an individual target application has been retrieved.’
WHEN 109 THEN ‘The group claims (2) for a group target application has been retrieved.’
WHEN 111 THEN ‘The claims (2) for the group of SSS users that are administrators for a target application have been retrieved.’
WHEN 113 THEN ‘The claims (2) for ticket redeemers for a target application have been retrieved’
WHEN 115 THEN ‘The definition for a target application has been retrieved.’
WHEN 117 THEN ‘The fields for a target application have been retrieved.’
WHEN 119 THEN ‘The definitions for all target applications have been retrieved.’
WHEN 121 THEN ‘The credentials for an SSS user have been set.’
WHEN 123 THEN ‘The credentials for a group target application have been set.’
WHEN 125 THEN ‘The credentials for an SSS user for a target application have been deleted.’
WHEN 127 THEN ‘The credentials for an SSS user for all target applications have been deleted.’
WHEN 128 THEN ‘An SSS ticket was issued.’
WHEN 130 THEN ‘An SSS ticket was redeemed.’
WHEN 132 THEN ‘The credentials for an SSS user have been retrieved.’
WHEN 134 THEN ‘The restricted credentials for an SSS user have been retrieved.’
WHEN 136 THEN ‘A SSS user has set his/her own credentials in the SSS store.’
ELSE CAST([ActionType] as nvarchar(100))
END
,[ActionResultCode]
,[ApplicationName]
,[PartitionId]
,[SubscriptionId]
,[Info1]
,[Info2]
,[Info3]
,[Info4]
,[Info5]
,[Machine]
FROM [dbo].[SSSAudit]
order by AuditDateTime DESC
SharePoint bietet Dokumentenbiliotheken von Typ “Data Connection Library” als Möglichkeit Verbindungsinformationen zu Datenquellen wie SQL Server Datenbanken, Analysis Services Cubes… zentral abzulegen und damit einfach für die Endanwender bekannt/zugänglich zu machen..
Problem:
Standardmäßig sind diese Bibliotheken nicht in dem Office-Client direkt sichtbar/verfügbar. Beispielsweise muss man in Excel erst die URL der SharePoint Library eingeben um auf eine dort abgelegte Datenverbindung zugreifen zu können:

Lösung:
To enable data connection libraries to display directly in the client application, the data connection library must be published from the server to the client computer. The client computer must be associated with that server, or a registry key must be set directly.
Option 1: Konfiguration SharePoint –> http://technet.microsoft.com/en-us/library/cc262899.aspx
Option 2: Funktioniert auch mit WSS! Registy Key manuell oder per Group Policy an den Clients setzen:
1. Navigate to the folder at HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Server Links\Published.
2. If the Published folder does not exist, you will need to create it. In this case, right-click the Server Links folder and select New Key, as shown I the following figure. Name the Key Published.
3. Create a new string value for the Published folder by right-clicking inside the folder and selecting New String value, as shown in the following figure.
4. Name the string the friendly name of the data connection library.
5. Right-click the string value, and select Modify, as shown in the following figure.
6. Enter the HTTP path to the data connection library in the Edit String dialog box, as shown in the following figure.

7. Click OK.
Full article: http://technet.microsoft.com/en-us/library/cc262899.aspx
Business Connectivity Services (BCS)
BCS ist die überarbeitete Version von SharePoint 2007 Business Data Catalog (BDC). Mit BCS ist es nun möglich externe Daten aus SQL Server, CRM, SAP, etc. bidirektional in SharePoint zu integrieren. So lassen sich beispielsweise Kundenkontaktdaten aus dem CRM System als Liste in SharePoint bereitstellen. Wird die Liste in SharePoint aktualisiert erfolgt auch automatisch eine Aktualisierung im angebundenen CRM System. Zusätzlich besteht noch die Möglichkeit über MS Workspace die BCS Inhalte offline zu nehmen und damit zu arbeiten. Bei der nächsten Onlineverbindung werden die Daten dann automatisch mit SharePoint und den angebundenen Quellen synchronisiert.
Die Entwicklung/Konfiguration von BCS Anwendungen kann bei einfachen Anforderungen direkt durch den Endanwender mit dem SharePoint Designer durchgeführt werden. Für komplexere Anwendungen können Entwickler Visual Studio nutzen.
Chart Web Parts & Status Indicators
Die neuen bzw. überarbeiteten Chart Webparts bieten ebenfalls einen einfach bedienbaren “BI Self Service” für SharePoint-Anwender. Dadurch können Endanwender ohne tiefe Kenntnisse, Daten aus SharePoint-Listen und Excel Services visualisieren und sich somit Dashboads zusammenbauen:
