19 February 2009

SharePoint server fails to boot at ACPITABL.DAT

My WSS server that hosts this blog, decided to crap out after a storm. It was a Windows Server 2003 Enterprise Edition server, but not a R2 server. It would boot but only so far and then it would reset itself and restart the boot process. I booted the server in Safe Mode in order to see where the problem was. The boot cycle would fail at the ACPITABL.DAT file. Searching Google and Live.com didn’t yield too much help other than that a “Repair Install” is probably going to be required.
Since my original OS disk was stolen some years ago, and since I had since purchased Windows Server 2003 Enterprise Edition R2 with SP2, I decided to use that set of disks to do the Repair Install. Windows of course considered it an Upgrade and proceeded with the upgrade process. The upgrade went fine except that Windows didn’t recognize my network cards anymore and I had to reinstall the NIC drivers in order to regain internet connectivity.
Then came time to ensure SharePoint was running as expected. Trying to hit my blog, I encountered the following problem:
The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files’.
The solution was to open a command prompt, change directory to the v2.0.50727 directory and then execute the following command:
After that, everything came up as expected. Now all I have to do is check to ensure backup and disaster recovery processes are still functioning as expected. 


SharePoint Remote Event Receivers are DEAD!!!

 Well, the time has finally come.  It was evident when Microsoft started pushing everyone to WebHooks, but this FAQ and related announcement...