السؤال Error using the WSS adapter in BizTalk 2009

  • 04/ربيع الأول/1431 03:40 م
     
     

    Hi all

    I am trying to get the wss adapter working on a BizTalk 2009 installation.

    What I have is this:

    A Sharepoint server, on which I have installed BizTalks wss adapter web service and configured it successfully to use the "DOMAIN\SharePoint Enabled Hosts" group.

    A BizTalk Server, with a host instance running as DOMAIN\biztalk which is a member of the "DOMAIN\SharePoint Enabled Hosts" group.

    I am setting up my Receive location as I believe it should be set up with strings for sharepoint site url, doc lib url and view name.

    When enabling the Receive Location I get this error:

    Event Type: Warning
    Event Source: BizTalk Server 2009
    Event Category: BizTalk Server 2009
    Event ID: 5740
    Date:  18-02-2010
    Time:  16:08:27
    User:  N/A
    Computer: <EDITED OUT BY ELIASEN>
    Description:
    The adapter "Windows SharePoint Services" raised an error message. Details "The Windows SharePoint Services adapter runtime does not have permissions to invoke the adapter Web service. In order to fix this issue, you have to add the DOMAIN\biztalk Windows account to the "SharePoint Enabled Hosts" Windows group on the Windows SharePoint Services machine. This operation will allow BizTalk host instances running under DOMAIN\biztalk Windows account to invoke the adapter Web service in order to send and receive messages to or from SharePoint sites. The group membership will not take effect until you restart the BizTalk host instance.

    This error was triggered by the Windows SharePoint Services receive location or send port with URI wss://adm-blankettertest.fvm.dk:80/PDirInfoPathDev?ViewName=EliasenVisning.

    Windows SharePoint Services adapter event ID: 12458".

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    which REALLY annoys me, because I KNOW that the DOMAIN\biztalk account is a member of that group.

    There is no local group called "SharePoint Enabled Hosts" on the sharepoint server, and I have even tried restarting both servers.

    Any thoughts are most welcome...


    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk

جميع الردود

  • 05/ربيع الأول/1431 03:49 م
    المشرف
     
     
    Did you grant contribute rights to the site your SharePoint list occurs on? I always remember making the "SharePoint Enabled Hosts" a local group, not a domain group. Try using a local group.

    Thanks,
    If this answers your question, please use the "Answer" button to say so | Ben Cline
  • 05/ربيع الأول/1431 05:27 م
     
     
    I came to think about a BizTalk Lab that had BizTalk and Sharepoint interacting using the described webservice. So I started the Lab up and went to Computer Management/Local Groups on the Lab Server and found the group SharePoint Enabled Hosts.

    So I think that the group SharePoint Enabled Hosts must be a local group on the Sharepoint Webservice Server and not a group on the AD.

    The Lab I went to is found on http://www.microsoft.com/biztalk/en/us/virtual-labs.aspx and is called BizTalk Server 2009: Integration with POP3 and SharePoint and Routing Failed Messages

    Thomas E.
  • 06/ربيع الأول/1431 12:01 م
     
     
    Did you grant contribute rights to the site your SharePoint list occurs on? I always remember making the "SharePoint Enabled Hosts" a local group, not a domain group. Try using a local group.

    Hi Ben

    Yes, I even tried providing full rights to that group... and I tried the same with a local group.

    Besides... if this is only supported for locla groups, I shall be very annoyed :-)

    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk
  • 06/ربيع الأول/1431 12:03 م
     
     
    I came to think about a BizTalk Lab that had BizTalk and Sharepoint interacting using the described webservice. So I started the Lab up and went to Computer Management/Local Groups on the Lab Server and found the group SharePoint Enabled Hosts.

    So I think that the group SharePoint Enabled Hosts must be a local group on the Sharepoint Webservice Server and not a group on the AD.

    Well, as mentioned, I have tried this. The lab you mention probably has everything on just one server, which means no domain accounts are created at all for any of the stuff anyways.


    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk
  • 03/ربيع الثاني/1431 07:59 م
     
     
    My issues when running in a mutliserver environment were not have proper rights in the database I had a very similar issue. You would be able to check it against the permissions in the lab you downloaded to make sure that the id that was added to the Share Point Enabled Hosts group has the proper access. Hope this helps.
    Gary L Bales - Infrastructure Architect
  • 08/ربيع الثاني/1431 09:12 ص
    المشرف
     
     

    I think the resolution is that the SharePoint Enabled Host group must be a local group on each WSS server and not a domain group.

    Also please ensure the host instance account is a part of the Contributor role in SharePoint.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • 08/ربيع الثاني/1431 06:19 م
    المشرف
     
     

    The directions mention the SharePoint Enabled hosts as a local group only. I do not think this is possible in a domain group.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
  • 08/ربيع الثاني/1431 07:21 م
     
     

    We experienced the same behaviour and ended up recreating the webservice by hand within IIS.

    BTW: We were not able to browse the webservice from IIS, do you experience this behaviour too?)

  • 14/ربيع الثاني/1431 06:35 م
     
     
    I think the resolution is that the SharePoint Enabled Host group must be a local group on each WSS server and not a domain group.
    Also please ensure the host instance account is a part of the Contributor role in SharePoint.

    Hi Wen-Jun

    I have created a support case to resolve my issue. If only local groups are supported, you will leave me VERY disappointed - say I have X SharePoint Servers in my farm. That would mean that I need to create X local groups, add the host instance account to X local groups and add X local groups as contributors to SharePoint. With a domain group, X is 1 no matter how many servers are in the farm.

    If you can find anywhere where it is clearly written that local groups are required or the opposite, naturally, I'd like to hear about it.

    If I look at “Installing BizTalk Server 2009 in a Multicomputer Environment.docx”, which is found at http://www.microsoft.com/downloads/details.aspx?FamilyID=9C697E02-D1BC-4684-8748-28B3A292D5BF&displaylang=en&displaylang=en it clearly states that “In a multicomputer environment, BizTalk Server supports only domain groups and domain service accounts.” Nowhere does it state that anything else applies to the SharePoint Enabled Hosts group.

    This is the first time I have heard of adding the host instance account as a contributor - others have only mentioned that the "SharePoint Enabled Host" group must be a contributor.

    I'll have to try this.

    Thanks.


    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk
  • 14/ربيع الثاني/1431 06:36 م
     
     
    The directions mention the SharePoint Enabled hosts as a local group only. I do not think this is possible in a domain group
    May I ask... why? I would think that the domain group is the best solution - local groups are evil! :-)
    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk
  • 21/ربيع الثاني/1431 08:01 م
    المجيب على الأسئلة
     
     

    Not that this really helps solve your problem, but this is exactly why we chose the domain group route.  We have 2 MOSS front end servers so using local groups would have made configuration and permissions more cumbersome.  We also put the host instance user into the domain\SharePoint Enabled Host and made sure that group/user had contribute permissions.  We have been running this configuration in Test/Prod for the last couple months without issue.

    Something to check is when you point a browser at the Adapter Web Service, do you get any 500 or security related errors?

    i.e. http://SharePointServer/BTSharePointAdapterWS/BTSharePointAdapterWS.asmx

     


    http://kentweare.blogspot.com
  • 22/ربيع الثاني/1431 08:46 ص
     
     
    Something to check is when you point a browser at the Adapter Web Service, do you get any 500 or security related errors?

    When I try to access it, I get a box from IE that asks for a username and password. I enter the credentials for the account running the BizTalk host instance but after three retries it gives up and gives me the error you can see at http://www.eliasen.dk/biztalk/wssadapterwserror.png 

    Also, when running DebugViewer on the SharePoint server I get this:

    [7956] GetRolesForUser called! username='MyDomain\biztalk'

    for each time I try.

    so my best guess is, that the code that tries to find roles for the user simply cannot determine that the user is in the right AD group.

     


    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk
  • 25/جمادى الثانية/1431 08:25 م
     
     

    I have had the same problem, I figured out how to view the web service, it's disabled for usage by the web.config, just comment out:

    <!-- <webServices>
       <protocols>
        <remove name="Documentation"/>
       </protocols>
      </webServices> -->

    This will allow you to see it's working at least.... did not solve my problem however.... still the problem exists....

  • 26/جمادى الثانية/1431 06:44 م
     
     
    I This will allow you to see it's working at least.... did not solve my problem however.... still the problem exists....

    Same here...
    eliasen, representing himself and not the company he works for.
    Three times MVP and three times MCTS in BizTalk.
    Blog: http://blog.eliasen.dk
  • 14/ربيع الثاني/1432 01:01 م
     
     
    I have a few questions, it might be possible that I can provide some information to help your situation.  We have a successfull BTS 2009 application which retrieves documents from a SharePoint document library using the WSS Adapter.  Additionally, we have a highly restrictive and complex AD imployed SharePoint User Group and User schema for accessing site collection and also content. SharePoint is not real forgiving with respect to permissions.  However, your problem seems to indicate a possible configuration or user permission situation at a site or subsite level. What version of WSS hosts the library you are trying to access? I know this might sound stupid but, how is the WSS site configured for Negotiate or NTLM?. Is the AD User Group on the Site Permission list and what type of Permissions are assigned to the group?  When in the source Document Library Settings under Permissions for this list; is the group listed or in one of the SP groups listed?  What Permission Levels does it have?