Greetings;

I work for a large school district which uses Oracle 9i and Weblogic extensively. Upon the update of Window Update KB968389, the weblogic services stopped starting automatically. They can be started manually, but the automatic 'start when windows loads' will not work. It throws the exception error:

Application popup: beasvc.exe - Application Error : The instruction at "0x7c82cac2" referenced memory at "0x00000000". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
For more information, see Help and Support Center at Events and Errors Message Center: Basic Search (http://go.microsoft.com/fwlink/events.asp).

The fin84prd-PIA service hung on starting.
For more information, see Help and Support Center at Events and Errors Message Center: Basic Search (http://go.microsoft.com/fwlink/events.asp).

Application popup: Service Control Manager : At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
For more information, see Help and Support Center at Events and Errors Message Center: Basic Search (http://go.microsoft.com/fwlink/events.asp).

We currently are researching this with Oracle as well, however the items that they believe may be causing this do not appear to be the cause. Having seen several posts on different forums pertaining to this update, I am now pursuing it from the OS side. I am wondering if anyone else is having memory issues or service startup failures since the update KB968389 was applied. When we remove the patch, the service auto-starts normally. The confusing part is that this patch is 'supposedly' not active until you adjust the registry manually. So what is this patch changing that people are having issues with it, particularly since it seems as though most posters mention not having implemented the activation of the patch?

The confusing part is that this patch is 'supposedly' not active until you adjust the registry manually...So what is this patch changing...

The feature may not need to be active. Code change usually brings unintended consequences without extensive testing. Extended Protection for Authentication (http://support.microsoft.com/default.aspx/kb/968389) lists all the files that the patch replaces. You might try adding the registry keys only to force disable Extended Protection for Authentication if you haven't attempted this already. Have you contacted Microsoft? They need to be party to the headache for issuing a non-security patch as a "critical" update, particularly if the patch breaks existing functionality.

Other Info:
Extended Protection for Authentication Overview (http://msdn.microsoft.com/en-us/library/dd767318.aspx)

Also see if you can uninstall the update and in future, do updates manually as if set to automatic, it would probably be installed again.

... Have you contacted Microsoft? They need to be party to the headache for issuing a non-security patch as a "critical" update, particularly if the patch breaks existing functionality.

Other Info:
Extended Protection for Authentication Overview (http://msdn.microsoft.com/en-us/library/dd767318.aspx)

Well since we don't have an active technical support contract with Microsoft, we have to pay, and I refuse to pay THEM to consult on an issue THEY caused.

We have automatic set to download only, and that patch has been unapproved so it will not install again. Since Microsoft released what appears to be such an innocuous looking patch and its causing people these headaches, I believe they should be offering up some explainations or at least in their feable world, a knowledge base article on it aside from the patch description.

I guess my question really is who else is having this issue and did you find a work around aside from removing the patch entirely?

Thanks

I do see many have had issues with this particular update but really no explanation.

I have XP SP3 and Vista SP2 and fortunately both systems installed this update without issue.

Sometimes in upcoming updates this issue is addressed and MS supplies some sort of supplemental update that will allow an update to install properly (not always the case).

In meantime, go with what will work for the situation and maybe try again to install at a later date and time.

... I refuse to pay THEM to consult on an issue THEY caused.

I understand that completely. However, for production type applications I also realize that with that attitude I'm cutting off my nose to spite my face so to speak. Microsoft may have an internal hotfix already worked out that hasn't been fully tested yet for general release. General release may take several weeks. In the meantime, I'm wasting my time randomly trying various things to develop a workaround myself. My focus should be getting the problem resolved in the most quick and most cost effective manner possible for my organization. Blame and punishment can be dispensed later.

I understand that completely. However, for production type applications I also realize that with that attitude I'm cutting off my nose to spite my face so to speak. ...... My focus should be getting the problem resolved in the quickest and most cost effective manner possible for my organization. Blame and punishment can be dispensed later.

Excellent point, and would apply if I hadn't learned years ago to deal with the production issue first, then whine and complain afterwards! *Wink* Always, always return production to as normal as possible first, then crack heads later when you can enjoy it more!

Thanks for at least confirming that we aren't alone.