Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 4281 Source: IPSEC

Source
Level
Description
Unable to allocate required resources. Initialization failed.
Comments
 
From a newsgroup post: "We tracked this one down to a Modem Pooling Software we use. SpartaCom MPNT causes this error and it is safe to ignore it. They do however have a fix to prevent this error. Go to "SpartaCom Support Technote Number: TN4937". This solved our problem".

As per Microsoft: "There was a shortage of some resource, probably memory, that this component requires". See MSW2KDB for additional information about this event.
From Microsoft:"There was a shortage of some resource, probably memory, that this component requires. Close some applications and try again. If you still get this message, check the event log to find out what other errors occurred at about the same time. Take the appropriate action for those errors, and try again. You might need to install more memory."
I had recently copied the system registry hive from the winnt\repair folder to replace the current one, which was giving me problems, after doing that, this error appeared.  I reinstalled SP4 and all was normal again.
In our case, this appeared due to the program MFL Pro, installed along with Brother Multifunction Printer (in my case an MFC 5100). Brother have released a registry fix which basically seems to remove any dependances the BR Serial service has on any other service. The patch can be downloaded from the link below - Brother Solutions Center FAQ, id prfaq0788.
The error occurred after installing W2K SP2. The solution was to replace the IPSEC.SYS file installed by SP2 with a previous version. If you had selected the uninstall option prior to the actual installation, simply copy/paste the IPSEC.SYS file from the uninstall folder "$NtServicePackUninstall$" to the "WINNT\SYSTEM32\DRIVERS" folder. Reboot the computer; check the system event protocol ... it's OK. The IPSEC.SYS file version installed by SP2 that failed was 5.0.28xx.x. The IPSEC.SYS file version I copy/pasted is 5.0.2195.2940.


This problem raised after I installed the LANcom LanCapi. According to LANCOM Systems this failure didnīt have any effect on the system and it would be a special behaviour of Windows 2000.
We encountered this error message on Windows 2000 Pro after printer drivers for NT (incompatible with windows 2000) were installed by mistake. We uninstalled these drivers and the error disappered.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...