If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

This is an upgrade weekend at the office. They’re migrating from SQL Server 2000 to SQL Server 2005. The upgrade went fine, but there was an error with Reporting Services 2005 that said:

SQL Server setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server] Cannot insert duplicate key row in object ‘dbo.ConfigurationInfo’ with unique index ‘IX_ConfigurationInfo’.. To continue, correct the problem, and then run SQL Server setup again.

Um, yeah. I have no idea what that means.

A guy I work with was here with our DBA, but he had to leave. So I came up to the office, and we started searching for a resolution to this error. Unfortunately, it’s not documented by anybody except this guy, who said the problem had something to do with EnableClientPrinting. Whatever that means. Here’s the quote (in case that link goes bad):

Turns out we got this because we had added an EnableClientPrinting entry to disable the print button in SQL 2000 after the SP2 bug that broke printing. Removing this entry prior to runing the upgrade made everything run smoothly.

Our DBA sat on hold with Microsoft - on hold, before talking to a technician - for 5 hours. That’s 300 minutes, if you’re keeping score. That would be bad if it was free, but it wasn’t. This is after she gave them a credit card number for a $500 per-incident support case. It only breaks out to $100/hour, so maybe that’s not so bad.

Anyway, things are looking up. I’ve gotten some routine maintenance taken care of, and she’s got some guy on the phone who seems to be pretty helpful. They’re working through the Report Server configuration now. Hopefully this means we’ll be out of here soon.

Lesson learned: when you need Microsoft’s per-incident support, be ready to wait. Next time I’ll just request a callback to my cell phone, and we’ll go up the road for food until the call comes. The people on the other end of the line seem helpful, but getting them on the phone isn’t as easy as it should be - especially at $500 per call.