Attempted to read or write protected memory

[nesineal]

We were running ESX Server 3.0.2 and Virtual Infrastructure Client 2.0 until today when we upgraded to 3.5 and 2.5, respectively. Now when trying to run the virtual machines through VIC I get this error:

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

We get the same error on a fresh install on a different machine. We were able to create a new virtual machine just fine, but when we click on 'Edit virtual machine' or try to look at the console, same error.

Interestingly, when accessing through Firefox, everything works fine.

Anybody seen this yet? If so, any solutions?

[Ben1839]

The copy of dll in the launcher folder corrected the problem for me.

Thank jevel

[jevel]

I have confirmed this bug and the workaround on at least three computers here at work now.

All three of them are Lenovo laptops, but none of them are running the Access Connections suite. Seems to be something else.

What model is your computer, Ben?

-KJ

[Ben1839]

I have a Dell Latitude d830 laptop...

I didn't found why, but with the administrator profile, there's any problem.

So, seems to have an application data in the profile that conflict with VI.

I tried to scrap my profile, but after some hours the problem came again.

With the DLL everything works fine, but if I find the reason I will say it to you.

Ben

[jevel]

I think I have narrowed it down to .net-related problems now, but still trying to reproduce my findings to be 100 % sure.

-KJ

[pbarendse]

Copying the dll's did the trick for me too. Am also using a Lenovo (in my case it is still an IBM...) notebook, an R52. Access Connections is installed on my notebook.

Thanks for the advice Jevel!

[jdeather]

On a Lenovo T60p. Seems to have worked well for me, although the problems have been so intermittent...

Experts-Exchange is the devil! PAY for well-placed-in-Google solution results? No thank you...

[jevel]

This is 100 % OT, but I've never payed a cent to experts-exchange. Most answers can be read if you just scroll down under the part where they tell you to join to see the answer.

-KJ

[livedrive777]

I actually kind of like experts exchange myself. I've never paid any money for it (and never would), but I did join as an expert and that seems to let me see pretty much any of the answers that I've ever searched for. I've answered a few here and there myself, so I don't know if it is a matter of once you have a few points to your name or what, but I've definitely never paid any money to them.

[sarah2]

I'm getting this on a terminal server. I've tried the following fix and the files already exist. The server OS is Windows 2003 64Bit Enterprise Edition (R2)

[vancod]

This issue appears to still exist in vSphere. Nice.

In my case, it manifested itself with the same pop-up error, but it also prevented the vCenter Converter plug-in from functioning.

[GeneNZ]

The problem in vSphere4 with the new converter can be solved from the details in the following thread:

http://communities.vmware.com/thread/118140?start=30&tstart=0

More specifically:

copy these two files:

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\2.5\libeay32.dll

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\2.5\ssleay32.dll

To

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher

[vancod]

Actually, the solution is on page 2 of this thread. I was merely stating that the issue still exists. I should have been equally clear that the fix works as well.

The issue appears to be largely with libeay32.dll - there are numerous versions on my system, from the Intel WiFi app discussed here, but also from an Adobe CS4 install (it' a dev machine, so I do lots of screen capture and doc work)

[GeneNZ]

Interestingly I got my vCenter 4 working by copying the ssleay32.dll and libeay32.dll file as instructed. However, I have now encountered the following problem as noted in the official Release notes:

vSphere Client fails with Microsoft Visual C++ Runtime Library error

In environments that include vSphere 4.0 components, VI Client version 2.5, and VMware vCenter Converter, the vSphere Client might fail with a Microsoft Visual C++ Runtime Library runtime exception.

Workaround: Delete

libeay32.dll

and

ssleay32.dll

located at the following path:

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher

Alternatively, uninstall VI Client version 2.5.

()

I have uninstalled the 2.5 VI client as stated, and have tried the other methods to fix the issue, however I'm somewhat stuck between a rock and a hard place. Whatever I do, the coverter doesn't work. Anyone have any previous experience with this?

[GeneNZ]

And the solution to my own question is as follows:

I would get the memory exception error if I didn't have the ssleay32.dll and the libeay32.dll in the Launcher folder. By sticking them in the Launcher folder the memory error would disappear, but each time I tried to import a machine using the VMWare converter, I would get a C++ runtime exception.

To fix it, I uninstalled the 2.5 Client, but this still didn't fix the problem. Turns out I was using the ssleay32.dll and the libeay32.dll from the older 2.5 folder. If I replaced them with the ssleay32.dll and the libeay32.dll from 4.0 folder, and place them into the Launcher directory, all was fine.

Hope this helps someone else.

[vancod]

It's rather sad that issues relating to these DLLs continue to persist with software this mature, particularly given that the fixes are quite simple.

[Eltiguere]

Thanks Jevel. problem fix now.

[dmetcalf]

THANK YOU!! THANK YOU!! Have spent two days with VMware support on this issue and gotten nowhere. Had looked at this string earlier but had not continued reading past the first two pages. Works like a champ now. Have an AWESOME day!!