3

コンポーネントのインライン編集を行うことができます。「フォーム ビュー」でコンポーネントを開き、コンポーネントを保存できますが、「プレビューの更新」ボタンをクリックしようとすると、「スキーマ参照 ID」というエラーが表示されます。「SDL Tridion」タグをクリックするか、ページを更新すると、同じエラー メッセージが警告として表示されます。

以下のエラーが Tridion Event Viewer に記録されました: 

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 で 1 つのページ タイプを作成しましたが。

問題の原因について誰か提案がありますか?

4

1 に答える 1

6

このタイプのページは頻繁にキャッシュされるため、ブラウザの更新またはキャッシュのクリアが必要になる場合があります。ブラウザを再度開くと、通常はそれが行われます。

もう 1 つの問題は、セッション プレビュー データベースの構成が間違っている可能性があるようです (バージョンが間違っているか、ストレージ ラッパーで正しく構成されていません)。

于 2013-01-23T17:39:53.870 に答える