Bug or Not?

  • Hello,

    Recently I discovered an issue with SQL 2000 SP3 with hot fix 814032 (replication fix when using binary sort order) installed. The issue is related to the NT User name associated with the SQL service accounts. I found that if the service account was created with different case (i.e. UsEr) within your domain, SQL did not have any issue with the case difference. However, once SP3 and 814032 were installed the service account information stored within master..sysxlogins must match the case of the NT user account previously created. Prior to these updates SQL would store the information is lower case regardless of how you entered the user name (so I have found). This account information is needed for the merge replication solution we are using. When the case is different between sysxlogins and the DC(s) the subscriber(s) are unable to retrieve the user’s information and you receive an 8198 error. This occurs in both a NT4 domain and Win2x Domains.

    I searched for quite sometime and found no documentation on this issue. The docs on errors 8198 and 15401 are not related to my findings. If this is an undocumented bug how would I go about getting such documented? If this is a known issue can anyone "point" me to the references? I am fairly new to SQL Server from an Administrations point and need a little assistance.

    Thanks,

    The SQL dabbler

    This and 25¢ will get you a cheap cup of coffee.

  • Not familiar with it. I reallllly try to avoid case sensitivity. If you dont get any help here, best bet is MS support. $250 a call, but they refund it turns out to be a new bug usually.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

  • Andy,

    Thanks for the quick post. Our application need the sort order due to it's business rules. Believe it or not I tried to call and of the nine numbers I have they were all busy. Go figure. I keep trying and looking.

    thanks again.

    p.s. Love your articles.

    This and 25¢ will get you a cheap cup of coffee.

  • Update. This is still an issue however I have recently located a hot fix release via MS http://support.microsoft.com/?kbid=838460

     

    Hopefully this will help anyone that runs into the same issue.

    This and 25¢ will get you a cheap cup of coffee.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply