Have you looked at the SQL error logs? There may be a corrupt .mdf from the power flash.

We recently just performed this exact scenario as we were wanting to add new hardware but keep the server name and SQL version. The one hang up we ran...

Please review the following Microsoft article on virtual memory size

http://support.microsoft.com/kb/889654

If you have room on the workstation, copy both CDs on to a common directory and title them CD1 and CD2 then run the setup. If this does not...

The error is regarding virtual memory, try modifying the virtual memory on the server in Computer Management.

Good luck

Is there a question involved?

Error code 2177217871 is not any error code associated with SQL Server that I have ever seen.

http://www.sql-server-helper.com/error-messages/msg-1-500.aspx - granted this is not a complete list, but it is one I...

Once you determine what file extension is taking up all of the drive space (if it turns out to be a SQL log file .ldf) then it is highly recommended...

Along the lines of what Keith mentioned, I would pay particular attention to the log file for TEMPDB

If, in your upgrade, you plan on performing a backup/restore to the new server. The full database backup will include the full-text catalog. This will assure that the Full-text...

The error is stating that the file is in use by another application. If I were to fathom a guess, I would say take a look at your virus...

Is this a SBS you are working on?

This will get you started, it is a list of all versions with a link to the right for each flavor. As Gail mentioned, a good Google search is...

We have come to trust Maintenance Plans since 2005 SP2 (there was a bug prior to this release having to do with the cleanup of backups). Currently we are...

Patch 2000.80.2187.0 includes the the security update, but if you want to be fully up to date, there are a few more available patches/updates for SQL 2000

Please take a look...