WSUS 3 Database Problems "Peter Ogden" <peter.ogden[ at ]dlgrd.nospam.wa.gov.au> 5/24/2007 1:05:53 AM I have recently upgraded WSUS 2 to 3 and have been having some problems with its database. This was a double upgrade (not a good idea, I know!) as WSUS 2 was running on Windows 2000 and MSDE previously, requiring me to upgrade the OS to Windows 2003 SP2 first before upgrading WSUS. I mistakenly thought that the free desktop version of SQL Server 2005 SP1 would be better than the Windows Internal Database and upgraded to that as well. I am now frequently getting Database errors when trying to use the MMC console (both remotely and on the server). This usually occurs with processes that take some time (e.g. listing synchronization logs). When these errors occur, I get errors like the following in the event log: "An inconsistency was detected during an internal operation. Please contact technical support. Reference number 4." "An inconsistency was detected during an internal operation in database 'tempdb'(ID:2) on page (1:133). Please contact technical support. Reference number 5." "An inconsistency was detected during an internal operation in database 'SUSDB'(ID:5) on page (1:74412). Please contact technical support. Reference number 4." Our WSUS server is a virtual server running under VMWare 1.0.2 (as it was quite successfully with WSUS 2), with less than 150 users. Is there a way to migrate the database back to the Windows Internal Database? If so, will doing this fix the problem? I have found article KB916086 in the knowledge base, but would rather not have to deal with MS support if I don't need to. - Peter Ogden

Re: WSUS 3 Database Problems "Peter Ogden" <peter.ogden[ at ]dlgrd.nospam.wa.gov.au> 5/29/2007 12:26:56 AM Does anyone have any ideas with regard to the database issues I have? I've run various database fixes that I have found on the net, but none have made any difference. I still randomly get these errors. - Peter Ogden "Peter Ogden" <peter.ogden[ at ]dlgrd.nospam.wa.gov.au> wrote in message news:eixzu%23ZnHHA.4896[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] >I have recently upgraded WSUS 2 to 3 and have been having some problems >with its database. > > This was a double upgrade (not a good idea, I know!) as WSUS 2 was running > on Windows 2000 and MSDE previously, requiring me to upgrade the OS to > Windows 2003 SP2 first before upgrading WSUS. > > I mistakenly thought that the free desktop version of SQL Server 2005 SP1 > would be better than the Windows Internal Database and upgraded to that as > well. > > I am now frequently getting Database errors when trying to use the MMC > console (both remotely and on the server). This usually occurs with > processes that take some time (e.g. listing synchronization logs). When > these errors occur, I get errors like the following in the event log: > > "An inconsistency was detected during an internal operation. Please > contact technical support. Reference number 4." > > "An inconsistency was detected during an internal operation in database > 'tempdb'(ID:2) on page (1:133). Please contact technical support. > Reference number 5." > > "An inconsistency was detected during an internal operation in database > 'SUSDB'(ID:5) on page (1:74412). Please contact technical support. > Reference number 4." > > Our WSUS server is a virtual server running under VMWare 1.0.2 (as it was > quite successfully with WSUS 2), with less than 150 users. > > Is there a way to migrate the database back to the Windows Internal > Database? If so, will doing this fix the problem? I have found article > KB916086 in the knowledge base, but would rather not have to deal with MS > support if I don't need to. > > - Peter Ogden >

Re: WSUS 3 Database Problems "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/29/2007 1:18:14 AM "Peter Ogden" <peter.ogden[ at ]dlgrd.nospam.wa.gov.au> wrote in message news:ObPmSgYoHHA.208[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > Does anyone have any ideas with regard to the database issues I have? I've > run various database fixes that I have found on the net, but none have > made any difference. I still randomly get these errors. I think I'm going to need a lot more detail on *exactly* what steps you performed in the process of upgrading the WSUS v2 on Win2000 to WSUS v3 on Win2003. There are at least a half dozen places where "gotchas" can make a mess of things. >> Is there a way to migrate the database back to the Windows Internal >> Database? Not an easy one, but it can be done. > If so, will doing this fix the problem? I have no way of knowing, until we can determine *where* the problem is. If it's a defect in the database, itself, then it won't matter what database edition it's running under. >> I have found article KB916086 in the knowledge base, but would rather not >> have to deal with MS support if I don't need to. Dealing with MS support wouldn't be on the agenda. The KB article suggests installing the service pack. You've indicated that you've already installed Express Edition SP1, so this KB article is of no use to you. (Although you might want to confirm that you did, in fact, install Express Edition =SP1= and not Express Edition =RTM=.) To revert your databases to the Windows Internal Database, perform the following: [a] Uninstall WSUS, selecting the options to keep the database, content, and logfiles. [b] Uninstall SQL Server Express Edition. [c] Reinstall WSUS, selecting the option to install SQL Server 2005 Embedded Edition, and then enter the pathname that contains the databases originally installed in SQL Server Express Edition. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....