MS security patch KB912883 / MS06-10 cauisng J2EE to crash

[Former Member]

I am running EP6.0 sp15 on NW '04 sp15 on J2SDK1.4.2_12 on WIN2003 SP1 (32bit load balanced system).

After applying MS security patch KB921883 / MS06-40, our dialogue server instance will not start at all. The central instance on the same machine as the SCS (message/enque server) still starts and runs fine.

This is unlike a java heap or license issue which I have tested at all the reccomended settings. The jlaunch.exe's never even start up in the MMC. It fails at the jcontrol.exe within seconds of start with an exit code of -2 in the developer trace.

We have been in contact with MS and are trying to get in touch with someone in SAP (with no success). According to MS, the netapi32.dll was changed by the patch. After removing the patch, the system starts/runs correctly.

Please forgive my ignorance and any mistakes in terminology as I have a hard time keeping up with what naming standards are used.

I have looked at note 664607 and 129813 but I am not sure what it means or if it truly applies in this case.

1. Does anyone have a recommended solution?

2. Is anyone else experiencing this problem (as I think it would be quite prevalent)?

[Former Member · Accepted solution]

Hello Lee,

The issue is caused by address space fragmentation by DLLs of the security patch similar to those of note #664607. I assume the /3GB option is set in the boot.ini file but if not then this should resolve by increasing the address space per process from 2GB to 3GB.

Otherwise problem should be fixed with adjusting Windows Hotfix 924054 (http://support.microsoft.com/kb/924054).

A note of interest is the following also, #853696 (Preloading DLLs to Avoid Address Space Fragmentation).

Hope this helps.

Regards, Mark

[Former Member · Accepted solution]

Mark,

Thank you for the reply.

Unfortunately MS HF 924054 was attempted on Friday/Aug 11 and appears to have caused irreversible damage. Now the system will not start even if we back the patches off.

OSS Note #853696 looks promising but I am not sure where the boot.ini file you refered to exist. Could you provide a likely path/location?

Thanks,

Lee

[Former Member · Accepted solution]

Problem appears to be resolved.

MS provided an updated version of KB924054 which was applied to all but one system after KB921883 successfully.

DEV system is being rebuilt from older image to fix previous HF KB924054 issue (see prev note).

Thanks again for the helpful advise...

[Former Member · Accepted solution]

Glad the information pointed you in the right direction to resolve. Information about the 3GB flag in the C:\boot.ini file can be found at locations such as the following:

http://support.microsoft.com/kb/283037 & http://support.microsoft.com/KB/291988.

Mark

[Former Member]

PD I have exactly the problem that you had. Thanks again.

[Former Member]

Jesus,

The currently available HF924054 is the latest version that resolves the issue:

http://support.microsoft.com/kb/924054/

It seems that we were the first to apply KB921883 to a JAVA system and report a problem to MS. The first version that was applied to our DEV system was a beta version which caused other issues. We later applied the current (updated) HF to our other systems and everything worked.

Since then we have rebuilt our DEV FE system and applied the current HF successfully.

Hope this helps,

Lee

[Former Member]

Hi,

Lee I saw your answer, and I noted that you have an updated version of KB924054, could you send me the link to can download that file, or could you send me the file to my email (jandonie@gmail.com) ?

Thanks in advance for your help.

Jesus

[Former Member]

Sorry, transposed patch number in heading: KB921883