External Exception C0000006 when creating an internal message

[bdbrower]

After creating a new message, as I begin to type the body of the message I get the above "Oooppsss..." message after typing a "space" after the first word (first word makes no difference, it can be any word). This doesn't happen every time, but once it starts there is no way to complete a new message without closing CommitCRM and reopening it, and it happens often enough (multiple times a day) to be an annoying hindrance to our productivity.

[Support Team]

Re: External Exception C0000006 when creating an internal message

Thank you for posting this. Usually the error C0000006 is related to network disconnects, however it may be also related to permissions. We recommend you to close any running services and sessions of RangerMSP and re-apply access right to the RangerMSP folder tree including sub-folders. In addition, if you keep seeing this error, verify that your network adapter is not configured to go-to-sleep-on-idle as in some cases this might cause disconnects that might cause this error.

Hope this help.

[sam.otago]

Re: External Exception C0000006 when creating an internal message

In relation to this, can you please make the CommitCRM more reslient to network blips? It would be great if the client was able to gracefully reconnect after brief outages, without a rather messy crash and exit.

[Support Team]

Re: External Exception C0000006 when creating an internal message

We would first recommend that you try to get to the bottom of what is causing such network blips as this might cause plenty of other issues, anyway, when using RangerMSP with its optional back-end SQL engine it does manage to reconnect and auto-overcome many small network disconnects and the like.