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

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?
bjshallenbergerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
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
bjshallenbergerAuthor Commented:
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
btanExec ConsultantCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.