Well, who would have thought. I mean really Micr*soft. Really? What the crap!? Here is what I am referring to. I recently updated our servers with Sql Server 2005 SP3. We updated our development server. It went without a hitch. We updated our test server. Again, went without a hitch. Our test server more resembles our production server. So I update our production server. Does it work like it’s supposed to? NO! After updating to SP3 for SQL Server 2005, the jobs broke. I first looked at permissions for a while. Nothing changed as far a permissions go, but I know where I work things are changed on the intranet without our knowledge. Kind of a communication breakdown in my opinion. Just sayin. Anyway, it turns out that there was a .dll that was (unregistered?). Is there such a thing? Apparently so. After looking into the issue for quit some time I found that the DTS.DLL needed to be re-registered. Go figure. Thanks Micr*soft! Great going! Make my life easy why don’t you. You need to run the below command at the c:\ prompt:
regsvr32 dts.dll.
I ran that command and it fixed my issue. Why it didnt break on development or test environment is beyond me.
Have fun and as always, if there are any questions or suggestions they are welcome. Thank you.
August 12, 2011 at 11:48 pm
wooow, like your things about DTS.DLL « Asp.snare Team’s Weblog