| Author |
Message |
Glenn Brensinger
Guest
|
Posted:
Wed Nov 02, 2005 9:51 pm Post subject:
Web Console will not allow access |
|
|
I originally posted this problem when I was running the console on a
standalone server and the database on a domain controller. I have
since attempted this again on a clean system, and am having the same
exact problem. When connecting to the server with a web browser, I get
a "Server error in /." I edited the Web.config file to show the full
error, and get:
Server Error in '/' Application.
--------------------------------------------------------------------------------
Access to the path
"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\root\c3e41230\415cb36a" is denied.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the
path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\root\c3e41230\415cb36a" is denied.
I am running on a Windows 2003 Standard Server (Service Pack 1.) I
keep reading that there's an issue when running on a domain
controller, but since MOM requires Active Directory, you sort of have
to run on a DC of some form. Installation meets all the requirements,
SQL 2000 SP4 (had to find a workaround to the version detection
problem on the Internet because MS's command line workaround didn't
work,) IIS and ASP.NET are both enabled, blah blah. I've done
everything that people have suggested - adding accounts to various
groups, changing permissions, etc. The only thing I can't try is the
WebConsoleFix - the CD image of MOM SP1 we downloaded does not have
that file.
Obviously people have this working, so what's the big secret? Why is
this refusing to work?
Glenn |
|
| Back to top |
|
 |
Arie de Haan
Guest
|
Posted:
Wed Nov 02, 2005 9:51 pm Post subject:
Re: Web Console will not allow access |
|
|
| Quote: | controller, but since MOM requires Active Directory, you sort of have
Not true see: |
http://www.microsoft.com/technet/prodtechnol/mom/mom2005/Library/7542d53
8-46cf-463a-a8f9-45fbb34f4d1b.mspx
and on the bottom there is a statement about installin MOM on a DC
--
Greetz,
Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc. |
|
| Back to top |
|
 |
Glenn Brensinger
Guest
|
Posted:
Wed Nov 02, 2005 9:51 pm Post subject:
Re: Web Console will not allow access |
|
|
On Wed, 2 Nov 2005 20:08:59 +0100, Arie de Haan
<com.pandinus@ariedh.reversed> wrote:
I demoted the server to standalone. Removed Active Directory. Set up
local accounts. Removed and reinstalled MOM 2005 and the Service Pack.
Made sure to install the Web Console. Now when I attempt to install
the agent to a remote system, it just sits there at "Waiting to be
Scheduled" and the web console gives me the same BS error about not
being allowed to access the site.
I'm about ready to call it quits. NO application should be this
difficult.
Glenn |
|
| Back to top |
|
 |
Glenn Brensinger
Guest
|
Posted:
Wed Nov 02, 2005 9:51 pm Post subject:
Re: Web Console will not allow access |
|
|
On Wed, 2 Nov 2005 20:08:59 +0100, Arie de Haan
<com.pandinus@ariedh.reversed> wrote:
When I ran the prereq check for Workgroup Edition, it said I needed AD
for MOM Express, and refused to allow an installation. I re-ran the
prereq check using the Enterprise Edition, checking off everything
except Reporting and the Connector Framework, and it is installing.
(We didn't WANT the Enterprise Edition...)
If the Web Console actually works, I'll drop over.
Glenn |
|
| Back to top |
|
 |
Arie de Haan
Guest
|
Posted:
Fri Nov 04, 2005 1:50 am Post subject:
Re: Web Console will not allow access |
|
|
In article <o28im1tql12pmp7q95sk3j8060l8o98h6p@4ax.com>,
glenn@GOAWAYthe-nest.com says...
If it is the WG version, then yes it will need AD. As i didn't notice
that in your original post i assumed you were using the full version.
It should be fairly easy to set up a WG version. I can't help you much
further on this remotly.
--
Greetz,
Arie
This posting is provide "AS IS" with no guarantees, warranties, rigths
etc. |
|
| Back to top |
|
 |
Kelly Morris [MSFT]
Guest
|
Posted:
Tue Nov 08, 2005 9:51 pm Post subject:
Re: Web Console will not allow access |
|
|
Good Morning,
Have you tried setting up two, separate servers? Setup one server as
the AD controller, do not install anything else on it. Configure one or
more user accounts in the new domain, follow the MOM security guide for
permissions on these accounts. Setup a second server, make it a member of
the domain controlled by the first server. Now, install MOM 2005 Workgroup
edition on the second server.
There are a number of known issues when installing any version of MOM on
a AD controller. While it is a supported configuration, it is not
recommended. The prerequisites state that, the product requires Active
Directory services, this does not mean it must be installed on a Domain
Controller. I hope this clarifies things.
--
Kelly Morris [MSFT]
Log a bug or Feature Request directly to the MOM Product Team by going to
http://www.microsoft.com/mom/feedback. This posting is provided "AS IS" with
no warranties, and confers no rights. Use of included script samples are
subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
"Glenn Brensinger" <glenn@COVERthe-nest.com> wrote in message
news:16cim15c29815bg43jijhsj1lt9h65273a@4ax.com...
| Quote: | On Wed, 2 Nov 2005 20:08:59 +0100, Arie de Haan
com.pandinus@ariedh.reversed> wrote:
Not true see:
http://www.microsoft.com/technet/prodtechnol/mom/mom2005/Library/7542d538-46cf-463a-a8f9-45fbb34f4d1b.mspx
I demoted the server to standalone. Removed Active Directory. Set up
local accounts. Removed and reinstalled MOM 2005 and the Service Pack.
Made sure to install the Web Console. Now when I attempt to install
the agent to a remote system, it just sits there at "Waiting to be
Scheduled" and the web console gives me the same BS error about not
being allowed to access the site.
I'm about ready to call it quits. NO application should be this
difficult.
Glenn |
|
|
| Back to top |
|
 |
|
|
|
|