A
Alex K
Hi,
I am testing a smart client application.
The application is practically composed from:
1. An Exe
2. A DLL
I put those files on my IIS server, after creating a
special virtual directory. I made all security settings
on IIS.
Then I went to Dot Net Framework wizards and I picked
those 2 assemblies and "I trusted them". I also modified
accordingly the "Security Zones".
Despite that when I am trying to start the EXE file thru
a shortcut placed on my desktop the EXE doesn't come out
of IIS. Is displaying the following message:
CGI Error
The specified CGI application misbehaved by not returning
a complete set of HTTP headers. The headers it did return
are:
....and there is no header displayed, so far.
I read several articles where is showed that IIS must be
setup to handle EXE files. I tried to do that but my "OK"
button is disabled. It doesn't make sense this behavior
since I am Admin on my system and also on IIS.
I suspect because this is not setup properly it doesn't
work.
Also I found an article presenting how an assembly must
be signed, using an utility called: sn
I tried it but it doesn't recognize this command.
What possibly can be? Should I reinstall IIS? or the Dot
Net Framework? All these are looking ok for me.
Definitely I think is related to security which Dot Net
Framework implements, but something is escaping me from
all of this...
What do you believe is the issue here?
Best regards,
Alex
I am testing a smart client application.
The application is practically composed from:
1. An Exe
2. A DLL
I put those files on my IIS server, after creating a
special virtual directory. I made all security settings
on IIS.
Then I went to Dot Net Framework wizards and I picked
those 2 assemblies and "I trusted them". I also modified
accordingly the "Security Zones".
Despite that when I am trying to start the EXE file thru
a shortcut placed on my desktop the EXE doesn't come out
of IIS. Is displaying the following message:
CGI Error
The specified CGI application misbehaved by not returning
a complete set of HTTP headers. The headers it did return
are:
....and there is no header displayed, so far.
I read several articles where is showed that IIS must be
setup to handle EXE files. I tried to do that but my "OK"
button is disabled. It doesn't make sense this behavior
since I am Admin on my system and also on IIS.
I suspect because this is not setup properly it doesn't
work.
Also I found an article presenting how an assembly must
be signed, using an utility called: sn
I tried it but it doesn't recognize this command.
What possibly can be? Should I reinstall IIS? or the Dot
Net Framework? All these are looking ok for me.
Definitely I think is related to security which Dot Net
Framework implements, but something is escaping me from
all of this...
What do you believe is the issue here?
Best regards,
Alex