When composing a new message or replying to a message the following error maybe presented within the browser: "Server communication error. Please refresh your browser and try again".
Another symptom for this issue can be in the form of a server error in the server application event logs as follows:
Event code: 3003
Event message: A validation error has occurred.
Along with the .NET error error information as follows:
Exception type: HttpRequestValidationException
Exception message: A potentially dangerous Request.Form value was detected from the client (MsgBody="<head></head><body s...").
The .NET framework is displaying an error because it detected ("<....>") brackets within the message being posted back to the server.
MailEnable Application Pool running under the Microsoft .NET 2.0 Framework:
To resolve the "server communication error" the ValidateRequest needs to be set to "false"so that the postback validation does not occur.
To disable request validation follow the steps below:
<pages validateRequest="true" enableEventValidation="false"/>
If MailEnable web mail is running as a virtual directory and the root sites "web.config" contains the post back validation check then this will override the MailEnable web mail's virtual directory "web.config" file settings. The same procedure applies as the above steps to disable the post back validation check by locating the root websites "web.config" file and setting the validateRequest to "false".
Alternately you can globally turn request validation off which maybe overriding the MailEnable "web.config" file settings. To globally turn request validation off follow the steps below:
<pages validateRequest="false" />
MailEnable Application Pool running under Microsoft .NET 4.0 Framework:
If the MailEnable application pool is set to run under 4.0 then the requestValidationMode="2.0" needs to be set within the MailEnable web mail web.config. Also the "validateRequest" set to "false" also applies.
<httpRuntime maxRequestLength="10240" executionTiemout="3600" requestValidationMode="2.0" />
Third party script blockers may
also throw similar exceptions and contribute to the "Server communications
error". To ensure that script blockers are not the cause of the post back
validation problems in web mail and causing the exceptions it is best to disable
the script blocking application and test within web mail again.
|Product:||MailEnable (Std-Any Pro-Any Ent-Any)|
|Class:||TRB: Troubleshooting (Configuration or Environment)|
|Revised:||Friday, October 6, 2017|