Apologies, when I had made the post, it said there was an error and the post
was not submitted. I waited a bit and checked to see if the post was made,
and when I didn't see it, I tried it again, pasting in the info.
It gave me the error once more before I waited a bit longer and it finally
worked.
--
I'll try the suggestions you gave me. Thanks for your help
--
"David Wang [Msft]" wrote:
> FYI: Please do not multi-post in newsgroups
>
> This sounds like a misconfiguration of the server by ServerBeach.com.
> Default Windows Server 2003 installations come with all the setting correct
> and working.
>
> In any case, the default values are probably inherited from the global
> ScriptMaps node, which you need to change.
>
> In the IIS Manager UI, right click properties on the "Web Sites" node.
> Select the "Home Directory" tab and click on the "Configuration" button. In
> the "Application Configuration" dialog, you need to fix all the paths in
> there. This is the default values being used by the new websites. Since
> you manually changed the per-website changes, they will no longer inherit
> from this global change -- This may cause problems for you in the future if
> you have SW that rely on property inheritance that no longer happens. You
> can fix it, but the choice is all up to you.
>
> Windows Server 2003 installations come with the right values configured (for
> example, my clean installation looks completely correct), I can only assume
> that the ServerBeach.com image for your server had some bugs in it that
> causes this -- either their tool uses the environment variable from the
> wrong machine, or they have a hard-coded value in their metabase update or
> OS install directory -- all of which are bugs in ServerBeach.com
> provisioning.
>
> If you see more problems like this, I suggest you contact ServerBeach.com to
> get a working image -- because if they have a few bugs in key locations, it
> can totally screw your system up down the road... like it is already doing
> right now.
>
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Chris" <Chris.RemoveThis@discussions.microsoft.com> wrote in message
> news:ADFF3525-0324-4F93-9258-1CA03FD8958D@microsoft.com...
> I ordered a server from ServerBeach.com which comes with an installation of
> Windows 2003 Standard.
>
> Everything was configured properly except for one thing: the default paths
> for ISAPI extensions, such as the preconfigured ASP/ASP.NET
>
> The server automatically assigns the path to
> C:\Windows\system32\inetsrv\ASP.DLL
>
> The problem is that this isn't where the file is. C:\Windows doesn't exist
> at all, Windows is located at C:\WINNT
>
> Every time I make a new domain on IIS, it gets the Windows directory. I have
> to manually correct it each time I create a new domain.
>
> How can I globally fix this problem to insure it doesn't happen again
> without reinstalling the OS?
>
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Correcting invalid default-ISAPI file paths in IIS 
FAQ
Profile
Private Messages
Log in
