Help with stubborn web.config

  • Thread starter Thread starter vickeybird
  • Start date Start date
V

vickeybird

Hi,
Im trying to implement flexwiki, an ASP.net based open source wiki.
I tried compliing and deploying the solution on my local machine and
it seems to be working fine.
However on remote testing server it just will not work.
When i try to access i get the following error :
Server Error in '/' Application.

Then im being told to change the value of customErrors mode to "Off"
in the web.config file.
* Changing the mode to 'Off', I'm still unable to view any clue about
what is going wrong as i get the same error.

* I tried to switch on application Tracing. But even on trying to
access trace.axd, I get the same error.

* I tried to view the web.config file in web browser, it seems well
formed.

If only i see at least one sentance of error, Im sure I can do
something about it.

Its really driving me up the wall and believe me i had tough time
smashing my machine out of frustration.

Is there any kind soul out there???
 
When you "deployed" it, was an actual web application created?

(Check in IIS Admin)
 
Hey John,

That is the problem. I have deployed on a testing server via a mapped
drive and i do not have permission to access IIS personally.

It is deployed in a subdirectory of some other application.
If the application was not created then it would not try to parse
web.config isn't it?


This was meant to be a surprise (pleasent I hope) for my clients and i
do not wish to tell them about it till i have it working in test setup.
Wiki seems the correct solution but i think it may not be encouraged if
i just talk without any working sample :)

Thanks a lot for taking time. I look forward to your comments.
 
vickeybird said:
Hey John,

That is the problem. I have deployed on a testing server via a mapped
drive and i do not have permission to access IIS personally.
Click to expand...

Did you do that via Visual Studio (Copy Project)?
It is deployed in a subdirectory of some other application.
If the application was not created then it would not try to parse
web.config isn't it?
Click to expand...

I think there is only one web.config per application.

So you would be running your application but using the web.config in the
main directory.

Even if you copied the files to a top level directory, an ASP.NET
project would still need it's own "application" name (you understand how
an Application is configured in IIS, right?)
This was meant to be a surprise (pleasent I hope) for my clients and i
do not wish to tell them about it till i have it working in test setup.
Click to expand...

You might want to try deploying it to a machine that you do have admin
access to -- just to try and "get it right" and then tackle the real
target...
 
Hi,
You were right, the directory was not set up as an IIS application. I
user a folder which was set to be one and it was working alright.
Thanks a lot for your advice and involvement.
 
Back
Top