Oppss this is a stupid mistake that I have ever made. This issue is caused by the guest machine date is in the past compare with the host machine. I only checked the time on guest and host machine that already the same. But, I forgot to check the date.
Here is the clue:
System.ServiceModel.Security.MessageSecurityException, System.ServiceModel,
Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>The security timestamp is stale because its expiration time
('2014-04-03T06:49:23.526Z') is in the past. Current time is '2014-04-04T06:44:14.447Z'
and allowed clock skew is '00:05:00'.</Message><StackTrace> at
System.ServiceModel.Security.SecurityTimestamp.ValidateFreshness(TimeSpan timeToLive,
TimeSpan allowedClockSkew)
Here is the best way to check some error that occurred on CRM (doesn't appear on client side):
- Enable tracing in Microsoft Dynamics CRM to get the real issue that occurs
- Read the log/stack trace file that usually available on C:\Program Files\Microsoft Dynamics CRM\Trace
Hope this steps is useful for the others.