?
Solved

Having trouble connecting to a Providex application after upgrading TrendMicro on the server

Posted on 2014-08-17
3
Medium Priority
?
503 Views
Last Modified: 2014-08-23
We have been accessing a Providex application by using remote desktop to a server 2008 machine, then Windx version 6.2  to get to the application.  We have been connecting in this way for a couple of years with no problems. We did a TrendMicro update to the latest version and since then we have been unable to connect.  We are getting the APPCRASH message from Windows with the exception code c0000005.   We have reinstalled the server but are still having the same problem. Has anyone had this kind of problem or know of a solution?
0
Comment
Question by:bjshallenberger
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 64

Expert Comment

by:btan
ID: 40267467
May want to chk TrendMicro FW rules as well just to make no blocking of RDP
http://esupport.trendmicro.com/solution/en-US/1055442.aspx

There are past sharing but not specific to Providex though - the focus is on the "Fault Module Name" which is causing such AppCrash and that can leads to whether which is the faulting file
http://community.trendmicro.com/t5/OfficeScan/Officescan-Consols-amp-Win-7/td-p/5850

And even the File check that allows users to scan for corruptions in Windows system files and restore corrupted files.
http://support.microsoft.com/kb/929833
http://blogs.technet.com/b/askcore/archive/2007/12/18/using-system-file-checker-sfc-to-fix-issues.aspx
0
 

Author Comment

by:bjshallenberger
ID: 40270686
Thanks for the response...

FW would be first thing checked in this case.  In our case we did not have the TM firewall on...nor the Windows firewall during the period we were troubleshooting.  Even turned off both, uninstalled TM.  Went through much troubleshooting and made the decision to do fresh install of server.  Continued our testing with no other software installed (nor Windows update, fresh server 2008, SP1).  The providex executable will actually run locally (always did).  We have command args that tell providex to act as a client and communicate to a server over the network via a specific TCP port.  At the point where it touches the server, I can log that connection.  The connection was being made at the proper TCP port and all looks normal.  As part of the next step in the communication, the server hands off the connection to the next TCP port available in a range so the client can maintain a client/server connection.  It's at this point the client fails.  I suspect the problem is in the handoff to the TCP port and a failure of the communication to be received, or interpreted by the client.  We would get a different (actual error) if the client could not communicate at all with the server.  A different version of the product works fine...but we need to run the current version for compatibility reasons.  Seems the solution would be to upgrade to working version, but we have been running our current version on same OS for over a year.  Furthermore, we have 3 other 2008 servers that are currently working with this 6.2 version.  Additional thoughts are appreciated.
0
 
LVL 64

Accepted Solution

by:
btan earned 1000 total points
ID: 40271465
besides port conflicts, and if local running of the Providex is fine then even if I RDP into the server and running into the Providex locally on the server again, it should still be running fine... ports used by TM as example  @ http://esupport.trendmicro.com/solution/en-US/1056094.aspx

I am not sure but sense the RDP connection seems to be in conflict with the newer Trend Micro version I guesses and hence certain holding of the resource like ports (like relay of TM etc) or services (like TM heartbeats etc) causes Providex not able to run over RDP ... the AppCrash message can be too general to diagnose .. maybe good to see if there is leading errors before and during the RDP connection established in the Windows server event viewer ..

it may also be other running that cause local admin to been locked out or have to tried other account of administrative too...may be best to have TM support coming in to advice upgrade steps
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article was originally published on Monitis Blog, you can check it here . Today it’s fairly well known that high-performing websites and applications bring in more visitors, higher SEO, and ultimately more sales. By the same token, downtime…
If you're a modern-day technology professional, you may be wondering if certifications are really necessary. They are. Here's why.
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question