stumped, server.execute issue on asp page

[Chris]

I have yet to understand or get a response on the issue I'm having.
I'm taking an asp web application and migrating it from Windows 2K to 2003.
I have the new website location (2003) settings correct, i.e. enable parent
paths, etc. and
still get these errors:

Server object error 'ASP 0228 : 80004005'
Server.Execute Error
/ASP_Procedures/PageHeader.asp, line 60
The call to Server.Execute failed while loading the page.

code:
Server.Execute("/ASP_Procedures/PageHeader.asp")

The path is correct, I've checked the executed page (i.e. rights, code, etc.)

The site and directory has execute rights, etc.
Why? Can Windows 2003 handle this use server.execute?

Any ideas, this ap runs fine on the Windows 2000 server

[Bob Barrows [MVP]]

Chris wrote:

I have yet to understand or get a response on the issue I'm having.
I'm taking an asp web application and migrating it from Windows 2K to
2003. I have the new website location (2003) settings correct, i.e.
enable parent paths, etc. and
still get these errors:

Server object error 'ASP 0228 : 80004005'
Server.Execute Error
/ASP_Procedures/PageHeader.asp, line 60
The call to Server.Execute failed while loading the page.

code:
Server.Execute("/ASP_Procedures/PageHeader.asp")

The path is correct, I've checked the executed page (i.e. rights,
code, etc.)

The site and directory has execute rights, etc.
Why? Can Windows 2003 handle this use server.execute?

Any ideas, this ap runs fine on the Windows 2000 server

Ah, I remember this.

Have you exhausted Google and the KB?

http://www.google.com/search?sourcei...ecute+Error%22

One of the links in the search resuts indicates that you can get this error
not only when the path to the page being executed is incorrect, but also
when the page being executed raises an error.

If nothing in these search results helps, you may be the victim of a bug in
IIS6. You should take a gamble and call MS Product Support to find out. If
it is a bug, you won't be charged for the call. If it is not a bug, at least
you will get somebody to take a first-hand look at your problem, which may
make the cost worth it.

Hopefully, if you get a resolution, you will share it with us.

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Chris]

Thanx for your reply. Yes, I have spent a couple days researching the web and
postings for ideas, no luck. I've contacted MS, today, and to my
dis-satisifaction spent 20 minutes on hold to final be transferred to what I
believe was India. Two very nice, but extrememly limited support personal
specialists, could not help me very much as they were supposed to be
asp/asp.net developers but had no idea of what server.transfer was, etc. I
finally gave up.

I'll try your link. The app runs fine on Windows 2000 but once moved it
craps out. So I'm stumped. The obvoius issue would be allow parent paths.

thanx again, let me know if you run accross anything else.

"Bob Barrows [MVP]" wrote:

Chris wrote:

I have yet to understand or get a response on the issue I'm having.
I'm taking an asp web application and migrating it from Windows 2K to
2003. I have the new website location (2003) settings correct, i.e.
enable parent paths, etc. and
still get these errors:

Server object error 'ASP 0228 : 80004005'
Server.Execute Error
/ASP_Procedures/PageHeader.asp, line 60
The call to Server.Execute failed while loading the page.

code:
Server.Execute("/ASP_Procedures/PageHeader.asp")

The path is correct, I've checked the executed page (i.e. rights,
code, etc.)

The site and directory has execute rights, etc.
Why? Can Windows 2003 handle this use server.execute?

Any ideas, this ap runs fine on the Windows 2000 server

Ah, I remember this.

Have you exhausted Google and the KB?

http://www.google.com/search?sourcei...ecute+Error%22

One of the links in the search resuts indicates that you can get this error
not only when the path to the page being executed is incorrect, but also
when the page being executed raises an error.

If nothing in these search results helps, you may be the victim of a bug in
IIS6. You should take a gamble and call MS Product Support to find out. If
it is a bug, you won't be charged for the call. If it is not a bug, at least
you will get somebody to take a first-hand look at your problem, which may
make the cost worth it.

Hopefully, if you get a resolution, you will share it with us.

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Chris]

Ok, I believe I've found the issue. Apparently this (server.execute) doesn't
work when the website (on IIS) is set up as a virtual directory under Default
websites. It must be a "stand-alone" website with its own IP (if other
website are running on that machine).
Learn something new everyday. Didn't see anything on that particular
requirement in any articles????
This kind of makes snese, but then again why can't it find the executed file
when set as a virtual directory?

Thanx.
"Bob Barrows [MVP]" wrote:

Chris wrote:

I have yet to understand or get a response on the issue I'm having.
I'm taking an asp web application and migrating it from Windows 2K to
2003. I have the new website location (2003) settings correct, i.e.
enable parent paths, etc. and
still get these errors:

Server object error 'ASP 0228 : 80004005'
Server.Execute Error
/ASP_Procedures/PageHeader.asp, line 60
The call to Server.Execute failed while loading the page.

code:
Server.Execute("/ASP_Procedures/PageHeader.asp")

The path is correct, I've checked the executed page (i.e. rights,
code, etc.)

The site and directory has execute rights, etc.
Why? Can Windows 2003 handle this use server.execute?

Any ideas, this ap runs fine on the Windows 2000 server

Ah, I remember this.

Have you exhausted Google and the KB?

http://www.google.com/search?sourcei...ecute+Error%22

One of the links in the search resuts indicates that you can get this error
not only when the path to the page being executed is incorrect, but also
when the page being executed raises an error.

If nothing in these search results helps, you may be the victim of a bug in
IIS6. You should take a gamble and call MS Product Support to find out. If
it is a bug, you won't be charged for the call. If it is not a bug, at least
you will get somebody to take a first-hand look at your problem, which may
make the cost worth it.

Hopefully, if you get a resolution, you will share it with us.

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.