February 24, 2011 at 7:21 am
gemisigo (2/22/2011)UPDATE!!!
I've found a mouse in the trap! Someone was trying to alter accesses to some catalogs and it implicitly resulted in an "EXEC sys.sp_configure N'allow updates', N'1'".
I made some tests and though the RECONFIGURE command does not fail after setting 'allow update' to 0 and it does fail after setting it to 1, it does not reset (and I guess it should not either) config_value to 0, hence it remains 1. I still don't know why this makes backups to fail but at least I know how to fight it until I can fix it for good. It might be related to some other settings that take effect after issuing RECONFIGURE. Any ideas are welcome.
Thanks to everyone for your help!
Glad to hear you found the culprit(s). I would suggest since you are able to duplicate it, submit it to Microsoft Connect's site. (http://connect.microsoft.com/sqlserver). The guys that watch that site are very good at helping you out, especially if they can duplicate it on their end. You will want to be as detailed as possible, include logs, queryies ran, etc.
They should be able to share some light on the problem and might even give a hotfix for it, if it they do find it to be a bug.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply