Progress Explorer and Windows 2008

For my sins, I regularly work with a legal case management application written in the Progress 4GL. I’m not a big fan of Progress, aka Open Edge, but I can do a passable job of database administration with it.

I recently needed to build a new virtual machine with a really old version: Progress 9.1C, although I believe it’s the same deal for Progress 9.1D and Progress 9.1E, Open Edge 10.0, Open Edge 10.1.

The problem seems to occur on any version of Windows Server 2008, including Windows Server 2008 R2.


The symptom is an AppCrash in MMC trying to start the Progress Explorer tool. It’s a c0000005 access violation.



The Progress Explorer uses the Microsoft Java Virtual Machine (jview, wjview, msjava). This is now completely unsupported, but let’s move on. On R2, you get two warnings, a bit like this


Ignore them and run it anyway. It’s best to make sure you have the latest JVM you can find –there are various versions still available on the internet. Use the msjavx86.exe that came with your copy of Progress – some of the later ones will cause more trouble. You’re behind a firewall and you’re not browsing the web from your server, so no security worries, eh?


Don’t, under any circumstance, install the Oracle Sun Java. It won’t work. If you have done this, get rid of it, and try installing Progress again. The installer should notice you have no Java, and install the unsupported MSJAVAVM.



HKEY_CURRENT_USER\Software\Microsoft\Java VM –> EnableJIT = 00 00 00 00 (binary)

Thanks to

You can use this .reg file to simplify things:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Java VM]

[HKEY_USERS\.Default\Software\Microsoft\Java VM]

And make sure you Run as Administrator…

This entry was posted in Uncategorized. Bookmark the permalink.

4 Responses to Progress Explorer and Windows 2008

  1. Tony Trus says:

    This is more of a workaround than a fix. I browsed the solutions online and found that Progress Explorer now works in Windows 7/Server2008 after being patched. If you are reading this and find that it still crashes after all steps above performed get a hold of 10.1C04 or 10.2A01 and that will correct the issue.
    Tony Trus
    Onepax Business Consulting

    • alasdaircs says:

      @Tony Trus: That makes sense, but the Progress world is very closed. App developers supply Progress with their app and then you get lumbered with it. I have clients still merrily bashing on with Line of Business apps running on Progress 9.1C. But thanks for the input – a valid point.

  2. Tony Trus says:

    Very true. I support the Syteline suite of products that run both on Progress and SQL and I know that each release of the app the company wants a very specific patch level for Progress. One thing I didn’t mention is that Progress Explorer on 10.1C actually has a web driven interface so that you can dump MS Java all together and that is available on the base version. That would work around the patch level requirements that the app developer imposes.

  3. Tom Voss says:

    I run into this problem continually on my OpenEdge 10.1C server. I’ve made the necessary registry tweak and occasionally Progress Explorer Tool will work, but usually it fails with an APPCRASH.

    FYI, the link should probably point to

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s