Re: CCM Server Framework Pool dies along with W3SVC in event log



In article <FB972E8C-AFD9-4BFB-A607-48190BE9AD6F@xxxxxxxxxxxxx>,
KrisG@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> Marin,
> The log files don't really tell me much. Also, I've double-checked
> permisions as per Microsoft's "Default permisions for IIS 6.0" at:
> http://support.microsoft.com/default.aspx/kb/812614
>
> However, the same errors persist. What's odd is that SMS and IIS are working
> perfectly in my test environment where I performed all the same steps with
> installing and configuring the Site Server. The _only_ difference is that
> with my test server, I installed W2k3 and then ran SP1, whereas my production
> server I installed with a slipstream W2k3SP1 install.
>
> If it means anything to you, after I redirected IIS's pools to run off of
> the local system account, I also needed to sync the IUSER and IWAM accounts
> passwords using the .vbs utility in order to get my reports working again.
>
> I'm considering locking things down via the firewall and leaving the pool's
> authenticating with Local System.
>
> -KrisG
<snip>
Hm...starting to run out of ideas. If you managed to get this to work
using Network Service, as you mentioned in your previous post, then
don't switch the pools to Local System. Running a firewall product won't
help you much since you have to allow access to the SMS virtual
directories and if there is a flaw in, say, the ISAPI filter that
handles the requests to the management point, the firewall won't prevent
someone from exploiting it.
I would try to reproduce the problem in a test lab (e.g., use your
slipstreamed CD, exactly the same media and settings, etc). Moving SMS
to a freshly installed server is also an option (you can also restore
your production SMS in an isolated lab to validate whether this would
bring you anything). BTW, did this machine show these symptoms from the
beginning or did they start at some point after SMS has been running
successfully?

--
Cheers,
Marin Marinov
MCT,MCSE,MCSE:Security,MCP+I
-
This posting is provided "AS IS" with no warranties, and confers no
rights.

"True knowledge exists in knowing that you know nothing."
Socrates
.



Relevant Pages

  • Re: Site Code Not Discovered.
    ... There is a Troubleshooting Management Points whitepaper on the SMS website ... installing a management point. ... DHCP Setup - are the clients looking at a specific DHCP Server ...
    (microsoft.public.sms.admin)
  • RE: Moving Server Options
    ... contains a move the server scenario. ... Make sure iis is installed prior to installing the recovery expert. ... MVP SMS ...
    (microsoft.public.sms.setup)
  • Re: CCM Server Framework Pool dies along with W3SVC in event log
    ... What's odd is that SMS and IIS are working ... installing and configuring the Site Server. ... "Marin Marinov" wrote: ...
    (microsoft.public.sms.admin)
  • Re: Fresh Install Doesnt Work...Again!
    ... discovered that you had to have BITS up and running before installing SMS2003 ... MVP Windows Server System - SMS ...
    (microsoft.public.sms.setup)
  • Legacy Clients not upgraded
    ... Installed SMS 2003 2 weeks ago on one server. ... days before installing SMS 2003 on a new W2003 server. ... installing the advanced client. ...
    (microsoft.public.sms.misc)

Loading