• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4590
  • Last Modified:

Windows Internal database error on Windows 2008 R2

Hi,

I have an issue on one of my wsus server (running on Windows 2008 R2).

It all started when the "Windows Internal Database Service Pack 4 for x64 Edition (KB2463332)" update refused to install on this specific server (no problems on my other servers).

So, I decided to remove wsus and Windows Internal database and then reinstall.

WSUS uninstalled correctly (no errors) but I am unable to uninstall the Windows Internal Database through the remove features in Server Manager.

I am getting an error "Windows Internal Database Removal failed 0x80070643" and some error to some msi.log located in c:\users\administrator\appdata\local\...\msi.log.

I wish I could uninstall the Internal database, and then reinstall it, update it with the patch above and then reinstall wsus.

Can anyone help?

Thanks.
0
benjilafouine
Asked:
benjilafouine
  • 13
  • 7
2 Solutions
 
benjilafouineAuthor Commented:
Seems like I found it by myself...

http://support.microsoft.com/kb/919945

It worked. I decided not to reinstall wsus on that server.

Benji.
0
 
DonNetwork AdministratorCommented:
FYI, you can manually remove the Windows Internal Database thru command line


http://technet.microsoft.com/en-us/library/cc708610%28WS.10%29.aspx


# On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
# On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe
0
 
benjilafouineAuthor Commented:
Seems like my issue is not resolved...

I have a second machine that exhbits the same problem: the update won't install and in this case, I do not have the luxury to uninstall it because I believe Windows Internal database is used by my Trend Micro Antivirus console (Worry Free).

So update Windows Internal Database Service Pack 4 for x64 Edition (KB2463332) will not install. Anyone has a clue how to solve it without destroying it?

Thanks.

Benji
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
DonNetwork AdministratorCommented:
Looks like "Worry free" is not one of the products mentioned that use MSDE(Windows Internal Database)



 http://us.trendmicro.com/us/products/enterprise/outbreak-prevention-services/system-requirements/
0
 
benjilafouineAuthor Commented:
Databases—any of the following:
Microsoft Data Engine (MSDE) 1.0 / 2000 (2000 + Service Pack 3 is recommended), Microsoft SQL Server 7.0, Microsoft SQL Server 2000 (2000 + Service Pack 3 is recommended)
Others—SQL ODBC driver 3.7 or higher
Windows Installer (included in Control Manager package)

I see MSDE here or SQL server. I am pretty sure it is being used because there is nothing else in this server that could possibly use Windows Interna Database. This is why I want to solve this update error.
0
 
DonNetwork AdministratorCommented:
Products Supported

Requires installation of one of the following Trend Micro
products. Gateway: InterScan™ eManager™, InterScan
Web Protect™ for ICAP, InterScan™ Messaging Security
Suite for Windows/Unix, InterScan Web Security Suite for
Windows/Solaris, Trend Micro™ Network VirusWall™. Mail:
ScanMail™ for Exchange, ScanMail for Lotus Notes,
ScanMail for eManager. Desktop: Server Protect™ for
Windows, OfficeScan™

"Worry free" is not one of the products mentioned



0
 
benjilafouineAuthor Commented:
I prefer not to uninstall the database because I don't know exactly why it is there in the first place. I am going to turn off the service and see what happens.

0
 
DonNetwork AdministratorCommented:
"I prefer not to uninstall the database because I don't know exactly why it is there in the first place."


Windows internal database is installed by a default install of WSUS
0
 
benjilafouineAuthor Commented:
This server has been up for a long time and wsus is definitely not there anymore. Windows Internal Database may just be a leftover. I stopped it and it did not affect my antivirus console.

I may just uninstall it (this I know how).
0
 
DonNetwork AdministratorCommented:
0
 
benjilafouineAuthor Commented:
Actually, a simple registry modification enables removal. It has something to do with the database being installed while the machine had a different role (such as a DC).
0
 
DonNetwork AdministratorCommented:
And what registry modification would that be ?
0
 
benjilafouineAuthor Commented:
See my link above.

To work around this problem, follow these steps:
Start Registry Editor, and then locate one of the following registry subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2005\Setup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup


Note Only one of these registry subkeys will exist on your computer.
Empty the following registry entries:
SQLGroup
FTSGroup
AGTGroup
Exit Registry Editor.


I did that and was able to uninstall it normally on another server with the same problem.
0
 
DonNetwork AdministratorCommented:
Ok, the msiexec /x would have worked as well :)


Did you get your WSUS up and running on a different server ?

0
 
benjilafouineAuthor Commented:
I have a few wsus servers across different sites and along the months/years, servers have changed. Probably that it was in this server many months ago. Not sure.

I installed several wsus servers and linked to the master but because of sync issues, I reverted them to independent ones.
0
 
benjilafouineAuthor Commented:
Its not abandoned, just not completed...
0
 
benjilafouineAuthor Commented:
Its not abandoned, just not completed...
0
 
benjilafouineAuthor Commented:
Still not completed. Do not delete.
0
 
benjilafouineAuthor Commented:
Finally took the time to clear up this situation.

In the end, Windows Internal Database was not required anymore on that machine. I removed the registry keys above, uninstall Windows Internal Database, rebooted and tested my Trend Micro application. Result: no issues.

I do not recall why Internal Database was installed in the first place (WSUS?) but for sure it was not needed anymore.

Problem solved.
0
 
benjilafouineAuthor Commented:
The registry keys must be deleted in the registry if you are sure you want to removed the product. Most likely, it was install under a different user or while the computer was a domain controller (which it is not anymore).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 13
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now