Freigeben über

WSS v3 Beta 2 is out - try it with WSS adapter

  • Artikel

Windows SharePoint Services V3 Beta 2 is out and you can download it here. WSS v3 does not install a policy file that redirects old SharePoint assembly requests to the new assemblies. For this reason, if you try to use WSS v3 Beta 2 with BizTalk 2006 WSS adapter, you will run into errors. In order to workaround this problem and take WSS v3 Beta 2 for a test drive together with BizTalk 2006 WSS adapter, you will need to write your own policy file or just update the web.config file of the WSS adapter web service. Here's what you need to do:

  1. Open web.config from C:\Program Files\Microsoft BizTalk Server 2006\Business Activity Services\BTSharePointAdapterWS
  2. Paste the following section into the web.config file, configuration section and save the file
     <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.SharePoint"
                              publicKeyToken="71e9bce111e9429c" />
            <bindingRedirect oldVersion="11.0.0.0"
                             newVersion="12.0.0.0"/>
          </dependentAssembly>
        </assemblyBinding>
      </runtime>

If you have other apps that were compiled against the old SharePoint assembly and you want to see if they will work with the new SharePoint assemblies, you can paste the snippet above in the configuration section of the machine.config file. That will make the changes global to entire machine.

During my tests, WSS adapter worked nicely with WSS v3 Beta 2. There were a few intermittent issues like [Microsoft.SharePoint.SPException] Unable to complete this operation. Please contact your administrator. or [Microsoft.SharePoint.SPException] The URL '/sites/BASSite/DestinationLibraryFromOrch/tmp-db04abaf-4a12-4e11-93c9-4338c17cc78c.xml' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.

However, the operation was succesful on the second retry performed by the adapter and since this is a beta product some annoyances are expected. If you decide to try WSS v3 Beta 2 yourself and you find worse problems, I would like to hear about them from you.

[Content below added/changed on June 14]

BizTalk 2006 Configuration routine for Windows SharePoint Services BizTalk Adapter Web Service/SharePoint Adapter fails to configure on WSS v3 Beta 2 (SharePoint 2007 Beta 2). In order to workaround this you can install and configure WSS adapter on WSS v2 and then upgrade to WSS v3.

An alternative is to configure the adapter web service manually. I haven't tried this approach but it should work. In this case you need to create a virtual folder on the IIS site hosting SharePoint and name that virtual folder BTSharePointAdapterWS. The virtual folder should point to C:\Program Files\Microsoft BizTalk Server 2006\Business Activity Services\BTSharePointAdapterWS folder. This virtual folder must run in its own application pool and this app pool needs to be a copy of the SharePoint app pool (app pool used by _layouts virtual folder). You also need to update the web.config file like below

  <authorization>
   <allow roles="MACHINENAME\SharePoint Enabled Hosts" verbs="GET,HEAD,POST"/>
   <deny users="*"/>
  </authorization>

These are my own workarounds and they are NOT supported by Microsoft. AFAIK, Microsoft has NOT announced yet if BizTalk 2006 will support WSS v3.

Comments

  • Anonymous
    July 26, 2006
    The comment has been removed
  • Anonymous
    July 26, 2006
    I believe you are getting this error because SharePoint is not routing the web service calls to the BTSharePointAdapterWS virtual folder. WSS v3 has been updated so that only included paths are managed explicitly (you can no longer define exludeded paths), instead they are excluded automatically. IISRESET should fix the problem. Can you update the BTSharePointAdapterWS web.config to comment out the
    <!--
    <protocols>
    <remove name="Documentation"/>
    </protocols>
    -->
    section, run IISRESET and then browse to the web service page? You should be able to see web service page. If you see the page, then try sending a message again.
  • Anonymous
    August 03, 2006
    The comment has been removed
  • Anonymous
    August 04, 2006
    The comment has been removed
  • Anonymous
    August 10, 2006
    The comment has been removed
  • Anonymous
    August 10, 2006
    For BAS and WSS adapter web service you need the following pre-requisites:

    WSS 2003
    SP2 for WSS 2003 (this is a WSS SP, not an OS SP)
    If WSS language is different from BizTalk language, you need to install a WSS language pack that adds support for the language that you have for BizTalk.
  • Anonymous
    August 10, 2006
    I realise that, and I am trying to install it onto a WSS v3 machine, so I am not too suprised.  The machine had never had WSS v2 installed, so I tried to trick the installer by creating a ..web server extensions60ISAPI directory and copying the v3 OWSSVR.DLL file into it.

    According to the installer log, it was happy with that, but obviously there is another check that the installer log does not report.
  • Anonymous
    August 11, 2006
    The comment has been removed
  • Anonymous
    August 16, 2006
    The comment has been removed
  • Anonymous
    August 16, 2006
    Can you update the BTSharePointAdapterWS web.config to comment out the
    <!--
    <protocols>
    <remove name="Documentation"/>
    </protocols>
    -->
    section, run IISRESET and then browse to the web service asmx page? What's the error message you get when you do this?
  • Anonymous
    August 16, 2006
    browsing to localostBTSharePointAdapterWS.asmx displays a sharepoint page that states "The file you are attempting to save or retrieve has been blocked from this Web site by the server administrators."  Owners & members have full control of the document library.
  • Anonymous
    August 16, 2006
    The comment has been removed
  • Anonymous
    August 25, 2006
    Is SharePoint Adapter enabled for SSL?

    I have WSS 3.0 site with SSL enabled (port 34103). When I specify in receive location  Adapter Web Service Port: 34103, and SharePoint Site URL: https://localhost - there are error messages in the EventLog:

    The adapter "Windows SharePoint Services" raised an error message. Details "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.".
  • Anonymous
    August 25, 2006
    Yes, SharePoint adapter is enabled for SSL. The error you get is probably normal because you used the "localhost" machine name. The SSL certificate of the server is used for 2 things:
    - to encrypt a symetrical key that's passed to the client for encrypting the HTTP requests/responses
    - to authentificate the identity of the server. This is what fails in your case.

    Your SSL certificate is issued for a particular machine name (usually something like www.microsoft.com). You MUST use that exact machine name in the URL (and not localhost or the NetBIOS name) otherwise the authentication of the server will fail with the error you just saw. You need to update the URL to include the correct name of the machine in order to fix this.

    If this problem is not fixed after you update the URL, then most likely that the authority that issued the certificate is not added to the 'trusted authorities' list on your machine. Most likely, you are using a certicate that you issued yourself. You will need to add that issueing authority as a trusted authority on the BizTalk Runtime machine in order to fix that (if you run into this problem). I believe you do that from MMC (run MMC, File ->Add/Remove Snapin, Add, select 'Certificates', Computer Account and then navigate to the Trusted Root Certification Authorities. I haven't tested this but I believe it's correct).
  • Anonymous
    December 11, 2006
    The comment has been removed
  • Anonymous
    December 19, 2006
    I tried to follow your suggestions with using the final version of WSS 3.0. Unfortunately I do not get it up and running. The error message is A message sent to adapter "Windows SharePoint Services" on send port "Archive CMDB Import Files" with URI "wss://10.90.51.85:47111/sp/OrderDesk" is suspended.Error details: The Windows SharePoint Services site was not found. The URL "http://10.90.51.85:47111/sp/" points to a SharePoint object for which there is no Windows SharePoint Services site.Have you got any suggestions?
  • Anonymous
    December 19, 2006
    Can you copy/paste the URL http://10.90.51.85:47111/sp/ in your browser and see if there is a SharePoint site at that URL? Do you get any error and if you do what's the exact error?
  • Anonymous
    January 01, 2007
    Thanks Andrian, it worked!! I followed your alternative way. -> An alternative is to configure the adapter web service manually.my experience here.http://biztalkblogs.com/fairycat/archive/2007/01/02/1546.aspx
  • Anonymous
    January 25, 2007
    Hi Adrian,I ran into a problem with WSS adapter when configuring the BizTalk Server 2006 at a customer.Configuration is cancelled, because it wants to delete the web.config but isn't allowed to set the according file attributes.I'm sorry that I can't give you the exact error message because it's a german BizTalk Server and I don't have a clou how to translate the message exactly. Must be something like "Error on setting file permissions on a temporary ASP.NET-directory or web service directory"My question now is: do you think that the manual workaround you discribed in your initial article will solve this problem.Oh ... by the way: I need to get WSS adapter running for WSS v2.GreetingsMatthias
  • Anonymous
    January 25, 2007
    Hi Matthias,The best way to troubleshoot this is:1) look in the configuration log file for more details on the failure2) run FileMon http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx and set a filter that includes the events generated by configuration.exe process. Then run configuration. This way you will see exactly the file causing the problem.Your translation of the error message makes me believe that the failure is not related to the web.config file. I think the configuration process fails to set some permissions on one of the ASP.NET temporary files folder, possiblyC:WINDOWSMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET FilesorC:WINDOWSTempThe configuration log fragment with the error would help me provide you with more information on this problem.
  • Anonymous
    January 28, 2007
    The comment has been removed
  • Anonymous
    June 06, 2007
    Hi Adrian,I am having BizTalk 2006 on 1 machine and Sharepoint 2007 on the othr machine. When I try to install the Sharepoint Adapter Webservice on Sharepoint machine the checkbox is disabled. Do i have to download the wss 3.0 v2 and try with that.Any help is appreciated.Thanks
  • Anonymous
    June 06, 2007
    No, you don't. Actually, unless you use BizTalk 2006 R2 Beta 2 you won't be able to make it work with WSS v3.What you probably need is the WSS language pack. The SharePoint language and the BizTalk language must match. If that's not the case for you then you have to install a WSS language pack for that checkbox to become enabled.
  • Anonymous
    August 31, 2007
    The scenario you have explained utilizes SharePoint Services V3 Beta 2 ;i have just downloded the latest release wss 3.0 versionSo, are there any changes with this newer version or can i go ahead and use the same approach
  • Anonymous
    August 31, 2007
    Hi AndrianI have downloaded the latest released version WSS 3.0, is there any chages in the procedure described by you or should i go with the same procedure as above?Thanx & Regards
  • Anonymous
    August 31, 2007
    The comment has been removed
  • Anonymous
    January 18, 2008
    The comment has been removed
  • Anonymous
    January 21, 2008
    BizTalk 2006 was released in 2006 (go figure :-) ...) and it doesn't support MOSS which was released in 2007. You need BizTalk 2006 R2 (released in September 2007) if you want to use it with MOSS. You can download an evaluation copy of BizTalk 2006 R2 here http://technet.microsoft.com/en-us/bb738059.aspxIt will work for 120 days.