Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 5512] New: msvcr80.dll error trying to start tshark on windows server 2003

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5512

           Summary: msvcr80.dll error trying to start tshark on windows
                    server 2003
           Product: Wireshark
           Version: 1.4.1
          Platform: Other
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: Blocker
          Priority: Low
         Component: TShark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: andybuckle@xxxxxxxxx


Build Information:
TShark 1.4.1 (SVN Rev 34476 from /trunk-1.4)

Copyright 1998-2010 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GLib 2.22.4, with WinPcap (version unknown), with libz
1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8, with c-ares
1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with
MIT Kerberos, with GeoIP.

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).

Built using Microsoft Visual C++ 9.0 build 30729
--
I tried win32 1.4.1 and 1.2.12 installers from wireshark.org.

When I try to start tshark I get an error about msvcr80.dll. 

The installer puts msvcr90.dll in the Wireshark directory. Is tshark built in
some way that is wrong for MS server 2003?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.