Error

Sharepoint WSS 3.0: Lists.asmx Error Codes

Chilberto — Thu, 06 Mar 2008 20:59:06 GMT

Just some notes relating to error codes received during Sharepoint integration using the UpdateListItems method of the lists.asmx service.

A value in the update for a column exceeded the maximum column size.

<ErrorCode xmlns="http://schemas.microsoft.com/sharepoint/soap/">Invalid text value

A text field contains invalid data. Please check the value and try again.</ErrorText>

A column to be updated was passed in that did not exist.

<ErrorCode xmlns="http://schemas.microsoft.com/sharepoint/soap/">One or more field types are not installed properly. Go to the list settings page to delete these fields.</ErrorText>
</Result>

The field being updated was a lookup field that allows multiple values and the value passed in contained a trailing ";". A trailing semi-colon only seems to be an issue when it is the first item in the list.

<ErrorCode xmlns="http://schemas.microsoft.com/sharepoint/soap/">Bad parameter passed to Web Server Extensions. Check the information you entered and try again.</ErrorText>
</Result>

Guidance Automation blues...

Chilberto — Fri, 25 Jan 2008 14:57:53 GMT

I've recently had a battle updating Guidance Automation to the most recent release.

The main issue was I had to remove old Guidance Automation Packages without the original source project. The only way I found was to an xml file in the C:\Documents and Settings\All Users\Application Data\Microsoft\RecipeFramework folder that contains a list of the installed packages.

BAM 2006 with SQL Server 2005

Chilberto — Fri, 21 Sep 2007 16:32:32 GMT

Just a post to help those newbies to BAM, like me, out there in regards to an issue I encountered getting my OLAP cubes to display data.

The BizTalk 2006 R2 documentation describing getting BAM to work is based on using a SQL Server 2000 database, and in particular DTS. In an environment using SQL Server 2005, DTS is not used, but Integration Services. So if you encounter a situation where you are successfully adding to BAM (re., the primary import database), but your aggregation views are not displaying data:

Make sure Integration Services is running
Run the relevant BAM packages in the Integration Services (e.g., connect to Integration Services using SQL Server Management Studio and find the packages under the stored packages section)

WCF BAM Interceptors and primaryImportConnectionString

Chilberto — Fri, 24 Aug 2007 20:50:05 GMT

When trying to get the example in Instrumenting the WCF Getting Started Sample (BizTalk Server Sample) to run, I encountered the following error:

Server Error in '/servicemodelsamples' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'primaryImportConnectionString'. Note that attribute names are case-sensitive.

Source Error:


            Line 50:       <endpointBehaviors>
Line 51:         <behavior name="bamBehavior">
Line 52: 			<BamBehaviorExtension primaryImportConnectionString=
"Integrated Security=SSPI;Data Source=.;Initial Catalog=BAMPrimaryImport;" PollingIntervalSec="1500"  >
Line 53: 			 </BamBehaviorExtension>
Line 54:

Source File: f:\inetpub\wwwroot\servicemodelsamples\web.config Line: 52

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

After using Lutz Roeder's Reflector, I was able to determine that the configuration should be changed to:

<behavior name="bamBehavior">
    <BamEndpointBehaviorExtension 
        ConnectionString="Integrated Security=SSPI;Data Source=.;Initial Catalog=BAMPrimaryImport;"
        PollingIntervalSec="1500" />
  </behavior>

I could not find a mention of this in Google, so hopefully this will save someone some time out there.