PCFormat Forum Archive

Posted: **03 Aug 2010, 00:01**

Hi there.

So I have a web site and I use mweb to host the site. Now I have been back and forth communicating with them to the point I want to pull my hair out.

If I point my browser to a non existent page I get the normal ugly 404 page informing me to use IIS to set custom pages.

This is where my headache starts.

Mweb said : place a web.config file in your root with the error handling in it and then place your 404.aspx file where ever your config file points.

Ok so I downloaded premade error pages from asp.net uploaded everything and it doesn't work.

If I point my browser to the 404.aspx file I get a 404 error file not found.

So I gather I need to use iis to set up the custom error pages.

HOW? I have installed everything and I have tried the following:

1) connect to server using server address : www5.shared.mwebhosting.net (tried ports 21, 80, 8080) username :***** Password: *****

I get a connection error (On port 21 the error is immediate that it could not start the underlying communication)

2) I have tried the same as above but trying to connect to website I get same problem.

Mweb answers my email:

We're not web designers maybe you should consider hiring the services of a professional designer.

Well that's bloody nice tech support if you ask me. I have my site designed and running I just want to know how to get IIS to connect.

Can anyone out there provide me some advice?

Posted: **03 Aug 2010, 11:41**

Bob-Skanking wrote:tried ports 21, 80, 8080

21 is the FTP control port and will bounce any traffic which isn't FTP... 8080 is standard for proxy connections, so you're trying to connect to a proxy.....

admit it...you're taking wild stabs in the dark here...

Bob-Skanking wrote:Well that's bloody nice tech support if you ask me.

i see nothing wrong with their response. it was helpful to the extent that you're not looking for help, you're looking for someone to do the work for free...

hire someone who knows what they're doing... this is why they spent all that cheese at night school...

alternatively, go spend some cheese at night school.... :/

Posted: **03 Aug 2010, 12:28**

rustypup wrote:
Bob-Skanking wrote:tried ports 21, 80, 8080
21 is the FTP control port and will bounce any traffic which isn't FTP... 8080 is standard for proxy connections, so you're trying to connect to a proxy.....

admit it...you're taking wild stabs in the dark here...

Bob-Skanking wrote:Well that's bloody nice tech support if you ask me.
i see nothing wrong with their response. it was helpful to the extent that you're not looking for help, you're looking for someone to do the work for free...

hire someone who knows what they're doing... this is why they spent all that cheese at night school...

alternatively, go spend some cheese at night school.... :/

Actually no i am not taking stabs at the dark! I just attempted those other ports to see. IIS will not connect to www5.shared.mwebhosting.net PERIOD!

I am not asking them to design anything but rather just to inform me how to connect using iis as I have only used linux servers. So in response to spending cheese, I would say I have seeing as in all my years I spent well over the average on courses including A+, N+, ICDL, HTML, and blah blah blah. but i am not here to give a quote of my qualifications nor provide a CV.

In future if you can't provide at least what one would consider to be useful info why not just read posts and move on instead of trolling!

Posted: **03 Aug 2010, 12:36**

Yes rusty! Shame on you!

Get out a spoon and feed the dragon the solution before he flames...

Posted: **03 Aug 2010, 12:37**

That's what a totally useless troll answer looks like...

Posted: **03 Aug 2010, 12:40**

LOL bt at least provides entertainment

Posted: **03 Aug 2010, 13:10**

Bob-Skanking wrote:why not just read posts and move on instead of trolling!

what?... read... posts?.. on the internets?!

madness...

imperfect application of the solution is no reason to throw toys..

Posted: **03 Aug 2010, 13:36**

and he was named the most knowledgable member 2009!!! seems like he aint any more...

Posted: **03 Aug 2010, 14:02**

KatrynKat wrote:and he was named the most knowledgable member 2009!!! seems like he aint any more...

I know you're not blonde so I'm assuming you're just misinformed...

He still is. And helpfull as well. But not into spoonfeeding...

Posted: **03 Aug 2010, 14:05**

Spoonfeeding? um..... correct me if I am wrong but this thread is about providing help to users when it comes to we design is it not? I am not asking to be spoon fed I am asking just for a it of help getting iis to work.

Spoonfeeding would be me asking to you to log onto my system and set it up for me Hmmmmph!

Posted: **03 Aug 2010, 14:06**

PM me your login detail. I'm sure I'll be able to do something with it...

Posted: **03 Aug 2010, 14:18**

KatrynKat wrote:and he was named the most knowledgable member 2009!!!

you've met the competition... how is this a surprise?

Mweb said : place a web.config file in your root with the error handling in it and then place your 404.aspx file where ever your config file points.

see this step here... this one... there is no reference in the OP as to what happened with this one.. .only lots of guff about leaping ahead and grabbing/uploading a custom 404.... whereas the preceding step is the actual solution...

@doo_much: jamin_za may have some suitable 404 pages....

Posted: **03 Aug 2010, 14:20**

Looking at the web.config file of the project I'm working on, I find the following in the file:

Code: Select all

<!--
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        -->

That is basically what you want. Now this isn't spoon feeding, but it should point you in the right direction.

(Sometimes I think rusty can really get anal on a guy)

Posted: **03 Aug 2010, 14:23**

rustypup wrote: jamin_za may have some suitable 404 pages....

The ones he did for the .xxx domain?

Posted: **03 Aug 2010, 14:24**

SykomantiS wrote: (Sometimes I think rusty can really get anal on a guy)

rusty is a sexual deviant?

No wonder he gets along with jamin!

Posted: **03 Aug 2010, 14:25**

Sometimes I think rusty can really get anal on a guy

...Nah, a joke would be too easy...

Edit:

Nevermind.

Posted: **03 Aug 2010, 14:42**

SykomantiS wrote:(Sometimes I think rusty can really get anal on a guy)

oh, my offended sensibilities...

Well that's bloody nice tech support if you ask me.

if that quote doesn't scream "whip me like i'm catholic", nothing will... they gave him the answer from the outset... he didn't like the answer so now it's here... in the hopes that someone who makes their living doing this will perform a little pro bono for the abuse... :/

unless i'm thoroughly mistaken, in which case i would proffer profuse apologies and a half hour of bug-riddled code...

Posted: **03 Aug 2010, 14:50**

rustypup wrote:... I would proffer ... bug-riddled code...

Pahhh, empty promises - you do that anyway?

Posted: **03 Aug 2010, 15:09**

You have got me wrong. I have setup everything as needed. here is my web.config file

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    
  <system.web>

    <httpModules>
        <add type="AspNetResources.CustomErrors4.MyErrorModule,CustomErrors4" name="MyErrorModule" />
    </httpModules>

    <compilation 
         defaultLanguage="c#"
         debug="true"
    />

    
    <customErrors mode="On" defaultRedirect="~/errors/GeneralError.aspx">
        <error statusCode="404" redirect="~/errors/PageNotFound.aspx" />
    </customErrors>

 
    <globalization 
            requestEncoding="utf-8" 
            responseEncoding="utf-8" 
   />
   
 </system.web>

</configuration>

I have my error pages uploded to root/errors

now if I goto my page http://xxxxx.xx.xx/xx causing a 404 error i still get the standard 404 error page telling me to configure it with iis.

this is what I am asking help for.... not how to script the pages that I have done already.

If I upload a aspx file to my server and point my browser at it I also get a 404 error even though I know the file is there.

hope that clears up the spoonfeeding thing
no matter what i try IIS will not connect to the mweb server and there is where i need help and what exactly to do once i is connected to get aspx working on the site like it is supposed to.

Posted: **03 Aug 2010, 21:34**

Which IIS version? IIS only went big on web.config files from the Server 2008 editions onwards, although the .NET framework has been using them since long before. If it's a Windows Server 2003 box and not a .NET web application, web.config files won't help you; you'll need to configure IIS itself (via remote desktop access or something similar).

Posted: **04 Aug 2010, 14:28**

there's always global.asax....

IIS on 2008 is.... unpleasant... it wasn't exactly cuddly before, but... yurgh...

<edit>
@Bob-Skanking: if my diligent research is accurate, you have yet to spam this thread... this behavior cannot be tolerated and will be met with slander... like being accused of wearing those fury boot abominations... with tassels....

Posted: **04 Aug 2010, 21:46**

Ron2K wrote:Which IIS version? IIS only went big on web.config files from the Server 2008 editions onwards, although the .NET framework has been using them since long before. If it's a Windows Server 2003 box and not a .NET web application, web.config files won't help you; you'll need to configure IIS itself (via remote desktop access or something similar).

This is just it! Mweb said put a web.config file there. I did that. doesn't do twak! IIS won't connect to the site no matter what i do. so i am buggered!

PCFormat Forum Archive

Custom Error pages using asp

Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp

Re: Custom Error pages using asp