0x656

[Nakia Schaf]

Try searching for all the files that the update "touched."

E.g. search all your harddrives for files changed that day,

then sort by Date Modified; then scroll to the minutes that

the update was running. Besides the two that you have already

found perhaps there are others?

Aha. So that's probably the *significant* error code that the 0x643 hides

E:\>net helpmsg 1622Error opening installation log file. Verify that the specified log file

location exists and that you can write to it.

In order to find out "which installation log file" this code is referring to

(if you don't find it in any other diagnostics) you may have to resort

to using ProcMon to trace another update attempt. Then you can

correlate the writes of these log messages by sequences of their lengths

and see whatever registry and file accesses were associated with each

to supplement the meaning of each.

Not necessarily. That could just be a diagnostic stub which you haven't

been asked to activate yet. ; ) I'd focus on the earlier error code.

Perhaps if you can find a way to resolve it you won't run into the second one

again? ; )BTW notice that we have already seen 0x656 before in its other guise:

E:\>set /a 0x656

1622

> It also makes me nervous that when I now compare this SQL Server

> installation to one working on another computer I see in the "C:\Program

> Files\Microsoft SQL Server" directory only an "80" and "90" subdirectory and

> no, say, "MSSQL.1", exists like in my other install. I'm hesitant to simply

> re-install the product as recommended because that means reinstalling

> SharePoint (since that's where my SQL Server install came from), and I don't

> what other havoc that might wreak. Right now, I just need my website data

> back.

>

> Any suggestions you have are welcome. My apologies in advanced if this has

> already been covered in another thread. I sampled the many entries regarding

> this install in the discussion group but didn't see a solution for this. If

> there is one, feel free to point me to the thread.

>

> Thanks,

> Alyson

3a8082e126