I can't seem to make my custom error pages work? When I do set the path (relative to the root directory) under HELM (control panel), two things happen.
1) the error pages only work for "Not found" error and even then only for .asp pages.
2) FrontPage won't upload/publish my new or updated files. Setting the error pages path back to default makes FrontPage work again.
:angry: & :bawling:

I read something about having to create a .httpaccess file but that might mess around with FrontPage settings that might already be there.
Any ideas?
:confused:

FrontPage won't upload/publish my new or updated files.
FrontPage sucks. I'm surprised you got far enough to actually publish something.
I read something about having to create a .httpaccess file but that might mess around with FrontPage settings that might already be there.
Any ideas?
I think you're actually looking to edit your .htaccess file, unless .httpaccess is some filetype found on Windows servers. I can't give you any info on how to send people to a custom page on a Windows server (it's easy on Linux), but I would think your host would have ample documentation online or would be able to help you via helpdesk/ticket or email!

.htaccess is an apache thing, and most likely he is using iis if it's a windows server.

Originally posted by Marble
.htaccess is an apache thing, and most likely he is using iis if it's a windows server.
That's what I was thinking, which is why it sounded strange that OP was referring to this type of file. But having never heard of ".httpaccess," I didn't want to jump to conclusions. I mean, who knows? Maybe Windows servers recently implemented this to give them some industry familiarity, to match .htaccess for Apache :)

Originally posted by Cosmos75
I read something about having to create a .httpaccess file but that might mess around with FrontPage settings that might already be there. Read this at some tutorial page for creating custom error pages... it didn't mention the type of server that the tutorial was meant for.

Was just wondering if this was a common enough problem that it would be a quick answer... guess not!
Originally posted by the_pm
That's what I was thinking, which is why it sounded strange that OP was referring to this type of file. OP? Err.. what is that?
:confused:

a .htaccess file is basically an extension to the httpd.conf file. This allows some flexibility for virtual accounts or in situations where you are on a shared server and you cannot directly edit the httpd.conf file, which is the main config file for Apache servers. You can make changes to the httpd.conf settings for your account and won't affect others. You won't find it on Windows IIS servers. But you will on windows Apache servers.

I haven't messed with IIS in a long time and I have never used HELM so I wish I could be more helpful - lol...

Originally posted by Marble
a .htaccess file is basically an extension to the httpd.conf file. This allows some flexibility for virtual accounts or in situations where you are on a shared server and you cannot directly edit the httpd.conf file, which is the main config file for Apache servers. You can make changes to the httpd.conf settings for your account and won't affect others. You won't find it on Windows IIS servers. But you will on windows Apache servers. Thanks for the info...
Originally posted by Marble
I haven't messed with IIS in a long time and I have never used HELM so I wish I could be more helpful - lol... That's OK. I appreciate anyone who takes time out of their day to answer questions. Bravo to you all!
:)

Originally posted by Cosmos75
I can't seem to make my custom error pages work? When I do set the path (relative to the root directory) under HELM (control panel), two things happen.
1) the error pages only work for "Not found" error and even then only for .asp pages.
2) FrontPage won't upload/publish my new or updated files. Setting the error pages path back to default makes FrontPage work again.
:angry: & :bawling:

I read something about having to create a .httpaccess file but that might mess around with FrontPage settings that might already be there.
Any ideas?
:confused:
Try making it virtual:

/404.html

What happens when you publish? Do you get a server error? Did you try to re-install the FP extensions?