The VMware VirtualCenter Server service terminated unexpectedly

The VMware VirtualCenter Server service terminated unexpectedly. It has done this X time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.”

I observed this error couple of times and in both of the scenarios disk space is the culprit. First thing go on and check the disk space on the SQL server.

Don't have much time to enter few more details.. bit busy.. Have a good day..

SQL Server 2008 R2 Setup fails with the error code: 1605

SQL Server 2008 R2 Setup fails with the error code: 1605. You may see the error message pop-up as follows.

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{72DE3C67-FB48-450E-8BEA-4EB1B3B5355D}'. Error code: 1605..

------------------------------
BUTTONS:

OK
------------------------------


After lot of troubleshooting and googling, I found the right article to fix this issue. Please refer the following link.

Click here

It worked like a charm. Enjoy..

0x80090016: Keyset does not exist

All of sudden or else when the Windows Operating System reboots unexpectedly, scheduled tasks will turn up with the following error message.

General page initialization failed.
The specific error is:
0×80090016: Keyset does not exist
An error has occurred attempting to retrieve task account information.
You may continue editing the task object, but will be unable to change the task account information.

After Googling a bit, The following mixed Solution (from different solutions) worked for me.

- Stop the Cryptographic Service windows service.
- Backup and Delete the contents the orphaned/corrupted files from the following location.
C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18
- Start the Cryptographic Service windows service. (I suggest giving a system reboot)
- Open the scheduled task properties and try to set the Run As user password again.

The above should resolve the issue. If not, Google it more than what I did.

Analysing the Windows XP MiniDump

Analysing the Windows XP MiniDump

Requirements: Microsoft Debugging Tools, Internet connection get communicate with Symbols from Microsoft website.

- Open command prompt
- Navigate to debugging tools installation directory
- kd -z \Minixxxxxxxx-xx.dmp
- kd> .logopen \debuglog.txt
- kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
- kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
- \debuglog.txt will be having the debug information.

Check the MODULE_NAME and IMAGE_NAME entries in the Debug logs, which shows you the process/program caused the BSOD crash.