Answered SharePoint exception on Publishing pages

  • Tuesday, June 21, 2011 6:58 PM
     
     

    The following exceptions on every publishing page while debugging, how to fix whatever is broken?

    System.IO.FileNotFoundException crossed a native/managed boundary
      Message=<nativehr>0x80070002</nativehr><nativestack></nativestack>
      Source=""
      StackTrace:
           at Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
           at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)
           at Microsoft.SharePoint.SPWeb.GetObjectForUrl(String strUrl, Guid& listId)
           at Microsoft.SharePoint.SPWeb.GetObject(String strUrl)
           at Microsoft.SharePoint.Publishing.CachedObjectFactory.CreateListItemFromUrl(String url, SPWeb contextWeb, Boolean enableCheckedOutItem)
      InnerException:

    System.ComponentModel.Win32Exception crossed a native/managed boundary

    System.ComponentModel.Win32Exception crossed a native/managed boundary

    System.ComponentModel.Win32Exception crossed a native/managed boundary
      Message=Cannot complete this function
      Source=Microsoft.SharePoint
      ErrorCode=-2147467259
      NativeErrorCode=1003
      StackTrace:
           at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)
      InnerException:

    System.ComponentModel.Win32Exception crossed a native/managed boundary
      Message=Cannot complete this function
      Source=Microsoft.SharePoint
      ErrorCode=-2147467259
      NativeErrorCode=1003
      StackTrace:
           at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)
      InnerException:

    System.ComponentModel.Win32Exception crossed a native/managed boundary
      Message=Cannot complete this function
      Source=Microsoft.SharePoint
      ErrorCode=-2147467259
      NativeErrorCode=1003
      StackTrace:
           at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)
      InnerException:

    System.ComponentModel.Win32Exception crossed a native/managed boundary
      Message=Cannot complete this function
      Source=Microsoft.SharePoint
      ErrorCode=-2147467259
      NativeErrorCode=1003
      StackTrace:
           at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)
      InnerException:

    System.ComponentModel.Win32Exception crossed a native/managed boundary
      Message=Cannot complete this function
      Source=Microsoft.SharePoint
      ErrorCode=-2147467259
      NativeErrorCode=1003
      StackTrace:
           at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)
      InnerException:

Answers

  • Wednesday, June 22, 2011 5:10 PM
     
     Answered

    By removing all projects not related to what is being debugged, seems to stop these exceptions.

    Thankfully. 

    • Marked As Answer by MULTISY Wednesday, June 22, 2011 5:10 PM
    •  

All Replies

  • Tuesday, June 21, 2011 7:21 PM
     
     

    Try to remove the tick for VS -> tools -> options -> debugging -> Break when exceptions cross AppDomain or managed/native boundaries 



  • Tuesday, June 21, 2011 9:24 PM
     
     

    Thank you, but exceptions still occur.  SharePoint is trying to do something it cannot.

    System.ComponentModel.Win32Exception occurred
      Message=Cannot complete this function
      Source=Microsoft.SharePoint
      ErrorCode=-2147467259
      NativeErrorCode=1003
      StackTrace:
           at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow(SPDocumentBindRequest& dbreq, SPDocumentBindResults& dbres)
      InnerException:

  • Wednesday, June 22, 2011 5:10 PM
     
     Answered

    By removing all projects not related to what is being debugged, seems to stop these exceptions.

    Thankfully. 

    • Marked As Answer by MULTISY Wednesday, June 22, 2011 5:10 PM
    •