Problem when changing update source

hi all,

we use win server 2008 r2 enterprise , wsus 3.2. until last friday, downoloading updates microsoft's website. had change the source wsus server in our headquarters (not being replica server). started problem: our product , classification changed, downloading lot of updates hadn't ever downloaded. now, when try modify update soure (to microsoft's web site again) set option console falls down - database error - , copying error clipboard, have message bellow:

the wsus administration console unable connect wsus server database.
   
verify sql server running on wsus server. if problem persists, try restarting sql.
   

system.data.sqlclient.sqlexception -- maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).
info:spsetconfiguration - synctomu or upstreamservername config value changed - no reset

source
.net sqlclient data provider

stack trace:
   @ microsoft.updateservices.ui.adminapiaccess.updateserverconfigurationmanager.saveserverconfiguration(iupdateserverconfiguration configuration)
   @ microsoft.updateservices.ui.snapin.dialogs.ussconnectionsettingsdialog.saveallsettings()
   @ microsoft.updateservices.ui.snapin.dialogs.basesettingsdialog.applydialogbutton_click(object sender, eventargs e)

we use windows internal database.

can me?

thanks!

---

att,
lpozatti
--------
comptia security+
cobit foundation
mcp

system.data.sqlclient.sqlexception -- maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).

info:spsetconfiguration - synctomu or upstreamservername config value changed - no reset

the error message describes issue is.

as documented in prepare network , server wsus 3.0 sp2 in wsus deployment guide, database server needs have nested triggers option enabled. option is, in fact, enabled, default, @ installation of sql server, if dba, whatever reason, disabled option -- 1 thing cause error.

using wid, however, tends eliminate cause, 1 have go through many hoops point option disabled (and i'm assuming can in wid; don't know possible).

in this particular case limit of 32 nesting levels implies that what failed after triggers, which do have a maximum nesting level of =32=. since there isn't in design of wsus environment exceed hard limit, must treated environmental issue, possibly indication of defect or fault in database itself. given scenario, triggered conversion of server upstream downstream server. error message implies that, given notes value change -- in fact, suspect attempting change value may explicitly triggered error. (just hunch, based on reading text of error message.)

while nice think 1 can flip upstream/downstream server switch @ will, fact there interactions , dependencies between upstream server , downstream server need taken consideration prior changing server downstream server. configuration options imposed upon downstream server upstream server, , conflict between these settings , in database could, potentially, cause unanticipated complications -- such nesting overflow.

my suggestion be, expedite whole process, abandon database, uninstall , reinstall wsus server downstream server, using existing ~\wsuscontent folder tree. configure server , synchronize, , run server cleanup wizard cleanup filesystem of files no longer needed. rebuild computer groups, reassign approvals, , monitor. fastest way restore reliable functionality of server.

however, before doing that, suggest researching dependencies , limitations of downstream server, , confirm dependencies , limitations not negatively impact manner in have traditionally managed wsus server, or restrict access products, classifications, or languages need access to.

---

lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2011)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
blog: http://onsitechsolutions.spaces.live.com

Windows Server  >  WSUS