• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4585
  • Last Modified:

Can't install Forefront Client Security

I have a clean install of W2K3R2 x86 and have installed WSUS 3 on top.
MMC 3.0 is installed, as is GPMC with SP1.
SQL Server 2005 Developer Edition is installed with all options including Reporting Services.
I'm attempting to install Forefront on this server from the CD, and am trying to put all server roles (management, collection server, collection database, reporting server/database, and distribution server) on this box.  When I go through the process, I specify the DAS account and leave everything pretty much at default.  During the verify settings and requirements phase, everything goes well except a warning about wanting 2 processors being recommended.  But when it gets to verifying URL's for reports, it throws an error:  Could not access this address:  http://servername/Reports and http://servername/ReportServer.  It says the remote server returned an error (500) Internal Server Error.
The Application log shows a warning:  ASP.NET error 1310, configuration error.
Any clues, pointers, hunches or suggestions would be greatly appreciated.  thanks, Bob
0
BobHerring
Asked:
BobHerring
1 Solution
 
meverestCommented:
Hi,

did you download and install the ASP.NET framework? (from www.asp.net)

Cheers.
0
 
BobHerringAuthor Commented:
When I go to Add/remove programs, it shows .Net Framework service pack 1 and service pack 2 installed.  In Add/remove Windows components, under Application Server, it shows ASP.Net installed.  Also under Windows components, it shows Microsoft .NET Framework 2.0 installed.  Let me check the URL you provided and see if there is more to download.  I thought the R2 edition of W2K3, plus every available update, would include every component I would need.  Thank you!
0
 
BobHerringAuthor Commented:
I went to www.asp.net and downloaded .NET 3.5, then re-booted the server, then tried reinstalling Forefront.  I get the same problem as before:  everything is fine except when it gets to verifying URL's for reporting, it throws an error:  Could not access this address:  http://servername/Reports and http://servername/ReportServer.  The application log shows an error:  first, a Windows Server Update as Source, Event ID 13042, "Self-update is not working".  Then, a Warning:  ASP.NET 2.0.50727.0, category Web Event, Event ID 1310, "A configuration error has occurred".

Should I uninstall/reinstall ASP.NET 2.0?  Thanks for your help.  Bob
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
meverestCommented:
Hi Bob,

it does seem like there is something up with the asp.net install.  Try "aspnet_regiis.exe -i" from a cmd shell first, if that fails, then uninstall everything and then put it back in order:  IIS, ASP.NET, Forefront

Cheers.
0
 
caw01Commented:
Do you have asp.net installed under IIS?  Thats a biggie.

I had this same exact problem originally.  I removed everything, reinstalled SQL server and it was fine.  For whatever reason it did not create my reportserver webistes.

Do you see your report server websites listed under your IIS Setup?  Can you go to the url http://servername/reportserver?  If not, then the problem is with your IIS and SQL setup.  It also requires a few other SQL services besides just the reporting svcs.  If your websites dont work, I would start with a SQL reinstall.
0
 
BobHerringAuthor Commented:
this sounds like the ticket.
I will try it at the first opportunity.
Thank you for your time/attention.
Bob
0
 
shenson69Commented:
There are two IIS sites related to Reportig Services. You must have .NET 2.0 installed and you must go into the properties of each of these sub sites and verify they are set to use the correct version of .NET on the .NET tab. I had the same issue and, in my case, the sites were set to use .NET 1.1. Changed them and applied and tried againa and everything worked.
0
 
soloITguyCommented:
shenson69, your suggestion worked for me.  One of my sites listed .NET 1.xxx.  I changed the version as you suggested and everything was working within seconds.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now