Unable to run any .Net exe in a newly build server

Question

1.00/5 (1 vote)

See more:

Hi All,

We have a newly build virtual server with Windows Server 2003 SE. Visual Studio frameworks 2.0 and 3.5 are both installed. But no matter what we try, .net exe's will not run in this server. When we try to run the exe, it shows up in task manager for a second and then vanishes. No logs are also created.

Can anyone help me with this please?

PS: Other exe's including notepad is working.

To add to this, do you think Symantec Endpoint Protection will cause such issues? We have SEP installed in the server. We are going to uninstall the same and try again.

Posted 21-Jan-15 21:48pm

Member 11194850

Updated 23-Jan-15 1:53am

v2

Add a Solution

Comments

Zoltán Zörgő 22-Jan-15 4:02am

It might depend on the executable. Is it running elsewhere? Try Sysinternal's process monitor to see what it does.

Member 11194850 23-Jan-15 7:51am

We have checked system internal process monitors. No information. The executables are running in other machines - both servers and local desktops.

Timberbird 22-Jan-15 4:46am

Did you check Event Log to see if there are any error records?

Member 11194850 23-Jan-15 7:51am

Yes, we did no log is created for this.

Richard MacCutchan 23-Jan-15 8:54am

Are you sure you are targetting the correct framework version?

RaisKazi 23-Jan-15 9:44am

One thing which helped me in the past - check if any pending windows updates in bottom right tray.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 11194850 · Accepted Answer · 2015-02-02T22:49:00

Solution 1

Thank you everyone. We found the root cause of this. Symantec Endpoint Protection installed in the server was causing the issue. Once, SEP was uninstalled all applications started working fine.

Posted 2-Feb-15 22:49pm

Member 11194850