Tridion UI - Bad Request

Question

I installed Tridion UI 2012 in the documentation, and everything seems fine, and I can use the user interface functions such as creating a new page, changing an existing page, etc., but all at once (I could not limit when or why). I get a "bad request" error when I click Update Preview. A detailed error is displayed in the event viewer:

Log Name: Tridion Source: Tridion Publishing Date: 10/07/2012 12:03:37 Event ID: 100 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ZZZZZ Description: Unable to update or add Binaries using OData Service. An error occurred while processing this request. BadRequest Component: Tridion.SiteEdit.FastTrackPublishing Errorcode: 1003 User: NT AUTHORITY\NETWORK SERVICE StackTrace Information Details: at System.Data.Services.Client.DataServiceContext.SaveResult.<HandleBatchResponse>d__1e.MoveNext() at System.Data.Services.Client.DataServiceContext.SaveResult.HandleBatchResponse() at System.Data.Services.Client.DataServiceContext.SaveResult.EndRequest() at System.Data.Services.Client.DataServiceContext.SaveChanges(SaveChangesOptions options) at Tridion.SiteEdit.FastTrackPublishing.ServiceImplementation.SaveBinaries(RenderedItem renderedItem, ContentDeliveryService service) at Tridion.SiteEdit.FastTrackPublishing.ServiceImplementation.SaveBinaries(RenderedItem renderedItem, ContentDeliveryService service) at Tridion.SiteEdit.FastTrackPublishing.ServiceImplementation.Preview(IEnumerable`1 publishedItemsInfo, TcmUri publishingTargetId) at Tridion.SiteEdit.FastTrackPublishing.ServiceImplementation.Preview(IEnumerable`1 publishedItemsInfo, TcmUri publishingTargetId) at SyncInvokePreview(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet) 

Have you seen this error before? Any ideas on how to avoid / restore it?

Relationship emma

Answer 1

A bit late for the party, but in my case it was caused by binaries that were too big. You can identify the problem in more detail by following these steps: (Tridion 2011, SP1, HR2, but I assume this also applies in 2013)

• On the CMS server, open TcmServiceHost.exe.config and uncomment the body of the following tag:

  <system.diagnostics><sources>

• Find the <sharedListeners> and create the directory specified in the initializeData attribute (or update this parameter)

• Restart the TcmServiceHost service and click Update Preview. A log file will appear and you can open it in SvcTraceViewer

Find the red entrance and from there.

To allow large binaries (consider the cost of execution!), Go to your OData session preview service and do the following:

• Open web.config and find <bindings><webHttpBinding> (corresponding binding, of course, but usually it's webHttpBinding .)

• Add a binding with the following properties (inside the <webHttpBinding> element):

  <binding name="AdustedBindingConfiguration" maxReceivedMessageSize="2097152000" maxBufferSize="2097152000"> <readerQuotas maxArrayLength="81920" maxBytesPerRead="5120" maxDepth="32" maxNameTableCharCount="81920" maxStringContentLength="2097152" /> </binding>

• Find the <services><service> and find the appropriate service ("Tridion.ContentDelivery.Webservice.ODataService" and update the bindingConfiguration attribute to match the name of the newly added binding (in this case, AdjustedBindingConfiguration)

• Click "Update Preview" again

Answer 2

I didn’t see this one, but something similar when the session preview delivery endpoint URL was configured incorrectly.

Reading the error description I would suggest that your final URL (oData session preview service) is up and running, but there may be a number of other problems. I would check if you can manually view this oData service, and if that looks fine, check its log files for more details.

In IIS, this usually means a problem with the correct banks and DLLs. To do this, follow these steps:

• For the oData website, make sure that the DLL files are copied from the folder "User Interface" \ "Content Delivery", "Roles" \ web service \ dotNET \ webapp \ x86_64.zip \ bin and the banks are updated with \ Content Delivery \ roles \ webservice \ dotNET \ webapp \ x86_64.zip \ Bin
• For the oData website, make sure the web.config "bindingConfiguration" attributes are correct.
• To view the website, make sure that the DLL files are copied from the "User Interface" \ "Content Delivery \ Roles \ Web \ dotNET \ webapp \ x86_64.zip \ bin" folder, and all banks are replaced by the contents from the "User Interface" \ Content Delivery \ Web \ Dotnet \ WebApp \ x86_64.zip \ Bin \ Lib

Answer 3

For me, the solution was to increase maxReceivedMessageSize to "524288000" and maxBufferSize to "524288000" in the standard session view web service web.config

 <webHttpBinding> <binding name="HttpBinding" maxReceivedMessageSize="524288000" maxBufferSize="524288000"> <readerQuotas maxArrayLength="81920" maxBytesPerRead="5120" maxDepth="32" maxNameTableCharCount="81920" maxStringContentLength="2097152" /> <security mode="TransportCredentialOnly"> <transport clientCredentialType="None" /> </security> </binding>