Asked by:
CRM 2013 IFD, 404 error for just some users, not all; Unrecognized error 232 (0xe8)

Question
-
Hi,
On a new implementation some, but not all, users get 404 - File or directory not found. error
These specific users were activated in CRM by another sysadmin user then the Original deployment administrative account used for the installation. I noticed that these activated users were not member of the ReportingGroup {GUID}. Adding the membership however did not fix the problem.
It's 2013 IFD UR 2; ADFS and CRM on one server.
On stack trace w3wp I see errors when the troubled user get 404:
[2014-05-16 07:55:23.045] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread: 15 |Category: Platform.Sdk |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: | ServiceModelTraceRedirector.TraceData ilOffset = 0x45
at ServiceModelTraceRedirector.TraceData(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, Object data) ilOffset = 0x45
at TraceSource.TraceData(TraceEventType eventType, Int32 id, Object data) ilOffset = 0x6E
at LegacyDiagnosticTrace.TraceEvent(TraceEventType type, Int32 code, String msdnTraceCode, String description, TraceRecord trace, Exception exception, Object source) ilOffset = 0x6B
at ExceptionUtility.ThrowHelper(Exception exception, TraceEventType eventType, TraceRecord extendedData) ilOffset = 0x61
at PipeConnection.StartSyncWrite(Byte[] buffer, Int32 offset, Int32 size, Object& holder) ilOffset = 0x79
at PipeConnection.WriteHelper(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, Object& holder) ilOffset = 0x4F
at PipeConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) ilOffset = 0x19
at BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager) ilOffset = 0x9E
at BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) ilOffset = 0x69
at ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count) ilOffset = 0x1A
at NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) ilOffset = 0x83
at NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) ilOffset = 0x4D
at NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count) ilOffset = 0x2D
at StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) ilOffset = 0x15
at StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager bufferManager) ilOffset = 0xD
at FramingDuplexSessionChannel.OnSendCore(Message message, TimeSpan timeout) ilOffset = 0x13
at TransportDuplexSessionChannel.OnSend(Message message, TimeSpan timeout) ilOffset = 0x7F
at OutputChannel.Send(Message message, TimeSpan timeout) ilOffset = 0x5C
at DuplexChannelBinder.Request(Message message, TimeSpan timeout) ilOffset = 0x76
at ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) ilOffset = 0x104
at ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) ilOffset = 0x25
at ServiceChannelProxy.Invoke(IMessage message) ilOffset = 0x68
at RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) ilOffset = 0x153
at ISandboxHost.Ping(SandboxCallInfo callInfo, SandboxHostConfiguration hostConfigurationInfo, SandboxWorkerConfiguration workerConfigurationInfo, CrmTraceRemoteSettings remoteSettings, SandboxWorkerExecutionRecord& workerExecutionRecord, String& hostSidSddlForm) ilOffset = 0xFFFFFFFF
at SandboxHostManager.PingSingleClient(SandboxClient pingClient, SandboxHostInfo info) ilOffset = 0xC4
at SandboxHostManager.PingHostsInternal(Object stateObject) ilOffset = 0x279
at SandboxHostManager.PingHosts(Object stateObject) ilOffset = 0x35
at ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) ilOffset = 0x70
at ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) ilOffset = 0x4
at TimerQueueTimer.CallCallback() ilOffset = 0x57
at TimerQueueTimer.Fire() ilOffset = 0x49
at TimerQueue.FireNextTimers() ilOffset = 0xE9
><TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/nl-NL/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>/LM/W3SVC/2/ROOT-1-130446930222157999</AppDomain><Exception><ExceptionType>System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error writing to the pipe: Unrecognized error 232 (0xe8).</Message><StackTrace> at System.ServiceModel.Channels.PipeConnection.StartSyncWrite(Byte[] buffer, Int32 offset, Int32 size, Object&amp; holder)
> at System.ServiceModel.Channels.PipeConnection.WriteHelper(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, Object&amp; holder)
> at System.ServiceModel.Channels.PipeConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
> at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager)
> at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
> at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count)
> at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest- Edited by Alexander Ruiter CRM Specialist Friday, May 16, 2014 6:33 AM
Friday, May 16, 2014 6:31 AM
All replies
-
It seems that the users were not created the right way: When you create a new CRM user and paste a user account, CRM should solve some fields from AD. When this does not happen, You do not enter these fields by hand but find out what is wrong first.
Thursday, September 3, 2015 9:25 AM