vCenter Service fails after upgrade to 4.1

Run the scripts attached to the article linked below before upgrading to vCenter Server 4.1. If you have already upgraded, this article provides detailed workaround steps if you are experiencing the issue. 1026688

Symptoms

• VirtualCenter Service fails after upgrading to vCenter Server 4.1.
• You see this error in the vpxd logs:
  
  Panic: Win32 exception: Access Violation (0xc0000005)
     Read (0) at address 0000000000000098
     rip: 000000014071edcc rsp: 000000000419c700 rbp: 000000000419e160
     rax: 000000000419c7a8 rbx: 0000000000000018 rcx: 0000000000000020
     rdx: 000000000419c798 rdi: 0000000000000000 rsi: 000000000e8667b0
     r8:  000000000419c7a8 r9:  000000000cab1eea r10: 0000000002d27fd0
     r11: 000000000419c750 r12: 0000000007279700 r13: 0000000007279740
     r14: 00000000032edeb0 r15: 0000000000000004
  
• In vCenter Server 4.0, operations such as Inventory > Search fails. The vws.log file truncates with a Chunked error stream error
• In vCenter Server 4.1, vCenter 4.1 fails immediately after it is started and the vpxd-*.log shows an ASSERT fails at one of the following:
  • ASSERT d:/build/ob/bora-258902/bora/vpx/vpxd/util/vpxdDbLoad.cpp:1059
  • ASSERT d:/build/ob/bora-258902/bora/vpx/vpxd/util/vpxdDbLoad.cpp:1066

http://kb.vmware.com/kb/1026688