web.config host error!! PLEASE help!

  • Thread starter Thread starter n3crius
  • Start date Start date
N

n3crius

hi,

i just got a web host with asp.net , seemed really cool. aspx with the
c# or vb IN the actual main page run fine, but when i use codebehind and
make another source file ( a .cs) to go with the aspx (as you would
realistically) I get this :

Details: To enable the details of this specific error message to be
viewable on remote machines, please create a <customErrors> tag within a
"web.config" configuration file located in the root directory of the
current web application. This <customErrors> tag should then have its
"mode" attribute set to "Off".

----- every damn time, and ive done what it says about the web.config,
ive tried everything. i get nothing back from the tech support at the
minute so im totally in the dark :(. any suggestions please?

thanks
 
What does your customErrors tag look like? Can you post it?

Matt Hawley, MCAD .NET http://www.eworldui.net hi,

i just got a web host with asp.net , seemed really cool. aspx with the
c# or vb IN the actual main page run fine, but when i use codebehind and
make another source file ( a .cs) to go with the aspx (as you would
realistically) I get this :

Details: To enable the details of this specific error message to be
viewable on remote machines, please create a <customErrors> tag within a
"web.config" configuration file located in the root directory of the
current web application. This <customErrors> tag should then have its
"mode" attribute set to "Off".

----- every damn time, and ive done what it says about the web.config,
ive tried everything. i get nothing back from the tech support at the
minute so im totally in the dark :(. any suggestions please?

thanks
 
Mmm thought I'd already put about this. I'll explain, basically I'm
tried all that. I've tried every thing in the web config, makes no
difference
 
I understand that, however there seems to be a problem with your web.config file, and without being able to see it, I can't help.

Matt Hawley, MCAD .NET http://www.eworldui.net Mmm thought I'd already put about this. I'll explain, basically I'm
tried all that. I've tried every thing in the web config, makes no
difference
 
I've tried a load of configs, I get the same error. If you have a
config you want me to try I'll do it, but I've tried the one .net studio
gneerates, Ive altered the custom errors to hell and back, and I've
tried suggestions from some others, I get the same error, its mental
 
dude you were right

i put the config in the root etc and now it work, but i have to put a
modded config in the actual application directory, but now i get this :

-----------------

Parser Error
Description: An error occurred during the parsing of a resource required
to service this request. Please review the following specific parse
error details and modify your source file appropriately.

Parser Error Message: Could not load type 'WebApplication1.WebForm1'.

Source Error:


Line 1: <%@ Page Language="vb" AutoEventWireup="false"
Codebehind="WebForm1.aspx.vb" Inherits="WebApplication1.WebForm1"%>
Line 2: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
Line 3: <html>


Source File:
D:\Webspace\necrius.net\wwwroot\WebApplication1\WebForm1.aspx Line: 1


any ideas ????
 
Looks like your codebehind .dll file with the WebForm1 code in it is
missing. It should be in the bin directory, under the web application
directory (where you have web.config)

Pete Beech
 
Also, you could just put the source file up there (WebForm1.aspx.vb) and
change 'Codebehind' to 'Src'. This will get the server to compile the
codebehind file for you, obviously with a slight hit in performance when
initially used.

I believe its generally recommended to deploy the dll though, and not use
the Src attribute.

Pete
 
Yeah - when you're using code-behind pages, you need to pre-compile your application. I think...if you had src="WebForm1.aspx.vb" to the page directive, then it should JIT compile on the server though. That is just speculation since I never do it, but its worth a shot.

Matt Hawley, MCAD .NET http://www.eworldui.net dude you were right

i put the config in the root etc and now it work, but i have to put a
modded config in the actual application directory, but now i get this :

-----------------

Parser Error
Description: An error occurred during the parsing of a resource required
to service this request. Please review the following specific parse
error details and modify your source file appropriately.

Parser Error Message: Could not load type 'WebApplication1.WebForm1'.

Source Error:


Line 1: <%@ Page Language="vb" AutoEventWireup="false"
Codebehind="WebForm1.aspx.vb" Inherits="WebApplication1.WebForm1"%>
Line 2: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
Line 3: <html>


Source File:
D:\Webspace\necrius.net\wwwroot\WebApplication1\WebForm1.aspx Line: 1


any ideas ????
 
Ok guys, thanks very much for your great responses you've helped me
lots. Unfortunately, I think the DLL is in there? I'm still getting
this message however? I have tried compiling, then loading up, theres a
file such as 'WebApplication#.dll' in the bin folder depending on the
applciation (#).
 
I'm just guessing, but try putting the dll into the bin directory that is
immediately under your root directory (i.e. /bin, not /WebApplication1/bin.)
If this works, it would imply that your subdirectory WebApplication1 hasn't
been set up as an application in IIS. (i.e. you need to have someone run
IIS, go to the properties for that directory, and press the Create
Application button)

It might be possible to do that remotely - if it has FrontPage extensions on
the server, then I often use the ability from VS.NET to create a project
directly on a server - that sets up the application in IIS on that
directory, then I can delete the project files and just upload my
application files. Theres probably much better ways of doing it. Otherwise
you could get Tech support for your hosting provider to create an
application in the WebApplication1 directory (and any other directories you
want).

Each web application that you create like this will have its own bin
directory which it will use (rather than using the root one) and it will run
separately from the other web applications you have on the server.

Anyway, try what I suggested at the top to see if that is the problem..

Cheers,
Pete

n3crius said:
Ok guys, thanks very much for your great responses you've helped me
lots. Unfortunately, I think the DLL is in there? I'm still getting
this message however? I have tried compiling, then loading up, theres a
file such as 'WebApplication#.dll' in the bin folder depending on the
applciation (#).
Click to expand...
application. I think...if you had src="WebForm1.aspx.vb" to the page
directive, then it should JIT compile on the server though. That is just
speculation since I never do it, but its worth a shot.
 
Hey Pete. I have frontpage extensions enabled and am running VS.NET
2003, how can i remote, and create a project on the host server? this
sounds cool
 
When you create an ASP.NET project, select a URL on your webserver to create
the project under, e.g. http://www.necrius.net/WebApplication1 (or try a new
one just in case theres a problem because this already exists)

There are 2 modes of Web Server Connection access, file share and Front
Page - if it tries to create the project using the default access mode and
it fails, you will get a prompt to try using the other method. You can see
or change the default mode under Tools->Options, Projects->Web Settings.

If it can successfully connect, the project is then created on the
webserver - I think the Solution file stays on the local machine, and the
rest is on the server, including proj files, source files, etc. You can then
develop your application directly on the server - its probably mainly useful
when you don't have IIS installed locally.

As I say, I use it to just create the application directory properly on the
server, so it has its own bin, and so it is separate from other applications
in my webspace. There may be a far easier way of doing this though, I've
never looked into it.

BTW, did you try moving your dll to the bin folder under root?

Cheers,
Pete Beech
 
I had this same problem but after fiddling around I discovered that my
application was looking for it's dll in a bin subfolder rather than in
the root web bin folder. So maybe in your case it is just looking in
the wrong place for the dll as suggested below.

My solution was to go into IIS and change the folder e.g.
"/webapplication1" to make it an ordinary folder and not an
application. Then my code worked correctly finding the /bin in the
root web folder. Somewhere in the process I must have created an
application for that folder.

Hope that helps
Jonathan
 
Back
Top