3

我能够对组件进行内联编辑。我可以在“表单视图”中打开组件并保存组件，但是当我尝试单击“更新预览”按钮时，它会提示错误“架构参考 ID”。当我单击“SDL Tridion”标签或刷新页面时，同样的错误消息也会显示为警告。

Tridion 事件查看器中记录了以下错误： 

SCHEMA_REFERENCE_ID Component: Tridion.ContentManager.CoreService
   Errorcode: 0 User: NT AUTHORITY\NETWORK SERVICE StackTrace
   Information Details: at
   Tridion.ContentManager.Session.GetList(SystemWideListFilter filter)
   at
   Tridion.ContentManager.CoreService.CoreServiceBase.GetSystemWideListXml(SystemWideListFilterData
   filter) at SyncInvokeGetSystemWideListXml(Object , Object[] ,
   Object[] ) at
   System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object
   instance, Object[] inputs, Object[]& outputs) at
   Tridion.ContentManager.CoreService.TransactionSupportInvoker.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)

The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'.
The read operation failed, see inner exception.
The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'.
An existing connection was forcibly closed by the remote host


Component: Tridion.ContentManager.CoreService
Errorcode: 0
User: NT AUTHORITY\NETWORK SERVICE

StackTrace Information Details:
   at System.ServiceModel.Channels.SocketConnection.BeginReadCore(Int32 offset, Int32 size, TimeSpan timeout, WaitCallback callback, Object state)
   at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult..ctor(IConnection connection, Byte[] buffer, Int32 offset, Int32 count, TimeSpan timeout, AsyncCallback callback, Object state)
   at System.ServiceModel.Channels.ConnectionStream.BeginRead(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback callback, Object state)
   at System.Net.FixedSizeReader.StartReading()
   at System.Net.Security.NegotiateStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.NegotiateStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.NegotiateStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.NegotiateStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.NegotiateStream.BeginRead(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback asyncCallback, Object asyncState)
   at System.ServiceModel.Channels.StreamConnection.BeginRead(Int32 offset, Int32 size, TimeSpan timeout, WaitCallback callback, Object state)
   at System.ServiceModel.Channels.StreamConnection.BeginRead(Int32 offset, Int32 size, TimeSpan timeout, WaitCallback callback, Object state)
   at System.ServiceModel.Channels.SessionConnectionReader.BeginReceive(TimeSpan timeout, WaitCallback callback, Object state)
   at System.ServiceModel.Channels.SynchronizedMessageSource.ReceiveAsyncResult.PerformOperation(TimeSpan timeout)
   at System.ServiceModel.Channels.SynchronizedMessageSource.SynchronizedAsyncResult`1..ctor(SynchronizedMessageSource syncSource, TimeSpan timeout, AsyncCallback callback, Object state)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.BeginReceive(TimeSpan timeout, AsyncCallback callback, Object state)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult..ctor(FramingDuplexSessionChannel channel, TimeSpan timeout, AsyncCallback callback, Object state)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.BeginTryReceive(TimeSpan timeout, AsyncCallback callback, Object state)
   at System.ServiceModel.Channels.TransactionReceiveChannelGeneric`1.BeginTryReceive(TimeSpan timeout, AsyncCallback callback, Object state)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.BeginTryReceive(TimeSpan timeout, AsyncCallback callback, Object state)

新页面和插入组件选项也显示为禁用。虽然我在 Tridion 中创建了一种页面类型。

有没有人对可能导致问题的原因提出建议？

4

1 回答 1

6

页面类型可能需要浏览器刷新或缓存清除，因为它被大量缓存。重新打开浏览器通常对我有用。

另一个问题看起来您可能有一个错误配置的会话预览数据库（错误的版本或未在您的存储包装器中正确配置）。

于 2013-01-23T17:39:53.870 回答