No touch deployment - IEEXEC won't fire up

[Guest]

We are experiencing a problem when trying to run an application using no
touch deployment.
All works fine on our W2K workstations but failes to run when browsing from
IE on a Win2K server with framework 1.1, IE 6.0.28.

On the server running the application like this works:
"C:\WINNT\Microsoft.NET\Framework\v1.1.4322\IEExec.exe
http://myserver/MyApp.exe" but failes when browsing to it in IE with
http://myserver/MyApp.exe

There is no error message.

Thank you for your help

Jag

 

[Ahmed Qurashi]

Tchuss Jag!

You know that to deploy No Touch Apps you need to be running IIS with
ASP.NET. Try creating a virtual directory and putting the assembly in a
hypertext link on an *.aspx page. Turn on debugging and then look for error
messages.

ok,
aq

 

[Guest]

hi Ahmed,

The point is that it all works fine from all workstation. I am trying to run
this from a server (windows 2000) setup with .net framework 1.1
The steps are:
I open IE
browse to http://myserver/MyApp.exe
And nothing happens, no error message or notification
no Ieexec process running
Download cache is empty

any idea of what could cause ieexec not to start?

cheers
Jag

 

[Ahmed Qurashi]

Oh, I see, the server doesn't seem to deploy to itself!
That is interesting behavior...

When you manually run IEExec does the assemply get 'downloaded' to the
assembly cache?

ok,
aq

 

[Guest]

yes running this is OK:
C:\WINNT\Microsoft.NET\Framework\v1.1.4322\IEExec.exe
http://myserver/MyApp.exe
Assembly cache get populated etc...

the problem happens with any of my win2k servers - not necessarly the one
where assemblies are deployed onto...

cheers
Jag

 

[Jon Lipp]

I'm having this same problem although a slightly different scenario. We are
all running XP Pro with all the latest service packs. We've had it happen
on some workstations. The strange thing is it will work, then stop working.
Then on other machines where it used to not work, it will work again. We've
not been able to determine any relation between the workstation
configuration and this happening.

So any new info or solutions on this problem?

Jon

 

[Guest]

I have exactly the same problem with an XP Professional workstation. I can
load the application via ieexec (either the 1.1 or the 2.0 beta 1 version),
but trying to load it using IE does nothing (no error message - just hangs).
Its not a web server problem as all the other PCs I have tried this on work.

 

[Guest]

I have got it working now, although I'm not sure exactly which step was the
one that fixed it. I created a new "runtime security policy - machine - code
group" to fully trust the web server for both versions of the framework I
have installed - 1.1 and 2.0 (it seems that the 2.0 ieexec.exe was the one
being used by IE), and also explicitly specified the runtime I wanted (1.1)
in the .exe.config file on the web server.

 

[Jon Lipp]

We are now dedicating some resources to figure this out, but before we start
calling Microsoft I have been doing some research.

Did you have any more details on this? As you know, a security code group
is not required to web-launch an app. In fact, my test app is a simple
WinForm with a button on it that is not strongly named. Anyway, we only
have framework 1.1, but still cannot get it to work on certain workstations.
But nonetheless I tried your idea and it didn't make any difference.

Also, what exe.config on the web server are you talking about? I don't
believe the web server has to have the framework even loaded, right? My
HelloWorld.exe is just a file that gets served up.

Any help you have is greatly appreciated!

Jon

 

[Jon Lipp]

FYI: we found the fix to this... clear the internet cache in IE:
Tools-Internet Options-Delete Files. We were able to show this fixed it on
two different systems.