I'm having a blast so far with Facebook. I don't have a ton of friends yet, and probably won't ever get HUGE numbers, but I hope to have good ones. :)
It seems pretty cool though. I'm considering writing applications, but first I need to figure out what that entails, and what people seem to want. Right now, it seems that most folks just want new and interesting things to share. That's easy enough to write, of course, if you have something interesting to provide.
Aye! There's the rub!
Saturday, October 18, 2008
Monday, May 19, 2008
Crappy Windows Server 2003 R2 x64 problem with corrupted .NET 2.0
Man, I just spent hours today googling around to find the answer to failing updates of Service Pack 1 to .NET Framework 2.0. The error, 0x643, told me to try the update again, which was useless.
This server was running Data Protection Manager 2007, so it had SQL Server 2005 installed also, which was crashing on startup. This seemed to indicate a corrupted install of .NET Framework 2.0.
Well, luckily, or so I though, that is what the built in "Repair" option is for under change/remove in Add/Remove Programs. Unfortunately, it failed, saying that there were invalid characters in the path "Program Files". This was a hint, but not a very good one. I spent hours trying to find other ways to "repair" the problem, since I couldn't really uninstall the Framework.
Finally, I stumbled across a single blog post from a user named "favorini" which had the magic hint, especially given the message I received when I first tried to repair it.
Aaron Stebner's WebLog
The answer to this problem was to run regedit, find all of the references to D:\Program Files, especially the ones with "D:\Program Files\Common Files\Microsoft Shared\DW", which is a leftover from a bug where Dr. Watson was installed on the D: drive instead of the C: drive, even though D: was a CD drive. Find all of those and change them to reference "C:" instead of "D:".
Just ick.
As always, be careful editing the registry, etc. etc. yada yada.
I hope this helps someone out there.
This server was running Data Protection Manager 2007, so it had SQL Server 2005 installed also, which was crashing on startup. This seemed to indicate a corrupted install of .NET Framework 2.0.
Well, luckily, or so I though, that is what the built in "Repair" option is for under change/remove in Add/Remove Programs. Unfortunately, it failed, saying that there were invalid characters in the path "Program Files". This was a hint, but not a very good one. I spent hours trying to find other ways to "repair" the problem, since I couldn't really uninstall the Framework.
Finally, I stumbled across a single blog post from a user named "favorini" which had the magic hint, especially given the message I received when I first tried to repair it.
Aaron Stebner's WebLog
The answer to this problem was to run regedit, find all of the references to D:\Program Files, especially the ones with "D:\Program Files\Common Files\Microsoft Shared\DW", which is a leftover from a bug where Dr. Watson was installed on the D: drive instead of the C: drive, even though D: was a CD drive. Find all of those and change them to reference "C:" instead of "D:".
Just ick.
As always, be careful editing the registry, etc. etc. yada yada.
I hope this helps someone out there.
Wednesday, February 6, 2008
The election season seems to be heating up!
I saw this cool primary leaderboard over at MSNBC and I had to snag it. It's pretty cool, and keeps updating.
Subscribe to:
Posts (Atom)