locked
Timer Job failed: The shim execution failed unexpectedly - Cannot find any matching endpoint configuration.. RRS feed

  • Question

  • Hi Team,

    I have a BDC service in SharePoint 2010 which connect one web service to pull some data. Now while executing the BDC service through timer job I am getting the below error

    xxxx.Metadata.Administration.MetaDataTimerJob.MetaDataBCSImportTimer (ID 46df5571-b98f-4f7e-ba7d-35417d1b149f) threw an exception. More information is included below.  The shim execution failed unexpectedly - Cannot find any matching endpoint configuration..           db5e9c3c-c840-47d4-bedb-2778a49ceb63.

    02/24/2016 13:55:17.71 OWSTIMER.EXE (WS175:0x22B0)               0x25A4 SharePoint Foundation                 Timer                                         72ae      Unexpected       Exception stack trace:    at Microsoft.SharePoint.BusinessData.Runtime.DataClassRuntime.ExecuteInternal(IDataClass thisDataClass, ILobSystemInstance lobSystemInstance, ILobSystem lobSystem, IMethodInstance methodInstanceToExecute, IMethod methodToExecute, IParameterCollection nonReturnParameters, Object[]& overrideArgs)     at Microsoft.SharePoint.BusinessData.Runtime.DataClassRuntime.Execute(IDataClass thisDataClass, IMethodInstance methodInstanceToExecute, ILobSystemInstance lobSystemInstance, Object[]& overrideArgs)     at Microsoft.SharePoint.BusinessData.MetadataModel.Static.DataClass.Execute(IMethodInstance methodInstanceToExecute, ILobSystemInstance lobSystemInstance, Object[]& overrideArgs)     at XXX.Metadata.Administration.BCSConnectivity.BCSDataManager.ExecuteFinderMethod(IEnti...             db5e9c3c-c840-47d4-bedb-2778a49ceb6302/24/2016 13:55:17.71*               OWSTIMER.EXE (WS175:0x22B0)               0x25A4 SharePoint Foundation                 Timer                                         72ae      Unexpected       ...ty entity, ILobSystemInstance application, String finderMethodName, String elementNo, Int32 parentId)     at XXX.Metadata.Administration.BCSConnectivity.BCSDataManager.GetBusinessData(String siteUrl, String applicationName, String entityNamespace, String entityName, String finderMethodName, String nameFieldName, String sourceIdFieldName, String elementNo, Int32 parentId, String sourceParentIdFieldName, String sourceDescriptionFieldName, String relationType)     at XXX.Metadata.Administration.MetaDataTimerJob.MetaDataBCSImportTimer.ExecuteBCSImport(SPWebApplication webApplication, String connectivitySettingsFileUri)     at XXX.Metadata.Administration.MetaDataTimerJob.MetaDataBCSImportTimer.ExecuteBCSImport()     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJob...             db5e9c3c-c840-47d4-bedb-2778a49ceb63 02/24/2016 13:55:17.71*               OWSTIMER.EXE (WS175:0x22B0)               0x25A4 SharePoint Foundation                 Timer                                         72ae      Unexpected       ...Definition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     db5e9c3c-c840-47d4-bedb-2778a49ceb63 02/24/2016 13:55:17.74 OWSTIMER.EXE (WS175:0x22B0)               0x25A4 SharePoint Foundation                 Monitoring                                    b4ly        Medium               Leaving Monitored Scope (Timer Job XXX Metadata Timer Job). Execution Time=112.534344448806               db5e9c3c-c840-47d4-bedb-2778a49ceb63

     

    We have checked and verified that BCS(BDC) service application is running correctly. But it thorws above exception. We don’t know any idea about this error message.


    Please find above error and give us excat solution for this..

    Thanks

    Ravikumar


    ravi sharepoint

    Thursday, February 25, 2016 6:57 AM

All replies

  • I have resolved this issue. In the following steps

    Step -1:  Clear the cache on sharepoint :

    Stop the Timer service. To do this, follow these steps:

    Click Start, point to Administrative Tools, and then click Services.
    Right-click SharePoint 2010 Timer, and then click Stop.
    Close the Services console.
    On the computer that is running Microsoft SharePoint Server 2010 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
    In Windows Explorer, locate and then double-click the following folder:
    %SystemDrive%\ProgramData\Microsoft\SharePoint\Config\GUID
    Notes
    The %SystemDrive% system variable specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
    The GUID placeholder specifies the GUID folder. There may be more than one of these.
    The ProgramData folder may be hidden. To view the hidden folder, follow these steps:
    On the Tools menu, click Folder Options.
    Click the View tab.
    In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.
    You can also simply type this directly in the path if you do not want to show hidden files and folders.
    Back up the Cache.ini file. (Make a copy of it. DO NOT DELETE THIS FILE, Only the XML files in the next step)
    Delete all the XML configuration files in the GUID folder (DO NOTE DELETE THE FOLDER). Do this so that you can verify that the GUID folders content is replaced by new XML configuration files when the cache is rebuilt. 
    Note When you empty the configuration cache in the GUID folder, make sure that you do NOT delete the GUID folder and the Cache.ini file that is located in the GUID folder.
    Double-click the Cache.ini file.
    On the Edit menu, click Select All.
    On the Edit menu, click Delete.
    Type 1, and then click Save on the File menu. (Basically when you are done, the only text in the config.ini file should be the number 1)
    On the File menu, click Exit.
    Start the Timer service. To do this, follow these steps:
    Click Start, point to Administrative Tools, and then click Services.
    Right-click SharePoint 2010 Timer, and then click Start.
    Close the Services console.
    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
    Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
    Check in the GUID folder to make sure that the xml files are repopulating. This may take a bit of time.

    Step -2: We can do as follows:

    1. Open the central administration

    2. Application management

    3. Service Applications

    4. Configure service application associations

    5. Check the web application in which your site exist

    6. Check the "application proxy group" column

    7. Make sure the BDC and secure store service applications check boxes are mark

    8. If they are not then please tick the check box and click OK

    Then I have restarted IIS admin service , run the metadata timerjob and Succeeded  after some time.

    Finally resolve the issue.

    Thanks

    ravikumar


    ravi sharepoint

    Thursday, February 25, 2016 12:48 PM