views:

100

answers:

3

hi ,

I've written a server programm lets call it progie , this progie working just like a clock on my windows 7 (my ms VS is installed on windows 7) after compiling the progie and transfer it to windows server 2003 I tried to run the progie but no chance.

here is the symptom :

when i was trying to run the progie I was also monitoring the task manager , in task manager it shows the progie for only couple of seconds and then the poor program vanishes from the task manager or its better to say from the memory.

I'm using .net 3.5 / C# libraries : generics , diagnostic , IO

installed frameworks on my server : dotnetfx 2.0 dotnetfx 3.0 dotnetfx 3.5

windows server 2003

A: 

Try to run it as an Administrator.

TTT
I did but no chance. the same problem still remained.
austin powers
A: 

Since it doesn't even crash, just vanishes, it sounds to me like a .Net FW mismatch (i.e. you're missing the right version) or another missing resource. Easiest way to get a hold of this: download SysInternals' ProcMon, and monitor which files/DLLs progie tries to open and fails. That should put you on the right track.

Traveling Tech Guy
@Traveling Tech Guy: Well...the OP clearly stated that the versions of framework was installed on the server....hence -1....
tommieb75
@tommieb75 it could still be a version discrepency. Nevertheless, the solution I offered is quite general and will address other resource issues as well.
Traveling Tech Guy
+2  A: 

Note that your progie runs fine on Windows 7 with VS installed and fails on the server. Possible causes can be,

  1. progie depends on third party libraries, which you did not yet install on the server. Things like DevExpress libraries and so on will lead to such problems. The fix is to deploy the dependencies along with your executable.

  2. Your code raises unhandled exception on server 2003. If so, you should be able to find crash records for progie in Application event log. The fix is to capture crash dump and analyze it. http://dumpanalysis.org

Lex Li