J
Juan Posadas
All,
I deployed my website that requires V1.1 in the
production server. I installed the framework v1.1 with
the dotnetfx.exe /c:"install /noaspupgrade" and
everything went fine.
Then, I installed my app via and installation pkg.
without a proble,
Then, I ran the following command to tell IIS to run my
app with V1.1
aspnet_regiis.exe w3svc\1\1root\Myapp
which did the job.
However, when I try to run it it gives me a blank page:
Page caanot be displayed
.....
....
TTP Error 500.
Q1. How can I make visible the actual error rather than
the default error page?
Q2. Should be 2 separate ASP.Net processes running for
the 2 diiferent versions: aspnet_wp.exe?
Q3. Do I need to configure something on the IIS?
I remembered that when I installed V1.0 long time ago, I
had to start the aspnet_wp.exe manually for the fist
time.
PS: I deployed the same app in two other testing-servers
and they worked fine. However, they only had V1.1
installed.
I deployed my website that requires V1.1 in the
production server. I installed the framework v1.1 with
the dotnetfx.exe /c:"install /noaspupgrade" and
everything went fine.
Then, I installed my app via and installation pkg.
without a proble,
Then, I ran the following command to tell IIS to run my
app with V1.1
aspnet_regiis.exe w3svc\1\1root\Myapp
which did the job.
However, when I try to run it it gives me a blank page:
Page caanot be displayed
.....
....
TTP Error 500.
Q1. How can I make visible the actual error rather than
the default error page?
Q2. Should be 2 separate ASP.Net processes running for
the 2 diiferent versions: aspnet_wp.exe?
Q3. Do I need to configure something on the IIS?
I remembered that when I installed V1.0 long time ago, I
had to start the aspnet_wp.exe manually for the fist
time.
PS: I deployed the same app in two other testing-servers
and they worked fine. However, they only had V1.1
installed.