Please be advised as we are getting microsoft visual C++ Runtime library error after installing the newer version i.e 1.8.2 , we also tried to reinstall the whole package but it didn't help either. The system never had the older version basically its the first time we started using it. asked 11 Sep '12, 14:29  crazii007 showing 5 of 6 show 1 more comments |
This is a static archive of our old Q&A Site.
Please post any new questions and answers at ask.wireshark.org.
O.K. some questions:
The same happened on two different server systems in our network after having installed Wireshark Version 1.8.2. We used Wireshark 1.2.4 on these servers before without any issues. The old version has been completely removed before installing 1.8.2. Complete re-installation of 1.8.2 (incl. winpcap) didn't help.
OS Version: Windows Server 2003 x86 (32 bit) Std. Ed. /w SP2 Error Message: - Header "Microsoft Visual C++ Runtime Library" - Content "Runtime Error! Program: <blank> This application has requested the Runtime to terminate it in an unusal way."
I am able to run WireShark using out of the box full trace capture for approximately 9 minutes 25 seconds before receiving the following:
***Begin Dialog
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
***End Dialog
Environment: - Version 1.8.5 (SVN Rev 47350 from /trunk-1.8) - Running on Windows Server 2003 Service Pack 2, build 3790, with WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.with PCAP 4.1.2 on Windows Server 2003R2 SP - Built using Microsoft Visual C++ 10.0 build 40219
Perhaps I should have just entered this in a comment instead of as an answer. My apology. If the expectation is to create a new thread please advise. T/Y
I converted it to a comment for you.
Likely to be due to running out of memory. How much do you have on the machine?
What line rate are you capturing at, what is the link utilisation rate, are you enabling promiscuous mode and do you have any capture filters?
Related to this bug? https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8281