reporter: Jiri Cincura [ cincura_net ] => tonim [ tonim ]

description: The function public void BuildExceptionMessage() Inside iscexception.cs file catch the formating errors, and provides the message "No message error found".
An example is the sql warning 204 for dialect 1 connections (order by code, where code can be a column of more than one
table)

This error message (warning) have no arguments but has inside the message the {0} so the appendformat expect an artument at least.

To fix this I think it should be done like this:
// Avoid incorrectly build mesage args
try
{
builder.AppendFormat(CultureInfo.CurrentCulture, message, args); } catch {
builder.Append(message);
}
Really the message exists but it's incorrectly build (or incorrectly translated for future multilingual messages).

Then the message is: Field Ambiguity, sql error {0}...
instead of "No error message found for.."

=>

The function public void BuildExceptionMessage()
Inside iscexception.cs file catch the formating errors, and
provides the message "No message error found".
An example is the sql warning 204 for dialect 1 connections
(order by code, where code can be a column of more than one
table)

This error message (warning) have no arguments but has
inside the message the {0} so the appendformat expect an
artument at least.

To fix this I think it should be done like this:
// Avoid incorrectly build mesage args
try
{
builder.AppendFormat(CultureInfo.CurrentCulture, message,
args);
}
catch
{
builder.Append(message);
}
Really the message exists but it's incorrectly build (or
incorrectly translated for future multilingual messages).

Then the message is: Field Ambiguity, sql error {0}...
instead of "No error message found for.."

status: Open [ 1 ] => Closed [ 6 ]

resolution: Cannot Reproduce [ 5 ]