Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security ISSForum
[Top] [All Lists]

[ISSForum] Internet Scanner 7 SP2 console consistently crashing at launc

Subject: [ISSForum] Internet Scanner 7 SP2 console consistently crashing at launch when DB > 256MB
Date: Fri, 2 Jun 2006 08:50:46 -0400

Internet Scanner 7 SP2, W2K current on patches, MSDE RelA...  Whenever
the DB gets about 256MB, the console GUI will crash during "Loading
database management...", with a generic MS Visual C++ Runtime Library
error "Program C:\Program
Files\ISS\ScannerConsole\InternetScanner_Console.exe - This application
has requested the Runtime to terminate it in an unusual way.".   This
will consistently happen on any of the 10 scanners we currently have
deployed, and it has done so for as long as I can remember - even with
the original 7.0 release, I believe, but it is just starting to become
more than an annoyance now.

The CLI will continue work fine, which is what I usually use for
scanning, so it wouldn't be a problem except that it appears the only
time the vulns table is updated after installing a new XPU is when the
you launch the GUI, and get the "Synchronizing Builtin Exploits...".
None of the CLI options for either installing XPU's or the DB functions
appear to address this.   The DB integrity check completes without
errors, and according to the log files, the new checks are actually
done.   I'm not sure if they'd actually show up using the built-in
reporting, but all my reporting is done directly from the DB itself, and
if the Vulns<->VulnsFound relation is missing, I'm out of luck (not sure
how the built-in reporting would handle this any differently...).

Any suggestions?

________________________________________________

SIEMENS                        Medical Solutions 
 
Brian Sims
Information Security

51 Valley Stream Parkway, Malvern PA  19355-1406
Phone:                          +01 610 219 4668
Fax:                              +01 610 219 3124
E-Mail:                   Brian.Sims@siemens.com
________________________________________________


-------------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions
USA, Inc. and are intended only for the addressee(s). 
The information contained herein may include trade secrets or privileged or
otherwise confidential information.  Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful.  If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to 
Central.SecurityOffice@shs.siemens.com

Thank you


_______________________________________________
ISSForum mailing list
ISSForum@iss.net

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to 
https://atla-mm1.iss.net/mailman/listinfo/issforum

To contact the ISSForum Moderator, send email to mod-issforum@iss.net

The ISSForum mailing list is hosted and managed by Internet Security Systems, 
6303 Barfield Road, Atlanta, Georgia, USA 30328.

<Prev in Thread] Current Thread [Next in Thread>