none
MIM 2016SP1 + MS Server 2016 + IIS crash RRS feed

  • Question

  • Hello!

    Does somebody have a problems with such configuration:

    1. MS Server 2016

    2. MIM Server 2016SP1

    3. SharePoint 2013SP1 foundation + latest fix from

    I have some problems with SharePoint in such config, but I think that all of them were resolved.

    I'm using this guide to install:

    https://docs.microsoft.com/en-us/microsoft-identity-manager/prepare-server-sharepoint

    And this one

    http://roger.dilsner.com/install-sharepoint-foundation-2013-windows-server-2016-solution/

    After install when I try to configure SharePoint to host Mim Portal and open IE to http://localhost:82 I constantly get crash of w3wp service and such error:

    Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a

    Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327897

    Exception code: 0xe0434352

    Fault offset: 0x0000000000033c58

    Faulting process id: 0x11b8

    Faulting application start time: 0x01d32c6de00ee71f

    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe

    Faulting module path: C:\Windows\System32\KERNELBASE.dll

    Report Id: b64e37af-91d1-466e-86e1-036626335ef9

    Faulting package full name:

    Faulting package-relative application ID:  

    Can anybody help?

    Thanks!


    1

    Wednesday, September 13, 2017 9:21 AM

All replies

  • What exactly are you doing when this error appears?  You are not done with SP yet, this is not MIM related at this point.


    Nosh Mernacaj, Identity Management Specialist

    Wednesday, September 13, 2017 1:28 PM
  • I'm simply trying to open IE with link to MIM SharePoint site, http://localhost:82

    I can see this site in IIS, but can't open it.


    1

    Wednesday, September 13, 2017 1:31 PM
  • Can you see the http://localhost:82 in SharePoint Administration?

    I don't think you have created the SharePoint application correctly. 


    Nosh Mernacaj, Identity Management Specialist

    Wednesday, September 13, 2017 6:18 PM
  • Yes, I can see site in IIS and I can browse it's structure, so it is not empty

    1

    Wednesday, September 13, 2017 6:24 PM
  • you have to show me the screen shots of IIS and SP. 
    I suggest you delete the site http://localhost:82 and start over again.

    Please make sure you follow this strictly. https://technet.microsoft.com/en-us/library/jj863242(v=ws.10).aspx


    Nosh Mernacaj, Identity Management Specialist


    Wednesday, September 13, 2017 6:32 PM



  • And yes, your instruction for FIM 2010 and SharePoint 2013 same as for MIM 2016, I can't see any differencies.
    • Edited by alexiszp Thursday, September 14, 2017 5:52 PM
    Thursday, September 14, 2017 5:34 PM
  • 1-Makes sure the ISS setting match mine, as in screen shot

    2- Login to SharePoint administration, and see if the site you created is accessible

    3- Make sure you are using the account that you used to install SharePoint, because that is the only one who has access right now


    Nosh Mernacaj, Identity Management Specialist

    Thursday, September 14, 2017 5:54 PM
  • SharePoint Administration gives same error

    Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
    Faulting module name: KERNELBASE.dll, version: 10.0.14393.1358, time stamp: 0x59327897
    Exception code: 0xe0434352
    Fault offset: 0x0000000000033c58
    Faulting process id: 0x3130
    Faulting application start time: 0x01d32d839efc76de
    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: 0efad7b8-3463-4daf-bfe5-96882e6c089e
    Faulting package full name: 
    Faulting package-relative application ID: 

    and

    Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
    Faulting module name: owssvr.dll, version: 15.0.4953.1000, time stamp: 0x596491f5
    Exception code: 0xc0000005
    Fault offset: 0x000000000000195d
    Faulting process id: 0x3130
    Faulting application start time: 0x01d32d839efc76de
    Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\isapi\owssvr.dll
    Report Id: a696b255-7209-4253-87d6-39a8cbbd56de
    Faulting package full name: 
    Faulting package-relative application ID: 

    And

    Service: WAS

    Error 5011

    A process serving application pool 'SharePoint Central Administration v4' suffered a fatal communication error with the Windows Process Activation Service. The process id was '12592'. The data field contains the error number.


    1

    Thursday, September 14, 2017 6:06 PM
  • Did you ensure the steps on the link I sent were successful?

    Seems your site is still running on Claims-Based mode. Your version needs to be 14, not 15, as shown in the error.

    Best thing is to uninstall SP completely and do it again.


    Nosh Mernacaj, Identity Management Specialist

    Thursday, September 14, 2017 6:19 PM
  • I have not seen error at install /config stage

    Version is 14, where you can see 15th version?

    Claims is false, so I think that they are disabled?

    

    Thanks!


    1

    Thursday, September 14, 2017 6:29 PM
  • Hello!

    I have reinstalled IIS and SharePoint, but I have now another problem.

    When I try to open Central administration link I get 403 error - forbidden, even if I use domain admin account.

    Also I can see this erros in Event Viewer:

    Error: 8306

    An exception occurred when trying to issue security token: There was no endpoint listening at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

    Error: 2138

    The SharePoint Health Analyzer detected a condition requiring your attention.  The Security Token Service is not available.
    The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.
    Administrator should try to restart the Security Token Service on the boxes where it is not issuing tokens. If problem persists, further troubleshooting may be available in the KB article. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=160531".

    I'm using procmon to investigate what causes 403 error. I can't see what something is going wrong

    

    Any ideas?

    Thanks!


    1


    • Edited by alexiszp Monday, September 18, 2017 1:05 PM
    Monday, September 18, 2017 12:42 PM