ASP.net configuration problem - new user

[James Warren]

I just installed VB.net 2003, upgrading from VB6. I tried to open a new
ASP.net Web Application and immediately got an error stating that my Web
Server isn't running ASP.net version 1.1. I tried running aspnet_regiis /i
and all the dotnetfix "framework repair" suggestions the Help link sent me
to, but no luck. I suspect I am not the first guy with this problem. I am
running IIS on a Windows XP system. Can anybody direct me to a site with
better directions then what I have been able to find thus far, or can you
tell me what the solution is (if it is as common as I suspect)?

Thanks in advance, and my appologies if this is an old problem that you guys
are tired of hearing about.

Jim

[James Warren]

Well, the problem is resolved. After about an hour with Microsoft Tech
Support (and by the way they were great to work with), we determined that my
static IP address being selected in the default website properties instead
of "All Unassigned" was the problem. We switched it, and all works fine. I
have no idea what the reason is, but I guess it doesn't really matter.

Thanks again for all the input!

Regards, Jim
"Ken Cox [Microsoft MVP]" <BA************ @sympatico.ca> wrote in message
news:em******** ******@tk2msftn gp13.phx.gbl...

Hi Terry,

According to this page, under phone support, you get "2 incidents and
unlimited installation support at no charge."

http://support.microsoft.com/default...s;prodoffer62a

You can check if you have an OEM version here:

http://support.microsoft.com/default.aspx?pr=notsureoem

Ken

"One Handed Man ( OHM - Terry Burns )" <news.microsoft .com> wrote in message news:%2******** *******@tk2msft ngp13.phx.gbl.. .

Does it ?, I was not aware of that I bought my professional under a bulk
licence deal last June, no one told me I had any incidents to use, how
many
do u get ?

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .

Time flies when you don't know what you're doing

"Ken Cox [Microsoft MVP]" <BA************ @sympatico.ca> wrote in message
news:uL******** ******@TK2MSFTN GP09.phx.gbl...

Hi Jim,

At this point, I would phone Microsoft Support and get it settled in real time.

They might have some tool that would diagnose what is going wrong. Don't forget that your VS.NET software comes with free support incidents and

this

sounds like a good time to use one.

Ken

"James Warren" <wa************ @att.net> wrote in message
news:wf******** ************@bg tnsc04-news.ops.worldn et.att.net...
> Ken, I built the aspx file according to the KB article and saved it in > the
> inetpub\wwwroot directory, which is the default for my server.
> Unfortunately, no change. I still get the same message from Visual

Studio

>
> What I didn't find was a web.config file on the server anywhere. I
> checked
> the development server on my laptop and there is one there, but it

appears

> to have been built by VB.net 2003 as part of a test web application, at > least based on the folder in which it resides.
>
> Thanks agan for the help
> Jim

[Ken Cox [Microsoft MVP]]

Wow. That was obscure!

Glad to hear you got going.
"James Warren" <wa************ @att.net> wrote in message
news:E_******** ***********@bgt nsc05-news.ops.worldn et.att.net...

Well, the problem is resolved. After about an hour with Microsoft Tech
Support (and by the way they were great to work with), we determined that
my
static IP address being selected in the default website properties instead
of "All Unassigned" was the problem. We switched it, and all works fine.
I
have no idea what the reason is, but I guess it doesn't really matter.

Thanks again for all the input!