Quine
Posts: 33
|
| Posted: 03/26/2012, 8:40 AM |
|
Hi,
Using the target
ASP.NET C# - InMotion Framework,
, I'm getting the configuration error below, when publishing the project. I don't get the errors, when
1) Using other web development tools to generate projects,
and
2) When using ccs5 to publish to a remote server.
Here's the error:
Warning:Configuration error
Filename: redirection.config
Line Number: 0
Description: Cannot read configuration file due to insufficient permissions
.
Warning:Error occurred when creating Virtual Directory in IIS: IIS is not running, or unable to find the Default Web Site in IIS.
Publishing to "C:\Inetpub\wwwroot\HelloWorld02"
Publish Project - 0 critical error(s), 0 error(s), 2 warning(s)
|
 |
 |
Quine
Posts: 33
|
| Posted: 03/26/2012, 8:50 AM |
|
Here's a further error, when using the browser to point to the folder:
Requested URL
http://localhost:80/HelloWorld02
Physical Path
C:\inetpub\wwwroot\HelloWorld02
...
...
Error
There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined
, but this was started from scratch, after trying to publish a real app, so there shouldn't be anything wrong with web.config. Anyway, there's only one scriptResourceHandler, in the <configSections> section.
|
|
|
|
FrankR
Posts: 154
|
| Posted: 03/29/2012, 12:10 PM |
|
I'll bet you are using IIS 7+, yes?
I went through this, too. Today as a matter of fact. :)
It has to do with the changes to IIS in 7 and up. There's not a duplicate in
your web.config, but the line is a duplicate of what is already established in
the IIS applicationhost file. One by one, remove the lines in your web.config
that are reported as duplicate, and you'll succeed.
_________________
FR |
|
|
|
Quine
Posts: 33
|
| Posted: 03/30/2012, 2:59 PM |
|
Yes, same one, IIS7. Ok, good, that's worth a try, thanks Frank.
Quote FrankR:
I'll bet you are using IIS 7+, yes?
I went through this, too. Today as a matter of fact. :)
It has to do with the changes to IIS in 7 and up. There's not a duplicate in
your web.config, but the line is a duplicate of what is already established in
the IIS applicationhost file. One by one, remove the lines in your web.config
that are reported as duplicate, and you'll succeed.
|
|
|
|
|
