Russk2t
asked on
IIS7 Invalid Application Path
Trying to get a web service working under IIS7 on a new Windows 7 development machine.
No matter what I do, if I select pass through authentication and then test connection, i get
"Invalid application path" error. If I connect as my user name and password then the test is ok,
but either way cannot connect from IE. I get a "The specified module could not be found" error
in IE, but when I look in procmon it seems that the real problem is that it cannot find web.config.
W3WP tries to open:
C:\inetpub\wwwroot\Payroll
See what is happening? It thinks that web.config is inside a folder named the same as my asmx
file for the web service!!! I cannot find a way to fix this.
I am installing the web app by creating a web setup project in VS2008, and then using the Install
feature from within VS2008.
What is worse is that this behaviour was not the problem when I started troubleshooting.
At that time this configuration error did not exist - instead W3WP was unable to find
MFC90D.DLL (yes this is the debug version for testing). I was using a converted setup
program that was originally created in VS2005. But when I deleted that project and created
a new setup project in VS2008, that is when this new behaviour started.
HELP PLEASE!!!
Russ
No matter what I do, if I select pass through authentication and then test connection, i get
"Invalid application path" error. If I connect as my user name and password then the test is ok,
but either way cannot connect from IE. I get a "The specified module could not be found" error
in IE, but when I look in procmon it seems that the real problem is that it cannot find web.config.
W3WP tries to open:
C:\inetpub\wwwroot\Payroll
See what is happening? It thinks that web.config is inside a folder named the same as my asmx
file for the web service!!! I cannot find a way to fix this.
I am installing the web app by creating a web setup project in VS2008, and then using the Install
feature from within VS2008.
What is worse is that this behaviour was not the problem when I started troubleshooting.
At that time this configuration error did not exist - instead W3WP was unable to find
MFC90D.DLL (yes this is the debug version for testing). I was using a converted setup
program that was originally created in VS2005. But when I deleted that project and created
a new setup project in VS2008, that is when this new behaviour started.
HELP PLEASE!!!
Russ
Last Comment
ASKER
Angel. I have resisted subscribing to Expert's Exchange for several years, thinking a for pay service was not necessary. But I could not find any information on the web to help me this time. So I subscribed and posted my question. I am quite dissappointed in the response. Not only did I get no responses, even after I posted that I had got it working but still had specific questions about why certain things happened - no one responded.
I have to assume that knowledgeable people are not reading the questions here and so I will not be renewing my membership in experts exchange.
Regards, Russ
I have to assume that knowledgeable people are not reading the questions here and so I will not be renewing my membership in experts exchange.
Regards, Russ
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Networking
Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.
102K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
Once I got global.asax installed, I was back to my original problem of not being able to find mfc90d.dll. I have no idea why w3wp.exe will not search the windows SXS folders for that file, but it doesn't. And this has been a problem since at lest IIS version 5. I used the same solution as I used in the previous versions - manually putting mfc90d.dll in the system32 folder where it can be found.
So, I answered my own question - except that I'd really like not to have to deal with mfci90d the way I do.
Thanks anyway, Russ