Could not find exactly 1 Member with name ‘%s’ Parameter name: fieldname – Business Data Catalog Definition Editor

    Recently I was building a BDC application using the “Business Data Catalog Definition Editor”. It’s a nice free tool that comes with the MOSS SDK, By default it generates the SpecificFinder and IdEnumerator methods.It doesn’t do the same for the Finder method. I was trying to create one Finder method and landed up in the following error that says “Could not find exactly 1 Member with name ‘[ColumnName]‘ Parameter name: fieldname”, before figuring out it is not my mistake I spent couple of hours to make sure that all the steps I have followed is right . Finally I came across this article that helped me to solve the issue {Thanks Chris}. As it was hard to find the solution in the net I am reposting the steps to resolve the error.

                         Key point here is that In Parameters should be specified before the Return parameter. That will solve the issue.

Adding Server Side code to the Publishing Page Layouts – PageParserPaths

This article is to give a brief introduction for the Functionality of PageParserPaths tag in the Web.Config file of SharePoint. (It serves as a Reference for me In future and for someone out there looking for a similar implementation).

All the Layout pages in the SharePoint 2007 are derived from the class

Microsoft.SharePoint.Publishing.PublishingLayoutPage .

This works very well for most of the cases and customization. But there will be very chance that for some reason you want the actual page instance to have a completely different class. Might be a case where you are using a third part tool or a component. In this case if you try to change the base class or put in some custom server side code in to the page layout file, SharePoint will complain you with a parser error.

This Article describes the approach that will help you to put in the code for the layout pages. It works like charm.

On additions to the above article is that in case if you are concerned about allowing all the pages having the server code as defined by below tag

<PageParserPath VirtualPath=”/_layouts/masterpage/*” CompilationMode=”Auto” AllowServerSideScript=”true”

IncludeSubFolders=”true”/>

You can make a particular page to have server side code as below

<PageParserPath VirtualPath=”/_layouts/masterpage/yourpage.aspx” CompilationMode=”Auto” AllowServerSideScript=”true”

IncludeSubFolders=”true”/>

While configuring a single page, make sure that you remove the attribute IncludeSubFolders=”true”. If you leave this tag as it is, all you are going to get is a plain HTTP 500 error code which is hard to debug. Validation that SharePoint makes here is IncludeSubFolders=”true” can be present only if the attribute VirtualPath ends with /*.

STSADM command – Quick Reference

This Poster will help you as Quick Reference for STSADM Command tool.

http://blogs.msdn.com/sharepoint/archive/2008/05/12/posters-for-sharepoint-stsadm-command-line-parameters-now-available.aspx

Unable to Create new SSP – Created new Web Application not getting listed in the list.

When you try to create a new SSP you might run in to surprise that the newly created web application will not get listed in the list web application of new SSP page.
One quick check you need to perform in this case is to check the App Pool account of the Web Application. If it is Network Services then that the issue. You can find the answer in same New Shared Services Provider page.

J

SharePoint – Quick Help Commands!!!

Process ID for the Web Application:

While debugging SharePoint application mainly SharePoint Workflow you will need to find the Process ID of the Web Application you are trying to Debug. If each of the web application runs in same user account its tough to find the same.

Run the below command that will list all the Application Pool and Its Process ID

c:\windows\system32\cscript.exe c:\windows\system32\iisapp.vbs

Run To access STSADM from any directory in command Prompt:

Add the 12Hive\Bin path to the Windows Environment PATH Variable.

More: Here

Enable Usage Analysis Processing in MOSS2007

Enabling the Usage analysis process in the V3.0 is quite different from V2.0 and here is the steps to enable the same.

Open Central Administration page of the SharePoint Server and Click open the Operations tab.

In the Operations Tab click open the link “Usage Analysis Processing ” in the section Logging and Reporting .

In the usage Analysis Processing Check enable the Check Box “Enable Logging “.

Set log file location and Number of log files to be created [ Note:If the Log file location is changed from default value then there are few additional steps needs to be followed to provide sharepoint server the rights to read,write and delete the files from that folder.]

Check enable the “Usage analysis Processing” check box and set the time that you like the server to process these files.

Click open the central admin page and select Shared Service Administration Link.

In the Manage shared service page select the shared service to which your site that needs be enabled for usage analysis is linked.In the below fig I am trying to set the usage analysis for the SharePoint – 6000,So I am selecting the SharedServices1.

Open the shared Admin page as below

In the Shared Admin page select the link Usage Reporting under the section Portal Usage Reporting

In the configure Advanced Usage Analysis processing Check enable the Enable Advanced Usage analysis processing.

Once done you can access the Report from Usage Report Link from the SiteSetting page of your site.Please note that the In order to get to view the report data you should allow the site for a day thus enabling it to get the sufficent data for the report.