sdnian 6 Posted March 22, 2017 Posted March 22, 2017 The newest version of MirrorTool v1.0.513.0 can't be run in Windows Server 2003. It appear a message 'MirrorTool.exe is not a valid Win32 application.' Where can download the previous version of MirrorTool?
kingoftheworld 10 Posted March 22, 2017 Posted March 22, 2017 The better question is why are you using Server 2003 to run a security application?
sdnian 6 Posted March 23, 2017 Author Posted March 23, 2017 Why don't you ask ESET if Mirror Tool shouldn't be supported for Server 2003.. Why it provide such information?
ESET Moderators Peter Randziak 1,223 Posted March 23, 2017 ESET Moderators Posted March 23, 2017 Hello, the Mirror tool requires Visual C++ Redistributable for Visual Studio 2015 (x86) to work properly, you can download them from the Microsoft site here: https://www.microsoft.com/en-us/download/details.aspx?id=48145 Regards, P.R.
Administrators Marcos 5,735 Posted March 23, 2017 Administrators Posted March 23, 2017 16 minutes ago, j-gray said: https://www.us-cert.gov/ncas/alerts/TA14-310A Although the best course of action (not only from the security POV) would be upgrading the server, not everyone can afford it or do it. We also have many even business users who run Windows XP which is no longer supported by Microsoft but we do our best to keep our products compatible with it.
sdnian 6 Posted March 23, 2017 Author Posted March 23, 2017 7 hours ago, Peter Randziak said: Hello, the Mirror tool requires Visual C++ Redistributable for Visual Studio 2015 (x86) to work properly, you can download them from the Microsoft site here: https://www.microsoft.com/en-us/download/details.aspx?id=48145 Regards, P.R. Thanks P.R. for your reply. But it doesn't help. I've installed Visual C++ Redistributable for Visual Studio 2015 (x86).. But it still popup the same error message. And I think the MirrorTool.exe requires Visual C++ 2010 Redistributable, not 2015. According my test.. it requires the file msvcr100.dll.
Administrators Marcos 5,735 Posted March 23, 2017 Administrators Posted March 23, 2017 We have it tracked as a bug. As soon as a fix is available, we will update this topic.
Recommended Posts