sys.sp_fulltext_load_thesaurus_file fails sometimes due to error - by Michael Zilberstein

Status : 


Sign in
to vote
ID 779257 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 2/14/2013 2:59:11 PM
Access Restriction Public


Caught following error messages in SQL Server error log:
Procedure sp_fulltext_load_thesaurus_file, Line 41, Message: The data type of substitution parameter 1 does not match the expected type of the format specification.

sys.sp_fulltext_load_thesaurus_file contains following code block (@lcid is input variable to the procedure, its datatype is INT):

    IF (@thesaurusFilePath IS NULL)
        RAISERROR(30048, 16, 1, @lcid) 

Simple execution of the following code fails:
DECLARE  @lcid INT =15;
RAISERROR(30048, 16, 1, @lcid);

Error message is: 
Msg 2786, Level 16, State 1, Line 2
The data type of substitution parameter 1 does not match the expected type of the format specification.

And indeed, if we query sys.messages for message_id = 30048, we'll see that it expects 2 substitute variables, first of them string and only second int. So following code works fine:

DECLARE  @lcid INT =15
RAISERROR(30048, 16, 1, 'abcd', @lcid) 

Checked the issue for SQL Server 2008 R2 SP2 and for SQL Server 2012 - same bug in both.
Sign in to post a comment.
Posted by IbexMark on 5/8/2013 at 10:42 AM
Very sad that the bug would be closed when such a simple fix could be made. I suspect that it is generally not reported as it tends not to cause much harm except when you are tracking another bug and it tends to lead you down the wrong path for a few hours
Posted by Michael [MSFT] on 4/23/2013 at 7:33 PM
Dear Michael,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available

If the scenario become more common, the bug may be reactivated.

Thanks again for reporting the product issue and continued support in improving our product.
Posted by Vishal [MSFT] on 3/27/2013 at 2:21 PM
Thanks for your feedback; we will look into this issue