Hi all,
I've filled this suspect bug to Connect:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=282812
The issue is: I'm unable to save any change to server properties if instance is set to Case Sensitive collation .
The process returns an error like (translated from Spanish, so not exact message):
"Error in metadata manager. Log file extension should be .LOG. Error in metadata manager. Error setting ConfigurationSettings\Log\File configuration property.".
As far as I've tested this happens with any property you're trying to set when in CS collation.
My bypass has been to edit msmdsrv.ini file directly with Notepad, reverting CollationName to case insensitive.
Then everything goes fine.
Details:
Tested with AS 2005 SP2 Collation: Latin1_General_CS_AI Happens both with SSMS and direct scripting (as expected)Best regards,
Jordi Rambla
Solid Quality Mentors
wenn Collation Latin1_CS and soon is, you should change in msmdsrv.ini in
<Log>
<File>msmdsrv.log</File>... </Log> to <File>msmdsrv.LOG</File>
No comments:
Post a Comment