We're working on setting up a BizTalk environment and have run into an issue
installing the BizTalk Adapter for Sharepoint from the GotDotNet.com website
.

Our environment consists of 4 servers: one BizTalk server and a
corresponding remote SQL server and a Sharepoint server with a corresponding
remote SQL server.

The BizTalk installation and configuration went without incident as well as
the Sharepoint server's installation and configuration.

We followed the adapter's installation instructions on the BizTalk server by
importing the REG file--that part went fine. Next step is to add the adapter
within BizTalk Server Administration Tool. We expand the Adapters area and
right-click and choose New--->Adapter, give it the name WSSLib and choose
WSSLib from the dropdown list of available adapters.

When we click on OK, however we get a dialog box with an error
"ArgumentNull_String" and when we click on the Advanced button on that
dialog, the additional information that is shown is "Parameter name: g"

Does anyone have any idea what might be going on? Nothing available in the
server's event logs and can't seem to find any other type of log that might
give more clues.

Thanks for any help.

[ Post a follow-up to this message ]

The information from the registry is used when you do the adapter
registration. This means that the registry information could be wrong.
One of the more common mistakes is to not escape the '' character in the
registry file. All the paths in your registry file must contain
doubled '' character. For instance the path "C:\Program Files\Microsoft
BizTalk' must show up like this in your registry file
"C:\\Program Files\\Microsoft BizTalk"

If the character '' is not escaped (showing up twice) that particular
registry value is not imported at all.  That could explain the null
exception.

Try to compare the registry with your registry file and make sure that all
the keys are present and that the values are correct.


--------------------[vbcol=seagreen] 
issue[vbcol=seagreen] 
website.[vbcol=seagreen] 
corresponding[vbcol=seagreen] 
as[vbcol=seagreen] 
by[vbcol=seagreen] 
adapter[vbcol=seagreen] 
and[vbcol=seagreen] 
the[vbcol=seagreen] 
might[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

Adrian,

We were just using the REG file that came with the Sharepoint adapter
installation files.  I double-checked the REG file, the paths that the REG
file points to for the DLL's and it looks like everything is in order.

Do you have any idea what type of error the "ArgumentNull_String" is?  Is it
caused by insufficient permissions somewhere?  The account I'm logged in wit
h
while trying to set up the adapter is a local administrator on the BizTalk
server, the Sharepoint server and the BizTalk's remote SQL server.  Any idea
where that account would possibly need additional rights if it's a rights
issue?

Thanks for your prompt response.

Shawn

"Adrian Hamza [MSFT]" wrote:

> The information from the registry is used when you do the adapter
> registration. This means that the registry information could be wrong.
> One of the more common mistakes is to not escape the '' character in the
> registry file. All the paths in your registry file must contain
> doubled '' character. For instance the path "C:\Program Files\Microsoft
> BizTalk' must show up like this in your registry file
> 	"C:\\Program Files\\Microsoft BizTalk"
>
> If the character '' is not escaped (showing up twice) that particular
> registry value is not imported at all.  That could explain the null
> exception.
>
> Try to compare the registry with your registry file and make sure that all
> the keys are present and that the values are correct.
>
>
> -------------------- 
> issue 
> website. 
> corresponding 
> as 
> by 
> adapter 
> and 
> the 
> might 
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> EBusiness Server Team
>
>

[ Post a follow-up to this message ]

Also--just another quick question: Is the Sharepoint adapter officially
supported by Microsoft?

Thanks.

"Adrian Hamza [MSFT]" wrote:

> The information from the registry is used when you do the adapter
> registration. This means that the registry information could be wrong.
> One of the more common mistakes is to not escape the '' character in the
> registry file. All the paths in your registry file must contain
> doubled '' character. For instance the path "C:\Program Files\Microsoft
> BizTalk' must show up like this in your registry file
> 	"C:\\Program Files\\Microsoft BizTalk"
>
> If the character '' is not escaped (showing up twice) that particular
> registry value is not imported at all.  That could explain the null
> exception.
>
> Try to compare the registry with your registry file and make sure that all
> the keys are present and that the values are correct.
>
>
> -------------------- 
> issue 
> website. 
> corresponding 
> as 
> by 
> adapter 
> and 
> the 
> might 
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> EBusiness Server Team
>
>

[ Post a follow-up to this message ]

No, the SharePoint adapter on GotDotNet is NOT supported by Microsoft.
With regard to permissions, you might have to be a BizTalk Administrator as
well.

--------------------[vbcol=seagreen] 
<7n3j6UOJFHA.132@TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen] 
the[vbcol=seagreen] 
Files\Microsoft[vbcol=seagreen] 
all[vbcol=seagreen] 
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl[vbcol=seagreen] 
microsoft.public.biztalk.appintegration:7752[vbcol=seagreen] 
an[vbcol=seagreen] 
well[vbcol=seagreen] 
server[vbcol=seagreen] 
area[vbcol=seagreen] 
choose[vbcol=seagreen] 
that[vbcol=seagreen] 
g"[vbcol=seagreen] 
in[vbcol=seagreen] 
rights.[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]

Shawn,

The Sharepoint Adapter on GotDotNet and all samples, adapters, etc.
produced by the community are not supported by Microsoft.

Regards,
Doug Girard [MSFT]

Note: This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
>Thread-Topic: BizTalk Adapter for Sharepoint installation problem
>thread-index: AcUk+91yA5wjFiUmSeiRzbLDzs2LcA==
>X-WBNR-Posting-Host: 63.172.241.18
>From: examnotes <shawn.hansen at lrs dot com>
>References:  <77FF914D-0841-4A2E-81D2-1984D9BF0CDD@microsoft.com>
<7n3j6UOJFHA.132@TK2MSFTNGXA02.phx.gbl>
>Subject: RE: BizTalk Adapter for Sharepoint installation problem
>Date: Wed, 9 Mar 2005 15:01:02 -0800
>Lines: 88
>Message-ID: <CF5DB138-444D-4D0D-A6D2-F916444662F4@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.biztalk.appintegration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.biztalk.appintegration:7755
>X-Tomcat-NG: microsoft.public.biztalk.appintegration
>
>Also--just another quick question: Is the Sharepoint adapter officially
>supported by Microsoft?
>
>Thanks.
>
>"Adrian Hamza [MSFT]" wrote:
> 
the[vbcol=seagreen] 
all[vbcol=seagreen] 
microsoft.public.biztalk.appintegration:7752[vbcol=seagreen] 
well[vbcol=seagreen] 
server[vbcol=seagreen] 
choose[vbcol=seagreen] 
g"[vbcol=seagreen] 
rights.[vbcol=seagreen] 
>

[ Post a follow-up to this message ]

Just as a follow up to this issue, the problem turned out not to be related
to the Sharepoint adapter itself.

Turns out that there were MSDTC communication problems between the BizTalk
server and the backend SQL server.  We had to uninstall and reinstall MSDTC
and things began working fine.

""Doug Girard [MSFT]"" wrote:

> Shawn,
>
> The Sharepoint Adapter on GotDotNet and all samples, adapters, etc.
> produced by the community are not supported by Microsoft.
>
> Regards,
> Doug Girard [MSFT]
>
> Note: This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> -------------------- 
> <7n3j6UOJFHA.132@TK2MSFTNGXA02.phx.gbl> 
> the 
> all 
> microsoft.public.biztalk.appintegration:7752 
> well 
> server 
> choose 
> g" 
> rights. 
>
>

[ Post a follow-up to this message ]

Hi Shawn,
Thanks for sharing this, it's going to help other people that face the same
problem.
Adrian.
--------------------[vbcol=seagreen] 
<7n3j6UOJFHA.132@TK2MSFTNGXA02.phx.gbl>
<CF5DB138-444D-4D0D-A6D2-F916444662F4@microsoft.com>
<T11BhzZJFHA.1136@TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen] 
related[vbcol=seagreen] 
BizTalk[vbcol=seagreen] 
MSDTC[vbcol=seagreen] 
no[vbcol=seagreen] 
microsoft.public.biztalk.appintegration:7755[vbcol=seagreen] 
officially[vbcol=seagreen] 
wrong.[vbcol=seagreen] 
in[vbcol=seagreen] 
Files\Microsoft[vbcol=seagreen] 
particular[vbcol=seagreen] 
that[vbcol=seagreen] 
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl[vbcol=seagreen] 
into an[vbcol=seagreen] 
GotDotNet.com[vbcol=seagreen] 
as[vbcol=seagreen] 
the[vbcol=seagreen] 
area[vbcol=seagreen] 
that[vbcol=seagreen] 
name:[vbcol=seagreen] 
available in[vbcol=seagreen] 
that[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]