up vote 0 down vote favorite
share [g+] share [fb]

I'm trying to install SQL Server 2005 Developer Edition on my Vista 32-bit PC. The installation keeps failing with this line in the install log:

Check_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.

The Native Client installs OK but I get this error when installing the SQL service, Integration Services or just the components (Manager Stuido, etc)

I previously had SQL 2005 Express Edition and SQL 2008 Studio Manager. I uninstalled as many SQL products as I can and ran through a few manual uninstall procedures but am not having any luck.

What's worse is that "Check_CommitFlag" returns nothing on Google. Not a good sign...

The "Setup Bootstrap\LOG\Summary.txt" file show the generic MSI error 1603 and directs you to "Setup Bootstrap\LOG\Files\SQLSetup0001_PCNAME_SQL.log

The MSI log with the error is below.

Any help would be greatly appreciated.

MSI (s) (B4:18) [13:58:49:501]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT Action,Type,Source,Target, NULL, ExtendedType FROM CustomAction WHERE Action = 'Check_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2' MSI (s) (B4:E0) [13:58:49:508]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI99B3.tmp, Entrypoint: Check_CommitFlag Action start 13:58:49: Check_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2. Function=Check_CommitFlag Doing Action: Check_CommitFlag PerfTime Start: Check_CommitFlag : Mon Oct 18 13:58:49 2010 Check_CommitFlag called successfully. flagCommit value 1 flagCommit value retrieved successfully. PerfTime Stop: Check_CommitFlag : Mon Oct 18 13:58:49 2010 Gathering darwin properties for failure handling. Action ended 13:58:49: Check_CommitFlag.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3. Action ended 13:58:49: INSTALL. Return value 3.

link|improve this question
What does your installation log show? This can be found in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Summary.txt – shiitake Oct 18 '10 at 21:02
Not so much an answer but a post-script: I noticed that even after the error pops up, all the SQL services are installed and running. I ran SP3 and things seem to be OK. Usually it would be just plain stupid to rely on something that bombed out during the install but this is my development environment and I have to get something done. – pjcdev Oct 27 '10 at 13:06
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.