«

I have an ASP.Net 2.0 application running on Windows Server 2003. The
application displays properly in Internet Explorer, however, when I use
a browser control embedded in a .net form, I get an error and am
directed to the Windows Application Event Log. The following message
is logged:

-------------

Source: ASP.NET 1.1.4322.0
Event ID: 1062

It is not possible to run two different versions of ASP.NET in the same
IIS process. Please use the IIS Administration Tool to reconfigure your
server to run the application in a separate process.

-------------

The application is setup under IIS as a 2.0 application. What would
make IIS try to serve it as a 1.1 app? How do I fix this?

Was the browser control written for ASP.NET 1.1 ?
You might have to recompile it for 2.0.

Otherwise...run your 1.1 and 2.0 apps in different Application pools.
You cannot run different-version apps in the same App Pool.



Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"jeremy" <> wrote in message
news: ups.com...
>I have an ASP.Net 2.0 application running on Windows Server 2003. The
> application displays properly in Internet Explorer, however, when I use
> a browser control embedded in a .net form, I get an error and am
> directed to the Windows Application Event Log. The following message
> is logged:
>
> -------------
>
> Source: ASP.NET 1.1.4322.0
> Event ID: 1062

> It is not possible to run two different versions of ASP.NET in the same
> IIS process. Please use the IIS Administration Tool to reconfigure your
> server to run the application in a separate process.
>
> -------------
>
> The application is setup under IIS as a 2.0 application. What would
> make IIS try to serve it as a 1.1 app? How do I fix this?

Juan, the browser control is the standard .Net browser control, dropped
in VS.Net 2005 onto a form.

That shouldn't matter though. Why would IIS change how it served the
..Net 2.0 ASP.Net page based on the browser? That's why I'm confused.
It works fine in the debug environment, on XP, but when I publish to
the webserver and run the .Net form on the same webserver, it breaks.

Juan T. Llibre wrote:
> Was the browser control written for ASP.NET 1.1 ?
> You might have to recompile it for 2.0.
>
> Otherwise...run your 1.1 and 2.0 apps in different Application pools.
> You cannot run different-version apps in the same App Pool.
>
>
>
> Juan T. Llibre, asp.net MVP
> aspnetfaq.com : http://www.aspnetfaq.com/
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en español : http://asp.net.do/foros/
> ===================================
> "jeremy" <> wrote in message
> news: ups.com...
> >I have an ASP.Net 2.0 application running on Windows Server 2003. The
> > application displays properly in Internet Explorer, however, when I use
> > a browser control embedded in a .net form, I get an error and am
> > directed to the Windows Application Event Log. The following message
> > is logged:
> >
> > -------------
> >
> > Source: ASP.NET 1.1.4322.0
> > Event ID: 1062
>
> > It is not possible to run two different versions of ASP.NET in the same
> > IIS process. Please use the IIS Administration Tool to reconfigure your
> > server to run the application in a separate process.
> >
> > -------------
> >
> > The application is setup under IIS as a 2.0 application. What would
> > make IIS try to serve it as a 1.1 app? How do I fix this?

re:
> the browser control is the standard .Net browser control, dropped
> in VS.Net 2005 onto a form.

Unless you do some fancy stepping, the webbrowser control is, normally,
used in Windows Forms applications, not in ASP.NET applications.

Would you describe the method(s) you're using to make it work within ASP.NET ?



Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"jeremy" <> wrote in message
news: ps.com...
Juan, the browser control is the standard .Net browser control, dropped
in VS.Net 2005 onto a form.

That shouldn't matter though. Why would IIS change how it served the
..Net 2.0 ASP.Net page based on the browser? That's why I'm confused.
It works fine in the debug environment, on XP, but when I publish to
the webserver and run the .Net form on the same webserver, it breaks.

Juan T. Llibre wrote:
> Was the browser control written for ASP.NET 1.1 ?
> You might have to recompile it for 2.0.
>
> Otherwise...run your 1.1 and 2.0 apps in different Application pools.
> You cannot run different-version apps in the same App Pool.
>
>
>
> Juan T. Llibre, asp.net MVP
> aspnetfaq.com : http://www.aspnetfaq.com/
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en español : http://asp.net.do/foros/
> ===================================
> "jeremy" <> wrote in message
> news: ups.com...
> >I have an ASP.Net 2.0 application running on Windows Server 2003. The
> > application displays properly in Internet Explorer, however, when I use
> > a browser control embedded in a .net form, I get an error and am
> > directed to the Windows Application Event Log. The following message
> > is logged:
> >
> > -------------
> >
> > Source: ASP.NET 1.1.4322.0
> > Event ID: 1062
>
> > It is not possible to run two different versions of ASP.NET in the same
> > IIS process. Please use the IIS Administration Tool to reconfigure your
> > server to run the application in a separate process.
> >
> > -------------
> >
> > The application is setup under IIS as a 2.0 application. What would
> > make IIS try to serve it as a 1.1 app? How do I fix this?

Juan,

he's running either a browser (where the code works) or a WinForms app
with the browser control (where the code fails).

> That shouldn't matter though. Why would IIS change how it served the
> .Net 2.0 ASP.Net page based on the browser? That's why I'm confused.
> It works fine in the debug environment, on XP, but when I publish to
> the webserver and run the .Net form on the same webserver, it breaks.

Are you sure both the browser and the browser control are sending the
request to the exact same URL?

I would also trace the HTTP requests to see if there are any differences
between them (Fiddler http://www.fiddlertool.com is your friend here)

Kevin

Juan T. Llibre wrote:
> re:
>> the browser control is the standard .Net browser control, dropped
>> in VS.Net 2005 onto a form.
>
> Unless you do some fancy stepping, the webbrowser control is, normally,
> used in Windows Forms applications, not in ASP.NET applications.
>
> Would you describe the method(s) you're using to make it work within ASP.NET ?
>
>
>
> Juan T. Llibre, asp.net MVP
> aspnetfaq.com : http://www.aspnetfaq.com/
> asp.net faq : http://asp.net.do/faq/
> foros de asp.net, en español : http://asp.net.do/foros/
> ===================================
> "jeremy" <> wrote in message
> news: ps.com...
> Juan, the browser control is the standard .Net browser control, dropped
> in VS.Net 2005 onto a form.
>
> That shouldn't matter though. Why would IIS change how it served the
> .Net 2.0 ASP.Net page based on the browser? That's why I'm confused.
> It works fine in the debug environment, on XP, but when I publish to
> the webserver and run the .Net form on the same webserver, it breaks.
>
> Juan T. Llibre wrote:
>> Was the browser control written for ASP.NET 1.1 ?
>> You might have to recompile it for 2.0.
>>
>> Otherwise...run your 1.1 and 2.0 apps in different Application pools.
>> You cannot run different-version apps in the same App Pool.
>>
>>
>>
>> Juan T. Llibre, asp.net MVP
>> aspnetfaq.com : http://www.aspnetfaq.com/
>> asp.net faq : http://asp.net.do/faq/
>> foros de asp.net, en español : http://asp.net.do/foros/
>> ===================================
>> "jeremy" <> wrote in message
>> news: ups.com...
>>> I have an ASP.Net 2.0 application running on Windows Server 2003. The
>>> application displays properly in Internet Explorer, however, when I use
>>> a browser control embedded in a .net form, I get an error and am
>>> directed to the Windows Application Event Log. The following message
>>> is logged:
>>>
>>> -------------
>>>
>>> Source: ASP.NET 1.1.4322.0
>>> Event ID: 1062
>>> It is not possible to run two different versions of ASP.NET in the same
>>> IIS process. Please use the IIS Administration Tool to reconfigure your
>>> server to run the application in a separate process.
>>>
>>> -------------
>>>
>>> The application is setup under IIS as a 2.0 application. What would
>>> make IIS try to serve it as a 1.1 app? How do I fix this?
>
>

re:
> he's running either a browser (where the code works) or a WinForms app with the browser control
> (where the code fails).

Thanks, Kevin. It wasn't very apparent that he's running both.

re:
> I would also trace the HTTP requests

Also, check that the code allows for the members to be handled, per:
http://msdn.microsoft.com/library/de...webbrowser.asp




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Kevin Jones" <> wrote in message
news:...
> Juan,
>
> he's running either a browser (where the code works) or a WinForms app with the browser control
> (where the code fails).
>
> > That shouldn't matter though. Why would IIS change how it served the
> > .Net 2.0 ASP.Net page based on the browser? That's why I'm confused.
> > It works fine in the debug environment, on XP, but when I publish to
> > the webserver and run the .Net form on the same webserver, it breaks.
>
> Are you sure both the browser and the browser control are sending the request to the exact same
> URL?
>
> I would also trace the HTTP requests to see if there are any differences between them (Fiddler
> http://www.fiddlertool.com is your friend here)
>
> Kevin
>
> Juan T. Llibre wrote:
>> re:
>>> the browser control is the standard .Net browser control, dropped
>>> in VS.Net 2005 onto a form.
>>
>> Unless you do some fancy stepping, the webbrowser control is, normally,
>> used in Windows Forms applications, not in ASP.NET applications.
>>
>> Would you describe the method(s) you're using to make it work within ASP.NET ?
>>
>>
>>
>> Juan T. Llibre, asp.net MVP
>> aspnetfaq.com : http://www.aspnetfaq.com/
>> asp.net faq : http://asp.net.do/faq/
>> foros de asp.net, en español : http://asp.net.do/foros/
>> ===================================
>> "jeremy" <> wrote in message
>> news: ps.com...
>> Juan, the browser control is the standard .Net browser control, dropped
>> in VS.Net 2005 onto a form.
>>
>> That shouldn't matter though. Why would IIS change how it served the
>> .Net 2.0 ASP.Net page based on the browser? That's why I'm confused.
>> It works fine in the debug environment, on XP, but when I publish to
>> the webserver and run the .Net form on the same webserver, it breaks.
>>
>> Juan T. Llibre wrote:
>>> Was the browser control written for ASP.NET 1.1 ?
>>> You might have to recompile it for 2.0.
>>>
>>> Otherwise...run your 1.1 and 2.0 apps in different Application pools.
>>> You cannot run different-version apps in the same App Pool.
>>>
>>>
>>>
>>> Juan T. Llibre, asp.net MVP
>>> aspnetfaq.com : http://www.aspnetfaq.com/
>>> asp.net faq : http://asp.net.do/faq/
>>> foros de asp.net, en español : http://asp.net.do/foros/
>>> ===================================
>>> "jeremy" <> wrote in message
>>> news: ups.com...
>>>> I have an ASP.Net 2.0 application running on Windows Server 2003. The
>>>> application displays properly in Internet Explorer, however, when I use
>>>> a browser control embedded in a .net form, I get an error and am
>>>> directed to the Windows Application Event Log. The following message
>>>> is logged:
>>>>
>>>> -------------
>>>>
>>>> Source: ASP.NET 1.1.4322.0
>>>> Event ID: 1062
>>>> It is not possible to run two different versions of ASP.NET in the same
>>>> IIS process. Please use the IIS Administration Tool to reconfigure your
>>>> server to run the application in a separate process.
>>>>
>>>> -------------
>>>>
>>>> The application is setup under IIS as a 2.0 application. What would
>>>> make IIS try to serve it as a 1.1 app? How do I fix this?
>>