Article ID: 983018 - Last Review: April 9, 2011 - Revision: 2.0

Error message when you use the Import-SPBusinessDataCatalogModel PowerShell cmdlet to retrieve the WSDL Business Data Catalog: "Proxy creation failed. Default context not found"

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You have a server that is running Microsoft SharePoint Server 2010 with Enterprise Client Access License (CAL) enabled. You use the following Windows PowerShell cmdlet to fetch the Web Services Description Language (WSDL) Business Data Catalog of the line-of-business (LOB) system: 
Import-SPBusinessDataCatalogModel
In this scenario, you receive the following error message:

Import-SPBusinessDataCatalogModel : Proxy creation failed. Default context not found.
Error was encountered at or just before Line: 'line#' and Position: 'position#'.
At line:line# char:char#
+ Import-SPBusinessDataCatalogModel <<<< -Identity $catalog -Path path_to_catalog\linkus.bdcm
+ CategoryInfo : InvalidData: (Microsoft.Share...alogModelCmdlet: SPImportSPBusinessDataCatalogModelCmdlet) [Import-SPBusinessDataCatalogModel], PackageFormatException
+ FullyQualifiedErrorId : Microsoft.SharePoint.BusinessData.SharedService.SPImportSPBusinessDataCatalogModelCmdlet

Back to the top

CAUSE

This issue occurs when the ServiceContext scope is not defined before you try to import the WSDL Business Data Catalog.
Back to the top

WORKAROUND

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

To work around this issue, you must define the ServiceContext scope before you try to use the Import-SPBusinessDataCatalogModel Windows PowerShell cmdlet. The following is an example Windows PowerShell script that implements this workaround: 
$ctx = Get-SPServiceContext http://localhost

$catalog = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType catalog -ServiceContext $ctx

$scope = new-object Microsoft.SharePoint.SPServiceContextScope $ctx; Import-SPBusinessDataCatalogModel -Identity $catalog -Path \\path_to_catalog\linkus.bdcm; 
$scope.Dispose()
To programmatically set the scope, you must use the following declarations:
SPServiceContextScope scope = null;
if (SPServiceContext.Current == null)

   {

    scope = new SPServiceContextScope(context);

   }
When the code finishes the import, you must dispose the scope as follows:
scope.Dispose()
Back to the top

MORE INFORMATION

For more information about how to set the scope for Business Data Catalog imports, visit the following SharePoint blog page:
SharePoint+PowerShell is (Usually) a Perfect Match (http://sharepoint.microsoft.com/Blogs/zach/Lists/Posts/Post.aspx?ID=34)
Back to the top
APPLIES TO
  • Microsoft SharePoint Server 2010
Back to the top
Keywords: 
kbprb kbsurveynew kbpubtypekc kbexpertiseadvanced kbcodefx kbscript KB983018
Back to the top