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. ---> System.Net.Sockets.SocketException: ... 70fd07d0-37eb-4743-a68a-a34707fb87b1
10/27/2011 09:17:14.74* w3wp.exe (0x20A8) 0x0F5C SharePoint Server Taxonomy fj2u Unexpected ...An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpCha... 70fd07d0-37eb-4743-a68a-a34707fb87b1
10/27/2011 09:17:14.74* w3wp.exe (0x20A8) 0x0F5C SharePoint Server Taxonomy fj2u Unexpected ...nnelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.Invok... 70fd07d0-37eb-4743-a68a-a34707fb87b1
...
...
...
It took me a couple of days to find the solution to this issue. To make it simple, the problem was that my custom content type had a document template which has a file size greater than 10MB. The managed metadata service is limit to an IIS default file size and so I thought I could try to allow the services to use greater file sizes.
In order to do this you have to go to the following location and open the web.config file:
Open the following file:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root\web.config
There I had to add some configuration lines (httpRuntime line,webServer section):
You wanna do an IISReset after this otherwise the application won't behave well.
After this was done I was able to use bigger files sizes for my document templates of my custom content types.
I hope this can help you too.
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. ---> System.Net.Sockets.SocketException: ... 70fd07d0-37eb-4743-a68a-a34707fb87b1
10/27/2011 09:17:14.74* w3wp.exe (0x20A8) 0x0F5C SharePoint Server Taxonomy fj2u Unexpected ...An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) --- End of inner exception stack trace --- Server stack trace: at System.ServiceModel.Channels.HttpCha... 70fd07d0-37eb-4743-a68a-a34707fb87b1
10/27/2011 09:17:14.74* w3wp.exe (0x20A8) 0x0F5C SharePoint Server Taxonomy fj2u Unexpected ...nnelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.Invok... 70fd07d0-37eb-4743-a68a-a34707fb87b1
...
...
...
It took me a couple of days to find the solution to this issue. To make it simple, the problem was that my custom content type had a document template which has a file size greater than 10MB. The managed metadata service is limit to an IIS default file size and so I thought I could try to allow the services to use greater file sizes.
In order to do this you have to go to the following location and open the web.config file:
Open the following file:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root\web.config
There I had to add some configuration lines (httpRuntime line,webServer section):
<system.web> <httpRuntime maxRequestLength="51200" /> <membership defaultProvider="i"> <providers> <clear /> <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> </providers> </membership> <roleManager enabled="true" defaultProvider="c"> <providers> <clear /> <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> </providers> </roleManager> </system.web> <system.webServer> <security> <requestFiltering allowDoubleEscaping="true"> <requestLimits maxAllowedContentLength="2147483647" /> </requestFiltering> </security> </system.webServer>
You wanna do an IISReset after this otherwise the application won't behave well.
After this was done I was able to use bigger files sizes for my document templates of my custom content types.
I hope this can help you too.
Comments
Post a Comment