30 01 2011
SharePoint installation error: dbwrap.exe failed with error code: -2068643839. Type: 8::CommandFailed
Got the following error when installing SharePoint Server 2010 to machine where SQL Server 2008 R2 was previously installed: dbwrap.exe failed with error code: -2068643839. Type: 8::CommandFailed. Here’s my painful guide how I solved the problem.
Messages in setup error log
- Successfully installed package: oserver path:G:\Global\oserver.MSI
- Executing command path: ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm.exe’, args: ‘updateproductinfo’
- Start C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm.exe updateproductinfo
Command ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm.exe’ returned: 0
- Executing command path: ‘C:\Program Files\Common Files\Microsoft Shared\SERVER14\Server Setup Controller\dbwrap.exe’, args: ‘timeout=2950’
- Start C:\Program Files\Common Files\Microsoft Shared\SERVER14\Server Setup Controller\dbwrap.exe timeout=2950
- Error: Command: ‘C:\Program Files\Common Files\Microsoft Shared\SERVER14\Server Setup Controller\dbwrap.exe’ failed with error code: -2068643839. Type: 8::CommandFailed.
1. Uninstall SQL Server 2008
I found some suggestions to uninstall SQL Server 2008 (R2) because there can be problems if standalone installation finds some existing database. Well, there are two instances in my server:
- Default instance
To make sure that there is nothing left from previous installations or experiments I uninstalled SQL Server 2008 completely.
2. Make sure you don’t have pending file operations
I found also some interesting suggestion from comments of MSDN library page Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008. Quote:
“If I go to regedit and then to HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Control>Session Manager I see a “PendingFileRenameOperations” registry. This was leftover by the Logitech install (sloppy codewriting no doubt). If I delete this and re-run the Repair then it works. The file refreshes itself on Restart though so I’ll need to figure out how to deal with this permanently.”
I had no data under this key but maybe this knowledge may help somebody.
3. Install SharePoint 2010 as single instance again
I ran setup again and let it repair last installation. After that I ran SharePoint configuration wizard and my SharePoint 2010 got nicely up again.