Prev: SBS2003 POP3 Connector error 1056 and 1053
Next: ISA 2004 Question
From: Gary on 5 Jul 2010 18:03
Yes, I should have mentioned that I tried that as well using the network
account then my own admin account attempting various permutations of
automatic, manual and shuttting it off. None worked, no matter what I did I
received the same error. The only thing left, I suppose, is to uninstall the
update altogether but I am hesistant to do this as subsequent updates could
have dependancies.

Thanks
--
Gary


"Paul Shapiro" wrote:

> I see the same thing. I believe that service is intended to optimize .Net
> application startup by caching compiled code. Since the server is not
> running applications, I wonder if it is ok to set the startup type to manual
> to prevent the daily warning? This service is apparently the .Net 4 version
> of the service that was called something like .Net Optimization in earlier
> ..Net versions. I don't remember what the start type was at that time.
>
> "Gary" <admin(a)starksgonzales.com> wrote in message
> news:1B5DD9C7-CE8E-4017-87BD-4C45DB95977E(a)microsoft.com...
> > This service was installed in a recent auto update on my SBS 2003 server
> > and
> > it was installed with automatic startup. But it just starts up and shuts
> > right back down.
> >
> > Because of that my daily server report is showing:
> >
> > Auto-started Services Not Running
> >
> > Service Name Microsoft .NET Framework NGEN v4.0.30319_X86
> >
> > Total auto-started services not running: 1
> >
> > In normal conditions, these services should be running.
> >
> > For details, it is recommended that you review errors in the
> >
> > Event log related to the service.
> >
> > It's a annoyance to have that in the daily server reports. (I want to see
> > all green items)
> >
> > I have tried disabling the monitoring of this service via Health Monitor
> > using the method below but it persists.
> >
> > Control Panel | Administrative Tools | Health Monitor |
> > <yourSBSservername>
> > Collector | Service Montior | Browse | (highlight) >. .NET Framework NGEN
> > v4.0.30319_X86| OK |
> > Apply |
> >
> > You should then see the .NET Framework NGEN v4.0.30319_X86 in:
> >
> > Server Management | Monitoring and Reporting | Change Alert Notification
> > --
> > Gary
>
> .
>
From: Chris Puckett [MSFT] on 5 Jul 2010 23:16
That behavior is normal for the Microsoft .NET Framework NGEN v4.0.30319_X86
service. If there is nothing for it to do it stops itself automatically.
It is set to automatic so it can perform some checks at startup.

This service is installed by the .NET Framework 4.0 package. If you change
the service to Manual, it is possible that future updates for .NET 4.0 could
change it back to Manual.

Your options are:

1. Make a mental note that this is okay to see in the report for this
service.
2. Set that service to Manual.
3. Uninstall .NET Framework 4.0.

SBS 2003 has no dependencies on .NET 4.0 and this package is not
auto-approved for install by default. Do you happen to recall how it got
installed? (Was it manually downloaded and installed? Do you use WSUS or
do you visit Microsoft Update manually?)

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"Gary" <admin(a)starksgonzales.com> wrote in message
news:466577A3-A777-4916-85BE-7DA3B42B8E86(a)microsoft.com...
> Yes, I should have mentioned that I tried that as well using the network
> account then my own admin account attempting various permutations of
> automatic, manual and shuttting it off. None worked, no matter what I did
> I
> received the same error. The only thing left, I suppose, is to uninstall
> the
> update altogether but I am hesistant to do this as subsequent updates
> could
> have dependancies.
>
> Thanks
> --
> Gary
>
>
> "Paul Shapiro" wrote:
>
>> I see the same thing. I believe that service is intended to optimize .Net
>> application startup by caching compiled code. Since the server is not
>> running applications, I wonder if it is ok to set the startup type to
>> manual
>> to prevent the daily warning? This service is apparently the .Net 4
>> version
>> of the service that was called something like .Net Optimization in
>> earlier
>> ..Net versions. I don't remember what the start type was at that time.
>>
>> "Gary" <admin(a)starksgonzales.com> wrote in message
>> news:1B5DD9C7-CE8E-4017-87BD-4C45DB95977E(a)microsoft.com...
>> > This service was installed in a recent auto update on my SBS 2003
>> > server
>> > and
>> > it was installed with automatic startup. But it just starts up and
>> > shuts
>> > right back down.
>> >
>> > Because of that my daily server report is showing:
>> >
>> > Auto-started Services Not Running
>> >
>> > Service Name Microsoft .NET Framework NGEN v4.0.30319_X86
>> >
>> > Total auto-started services not running: 1
>> >
>> > In normal conditions, these services should be running.
>> >
>> > For details, it is recommended that you review errors in the
>> >
>> > Event log related to the service.
>> >
>> > It's a annoyance to have that in the daily server reports. (I want to
>> > see
>> > all green items)
>> >
>> > I have tried disabling the monitoring of this service via Health
>> > Monitor
>> > using the method below but it persists.
>> >
>> > Control Panel | Administrative Tools | Health Monitor |
>> > <yourSBSservername>
>> > Collector | Service Montior | Browse | (highlight) >. .NET Framework
>> > NGEN
>> > v4.0.30319_X86| OK |
>> > Apply |
>> >
>> > You should then see the .NET Framework NGEN v4.0.30319_X86 in:
>> >
>> > Server Management | Monitoring and Reporting | Change Alert
>> > Notification
>> > --
>> > Gary
>>
>> .
>>
From: Gary on 6 Jul 2010 23:02
It was through WSUS...also setting this service to Manual had not effect on
the red indicator and and could not start the service.
--
Gary


"Chris Puckett [MSFT]" wrote:

> That behavior is normal for the Microsoft .NET Framework NGEN v4.0.30319_X86
> service. If there is nothing for it to do it stops itself automatically.
> It is set to automatic so it can perform some checks at startup.
>
> This service is installed by the .NET Framework 4.0 package. If you change
> the service to Manual, it is possible that future updates for .NET 4.0 could
> change it back to Manual.
>
> Your options are:
>
> 1. Make a mental note that this is okay to see in the report for this
> service.
> 2. Set that service to Manual.
> 3. Uninstall .NET Framework 4.0.
>
> SBS 2003 has no dependencies on .NET 4.0 and this package is not
> auto-approved for install by default. Do you happen to recall how it got
> installed? (Was it manually downloaded and installed? Do you use WSUS or
> do you visit Microsoft Update manually?)
>
> --
> Chris Puckett
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Gary" <admin(a)starksgonzales.com> wrote in message
> news:466577A3-A777-4916-85BE-7DA3B42B8E86(a)microsoft.com...
> > Yes, I should have mentioned that I tried that as well using the network
> > account then my own admin account attempting various permutations of
> > automatic, manual and shuttting it off. None worked, no matter what I did
> > I
> > received the same error. The only thing left, I suppose, is to uninstall
> > the
> > update altogether but I am hesistant to do this as subsequent updates
> > could
> > have dependancies.
> >
> > Thanks
> > --
> > Gary
> >
> >
> > "Paul Shapiro" wrote:
> >
> >> I see the same thing. I believe that service is intended to optimize .Net
> >> application startup by caching compiled code. Since the server is not
> >> running applications, I wonder if it is ok to set the startup type to
> >> manual
> >> to prevent the daily warning? This service is apparently the .Net 4
> >> version
> >> of the service that was called something like .Net Optimization in
> >> earlier
> >> ..Net versions. I don't remember what the start type was at that time.
> >>
> >> "Gary" <admin(a)starksgonzales.com> wrote in message
> >> news:1B5DD9C7-CE8E-4017-87BD-4C45DB95977E(a)microsoft.com...
> >> > This service was installed in a recent auto update on my SBS 2003
> >> > server
> >> > and
> >> > it was installed with automatic startup. But it just starts up and
> >> > shuts
> >> > right back down.
> >> >
> >> > Because of that my daily server report is showing:
> >> >
> >> > Auto-started Services Not Running
> >> >
> >> > Service Name Microsoft .NET Framework NGEN v4.0.30319_X86
> >> >
> >> > Total auto-started services not running: 1
> >> >
> >> > In normal conditions, these services should be running.
> >> >
> >> > For details, it is recommended that you review errors in the
> >> >
> >> > Event log related to the service.
> >> >
> >> > It's a annoyance to have that in the daily server reports. (I want to
> >> > see
> >> > all green items)
> >> >
> >> > I have tried disabling the monitoring of this service via Health
> >> > Monitor
> >> > using the method below but it persists.
> >> >
> >> > Control Panel | Administrative Tools | Health Monitor |
> >> > <yourSBSservername>
> >> > Collector | Service Montior | Browse | (highlight) >. .NET Framework
> >> > NGEN
> >> > v4.0.30319_X86| OK |
> >> > Apply |
> >> >
> >> > You should then see the .NET Framework NGEN v4.0.30319_X86 in:
> >> >
> >> > Server Management | Monitoring and Reporting | Change Alert
> >> > Notification
> >> > --
> >> > Gary
> >>
> >> .
> >>
> .
>
From: Chris Puckett [MSFT] on 13 Jul 2010 16:16
The idea of setting the Microsoft .NET Framework NGEN v4.0.30319_X86 service
to Manual is so that it will not show up in the Performance report as an
automatic startup type service that is not started. It is not to keep that
service in a running state. That service has been designed to stop itself
if it has nothing to do.

The performance report must also be refreshed after the service has been set
to Manual for the red indicator to go away.

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"Gary" <admin(a)starksgonzales.com> wrote in message
news:4B160E01-4070-45B3-BF00-CEAFF7738645(a)microsoft.com...
> It was through WSUS...also setting this service to Manual had not effect
> on
> the red indicator and and could not start the service.
> --
> Gary
>
>
> "Chris Puckett [MSFT]" wrote:
>
>> That behavior is normal for the Microsoft .NET Framework NGEN
>> v4.0.30319_X86
>> service. If there is nothing for it to do it stops itself automatically.
>> It is set to automatic so it can perform some checks at startup.
>>
>> This service is installed by the .NET Framework 4.0 package. If you
>> change
>> the service to Manual, it is possible that future updates for .NET 4.0
>> could
>> change it back to Manual.
>>
>> Your options are:
>>
>> 1. Make a mental note that this is okay to see in the report for this
>> service.
>> 2. Set that service to Manual.
>> 3. Uninstall .NET Framework 4.0.
>>
>> SBS 2003 has no dependencies on .NET 4.0 and this package is not
>> auto-approved for install by default. Do you happen to recall how it got
>> installed? (Was it manually downloaded and installed? Do you use WSUS
>> or
>> do you visit Microsoft Update manually?)
>>
>> --
>> Chris Puckett
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>> "Gary" <admin(a)starksgonzales.com> wrote in message
>> news:466577A3-A777-4916-85BE-7DA3B42B8E86(a)microsoft.com...
>> > Yes, I should have mentioned that I tried that as well using the
>> > network
>> > account then my own admin account attempting various permutations of
>> > automatic, manual and shuttting it off. None worked, no matter what I
>> > did
>> > I
>> > received the same error. The only thing left, I suppose, is to
>> > uninstall
>> > the
>> > update altogether but I am hesistant to do this as subsequent updates
>> > could
>> > have dependancies.
>> >
>> > Thanks
>> > --
>> > Gary
>> >
>> >
>> > "Paul Shapiro" wrote:
>> >
>> >> I see the same thing. I believe that service is intended to optimize
>> >> .Net
>> >> application startup by caching compiled code. Since the server is not
>> >> running applications, I wonder if it is ok to set the startup type to
>> >> manual
>> >> to prevent the daily warning? This service is apparently the .Net 4
>> >> version
>> >> of the service that was called something like .Net Optimization in
>> >> earlier
>> >> ..Net versions. I don't remember what the start type was at that time.
>> >>
>> >> "Gary" <admin(a)starksgonzales.com> wrote in message
>> >> news:1B5DD9C7-CE8E-4017-87BD-4C45DB95977E(a)microsoft.com...
>> >> > This service was installed in a recent auto update on my SBS 2003
>> >> > server
>> >> > and
>> >> > it was installed with automatic startup. But it just starts up and
>> >> > shuts
>> >> > right back down.
>> >> >
>> >> > Because of that my daily server report is showing:
>> >> >
>> >> > Auto-started Services Not Running
>> >> >
>> >> > Service Name Microsoft .NET Framework NGEN v4.0.30319_X86
>> >> >
>> >> > Total auto-started services not running: 1
>> >> >
>> >> > In normal conditions, these services should be running.
>> >> >
>> >> > For details, it is recommended that you review errors in the
>> >> >
>> >> > Event log related to the service.
>> >> >
>> >> > It's a annoyance to have that in the daily server reports. (I want
>> >> > to
>> >> > see
>> >> > all green items)
>> >> >
>> >> > I have tried disabling the monitoring of this service via Health
>> >> > Monitor
>> >> > using the method below but it persists.
>> >> >
>> >> > Control Panel | Administrative Tools | Health Monitor |
>> >> > <yourSBSservername>
>> >> > Collector | Service Montior | Browse | (highlight) >. .NET Framework
>> >> > NGEN
>> >> > v4.0.30319_X86| OK |
>> >> > Apply |
>> >> >
>> >> > You should then see the .NET Framework NGEN v4.0.30319_X86 in:
>> >> >
>> >> > Server Management | Monitoring and Reporting | Change Alert
>> >> > Notification
>> >> > --
>> >> > Gary
>> >>
>> >> .
>> >>
>> .
>>
 | 
Pages: 1
Prev: SBS2003 POP3 Connector error 1056 and 1053
Next: ISA 2004 Question