11

Recently i have migrated my database and CME to SDL Tridion 2013 . Publishing and creating of components are success. But when i try to edit a schema or copy a schema and try to open its design I get the following errors.

  1. Unable to save schema

  2. Unable to retrieve converted schema.

enter image description here

enter image description here

Improve this question
7
  • Hi Sam, I have reformatted your question to make it a little easier to understand, you may want to add a specific question to the text.
    – Rob Stevenson-Leggett
    Commented Jun 10, 2013 at 14:11
  • 2
    Can you post what's in the "Show details" and if there's anything in the Tridion event log?
    – Andrey Marchuk
    Commented Jun 10, 2013 at 14:20
  • Tridion event log gives "System Error" . Show details is the pop up which i have shown in the screenshot .
    – Sam
    Commented Jun 11, 2013 at 4:55
  • Can you post stack trace from Tridion event log?
    – Andrey Marchuk
    Commented Jun 11, 2013 at 10:53
  • System error. Component: Tridion.ContentManager.CoreService Errorcode: 0 User: NT AUTHORITY\NETWORK SERVICE StackTrace Information Details: at System.ServiceModel.Dispatcher.DispatchOperationRuntime.ValidateMustUnderstand(MessageRpc& rpc) 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 isOperation)
    – Sam
    Commented Jun 12, 2013 at 3:57

2 Answers 2

Reset to default
6

Thanks for your valuable responses and we have figured out the issue with the support from SDL Tridion

Note : we have all the DTC configurations in place .

Resolution : In Tridion_Home/bin/TcmServiceHost.exe.config . In the bindings the transaction protocol is changed to OLEtransactions from WSAtomicTransaction11. Previously it was written as: 

<binding name="CoreService_netTcpBinding" transactionFlow="true" 
         transactionProtocol="WSAtomicTransaction11" 
         maxReceivedMessageSize="2147483647" closeTimeout="00:30:00" 
         openTimeout="00:30:00" receiveTimeout="00:30:00" sendTimeout="00:30:00">

It has been changed to:

<binding name="CoreService_netTcpBinding" transactionFlow="true" 
         transactionProtocol="OleTransactions" maxReceivedMessageSize="2147483647" 
         closeTimeout="00:30:00" openTimeout="00:30:00" receiveTimeout="00:30:00" 
         sendTimeout="00:30:00">
Improve this answer
3

Had a similiar problem with schemas on a fresh install of 2013 in Windows 2012
It turned out that DTC had been installed but not configured. We just enabled everything, but check older version installation instructions for the actual DTC configuration required, I am sure I recall it was a requirement in earlier versions.
Security Settings
[x] Network DTC Access
Client and Administration
[x] Allow Remote Clients
Transaction Manager Communication
[x] Allow Inbound [x] Allow Outbound
(0) No authentication Required

[x] Enable XA Transations [x] Enable SNA LU 6.2 Transactions

(will update with a screen shot when I have more points)

Improve this answer
0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.