ASDM V7.2(2) and JRE V1.6 Update

luminare-it · ‎04-25-2007

Is anyone else having problems using ASDM after applying the Java JRE V1.6 update? If so, is there any workaround other than removeing the update to refresh back to V1.5?

jreekers · ‎04-25-2007

Hi...actually, this is a Sun bug, as MSVCR71.dll is in a different directory now than it was in previous Java versions.

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291

If you don't want to roll-back to a supported Java version, there are 2 ways in which you could possibly get by this...

- Add your JRE installed directory to your path. So lets say your path is:

"C:\Program Files\Java\JRE1.6\bin". (Depends on where you installed)

into system path by going to Computer -> Properties -> Environment

Variables -> PATH. (Append it to existing one). By doing this you are

adding the directory in path that contains MSVCR61.DLL.

Note that is should be added in System Variables, not User Variables.

- OR as a quick try you can also copy MSVCR71.DLL from your JRE bin

directory ("C:\Program Files\Java\JRE1.6\bin") into system 32 and see

if it works.

Good luck and please rate!

jwilliamson · ‎05-15-2007

I was having a problem with my PDM 3.0(4) on my PIX 501 ver. 6.3(5) being able to apply changes to the PIX configuration.

There was an older version of the MSVCR71.DLL already in my system 32 folder. I copied the one from JRE1.6\bin to system 32 and the problem went away.

However, I still could not save the configuration to memory using PDM.