We ran into this error in our own testing environment and that is a mean one. As that service failure is based on a software bug, it was pure luck to find the solution in one of the VMware KB articles.

You recognize the issue of course immediately as you can’t login into VMware vCenter anymore and looking up the windows services, you figure out, that it’s not started.

It seems that only VMware vCenter 5.5 is affected with the access violation .

The KB article summarizes:

  • You are unable to log in to VMware vCenter Server
  • The VMware VirtualCenter Server service fails immediately after starting
  • In C:ProgramDataVMwareVMware VirtualCenterLogsvpxd.log, you see the errors:2015-04-23T06:09:02.047+09:00 [07576 info ‘[SSO]’ opID=13ad18a1] [UserDirectorySso] Authenticate(administrator@domain.com, "not shown") …2015-04-23T06:09:02.047+09:00 [07576 info ‘Default’ opID=13ad18a1] CoreDump: Writing minidump2015-04-23T06:09:02.047+09:00 [07576 panic ‘Default’ opID=13ad18a1]  –>  –> Panic: Win32 exception: Access Violation (0xc0000005) –>    Read (0) at address 0000000000000008 –>    rip: 000000018014c958 rsp: 000000000752d000 rbp: 0000000000000000 –>    rax: 0000000000000001 rbx: 000000000b052a60 rcx: 0000000000000002 –>    rdx: 000000000752d2b0 rdi: 0000000000000000 rsi: 0000000000000b07 –>    r8:  0000000000000b07 r9:  000000000752d5a8 r10: 00000000000007af –>    r11: 000000018021b6f0 r12: 0000000000000002 r13: 000000000752d5a8 –>    r14: 0000000000000000 r15: 000000000a8af760 –> 

There are not too many workaround, either you restart the service in good faith it doesn’t stop again or you need to upgrade to vCenter version 6.

Access Violation

Photo courtesy of Mike Licht, NotionsCapital.com(CC Attribution)

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.