Ingo Karstein's Blog @ kenaro

Walkthrough: Create a simple BCS connection with SharePoint Designer 2010

First: You need a SharePoint 2010 platform. You can use Foundation because BCS = Business Connectivity Services – former BDC = Business Data Catalog in SharePoint 2007 – included in this “free” edition.

Second: You need a database for the walkthrough. You can use Microsoft’s sample database “AdventureWorks”. You can download them here: http://msftdbprodsamples.codeplex.com – I’ll use the database “AdventureWorksLT2008R2”: This is the lite version of the sample database.

Third: The BCS Application of SharePoint 2010 must be configured. – Create this application in the Central Administration –> Manage Service Applications

Fourth: You need a Site Collection. – In my sample it’s “http://sharepoint.local”

1. Open SharePoint Designer 2010 (“SPD”)

Open the site collection.

2. Click “External Content Types” in the Site Objects Navigation.

3. Click “External Content Type” in the Group “New” on the Ribbon.

In the “External Content Type Information” group click the text message “New external content type” beside the label “Name”.

Enter “AdventureWorks SalesOrderDetails”.

After that the same text will appear beside “Display Name”.

4. Click on the text message beside “External System”:

5. Click “Add Connection”

Select “SQL Server” in the drop down “Data Source Type” in the dialog.

On the next dialog enter the Database Server Name, Database Name and the Name of the new connection. Select “Connect with User’s Identity”.

6. Now the Data Source Explorer view is filled:

Scroll down and select the table “SalesOrderDetails” in the tree view.

Right click on “SalesOrderDetails”. Click on “Create All Operations”.

7. You get this dialog.

Click “Next”.

Click “Finish”.

8. Click “Save” or Ctrl+S.

9. After the upload click on “Create Lists & Form”.

Now the list will be created:

10. Open the browser and navigate to the site collection. You’ll see the previously created list:

11. Open the list view.

12. You may get the error “Access denied by Business Data Connectivity”.

13. Then open “Central Administration” –> Manage Service Application –> Business Connectivity Service Application

Select the BCS application. Open the context menu. Click “Set Permissions”.

On the next dialog add all users that should have access to the BCS app and it’s lists.

Click “OK”.

14. Try to open the list on the site collection.

15. You may get the error message “Login failed for user NT AUTHORITYIUSR”.

This means: IUSR account has no rights to access the AdventureWorks database.

Open SQL Server Management Studio. Open “Security” –> “Logins” (at server level).

Add “NT AUTHORITYIUSR” as new login.

On the “User Mapping” tab change the security settings:

Click “OK”.

16. Open the list again.

Now it works (for me).

Walkthrough: How to move or copy a SharePoint Designer 2010 List Workflow to another list on the same site or another site.

I had to develop a Holiday Approval Workflow with SharePoint Designer 2010. – I used a “List Workflow”. – Bad mistake! – It’s not possible to copy this kind of workflow to another list on the same site or another site.

I thought I could use the “Export to Visio” functionality with the workflow at my development site and the “Import from Visio” functionality at the destination list. – That’s impossible. You get this message:

(“This workflow cannot be imported because it was created in SharePoint Designer for a different site, or the original workflow has been moved or deleted. To move a workflow between sites, use Save as Template (.wsp file) instead of a Visio workflow drawing.”)

You cannot “Save as Template” because it’s a “List Workflow”.

Okay. – I’ve found a workaround.

Let’s do it in detail.

1. Create a site collection “http://sharepoint.local/sites/dev”.

2. Open SharePoint Designer 2010. Open the previously created site.

3. Open the “Workflows” view.

4. On the Ribbon click “List Workflow” and select “Shared Documents”. – We will create a workflow for the list “Shared Documents”.

Name the workflow “Workflow 1”. Leave “Description” empty.

5. Insert any workflow steps you like.

6. Change the workflow settings. Select “Task List” and “History List”.

7. Click “Publish” to publish the workflow Winking smile

8. Click “Export to Visio”. Save to Workflow as .vwi file, e.g. on the desktop.

9. Let’s test the workflow. – I’ve created a text file “test.txt” on the desktop. Now I upload the file to the “Shared Documents” library of “http://sharepoint.local/sites/dev”.

Open the item context menu. Click “Workflow”.

Manually start the “Workflow 1”.

*

Click “Start”.

In the list view you see the workflow status.

Click on the status. In my case it’s “Completed”.

The workflow history says “Workflow executed” as specified in the workflow definition above.

10. Okay. Let’s copy the workflow to the production site “http://sharepoint.local”. – A simple “import” is impossible, because it’s a list workflow… Follow my steps.

11. Start the SharePoint Designer 2010 and open the site “http://sharepoint.local”.

12. On the Ribbon click “List Workflow” and select “Shared Documents”. – We will create a workflow for the list “Shared Documents”.

Name the workflow “Workflow 1 Production”. Leave “Description” empty.

11. Do not add any workflow step!

12. Click on “Workflow Settings” menu item on the Ribbon.

13. Click “Publish” to publish the (empty) workflow.

14. After publishing click “Export to Visio” and save the file as “workflow 1 production.vwi” on the desktop.

15. Open a Windows Explorer. Select “Desktop”. You see both “.vwi” files.

16. Add the extension “.zip” to both files.

17. Open both “.vwi.zip” files. You see:

18. Copy “workflow.xoml.wfconfig” from “workflow 1 production.vwi.zip” to “workflow 1.vwi.zip”.

19. Now remove the “.zip” extension from both files. You’ll get two “.vwi” files.

20. In SharePoint Designer 2010 open the site “http://sharepoint.local”.

21. Click “Import from Visio” and select “workflow 1.vwi”

Click “Next”. (Maybe you get a message: “You must close all views of this workflow before importing this file.” Then stop the import. Close all views of the Workflow and restart from Step 21.)

22. Now you see the this window:

That it!

23. Now the workflow designer opens:

24. Now you can publish the workflow and test it…

25. Be as happy as me with that !!!

PS: Of course you can use any library as destination. In the sample above it does not have to be “Shared Documents” on “http://sharepoint.local” It could be another list or library as well!

Enumerate, add, update and remove SQL Server aliases by using PowerShell

I’ve created a PowerShell script for adding, updating, enumerating und removing SQL Server aliases. – You can use the script to create/remove/enumerate both 32bit und 64bit aliases in one step or only 32bit or only 64bit aliases.

You can change this script into a PowerShell module. Just see the comment below inside the script.

I’ve tested the script on Windows Server 2008 R2 with SQL Server 2008 R2 on it. – Please post your comments how it works on other systems.

Here is the script:

#region Author: Ingo Karstein / Blog: blog.kenaro.com

SharePoint Warm Up with PowerShell

Every SharePoint farm needs a warm up – After giving the IIS 7.5 Application Warmup a chance… I had to do it in another way…

I created a warmup script in PowerShell.

Here it is…

[Update 2011/08/03] New script with “timeout” capability: https://blog.kenaro.com/2011/08/03/sharepoint-warm-up-now-with-timeout/

$urls= @("http://sharepoint.local", "http://anothersharepoint.local")

New-EventLog -LogName "Application" -Source "SharePoint Warmup Script" -ErrorAction SilentlyContinue | Out-Null

$urls | % {
    $url = $_
    try {
        $wc = New-Object System.Net.WebClient
        $wc.Credentials = [System.Net.CredentialCache]::DefaultCredentials
        $ret = $wc.DownloadString($url)
        if( $ret.Length -gt 0 ) {
            $s = "Last run successful for url ""$($url)"": $([DateTime]::Now.ToString('yyyy.dd.MM HH:mm:ss'))" 
            $filename=((Split-Path ($MyInvocation.MyCommand.Path))+"lastrunlog.txt")
            if( Test-Path $filename -PathType Leaf ) {
                $c = Get-Content $filename
                $cl = $c -split '`n'
                $s = ((@($s) + $cl) | select -First 200)
            }
            Out-File -InputObject ($s -join "`r`n") -FilePath $filename
        }
    } catch {
          Write-EventLog -Source "SharePoint Warmup Script"  -Category 0 -ComputerName "." -EntryType Error -LogName "Application" `
            -Message "SharePoint Warmup failed for url ""$($url)""." -EventId 1001

        $s = "Last run failed for url ""$($url)"": $([DateTime]::Now.ToString('yyyy.dd.MM HH:mm:ss')) : $($_.Exception.Message)" 
        $filename=((Split-Path ($MyInvocation.MyCommand.Path))+"lastrunlog.txt")
        if( Test-Path $filename -PathType Leaf ) {
          $c = Get-Content $filename
          $cl = $c -split '`n'
          $s = ((@($s) + $cl) | select -First 200)
        }
        Out-File -InputObject ($s -join "`r`n") -FilePath $filename
    }
}

It will write a log file to the same directory as the script itself is stored.

Exceptions will be written to the event log!

Run it as “Scheduled Task” with the farm account credentials. – Check “Run with Highest Priviledges” !!!

Be sure this account can write to the scripts directory (for logging purpose)!

You can use this XML file for quick importing the scheduled task defintion. Therefore the script must be placed in the folder “C:Program FilesSharePoint Warmup”. The script itself must be named “sharepointwarmup.ps1”.

 <?xml version="1.0" encoding="utf-16"?>

 <Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">

   <RegistrationInfo>

     <Date>2011-01-26T00:00:37.2455395</Date>

     <Author>DOMAIN\ikarstein</Author>

   </RegistrationInfo>

   <Triggers>

     <CalendarTrigger>

       <Repetition>

         <Interval>PT5M</Interval>

         <Duration>P1D</Duration>

         <StopAtDurationEnd>false</StopAtDurationEnd>

       </Repetition>

       <StartBoundary>2011-01-26T00:00:37.2455395</StartBoundary>

       <Enabled>true</Enabled>

       <ScheduleByDay>

         <DaysInterval>1</DaysInterval>

       </ScheduleByDay>

     </CalendarTrigger>

   </Triggers>

   <Principals>

     <Principal id="Author">

       <UserId>DOMAIN\spfarm</UserId>

       <LogonType>Password</LogonType>

       <RunLevel>HighestAvailable</RunLevel>

     </Principal>

   </Principals>

   <Settings>

     <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>

     <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>

     <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>

     <AllowHardTerminate>true</AllowHardTerminate>

     <StartWhenAvailable>false</StartWhenAvailable>

     <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>

     <IdleSettings>

       <StopOnIdleEnd>true</StopOnIdleEnd>

       <RestartOnIdle>false</RestartOnIdle>

     </IdleSettings>

     <AllowStartOnDemand>true</AllowStartOnDemand>

     <Enabled>true</Enabled>

     <Hidden>false</Hidden>

     <RunOnlyIfIdle>false</RunOnlyIfIdle>

     <WakeToRun>false</WakeToRun>

     <ExecutionTimeLimit>P3D</ExecutionTimeLimit>

     <Priority>7</Priority>

   </Settings>

   <Actions Context="Author">

     <Exec>

       <Command>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</Command>

       <Arguments>-command ".\SharePointWarmup.ps1"</Arguments>

       <WorkingDirectory>C:\Program Files\SharePoint Warmup</WorkingDirectory>

     </Exec>

   </Actions>

 </Task>

1. Copy this XML code to a file, then open the “Scheduled Tasks” management console of Windows.

2. Open the “Task Scheduler Library”, right-click on it’s node. Choose “Import”.

3. Then select the XML file.

4. In the task edit dialog: Change the execution account.

5. Save the task.

6. Now enter the password of the execution account in the credential dialog.

7. Now right-click on the created scheduled task.

8. Choose “Run” to test the task.

9. Have a look into the scripts folder in file system. there must be a file named “lastrunlog.txt” – This file will contain at most 200 lines of loggin informations!

Demo project: Excel Export feature for SharePoint 2010

I’ve uploaded another private demo project. It was planned as part of an SharePoint solution I liked to create but I cannot finalize this project. So I publish this project as “stand alone” project…. You may find it useful.

You are invited to use / develop / update the project! Every help is welcome!

You find the source code here:

http://spexcelexport.codeplex.com/

The project is ALPHA!!!

The intention of the project is to create a possibility to export SharePoint lists to "plain" Excel files. Not the kind of Excel files you can download by using the SharePoint standard functionality: With that you download a "linked" Excel file that contains a permanent connection the SharePoint. It’s a query. – With my project you’ll download a real XLSX file. – And you have the possibility to store an template file that contains formatting instructions.

It’s not finished but it works! – The test project included in the source code demonstrates the feature. Use "Test List 1". (Not "Test List 2".)

Some screenshots:

This is the “Test List 1”:

There is a link in the upper right. This you can use to download the Excel file:

When you click the link you get the well known download window:

Clicking “Open” will open the Excel Viewer – or the “real” Excel (that I do not have on my dev machine).

In Excel you can resize the “C” column.

May you have seen it: There is an error in the solution: Date values are not exported correctly. There is a gap of 1 day…

The goal is to implement a Ribbon button.

See the hidden list:

Have a look into the single Excel file:

Ok… Lots of work to do Smile

Walkthrough: Create custom SharePoint 2010 list form for deployment in a Visual Studio 2010 project – PART 2

This is part 2 of my demo project about “How to create a custom list form…” –

See this post for part one:

https://blog.kenaro.com/2010/12/29/walkthrough-create-custom-sharepoint-2010-list-form-for-deployment-in-a-visual-studio-2010-project/

Here you can download the demo project as source code:

http://spcustomlistformdemo.codeplex.com/

Let’s start…

(See “ListDefinition2” in the demo project source!)

1. Create an new List Definition project item as described in the previous blog post (“Part 1”).

2. In the ASPX file of your list form be sure to add the attribute UseLegacyForm=”True” to your Form-Tag. – Like in this screenshot:

3. Then you need to create the field edit controls by yourself. Therefore you have to add some code to the ASPX file.

Here is some demo code. (The “ListDefinition2” based upon “Announcement List Template”…)

1:                 <WebPartPages:WebPartZone  runat="server"  FrameType="None"  ID="Main"  Title="loc:Main"

2:                     Visible="true">

3:                     <ZoneTemplate>

4:                     </ZoneTemplate>

5:                 </WebPartPages:WebPartZone>

6:

7:                 <!-- ikarstein: Insert such a structure for each field you want to show on you page -->

8:                 <table  border="0"  width="100%">

9:                     <tr>

10:                         <td  class="ms-toolbar"  nowrap="nowrap">

11:                             <SharePoint:FormToolBar  runat="server"  ControlMode="New"  />

12:                         </td>

13:                     </tr>

14:                     <tr>

15:                         <td>

16:                             <span  id="part1">  <!-- ikarstein: This line is important for "Attachments" -->

17:                                 <table  border="0"  cellspacing="0"  width="100%">

18:                                     <!-- ikarstein: Insert such a table row for each field / BEGIN-->

19:                                     <tr>

20:                                         <td  width="190px"  valign="top"  class="ms-formlabel">

21:                                             <h3  class="ms-standardheader">

22:                                                 <nobr> Title<span  class="ms-formvalidation">  *</span></nobr>

23:                                             </h3>

24:                                         </td>

25:                                         <td  width="400px"  valign="top"  class="ms-formbody">

26:                                             <SharePoint:FormField  runat="server"  ID="field_Title"  ControlMode="New"  FieldName="Title"  />

27:                                             <SharePoint:FieldDescription  runat="server"  ID="field_Title_Description"  FieldName="Title"

28:                                                 ControlMode="New"  />

29:                                         </td>

30:                                     </tr>

31:                                     <!-- karstein: END -->

32:                                     <tr>

33:                                         <td  width="190px"  valign="top"  class="ms-formlabel">

34:                                             <h3  class="ms-standardheader">

35:                                                 <nobr> Body</nobr>

36:                                             </h3>

37:                                         </td>

38:                                         <td  width="400px"  valign="top"  class="ms-formbody">

39:                                             <SharePoint:FormField  runat="server"  ID="field_Body"  ControlMode="New"  FieldName="Body"  />

40:                                             <SharePoint:FieldDescription  runat="server"  ID="field_Body_Description"  FieldName="Body"

41:                                                 ControlMode="New"  />

42:                                         </td>

43:                                     </tr>

44:                                     <tr>

45:                                         <td  width="190px"  valign="top"  class="ms-formlabel">

46:                                             <h3  class="ms-standardheader">

47:                                                 <nobr> Expires</nobr>

48:                                             </h3>

49:                                         </td>

50:                                         <td  width="400px"  valign="top"  class="ms-formbody">

51:                                             <SharePoint:FormField  runat="server"  ID="field_Expires"  ControlMode="New"  FieldName="Expires"  />

52:                                             <SharePoint:FieldDescription  runat="server"  ID="field_Expires_Description"  FieldName="Expires"

53:                                                 ControlMode="New"  />

54:                                         </td>

55:                                     </tr>

56:                                     <!-- ikarstein: optionally add this table row / BEGIN -->

57:                                     <tr  id="idAttachmentsRow">

58:                                         <td  nowrap="true"  valign="top"  class="ms-formlabel"  width="20%">

59:                                             <SharePoint:FieldLabel  ControlMode="New"  FieldName="Attachments"  runat="server"  />

60:                                         </td>

61:                                         <td  valign="top"  class="ms-formbody"  width="80%">

62:                                             <SharePoint:FormField  runat="server"  ID="AttachmentsField"  ControlMode="New"  FieldName="Attachments"  />

63:                                             <script  language="javascript"  type="text/javascript">

64:                                               var  elm = document.getElementById("idAttachmentsTable" );

65:                                               if  (elm == null  || elm.rows.length == 0)

66:                                                 document.getElementById("idAttachmentsRow" ).style.display=< span> ;

67:                                             </script>

68:                                         </td>

69:                                     </tr>

70:                                     <!-- ikarstein: END -->

71:

72:                                     <!-- ikarstein: Add this table for "Save" and "Cancel" buttons / BEGIN -->

73:                                     <table  width="100%"  border="0"  cellspacing="0">

74:                                         <tr>

75:                                             <td  width="99%"  class="ms-toolbar"  nowrap="nowrap">

76:                                                 <img  src="/_layouts/images/blank.gif"  width="1"  height="18"  />

77:                                             </td>

78:                                             <td  class="ms-toolbar"  nowrap="nowrap">

79:                                                 <SharePoint:SaveButton  runat="server"  ControlMode="New"  ID="savebutton"  />

80:                                             </td>

81:                                             <td  class="ms-separator">

82:                                             </td>

83:                                             <td  class="ms-toolbar"  nowrap="nowrap"  align="right">

84:                                                 <SharePoint:GoBackButton  runat="server"  ControlMode="New"  ID="gobackbutton"  />

85:                                             </td>

86:                                         </tr>

87:                                     </table>

88:                                     <!-- ikarstein: END -->

89:                             </span>

90:                             <SharePoint:AttachmentUpload  runat="server"  ControlMode="New"  />

91:                             <SharePoint:ItemHiddenVersion  runat="server"  ControlMode="New"  />

92:                         </td>

93:                     </tr>

94:                 </table>

95:

96:

(You see my comments inline ?! Not much, I know…)

Behind the “<WebPartZone>” tag add the HTML code.

You can add input fields by using this snipped:

1:                                     <!-- ikarstein: Insert such a table row for each field / BEGIN-->

2:                                     <tr>

3:                                         <td  width="190px"  valign="top"  class="ms-formlabel">

4:                                             <h3  class="ms-standardheader">

5:                                                 <nobr> Title<span  class="ms-formvalidation">  *</span></nobr>

6:                                             </h3>

7:                                         </td>

8:                                         <td  width="400px"  valign="top"  class="ms-formbody">

9:                                             <SharePoint:FormField  runat="server"  ID="field_Title"  ControlMode="New"  FieldName="Title"  />

10:                                             <SharePoint:FieldDescription  runat="server"  ID="field_Title_Description"  FieldName="Title"

11:                                                 ControlMode="New"  />

12:                                         </td>

13:                                     </tr>

14:                                     <!-- karstein: END -->

15:

Of course you can change the page design. You only need the tag “<SharePoint:FormField>”, optionally “<SharePoint:FieldDescription>”. In every case the “FieldName” Attribute represents the List field the input field is connected with.

You do not need to create any Code Behind!

Just add "<SharePoint:GoBackupButton>” for cancel and “<SharePoint:SaveButton>” for submit.

Furthermore you have some controls for adding attachments to your List item.

AND: It’s the same for “Edit” list form. You only need to change the attributes “ControlMode” to “Edit”… Totally easy, isn’t it?

4. Deploy it and have a look…

Error while executing the SharePoint 2010 PowerShell cmdlet Mount-SPContentDatabase: “Exception of type ‘Microsoft.SharePoint.Upgrade.SPUpgradeException’ was thrown.”

Mount-SPContentDatabase : Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
At D:TempAttach_OldContentDBs_DoIt.ps1:63 char:28
+              Mount-SPContentDatabase <<<<  -WebApplication $webapp -Name $thisdb
    + CategoryInfo          : InvalidData: (Microsoft.Share...ContentDatabase:SPCmdletMountContentDatabase) [Mount-SPContentDatabase], SPUpg
   radeException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletMountContentDatabase

Have a look into the SQL Server Management Studio. – The content database is read only. That’s the problem Smile

SharePoint 2010 Help doesn’t work after migration

I had to migrate a MOSS 2007 farm to SharePoint 2010. – After migration the SharePoint Help did not work. (It’s the button upper right on a SharePoint site.)

A popup window appeared and I got an empty site with the message “Help not available” (or something like that: It was a german site so the error message was german…)

I tried a new created web application with a Team Site collection. There the help does work as expected.

Then I had a look into the Windows Event Log. There I found a related error. The web application pool account of my migrated web application did not has access to the Admin Content database. But the application pool account of the new created web application was enabled to access this database. – After adding the application pool account of my migrated web application as “db_owner” the help was shown as expected.

(I have no screenshots of that. Sorry. But I think, that can be reproduced easily by removing the application pool account from the Admin Content database.)

Missing “View in Browser” and “Edit in Browser” in the context menu of Excel files in a SharePoint 2010 document library…

You have installed the Office Web Apps on your SharePoint 2010 server. Now you are missing the menu entries “View in Browser” and “Edit in Browser”.

You create a new Excel file in Excel 2007 or 2010, upload it and… there are the menu entries… maybe…

This was the situation of my customer yesterday. He tried to open documents in the Office Web Apps after migration from MOSS to SharePoint 2010. Everything seems to work: Word Web App, PowerPoint Web App, OneNote Web App…

I created a new site collection and uploaded a Excel file (XLSX). – The menu entries appeared.

Then I uploaded a document I’ve downloaded before from the migrated site collection. The menu entries were gone… – THEN I REALIZED: To new document was in OpenXML format (Excel 2007, Excel 2010), the migrated documents in native Excel format of Excel 97…2003. Thats the problem: Only OpenXML Excel files can be viewed an edited in the browser!!! – Thats diffrent from Word Web App and PowerPoint Web App.

I’m looking around on the Microsoft web site, but till now I’ve not found an official comment on that. But this seems to be “behavior by design”… Don’t waste as much time as I’ve wasted with that!

Error while connecting to a SharePoint 2010 web site in SharePoint Designer 2010

Today I got this error:

(“The server could not complete your request. For more specific information, click the Details button.”)

I clicked the “Details” button as commanded.

(“Below is the message that the server returned. For more information, contact your Internet service provider or web server administrator.”)

I asked myself (because I’m the web server administrator in this case) – I had no answer for me.

I clicked: “OK” and “OK” and got:

(‘An error occurred while trying to fetch data from your SharePoint site. Unexpected response from the server. The content type type of the response is “” This status code is “OK”.’)

“OK”??????????? Okay…

…

I read the event viewer log:

WebHost failed to process a request.
 Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/64923656
 Exception: System.ServiceModel.ServiceActivationException: The service '/_vti_bin/client.svc' cannot be activated due to an exception during compilation.  The exception message is: Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.. ---> System.NotSupportedException: Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.
   at System.ServiceModel.Channels.HttpChannelListener.ApplyHostedContext(VirtualPathExtension virtualPathExtension, Boolean isMetadataListener)
   at System.ServiceModel.Channels.HttpTransportBindingElement.BuildChannelListener[TChannel](BindingContext context)
   at System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener[TChannel]()
   at System.ServiceModel.Channels.MessageEncodingBindingElement.InternalBuildChannelListener[TChannel](BindingContext context)
   at System.ServiceModel.Channels.WebMessageEncodingBindingElement.BuildChannelListener[TChannel](BindingContext context)
   at System.ServiceModel.Channels.BindingContext.BuildInnerChannelListener[TChannel]()
   at System.ServiceModel.Channels.Binding.BuildChannelListener[TChannel](Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, BindingParameterCollection parameters)
   at System.ServiceModel.Description.DispatcherBuilder.MaybeCreateListener(Boolean actuallyCreate, Type[] supportedChannels, Binding binding, BindingParameterCollection parameters, Uri listenUriBaseAddress, String listenUriRelativeAddress, ListenUriMode listenUriMode, ServiceThrottle throttle, IChannelListener& result, Boolean supportContextSession)
   at System.ServiceModel.Description.DispatcherBuilder.BuildChannelListener(StuffPerListenUriInfo stuff, ServiceHostBase serviceHost, Uri listenUri, ListenUriMode listenUriMode, Boolean supportContextSession, IChannelListener& result)
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
 Process Name: w3wp
 Process ID: 7248

…………….. It was my mistake. ………………………….

An hour before I configured my SharePoint Site to use KERBEROS. – In the IIS I configured the Web application “Authentication” settings: I choose the provider “Negotiate” but I also removed “NTLM”. This was my fault.

This is the correct setting: