Skip to Content
Former Member
Jun 23, 2005 at 07:30 PM

Inconsistent behavior of local J2E engine



Last week I patched my local J2E engine to SP stack 11.

Ever since, I've been getting inconsistent behavior with the local engine.

Before the patch I was always able to go into the MMC and start the engine. Now when I go into the MMC the engine is either already started or I can't start it at all. The "Start" option shows up on the context menu in the MMC but nothing happens when I click on it.

In those cases, I have to go into Services, find the SAPJ2E_00 service, bring up its properties and change the password. Once I do that the service starts and if I go into MMC I can see that it's started.

By the way, the SAPJ2E_01 and SAPJ2E_01 services are both setup with "Automatic" for Startup Type.

I have a couple of questions about this:

1) Why was I able to ALWAYS start engine from MMC before patch?

2) Why does it not remember the password when I change it in the Service's properties?

Thanks in advance for any help.