Hi Mamina,
We have tried all different kinds of traces and there was no noticeable issues. Several cases were opened with Microsoft and there was no issues at application or database end. The conclusion of all that is that it's an environmental issue related to the customer's specific environment.
But the customer really wants to understand what's wrong with their environment even if they need an infrastructure engineer to understand the root cause of the issue and how they can solve it.
This customer is working with Microsoft Dynamics GP since 2007 with 73 concurrent users and very heavy inventory, sales & manufacturing transactions. Their end results despite of the hang issues & posting interruptions are accurate because they have a good technical team that follow & solve errors caused by the posting interruptions but the cost of this is so much time spent to correct those issues.
Our conclusion is that this happens sometimes when there are 15 to 20 users posting very heavy batches at the same time, We see that this causes deadlocks and that posting stops processing, DEX_Session & DEX_Lock tables become inaccessible & in order to get over that we either have to restart the SQL server service or restart the server and then clear DEX_Session, DEX_Lock, Activity, SY00800 & SY00801 and solve the realated issues afterwards but this doesn't guarantee that the issue won't happen again as it keeps coming once or twice a week.
They are willing to make changes to their infrastructure but they want to know the real cause whether it's related to their server resources or internet provider as their branches use RDS to enter & post their transactions but the problem is that this issue is not within the application scope so they never got a satisfying reply to any of their queries to Microsoft.
