Sorry, I'm not aware of any "ready for use". It is pretty simple to write
one, and ADSUTIL is pretty safe when you don't know how to write one but can
give the right input parameters and know what you are doing (that one
character change in code as I had suggested is needed if you plan to specify
>9 CustomError definitions at a time).
For example, I gave an example that safely edits custom errors for the
default website to only have two defined entries. If you need to define
more, just add more strings at the end of the command.
You DO have backups of your metabase, correct? If you do, this is quite
harmless -- I always backup the metabase at known "good" values, I can screw
it up however I want, and I can just run:
NET STOP /y IISADMIN
COPY /y BackedUpMetabase %SYSTEMROOT%\System32\inetsrv\metabase.bin (or
metabase.xml for IIS6)
NET START W3SVC
And everything is back to normal
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Alex" <ntnewsNO.TakeThisOut@SPAM.hrz3.hrz.tu-darmstadt.de> wrote in message
news:eVQtMPQ8DHA.1504@TK2MSFTNGP12.phx.gbl...
David Wang [Msft] wrote:
> I'd suggest using ADSUTIL.VBS (with one hack -- change its max-number of
> commandline parameters from 9 to something larger), as well as the
> documentation for the HttpErrors property on MSDN.
>
> ADSUTIL.VBS SET W3SVC/1/ROOT/HttpErrors "404,*,URL,/404.htm"
> "404,2,FILE,C:\Errors\404-2.htm"
>
hm... i don't like to kill my metabase with a programming error
...
isn't there anything ready for use?
Alex<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: how can i change error files by script? 
FAQ
Profile
Private Messages
Log in
