(cross-post added to SQL Server Setup)
"Vinh" <Vinh@discussions.microsoft.com> wrote in message
news:CC4A03C1-3BB4-4A44-9682-1FEF51EAA082@microsoft.com...
> I'm having the same exact issue. Did you ever get your issue resolved?
> Microsoft SQL Server 2005 Service Pack 2 (KB 921896).
> Failed 1 update
> Error(s) found:
> Code 2BC3

<cmd_output OS="XPsp2">E:\>
set /a c = 0x2BC3
11203
E:\>net msg %c%
11203 is not a valid Windows network message number.

More is available by typing NET MSG 3871.
</cmd_output>


Does having SQL installed gives you something different for: net msg 11203


See if poster Alex_Rue's solution s you:

https://forums.microsoft.com/TechNet...5823&SiteID=17

(Live Search for
11203 SQL site:microsoft.com
)

<quote>
we just had the same issue and solved it by restricting the possible onwers
of the sql server ressource to the new node. Then the sp2 did not check
the already patched old node and installed successfully.
</quote>


>
> OS: Windows Server 2008 Standard x64 (Hyper-V)


Good luck

Robert Aldwinckle
---

Thanks for the quick post, Robert. I will check this out in the morning and
post the results since my brain is currently burnt and I do not want to get
sloppy executing SQL statements.

Thanks again for the advise.

Vinh

In my case, the cause was an imcomplete installation (via Windows Update) of
SQL 2005 x64 SP2. It left mixed versions of my SQL components. When I
downloaded the service pack and executed it, I was notified that certain
modules were already patched:
These product instances MSSQLSERVER have been patched with more recent
updates:
Database Services (MSSQLSERVER)
Analysis Services (MSSQLSERVER)
Reporting Services (MSSQLSERVER)
Notification Services
Client Components

The work around was quite simple:
1.) Download the SQL 2005 x64 SP2:
http://www.microsoft.com/downloads/d...DisplayLang=en
2.)The SQL components that were already updated sere exclude in the list of
items to update. If you can't select an item, it has already been update.
Complete the install.

Vinh