Installation Notice: Pending File Operations 1

[toekneel]

I found some partial threads on this, but couldn't find anything complete enough to get an answer on this.

I'm on Windows 2000, and loaded SQL Server 2000 as a standalone. I had problems with SQL Server 2000 (not able to get connection, insufficient access rights) and figured that I messed something up in the installation. I performed an uninstall via Control Panel icon. When I went to re-install SQL, I get a message: "A previous program installation created pending file operations on the installation machine. You must restart the computer before running setup."

Rebooting hasn't helped after several attempts. Microsoft's kb was of no use on this one. They had instructions for rebuilding SQL Server Registry Entries that applied to earlier versions of SQL but didn't impact this at all.

 

[tlbroadbent]

This problem is documented in several KB articles. It is not limited to the SQL Server 2000 installation. The resolution is simple.[ol][li]Open REGEDIT and find the following key.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager
[li]Delete any PendingFileRenameOperations values in this key.
[li]In some cases, you may need to delete the files in your TEMP directory.
[li]If these steps don't resolve the problem, search for WININIT.INI and rename it to WININIT.XXX. [/ol]Review the KB article at

http://support.microsoft.com/support/kb/articles/Q214/6/43.ASP

Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[toekneel]

In checking my computer, I do not have any such key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager as "PendingFileRenameOperations"

My search for "WININIT.INI" on all computer hard drives did not locate anything.

I have double checked the link to the MS kb, and verified that I'm looking for the right stuff. Ever feel like you're loosing your mind on something that seems like it should be quite simple? I'm just about ready to reformat my hard drives and start all over again.

 

[toekneel]

I had another system tech working on my computer on another seemingly unrelated problem, and in working on the problem, it resolved this one. I had been having problems with Virtual Memory accepting the changes that I was setting up, and continually had messages that my memory was too low. I turns out that the problem had to do with sharing on my W2K machine. There is a "System" user that had not been assigned to utilize all the files it was supposed to have access to. When that was shared properly throughout my computer, this problem was overcome, and SQL Server 2000 was able to load without a problem.

 

[tlbroadbent]

Excellent. Thanks for the update. It is very helpful to know when problems are solved and how. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.