Skip to main content

Posts

Showing posts from October, 2011

Power Automate: SharePoint Copy file action fails on file names with a plus (+) sign

SharePoint 2010: Taxonomy field and System.UnauthorizedAccessException

These days I had a problem with provisioning a list instance of a custom list definition which uses a taxonomy field. This feature is part of a custom site definition also. Interestingly I was able to use my site defintion to create a new site collection. All custom lists that had my taxonomy field on it did not make any trouble in this instance. But when I tried to create a sub web site with the same site definition the provisiong stopped with the following error: 10/27/2011 16:55:51.24 w3wp.exe (0x21D0) 0x197C SharePoint Foundation Feature Infrastructure 889w High The element of type 'ListInstance' for feature My.SiteDefinitions.Project.SGD_ProjectLists' (id: b7cbc5b3-decd-48ff-aa23-29fb7a0223f7) threw an exception during activation: Exception has been thrown by the target of an invocation. 0c0e2c1b-db4f-4619-911f-116a086ba2c1 10/27/2011 16:55:51.24 w3wp.exe (0x21D0) 0x197C SharePoint Foundation General 72by High Feature Activation: Threw an exception, attempting

SharePoint 2010: Error on publishing a custom content type via content type hub

Recently I tried to publish a custom content type of my content type hub from within a feature receiver and received the following error: 10/27/2011 09:17:14.74 w3wp.exe (0x20A8) 0x0F5C SharePoint Server Taxonomy fj2u Unexpected Content type publish failed with exception. Proxy MMS - CTH. Content type IT Document Set. System.ServiceModel.CommunicationException: An error occurred while receiving the HTTP response to http://sgdv01101:32843/8c74a6e67762437ea1547ee5f61d6236/MetadataWebService.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---&