While installing the update Microsoft SQL Server 2005 Service Pack 2 (KB
921896), received an Installation Failure with the Error Code: 0x736D. Has
anyone else seen this Error Code? I was unable to find a reference to it.
Thanks,
Bob
Printable View
While installing the update Microsoft SQL Server 2005 Service Pack 2 (KB
921896), received an Installation Failure with the Error Code: 0x736D. Has
anyone else seen this Error Code? I was unable to find a reference to it.
Thanks,
Bob
I've got the problem, but with a different error code... (ref: 0x2B33) What
does it mean?
I've got the problem, but with a different error code... (ref: 0x2B33) What
does it mean?
"RiXx" <RiXx@discussions.microsoft.com> wrote in message
news:D8CBE460-A632-4A1F-846F-D79A7326AE8E@microsoft.com...
> I've got the problem, but with a different error code... (ref: 0x2B33) What
> does it mean?
By itself not much. Find the code in the install logs and capture its context.
Also often it is useful to convert hex codes to decimal and search for the
equivalent value using the different representation. So if you see 11059
in the context of the hex code you can be sure that it is related.
HTH
Robert Aldwinckle
---
"RiXx" <RiXx@discussions.microsoft.com> wrote in message
news:D8CBE460-A632-4A1F-846F-D79A7326AE8E@microsoft.com...
> I've got the problem, but with a different error code... (ref: 0x2B33) What
> does it mean?
By itself not much. Find the code in the install logs and capture its context.
Also often it is useful to convert hex codes to decimal and search for the
equivalent value using the different representation. So if you see 11059
in the context of the hex code you can be sure that it is related.
HTH
Robert Aldwinckle
---
In order to find the problem, I tried installing the Patch manually.
During the process I found that the SQLExpress service was disabled.
Set service to Automatic, started Service, and everything worked fine.
If that does not work, Check your authentication settings (that is where it failed manually)
Hope it helps.