ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* Sequential Memory Access and Hyperthreading
* Disk Sizing
* SCSI Disks "broken" under Solaris (X86) VS2005
* How to execute a shell command on guest from host
* Network link is down while loading Windows Updates from host serve
* connect a 98se to a 2003 std server
* Add SCSI Virtual Adapter
* Restore VM"s in VS2005
* Slowdown on SCSI Disk
* Can anybody answer 2 questions for me
* clone a Virtual machine?
* Can access virtualserver via remote client (or in IE either)
* Attaching a Virtual server to host scsi DDS4
* MOM Managment Pack for Virtual Server ??
* Does anybody have a vbscript sample of using the HardDisk.Compact?
* cannot install VS
* Network circuit was disconnected - deployment step
* VMRC Encryption Disabled
* Network Boot Support
* Virtual Network Problems

Add Solution

Admin Website Not Available

Source: microsoft.public.virtualserver
Sent: 01/15/2005
From: "Trey Shaffer" <(email address - cut out)>
Message:

This is a fresh installation of VS "05 on top of a fresh install of Windows
Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
1/12.

Symptom:
Attempting to access the Admin website returns:
You are not authorized to view this page...
HTTP Error 403 - Forbidden: Access is denied.

Symptom is same from VS Server or remote client.

User attempting access is Administrator.
Installation of VS used the Complete Install option with all defaults.

I have seen information about this symptom as an issue with DCOM
permissions, as discussed in, MS KB Article 887491:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491

DCOM Security settings have been changed to allow "Everyone" to Launch and
Access the component.

The web server appears to be OK. A basic Default.htm in the Default Web
root is functional. The IIS log for the Virtual Server subweb contains no
errors. The log entries appear to reflect the successful GET of the
VSWebApp. There are no suspicious entries in the Event Viewer System,
Application or Security logs.

This isn't my first experience with VS, but it is becoming my most
frustrating...

All assistance appreciated.

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Admin Website Not Available

Sent: 01/15/2005
From: "David Wang [Msft]" <(email address - cut out)>
Message:

Can you please post all log entries that access VSWebApp.exe for a request
that returns your 403 error . I want all the status/error codes in the
order of appearance in the log file.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...
This is a fresh installation of VS "05 on top of a fresh install of Windows
Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
1/12.

Symptom:
Attempting to access the Admin website returns:
You are not authorized to view this page...
HTTP Error 403 - Forbidden: Access is denied.

Symptom is same from VS Server or remote client.

User attempting access is Administrator.
Installation of VS used the Complete Install option with all defaults.

I have seen information about this symptom as an issue with DCOM
permissions, as discussed in, MS KB Article 887491:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491

DCOM Security settings have been changed to allow "Everyone" to Launch and
Access the component.

The web server appears to be OK. A basic Default.htm in the Default Web
root is functional. The IIS log for the Virtual Server subweb contains no
errors. The log entries appear to reflect the successful GET of the
VSWebApp. There are no suspicious entries in the Event Viewer System,
Application or Security logs.

This isn't my first experience with VS, but it is becoming my most
frustrating...

All assistance appreciated.

Re: Admin Website Not Available

Sent: 01/17/2005
From: "David Wang [Msft]" <(email address - cut out)>
Message:

Ok, you are getting 403.19 for all of the CGI requests with error 1314 (A
required privilege is not held by the client)

This commonly happens if you changed the Application Pool Identity to a
custom identity but failed to give that identity two documented privileges
necessary to run CGI applications.

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp

I believe IIS installs with application pool identity that just works by
default, and Virtual Server has no reason to change it -- so I have to ask
if you've changed it and did you follow documentation.

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Attached is log file for VS web...

"David Wang [Msft]" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Can you please post all log entries that access VSWebApp.exe for a request
> that returns your 403 error . I want all the status/error codes in the
> order of appearance in the log file.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> This is a fresh installation of VS "05 on top of a fresh install of
> Windows
> Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
> 1/12.
>
> Symptom:
> Attempting to access the Admin website returns:
> You are not authorized to view this page...
> HTTP Error 403 - Forbidden: Access is denied.
>
> Symptom is same from VS Server or remote client.
>
> User attempting access is Administrator.
> Installation of VS used the Complete Install option with all defaults.
>
> I have seen information about this symptom as an issue with DCOM
> permissions, as discussed in, MS KB Article 887491:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>
> DCOM Security settings have been changed to allow "Everyone" to Launch and
> Access the component.
>
> The web server appears to be OK. A basic Default.htm in the Default Web
> root is functional. The IIS log for the Virtual Server subweb contains no
> errors. The log entries appear to reflect the successful GET of the
> VSWebApp. There are no suspicious entries in the Event Viewer System,
> Application or Security logs.
>
> This isn't my first experience with VS, but it is becoming my most
> frustrating...
>
> All assistance appreciated.
>
>
>
>

Re: Admin Website Not Available

Sent: 01/18/2005
From: "Trey Shaffer" <(email address - cut out)>
Message:

No, I made no changes to IIS that I am aware of. As I mentioned, I did make
DCOM permission changes for the VS component.
IIS was installed in the initial build.

The only changes made to IIS, that I am aware of, were the change of the
default web and default ftp roots to D:\InetPub\wwwRoot and ftpRoot,
respectively.

The first installation of VS "05 was directed to D:\Program Files\Virtual
Server.

I un/reinstalled VS 3 or 4 times with different options/locations. The
current install is with straight defaults, on the C: drive.

Since you are, I think, questioning IIS configuration. Would a solution be
to un/reinstall IIS? Or during reinstallation will it pick up the current
configuration?

Update...
Following the information in the second link, below, I changed the
application pool identity. I first went "all the way," and set it to
Configurable\administrator account (and put the account into the IIS WPG
group. After that change, the VS website would not recognize my credentials
for login, ending in a 401 error.

I then changed the app pool identity to Predefined\Local System and the
Administration Website came up. Yea! As you are probably aware, making
this change brings up a "Sky is falling..." security message. Hope I don't
have to stay in this configuration.

For grins, I then set the Identity to Predefined\Local Service. That would
not allow the Admin website to come up. For that matter, it changed an open
browser, looking at the Admin website, into a 403 error page...

That was a bit long-winded. Please let me know how I might tighten security
and retain function...

Thanks

"David Wang [Msft]" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Ok, you are getting 403.19 for all of the CGI requests with error 1314 (A
> required privilege is not held by the client)
>
> This commonly happens if you changed the Application Pool Identity to a
> custom identity but failed to give that identity two documented privileges
> necessary to run CGI applications.
>
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp
>
> I believe IIS installs with application pool identity that just works by
> default, and Virtual Server has no reason to change it -- so I have to ask
> if you've changed it and did you follow documentation.
>
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> Attached is log file for VS web...
>
>
> "David Wang [Msft]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Can you please post all log entries that access VSWebApp.exe for a
>> request
>> that returns your 403 error . I want all the status/error codes in the
>> order of appearance in the log file.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "Trey Shaffer" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> This is a fresh installation of VS "05 on top of a fresh install of
>> Windows
>> Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
>> 1/12.
>>
>> Symptom:
>> Attempting to access the Admin website returns:
>> You are not authorized to view this page...
>> HTTP Error 403 - Forbidden: Access is denied.
>>
>> Symptom is same from VS Server or remote client.
>>
>> User attempting access is Administrator.
>> Installation of VS used the Complete Install option with all defaults.
>>
>> I have seen information about this symptom as an issue with DCOM
>> permissions, as discussed in, MS KB Article 887491:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>>
>> DCOM Security settings have been changed to allow "Everyone" to Launch
>> and
>> Access the component.
>>
>> The web server appears to be OK. A basic Default.htm in the Default Web
>> root is functional. The IIS log for the Virtual Server subweb contains
>> no
>> errors. The log entries appear to reflect the successful GET of the
>> VSWebApp. There are no suspicious entries in the Event Viewer System,
>> Application or Security logs.
>>
>> This isn't my first experience with VS, but it is becoming my most
>> frustrating...
>>
>> All assistance appreciated.
>>
>>
>>
>>
>
>
>
>

Re: Admin Website Not Available

Sent: 01/19/2005
From: "David Wang [Msft]" <(email address - cut out)>
Message:

When you are reporting IIS errors, always report the exact web log
entries -- it has additional details (such as the substatus and Win32 error
codes -- which is all I used for your diagnosis) useful for debugging. The
custom error page that IIS returns is intentionally not useful for
troubleshooting. I have no idea what your new 401 or 403 errors are, so I
cannot comment on your new information.

403.19 indicates that the process identity is lacking the two documented
permissions (and as always, make sure to add the user to IIS_WPG per
documentation).

Additional questions:
1. Are you accessing the website via a local login or via Remote Desktop.
2. Is this on a Domain Controller or not.
3. Is this machine in a domain or not
4. What authentication method(s) are enabled on the VS admin website

Because you said that when you changed it to Administrator and you got 401
(and VS admin website should have Integrated authentication by default), I
suspect your machine is in a domain. The solution to the 401 in that case
is in the second URL I sent in my last reply. Totally unrelated to the
original issue of 403.19.

Otherwise, I cannot think of anything else. Your issue has to do with
process identity and permissions for the CGI since it (VSWebAp.exe --
Virtual Server's CGI that is responsible for generating the admin website
pages) is failing to launch. I would NOT recommend reinstalling IIS since
it won't change those permissions requirements and probably breaks more
things than it fixes. I can only say that Local System is not required -- I
run it just fine with the default Network Service account on WS03 -- without
needing to change DCOM. You need to change DCOM only if you are running
WS03SP1 builds.

I would totally look at user privileges -- if you are in a domain, make sure
that you do not have group policy that is locking down your server and/or
user privileges more than you know.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...
No, I made no changes to IIS that I am aware of. As I mentioned, I did make
DCOM permission changes for the VS component.
IIS was installed in the initial build.

The only changes made to IIS, that I am aware of, were the change of the
default web and default ftp roots to D:\InetPub\wwwRoot and ftpRoot,
respectively.

The first installation of VS "05 was directed to D:\Program Files\Virtual
Server.

I un/reinstalled VS 3 or 4 times with different options/locations. The
current install is with straight defaults, on the C: drive.

Since you are, I think, questioning IIS configuration. Would a solution be
to un/reinstall IIS? Or during reinstallation will it pick up the current
configuration?

Update...
Following the information in the second link, below, I changed the
application pool identity. I first went "all the way," and set it to
Configurable\administrator account (and put the account into the IIS WPG
group. After that change, the VS website would not recognize my credentials
for login, ending in a 401 error.

I then changed the app pool identity to Predefined\Local System and the
Administration Website came up. Yea! As you are probably aware, making
this change brings up a "Sky is falling..." security message. Hope I don't
have to stay in this configuration.

For grins, I then set the Identity to Predefined\Local Service. That would
not allow the Admin website to come up. For that matter, it changed an open
browser, looking at the Admin website, into a 403 error page...

That was a bit long-winded. Please let me know how I might tighten security
and retain function...

Thanks

"David Wang [Msft]" <(email address - cut out)> wrote in message
news:(email address - cut out)...
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp

Show quoted text

> Ok, you are getting 403.19 for all of the CGI requests with error 1314 (A
> required privilege is not held by the client)
>
> This commonly happens if you changed the Application Pool Identity to a
> custom identity but failed to give that identity two documented privileges
> necessary to run CGI applications.
>
>
>
> I believe IIS installs with application pool identity that just works by
> default, and Virtual Server has no reason to change it -- so I have to ask
> if you've changed it and did you follow documentation.
>
>
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> Attached is log file for VS web...
>
>
> "David Wang [Msft]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Can you please post all log entries that access VSWebApp.exe for a
>> request
>> that returns your 403 error . I want all the status/error codes in the
>> order of appearance in the log file.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "Trey Shaffer" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> This is a fresh installation of VS "05 on top of a fresh install of
>> Windows
>> Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
>> 1/12.
>>
>> Symptom:
>> Attempting to access the Admin website returns:
>> You are not authorized to view this page...
>> HTTP Error 403 - Forbidden: Access is denied.
>>
>> Symptom is same from VS Server or remote client.
>>
>> User attempting access is Administrator.
>> Installation of VS used the Complete Install option with all defaults.
>>
>> I have seen information about this symptom as an issue with DCOM
>> permissions, as discussed in, MS KB Article 887491:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>>
>> DCOM Security settings have been changed to allow "Everyone" to Launch
>> and
>> Access the component.
>>
>> The web server appears to be OK. A basic Default.htm in the Default Web
>> root is functional. The IIS log for the Virtual Server subweb contains
>> no
>> errors. The log entries appear to reflect the successful GET of the
>> VSWebApp. There are no suspicious entries in the Event Viewer System,
>> Application or Security logs.
>>
>> This isn't my first experience with VS, but it is becoming my most
>> frustrating...
>>
>> All assistance appreciated.
>>
>>
>>
>>
>
>
>
>

Re: Admin Website Not Available

Sent: 01/28/2005
From: Gabe W
Message:

I have this same identical problem - fresh install of Windows 2003 Standard
Edition, fresh install of VS 2005, and I get the "not authorized to view this
page" error.

I too tried the DCOM fixes to no avail. My users are all local admins to
that server (I have tried several different accounts) and I cannot get to it
remotely or locally on the server.

"David Wang [Msft]" wrote:

Show quoted text

> When you are reporting IIS errors, always report the exact web log
> entries -- it has additional details (such as the substatus and Win32 error
> codes -- which is all I used for your diagnosis) useful for debugging. The
> custom error page that IIS returns is intentionally not useful for
> troubleshooting. I have no idea what your new 401 or 403 errors are, so I
> cannot comment on your new information.
>
> 403.19 indicates that the process identity is lacking the two documented
> permissions (and as always, make sure to add the user to IIS_WPG per
> documentation).
>
> Additional questions:
> 1. Are you accessing the website via a local login or via Remote Desktop.
> 2. Is this on a Domain Controller or not.
> 3. Is this machine in a domain or not
> 4. What authentication method(s) are enabled on the VS admin website
>
> Because you said that when you changed it to Administrator and you got 401
> (and VS admin website should have Integrated authentication by default), I
> suspect your machine is in a domain. The solution to the 401 in that case
> is in the second URL I sent in my last reply. Totally unrelated to the
> original issue of 403.19.
>
> Otherwise, I cannot think of anything else. Your issue has to do with
> process identity and permissions for the CGI since it (VSWebAp.exe --
> Virtual Server's CGI that is responsible for generating the admin website
> pages) is failing to launch. I would NOT recommend reinstalling IIS since
> it won't change those permissions requirements and probably breaks more
> things than it fixes. I can only say that Local System is not required -- I
> run it just fine with the default Network Service account on WS03 -- without
> needing to change DCOM. You need to change DCOM only if you are running
> WS03SP1 builds.
>
> I would totally look at user privileges -- if you are in a domain, make sure
> that you do not have group policy that is locking down your server and/or
> user privileges more than you know.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> No, I made no changes to IIS that I am aware of. As I mentioned, I did make
> DCOM permission changes for the VS component.
> IIS was installed in the initial build.
>
> The only changes made to IIS, that I am aware of, were the change of the
> default web and default ftp roots to D:\InetPub\wwwRoot and ftpRoot,
> respectively.
>
> The first installation of VS "05 was directed to D:\Program Files\Virtual
> Server.
>
> I un/reinstalled VS 3 or 4 times with different options/locations. The
> current install is with straight defaults, on the C: drive.
>
> Since you are, I think, questioning IIS configuration. Would a solution be
> to un/reinstall IIS? Or during reinstallation will it pick up the current
> configuration?
>
> Update...
> Following the information in the second link, below, I changed the
> application pool identity. I first went "all the way," and set it to
> Configurable\administrator account (and put the account into the IIS WPG
> group. After that change, the VS website would not recognize my credentials
> for login, ending in a 401 error.
>
> I then changed the app pool identity to Predefined\Local System and the
> Administration Website came up. Yea! As you are probably aware, making
> this change brings up a "Sky is falling..." security message. Hope I don't
> have to stay in this configuration.
>
> For grins, I then set the Identity to Predefined\Local Service. That would
> not allow the Admin website to come up. For that matter, it changed an open
> browser, looking at the Admin website, into a 403 error page...
>
> That was a bit long-winded. Please let me know how I might tighten security
> and retain function...
>
> Thanks
>
>
> "David Wang [Msft]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Ok, you are getting 403.19 for all of the CGI requests with error 1314 (A
> > required privilege is not held by the client)
> >
> > This commonly happens if you changed the Application Pool Identity to a
> > custom identity but failed to give that identity two documented privileges
> > necessary to run CGI applications.
> >
> >
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp
> >
> > I believe IIS installs with application pool identity that just works by
> > default, and Virtual Server has no reason to change it -- so I have to ask
> > if you've changed it and did you follow documentation.
> >
> >
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp
> >
> > --
> > //David
> > IIS
> > http://blogs.msdn.com/David.Wang
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > //
> > "Trey Shaffer" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > Attached is log file for VS web...
> >
> >
> > "David Wang [Msft]" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> Can you please post all log entries that access VSWebApp.exe for a
> >> request
> >> that returns your 403 error . I want all the status/error codes in the
> >> order of appearance in the log file.
> >>
> >> --
> >> //David
> >> IIS
> >> http://blogs.msdn.com/David.Wang
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> //
> >> "Trey Shaffer" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> This is a fresh installation of VS "05 on top of a fresh install of
> >> Windows
> >> Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
> >> 1/12.
> >>
> >> Symptom:
> >> Attempting to access the Admin website returns:
> >> You are not authorized to view this page...
> >> HTTP Error 403 - Forbidden: Access is denied.
> >>
> >> Symptom is same from VS Server or remote client.
> >>
> >> User attempting access is Administrator.
> >> Installation of VS used the Complete Install option with all defaults.
> >>
> >> I have seen information about this symptom as an issue with DCOM
> >> permissions, as discussed in, MS KB Article 887491:
> >> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
> >>
> >> DCOM Security settings have been changed to allow "Everyone" to Launch
> >> and
> >> Access the component.
> >>
> >> The web server appears to be OK. A basic Default.htm in the Default Web
> >> root is functional. The IIS log for the Virtual Server subweb contains
> >> no
> >> errors. The log entries appear to reflect the successful GET of the
> >> VSWebApp. There are no suspicious entries in the Event Viewer System,
> >> Application or Security logs.
> >>
> >> This isn't my first experience with VS, but it is becoming my most
> >> frustrating...
> >>
> >> All assistance appreciated.
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
>
>

Re: Admin Website Not Available

Sent: 01/28/2005
From: "David Wang [Msft]" <(email address - cut out)>
Message:

I did not have problems installing VS2005 on WS03, so I suspect you are
looking at some local configuration problem on your server. I must first
ask you whether your server is in a domain or not, and if it is in a domain,
is it the DC.

Turn off IE's "Show Friendly HTTP Errors" option and report the actual HTTP
status code/substatus code as well as error code (or you can report the
entire web log entries corresponding to your request), and we can go from
there.

In general, I do not recommend pattern matching generic issues with
particular fixes without diagnosing the actual error. Guessing is not
troubleshooting.

WS03RTM and VS2005 does not have any DCOM issues. You only see DCOM issues
on XPSP2 as well as WS03SP1 (since it pulls in XPSP2 changes).

You also do not need to make users local admins to the server to allow them
web access nor Virtual Machine access -- Virtual Server security
documentation clarifies that.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Gabe W" <Gabe (email address - cut out)> wrote in message
news:(email address - cut out)...
I have this same identical problem - fresh install of Windows 2003 Standard
Edition, fresh install of VS 2005, and I get the "not authorized to view
this
page" error.

I too tried the DCOM fixes to no avail. My users are all local admins to
that server (I have tried several different accounts) and I cannot get to it
remotely or locally on the server.

"David Wang [Msft]" wrote:

error
The
I
without
sure
rights.
make
be
credentials
don't
would
open
security
(A
privileges
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp
ask
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp
of
Web

Show quoted text

> When you are reporting IIS errors, always report the exact web log
> entries -- it has additional details (such as the substatus and Win32
> codes -- which is all I used for your diagnosis) useful for debugging.
> custom error page that IIS returns is intentionally not useful for
> troubleshooting. I have no idea what your new 401 or 403 errors are, so I
> cannot comment on your new information.
>
> 403.19 indicates that the process identity is lacking the two documented
> permissions (and as always, make sure to add the user to IIS_WPG per
> documentation).
>
> Additional questions:
> 1. Are you accessing the website via a local login or via Remote Desktop.
> 2. Is this on a Domain Controller or not.
> 3. Is this machine in a domain or not
> 4. What authentication method(s) are enabled on the VS admin website
>
> Because you said that when you changed it to Administrator and you got 401
> (and VS admin website should have Integrated authentication by default), I
> suspect your machine is in a domain. The solution to the 401 in that case
> is in the second URL I sent in my last reply. Totally unrelated to the
> original issue of 403.19.
>
> Otherwise, I cannot think of anything else. Your issue has to do with
> process identity and permissions for the CGI since it (VSWebAp.exe --
> Virtual Server's CGI that is responsible for generating the admin website
> pages) is failing to launch. I would NOT recommend reinstalling IIS since
> it won't change those permissions requirements and probably breaks more
> things than it fixes. I can only say that Local System is not required --
> run it just fine with the default Network Service account on WS03 --
> needing to change DCOM. You need to change DCOM only if you are running
> WS03SP1 builds.
>
> I would totally look at user privileges -- if you are in a domain, make
> that you do not have group policy that is locking down your server and/or
> user privileges more than you know.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> No, I made no changes to IIS that I am aware of. As I mentioned, I did
> DCOM permission changes for the VS component.
> IIS was installed in the initial build.
>
> The only changes made to IIS, that I am aware of, were the change of the
> default web and default ftp roots to D:\InetPub\wwwRoot and ftpRoot,
> respectively.
>
> The first installation of VS "05 was directed to D:\Program Files\Virtual
> Server.
>
> I un/reinstalled VS 3 or 4 times with different options/locations. The
> current install is with straight defaults, on the C: drive.
>
> Since you are, I think, questioning IIS configuration. Would a solution
> to un/reinstall IIS? Or during reinstallation will it pick up the current
> configuration?
>
> Update...
> Following the information in the second link, below, I changed the
> application pool identity. I first went "all the way," and set it to
> Configurable\administrator account (and put the account into the IIS WPG
> group. After that change, the VS website would not recognize my
> for login, ending in a 401 error.
>
> I then changed the app pool identity to Predefined\Local System and the
> Administration Website came up. Yea! As you are probably aware, making
> this change brings up a "Sky is falling..." security message. Hope I
> have to stay in this configuration.
>
> For grins, I then set the Identity to Predefined\Local Service. That
> not allow the Admin website to come up. For that matter, it changed an
> browser, looking at the Admin website, into a 403 error page...
>
> That was a bit long-winded. Please let me know how I might tighten
> and retain function...
>
> Thanks
>
>
> "David Wang [Msft]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Ok, you are getting 403.19 for all of the CGI requests with error 1314
> > required privilege is not held by the client)
> >
> > This commonly happens if you changed the Application Pool Identity to a
> > custom identity but failed to give that identity two documented
> > necessary to run CGI applications.
> >
> >
>
> >
> > I believe IIS installs with application pool identity that just works by
> > default, and Virtual Server has no reason to change it -- so I have to
> > if you've changed it and did you follow documentation.
> >
> >
>
> >
> > --
> > //David
> > IIS
> > http://blogs.msdn.com/David.Wang
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > //
> > "Trey Shaffer" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > Attached is log file for VS web...
> >
> >
> > "David Wang [Msft]" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> Can you please post all log entries that access VSWebApp.exe for a
> >> request
> >> that returns your 403 error . I want all the status/error codes in the
> >> order of appearance in the log file.
> >>
> >> --
> >> //David
> >> IIS
> >> http://blogs.msdn.com/David.Wang
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> //
> >> "Trey Shaffer" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> This is a fresh installation of VS "05 on top of a fresh install of
> >> Windows
> >> Server 2003 Std. OS is fully patched/updated to MS Windows Update as
> >> 1/12.
> >>
> >> Symptom:
> >> Attempting to access the Admin website returns:
> >> You are not authorized to view this page...
> >> HTTP Error 403 - Forbidden: Access is denied.
> >>
> >> Symptom is same from VS Server or remote client.
> >>
> >> User attempting access is Administrator.
> >> Installation of VS used the Complete Install option with all defaults.
> >>
> >> I have seen information about this symptom as an issue with DCOM
> >> permissions, as discussed in, MS KB Article 887491:
> >> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
> >>
> >> DCOM Security settings have been changed to allow "Everyone" to Launch
> >> and
> >> Access the component.
> >>
> >> The web server appears to be OK. A basic Default.htm in the Default
> >> root is functional. The IIS log for the Virtual Server subweb contains
> >> no
> >> errors. The log entries appear to reflect the successful GET of the
> >> VSWebApp. There are no suspicious entries in the Event Viewer System,
> >> Application or Security logs.
> >>
> >> This isn't my first experience with VS, but it is becoming my most
> >> frustrating...
> >>
> >> All assistance appreciated.
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
>
>

Re: Admin Website Not Available

Sent: 01/29/2005
From: "Rick Barber" <(email address - cut out)>
Message:

Hi Trey,

It sounds like you have a permissions issue. After you see that error,
check the security event viewer and it should clue you in to which user(s)
don't have the appropriate permissions to which directories. If this is a
default install, I'm guessing that possibly IIS_WPG doesn't have read and
execute permissions to the new location. That is just a guess as event
viewer should give you the exact permissions issues.

If for some reason you're not seeing any permissions errors, make sure that
Audio object access is set to log failures in your Local Security
Settings -> Local Policies -> Audio Policy.

Thank you,

Rick Barber

http://www.orcsweb.com
Powerful Web Hosting Solutions
#1 in Service and Support

"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> No, I made no changes to IIS that I am aware of. As I mentioned, I did
> make DCOM permission changes for the VS component.
> IIS was installed in the initial build.
>
> The only changes made to IIS, that I am aware of, were the change of the
> default web and default ftp roots to D:\InetPub\wwwRoot and ftpRoot,
> respectively.
>
> The first installation of VS "05 was directed to D:\Program Files\Virtual
> Server.
>
> I un/reinstalled VS 3 or 4 times with different options/locations. The
> current install is with straight defaults, on the C: drive.
>
> Since you are, I think, questioning IIS configuration. Would a solution
> be to un/reinstall IIS? Or during reinstallation will it pick up the
> current configuration?
>
> Update...
> Following the information in the second link, below, I changed the
> application pool identity. I first went "all the way," and set it to
> Configurable\administrator account (and put the account into the IIS WPG
> group. After that change, the VS website would not recognize my
> credentials for login, ending in a 401 error.
>
> I then changed the app pool identity to Predefined\Local System and the
> Administration Website came up. Yea! As you are probably aware, making
> this change brings up a "Sky is falling..." security message. Hope I
> don't have to stay in this configuration.
>
> For grins, I then set the Identity to Predefined\Local Service. That
> would not allow the Admin website to come up. For that matter, it changed
> an open browser, looking at the Admin website, into a 403 error page...
>
> That was a bit long-winded. Please let me know how I might tighten
> security and retain function...
>
> Thanks
>
>
> "David Wang [Msft]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Ok, you are getting 403.19 for all of the CGI requests with error 1314 (A
>> required privilege is not held by the client)
>>
>> This commonly happens if you changed the Application Pool Identity to a
>> custom identity but failed to give that identity two documented
>> privileges
>> necessary to run CGI applications.
>>
>> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp
>>
>> I believe IIS installs with application pool identity that just works by
>> default, and Virtual Server has no reason to change it -- so I have to
>> ask
>> if you've changed it and did you follow documentation.
>>
>> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "Trey Shaffer" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> Attached is log file for VS web...
>>
>>
>> "David Wang [Msft]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Can you please post all log entries that access VSWebApp.exe for a
>>> request
>>> that returns your 403 error . I want all the status/error codes in the
>>> order of appearance in the log file.
>>>
>>> --
>>> //David
>>> IIS
>>> http://blogs.msdn.com/David.Wang
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>> //
>>> "Trey Shaffer" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>> This is a fresh installation of VS "05 on top of a fresh install of
>>> Windows
>>> Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
>>> 1/12.
>>>
>>> Symptom:
>>> Attempting to access the Admin website returns:
>>> You are not authorized to view this page...
>>> HTTP Error 403 - Forbidden: Access is denied.
>>>
>>> Symptom is same from VS Server or remote client.
>>>
>>> User attempting access is Administrator.
>>> Installation of VS used the Complete Install option with all defaults.
>>>
>>> I have seen information about this symptom as an issue with DCOM
>>> permissions, as discussed in, MS KB Article 887491:
>>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>>>
>>> DCOM Security settings have been changed to allow "Everyone" to Launch
>>> and
>>> Access the component.
>>>
>>> The web server appears to be OK. A basic Default.htm in the Default Web
>>> root is functional. The IIS log for the Virtual Server subweb contains
>>> no
>>> errors. The log entries appear to reflect the successful GET of the
>>> VSWebApp. There are no suspicious entries in the Event Viewer System,
>>> Application or Security logs.
>>>
>>> This isn't my first experience with VS, but it is becoming my most
>>> frustrating...
>>>
>>> All assistance appreciated.
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>

Re: Admin Website Not Available

Sent: 01/31/2005
From: "David Wang [Msft]" <(email address - cut out)>
Message:

I'm thinking of various causes of 403.19, and I thought of another one:

There was an IIS6 issue in WS03RTM where if you access a local CGI under
NTLM authentication while inside of a Remote Desktop session, it would fail
with a 403.19. VS Admin website would be a CGI under NTLM authentication,
so if you access the website locally while under Remote Desktop, it would
fail. I cannot find if it was fixed or not -- I remember there was a bunch
of contortion necessary to get into this case -- needs to be CGI, needs NTLM
authentication, must be request to the same local machine, and must be under
Remote Desktop.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...
No, I made no changes to IIS that I am aware of. As I mentioned, I did make
DCOM permission changes for the VS component.
IIS was installed in the initial build.

The only changes made to IIS, that I am aware of, were the change of the
default web and default ftp roots to D:\InetPub\wwwRoot and ftpRoot,
respectively.

The first installation of VS "05 was directed to D:\Program Files\Virtual
Server.

I un/reinstalled VS 3 or 4 times with different options/locations. The
current install is with straight defaults, on the C: drive.

Since you are, I think, questioning IIS configuration. Would a solution be
to un/reinstall IIS? Or during reinstallation will it pick up the current
configuration?

Update...
Following the information in the second link, below, I changed the
application pool identity. I first went "all the way," and set it to
Configurable\administrator account (and put the account into the IIS WPG
group. After that change, the VS website would not recognize my credentials
for login, ending in a 401 error.

I then changed the app pool identity to Predefined\Local System and the
Administration Website came up. Yea! As you are probably aware, making
this change brings up a "Sky is falling..." security message. Hope I don't
have to stay in this configuration.

For grins, I then set the Identity to Predefined\Local Service. That would
not allow the Admin website to come up. For that matter, it changed an open
browser, looking at the Admin website, into a 403 error page...

That was a bit long-winded. Please let me know how I might tighten security
and retain function...

Thanks

"David Wang [Msft]" <(email address - cut out)> wrote in message
news:(email address - cut out)...
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/ca_configcgi.asp
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/ca_cfgwrkridentity.asp

Show quoted text

> Ok, you are getting 403.19 for all of the CGI requests with error 1314 (A
> required privilege is not held by the client)
>
> This commonly happens if you changed the Application Pool Identity to a
> custom identity but failed to give that identity two documented privileges
> necessary to run CGI applications.
>
>
>
> I believe IIS installs with application pool identity that just works by
> default, and Virtual Server has no reason to change it -- so I have to ask
> if you've changed it and did you follow documentation.
>
>
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> Attached is log file for VS web...
>
>
> "David Wang [Msft]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Can you please post all log entries that access VSWebApp.exe for a
>> request
>> that returns your 403 error . I want all the status/error codes in the
>> order of appearance in the log file.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "Trey Shaffer" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> This is a fresh installation of VS "05 on top of a fresh install of
>> Windows
>> Server 2003 Std. OS is fully patched/updated to MS Windows Update as of
>> 1/12.
>>
>> Symptom:
>> Attempting to access the Admin website returns:
>> You are not authorized to view this page...
>> HTTP Error 403 - Forbidden: Access is denied.
>>
>> Symptom is same from VS Server or remote client.
>>
>> User attempting access is Administrator.
>> Installation of VS used the Complete Install option with all defaults.
>>
>> I have seen information about this symptom as an issue with DCOM
>> permissions, as discussed in, MS KB Article 887491:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>>
>> DCOM Security settings have been changed to allow "Everyone" to Launch
>> and
>> Access the component.
>>
>> The web server appears to be OK. A basic Default.htm in the Default Web
>> root is functional. The IIS log for the Virtual Server subweb contains
>> no
>> errors. The log entries appear to reflect the successful GET of the
>> VSWebApp. There are no suspicious entries in the Event Viewer System,
>> Application or Security logs.
>>
>> This isn't my first experience with VS, but it is becoming my most
>> frustrating...
>>
>> All assistance appreciated.
>>
>>
>>
>>
>
>
>
>

Re: Admin Website Not Available

Sent: 02/05/2005
From: "Trey Shaffer" <(email address - cut out)>
Message:

My issue resolved.

Not sure what the protocol is for "closing" an item in the newsgroup...

My issue was the account used for the Application Pool security. I needed
to escalate it from the Network account to Local System. I realize that has
other security implications, but those will be an issue for another
installation.

Thanks to all...

"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> This is a fresh installation of VS "05 on top of a fresh install of
> Windows Server 2003 Std. OS is fully patched/updated to MS Windows Update
> as of 1/12.
>
> Symptom:
> Attempting to access the Admin website returns:
> You are not authorized to view this page...
> HTTP Error 403 - Forbidden: Access is denied.
>
> Symptom is same from VS Server or remote client.
>
> User attempting access is Administrator.
> Installation of VS used the Complete Install option with all defaults.
>
> I have seen information about this symptom as an issue with DCOM
> permissions, as discussed in, MS KB Article 887491:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>
> DCOM Security settings have been changed to allow "Everyone" to Launch and
> Access the component.
>
> The web server appears to be OK. A basic Default.htm in the Default Web
> root is functional. The IIS log for the Virtual Server subweb contains no
> errors. The log entries appear to reflect the successful GET of the
> VSWebApp. There are no suspicious entries in the Event Viewer System,
> Application or Security logs.
>
> This isn't my first experience with VS, but it is becoming my most
> frustrating...
>
> All assistance appreciated.
>
>
>

Re: Admin Website Not Available

Sent: 02/05/2005
From: "Colin Barnhorst" <colinbarharst(nojunk)@msn.com>
Message:

Stop posting? :)

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> My issue resolved.
>
> Not sure what the protocol is for "closing" an item in the newsgroup...
>
> My issue was the account used for the Application Pool security. I needed
> to escalate it from the Network account to Local System. I realize that
> has other security implications, but those will be an issue for another
> installation.
>
> Thanks to all...
>
>
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> This is a fresh installation of VS "05 on top of a fresh install of
>> Windows Server 2003 Std. OS is fully patched/updated to MS Windows
>> Update as of 1/12.
>>
>> Symptom:
>> Attempting to access the Admin website returns:
>> You are not authorized to view this page...
>> HTTP Error 403 - Forbidden: Access is denied.
>>
>> Symptom is same from VS Server or remote client.
>>
>> User attempting access is Administrator.
>> Installation of VS used the Complete Install option with all defaults.
>>
>> I have seen information about this symptom as an issue with DCOM
>> permissions, as discussed in, MS KB Article 887491:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
>>
>> DCOM Security settings have been changed to allow "Everyone" to Launch
>> and Access the component.
>>
>> The web server appears to be OK. A basic Default.htm in the Default Web
>> root is functional. The IIS log for the Virtual Server subweb contains
>> no errors. The log entries appear to reflect the successful GET of the
>> VSWebApp. There are no suspicious entries in the Event Viewer System,
>> Application or Security logs.
>>
>> This isn't my first experience with VS, but it is becoming my most
>> frustrating...
>>
>> All assistance appreciated.
>>
>>
>>
>
>

Re: Admin Website Not Available

Sent: 02/05/2005
From: "David Wang [Msft]" <(email address - cut out)>
Message:

The solution does not make sense.

I am only going to note that on a clean WS03 installation, LocalSystem is
not necessary for VS Web Admin to function.

So, while I'm happy that your issue is "resolved", it is definitely not a
correct "solution".

I suspect you are running on a Domain Controller, but you never answered my
last post to you on 1/17/2005 either way. You were describing other problems
with using Application Pool Identity that simply do not correspond to a
functioning IIS installation (I had no problems running your commands, for
example). You were also reporting 403.19 errors with a CGI, corresponding to
missing privileges on the process identity -- which I suspect you need to
customize when on a Domain Controller.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...
My issue resolved.

Not sure what the protocol is for "closing" an item in the newsgroup...

My issue was the account used for the Application Pool security. I needed
to escalate it from the Network account to Local System. I realize that has
other security implications, but those will be an issue for another
installation.

Thanks to all...

"Trey Shaffer" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

Re: Admin Website Not Available

Sent: 05/19/2005
From: Danny F
Message:

I am having this exact same issue and am running VS 05 on a domain
controller. What permissions do i need to change to make this work.

Thanks in advance for your help.

-Danny

"David Wang [Msft]" wrote:

Show quoted text

> The solution does not make sense.
>
> I am only going to note that on a clean WS03 installation, LocalSystem is
> not necessary for VS Web Admin to function.
>
> So, while I'm happy that your issue is "resolved", it is definitely not a
> correct "solution".
>
> I suspect you are running on a Domain Controller, but you never answered my
> last post to you on 1/17/2005 either way. You were describing other problems
> with using Application Pool Identity that simply do not correspond to a
> functioning IIS installation (I had no problems running your commands, for
> example). You were also reporting 403.19 errors with a CGI, corresponding to
> missing privileges on the process identity -- which I suspect you need to
> customize when on a Domain Controller.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> My issue resolved.
>
> Not sure what the protocol is for "closing" an item in the newsgroup...
>
> My issue was the account used for the Application Pool security. I needed
> to escalate it from the Network account to Local System. I realize that has
> other security implications, but those will be an issue for another
> installation.
>
> Thanks to all...
>
>
> "Trey Shaffer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > This is a fresh installation of VS "05 on top of a fresh install of
> > Windows Server 2003 Std. OS is fully patched/updated to MS Windows Update
> > as of 1/12.
> >
> > Symptom:
> > Attempting to access the Admin website returns:
> > You are not authorized to view this page...
> > HTTP Error 403 - Forbidden: Access is denied.
> >
> > Symptom is same from VS Server or remote client.
> >
> > User attempting access is Administrator.
> > Installation of VS used the Complete Install option with all defaults.
> >
> > I have seen information about this symptom as an issue with DCOM
> > permissions, as discussed in, MS KB Article 887491:
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;887491
> >
> > DCOM Security settings have been changed to allow "Everyone" to Launch and
> > Access the component.
> >
> > The web server appears to be OK. A basic Default.htm in the Default Web
> > root is functional. The IIS log for the Virtual Server subweb contains no
> > errors. The log entries appear to reflect the successful GET of the
> > VSWebApp. There are no suspicious entries in the Event Viewer System,
> > Application or Security logs.
> >
> > This isn't my first experience with VS, but it is becoming my most
> > frustrating...
> >
> > All assistance appreciated.
> >
> >
> >
>
>
>
>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: