Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Windows 2000 memory heap issues

Original Message
Name: LG (by leezerz)
Date: December 7, 2007 at 13:36:07 Pacific
Subject: Windows 2000 memory heap issues
OS: Win2k/SP4
CPU/Ram: 2.8GHz
Comment:
I am receiving an error from a Tivoli Workload Scheduler process due to a Windows 2000 memory heap issue. I'm then unable to restart the TWS service: "The service could not start in a timely fashion"

Error in TWS log:

AWSBIK005E Error connecting socket to server
../../src/jobman/winutil.c:219
error = Bad file descriptor. : 9.
AWSBIK202E Error creating JOBMON ../../src/jobman/monitor.c:191.

Online doc indicates to increase system memory heap size http://www-1.ibm.com/support/docvie... I have increased the value to SharedSection=1024,3072,512,512 but the issue is still occurring. The only way to restart the required service is to reboot.

LG


Report Offensive Message For Removal





Use following form to reply to current message: 

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Windows 2000 memory heap issues

Comments:
         

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL:
 


Data Recovery Software



CMOS/GPNV checksum bad

3 Strikes

how to find complete path of a file

Replication of DC with ADC

Deleting a block of text with sed

The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC