I found that the problem is a .net problem and not an application problem.
When I tried to run IEExec.exe, I get the same message. I unistalled .net
v1.1 and repaired the .net 2 installation with no luck, same problem. Any
advice will be appreciated.
Run a virus scan?
Is IEExec.exe the name of your application? I've never heard of "Microsoft
IE Execute shell" nor "IEExec.exe" before, and the naming sounds very
suspicious.
http://support.microsoft.com/kb/822485
Dean, could this apply?
http://blogs.msdn.com/robgruen/archive/2004/09/28/235074.aspx
"Ben Voigt" <r...@nospam.nospam> ha scritto nel messaggio
news:u7xwjXVg...@TK2MSFTNGP03.phx.gbl...
Rayudu Addagarla
> On Tuesday, April 10, 2007 4:22 PM Dean wrote:
> I recently had .net version 2 installed to support a product that requires
> .net 2. When the application is run, I get the message "Microsoft IE Execute
> shell has encountered a problem and needs to close. We are sorry for the
> inconvenience".
>
> I found that the problem is a .net problem and not an application problem.
> When I tried to run IEExec.exe, I get the same message. I unistalled .net
> v1.1 and repaired the .net 2 installation with no luck, same problem. Any
> advice will be appreciated.
>> On Thursday, April 12, 2007 9:20 AM Ben Voigt wrote:
>> Run a virus scan?
>>> On Tuesday, April 17, 2007 6:40 AM Dean wrote:
>>> VirusScan is always on , but I am running a manual scan now. Since the .net
>>> problem affects every PC on this site, I suspect that there is something in
>>> the image (like VOIP) causing the problem.
>>>
>>> "Ben Voigt" wrote:
>>>> On Tuesday, April 17, 2007 9:05 PM Ben Voigt wrote:
>>>> Is IEExec.exe the name of your application? I have never heard of "Microsoft
>>>> IE Execute shell" nor "IEExec.exe" before, and the naming sounds very
>>>> suspicious.
>>>>> On Wednesday, April 18, 2007 4:27 AM Laura T. wrote:
>>>>> IEExec.exe is standard IE helper app for zero deployment.
>>>>>
>>>>> http://support.microsoft.com/kb/822485
>>>>>
>>>>> Dean, could this apply?
>>>>>
>>>>> http://blogs.msdn.com/robgruen/archive/2004/09/28/235074.aspx
>>>>>
>>>>>
>>>>> "Ben Voigt" <r...@nospam.nospam> ha scritto nel messaggio
>>>>> news:u7xwjXVg...@TK2MSFTNGP03.phx.gbl...
>>>>>> On Wednesday, April 18, 2007 1:36 PM Dean wrote:
>>>>>> Thanks for trying. My Tech support solved the problem. We needed to download
>>>>>> the SDK and run the security configuration file (mscorcfg.msc). Security
>>>>>> configuration was previously included with the .net Framework files and the
>>>>>> configuration set up using v 1.1 is not carried over to the 2.0 installation.
>>>>>> I hope this helps anyone else.
>>>>>>
>>>>>> "Laura T." wrote:
>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>> A Comparison of Managed Compression Algorithms
>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/71485ecc-2d2d-435a-9c35-3d12b279f9ae/a-comparison-of-managed-compression-algorithms.aspx
Did you just install .net 2.0, what was changed with the config tool.
we have several issues similar with clickonce app.
not sure if users are upgrading or installing something.
but get this message with our clickonce app all of a sudden
thanks
> On Tuesday, April 10, 2007 4:22 PM Dean wrote:
> I recently had .net version 2 installed to support a product that requires
> .net 2. When the application is run, I get the message "Microsoft IE Execute
> shell has encountered a problem and needs to close. We are sorry for the
> inconvenience".
>
> I found that the problem is a .net problem and not an application problem.
> When I tried to run IEExec.exe, I get the same message. I unistalled .net
> v1.1 and repaired the .net 2 installation with no luck, same problem. Any
> advice will be appreciated.
>> On Thursday, April 12, 2007 9:20 AM Ben Voigt wrote:
>> Run a virus scan?
>>> On Tuesday, April 17, 2007 6:40 AM Dean wrote:
>>> VirusScan is always on , but I am running a manual scan now. Since the .net
>>> problem affects every PC on this site, I suspect that there is something in
>>> the image (like VOIP) causing the problem.
>>>
>>> "Ben Voigt" wrote:
>>>> On Tuesday, April 17, 2007 9:05 PM Ben Voigt wrote:
>>>> Is IEExec.exe the name of your application? I have never heard of "Microsoft
>>>> IE Execute shell" nor "IEExec.exe" before, and the naming sounds very
>>>> suspicious.
>>>>> On Wednesday, April 18, 2007 4:27 AM Laura T. wrote:
>>>>> IEExec.exe is standard IE helper app for zero deployment.
>>>>>
>>>>> http://support.microsoft.com/kb/822485
>>>>>
>>>>> Dean, could this apply?
>>>>>
>>>>> http://blogs.msdn.com/robgruen/archive/2004/09/28/235074.aspx
>>>>>
>>>>>
>>>>> "Ben Voigt" <r...@nospam.nospam> ha scritto nel messaggio
>>>>> news:u7xwjXVg...@TK2MSFTNGP03.phx.gbl...
>>>>>> On Wednesday, April 18, 2007 1:36 PM Dean wrote:
>>>>>> Thanks for trying. My Tech support solved the problem. We needed to download
>>>>>> the SDK and run the security configuration file (mscorcfg.msc). Security
>>>>>> configuration was previously included with the .net Framework files and the
>>>>>> configuration set up using v 1.1 is not carried over to the 2.0 installation.
>>>>>> I hope this helps anyone else.
>>>>>>
>>>>>> "Laura T." wrote:
>>>>>>> On Monday, September 27, 2010 12:16 PM Rayudu Addagarla wrote:
>>>>>>> Can you be more particular
>>>>>>>
>>>>>>> What exactly was changed using the mscorcfg.msc tool.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> did you just install/upgrade to .Net 2.0 and it worked?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Rayudu Addagarla
>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>> Kentico CMS for ASP.NET Sites
>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/ee551a85-2206-446e-bc7d-c978f60ec671/kentico-cms-for-aspnet-sites.aspx