Site system status (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

betemtl -> Site system status (4/28/2008 11:48:12 AM)

Hi,

every 1 of 2 days I obatain the following critical messages on my site system status.

ConfigMgr componenet server is critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr fallback status pointis critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr nabagement point is critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr PXE service point is critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr reporting point is critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr server locator point is critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr Site Server is critical. total, free, %Free, Availability are all set to unknown.
ConfigMgr software update point is critical. total, free, %Free, Availability are all set to unknown.

I have the following message:

SMS Site System Status Summarizer still cannot access storage object "\\{computername}\d$\Program Files\Microsoft Configuration Manager" on site system "\\{computernmae}". The operating system reported error 2147943530: Not enough server storage is available to process this command.
Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
Possible cause: SMS Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object.
Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to connect to the site system and access the storage object.
Possible cause: Network problems are preventing SMS Site System Status Summarizer from connecting to the site system.
Solution: Investigate and correct any problems on your network.
Possible cause: You took the site system out of service and do not intend on using it as a site system any more.
Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the SMS Administrator console.
Possible cause: You accidentally deleted the storage object or took the storage object out of service.
Solution: The SMS components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other SMS components to verify that this occurs properly.
The storage object has been inaccessible since "4/27/2008 6:00:01 PM". When you correct the problem and SMS Site System Status Summarizer successfully accesses the storage object, SMS Site System Status Summarizer will set the storage object's status to OK, providing that the storage object has sufficient free space.

------------------------------------------------------------
I do NOT have any network issues. I have 250GB of free space.
Everytime I reboot my server it works for 1 or 2 days, then the problem comes back.


According to Microsoft EVENT ID 2011: antivirus software may cause event ID 2011

I am ruinning symantec antivirus on this system

They recomment to increase the IRPStackSize in the registry. Which I have already done.

Can someone please help me out

Thanks



phaustein -> RE: Site system status (4/28/2008 12:48:40 PM)

Is the site server in question a child site or the central site?



betemtl -> RE: Site system status (4/28/2008 12:49:48 PM)

HI,

its a Central site. Primary site

thanks



nenglish -> RE: Site system status (4/29/2008 9:09:26 AM)

Hi there

I am having exactly the same issue. It tends to happen at 4am on my server every few days. I am running SCCM on Windows 2003 x64 with 4GB Ram and plenty of SAN attached storage space.

A reboot cures the issue for another few days. The fact it happens at 4am exactly indicates it is not a random thing.

Also not running any Anti Virus software.

Norman



phaustein -> RE: Site system status (4/29/2008 9:35:30 AM)

Take a look at your sitestat.log, sitecomp.log and smsprov.log for any errors and also try and match up the times the events have occured in the logs as well.  It would be interesting to see what is going on around that time.



betemtl -> RE: Site system status (4/29/2008 10:20:37 AM)

HI,

I checked sitestat.log, sitecomp.log and smsprov.log and no error msgs reported.

Can I check anythign else?

thanks



phaustein -> RE: Site system status (5/2/2008 7:49:52 PM)

Do you have anything in your windows event logs that may correspond with the times these events occurs? Did you restart the server or the server service after making the registry change? Does the sms executive service or sms component manager restart around that time?



betemtl -> RE: Site system status (5/5/2008 1:43:47 PM)

yes, I did restart the server after performing the registry changed.

SCCM worked fine after a while and the same problem comes back after a few days.

I did find the following error message on event viewer under Application: Not sure if these messages are related to my problem.
Login failed for user "NT Authority\system'.(client xxx.xxx.xx.)
event ID 18456

also
the Open Procedure for service "WDSServer" in DLL "C:\WINDOWS\system32\wdssrv.dll" failed. Performance data for this service will not be available. The status code returned is the first DWORD in the attached data, Event ID 1008.

another message is:

The configuration infomration of the performance library "C:\WINDOWS\system32\perfts.dll" for the "TermService" service does not match the trusted performance library information stored in the registry. the functions in this library will not be treated as trusted.

another message:

The configuration infomration of the performance library "C:\WINDOWS\system32\infoctrss.dll" for the "InetInfo" service does not match the trusted performance library information stored in the registry. the functions in this library will not be treated as trusted.

another message:

The configuration infomration of the performance library "C:\WINDOWS\system32\aspperf.dll" for the "ASP" service does not match the trusted performance library information stored in the registry. the functions in this library will not be treated as trusted.

thanks for your help



phaustein -> RE: Site system status (5/5/2008 7:00:27 PM)

For the Termservice, inetinfo & APS counters use the below to remedy
Termservice:
lodctr /T:TermService

Inetinfo & APS:
unlodctr w3svc
unlodctr msftpsvc
unlodctr asp
unlodctr inetinfo
lodctr w3ctrs.ini
lodctr ftpctrs.ini
lodctr axperf.ini
lodctr infoctrs.ini




jkuta -> RE: Site system status (5/15/2008 11:32:12 AM)

I had this exact same issue but it was only occuring on my secondary site servers.  (Dell 1850's & 1950's which are also domain controllers)
I opened a support ticket with Microsoft Professional Support Services and this was the solution:

Create a new DWord registry entry called IRPStackSize in the following subkey:
HKLM\System\CurrentControlSet\Services\LanManServer\Parameters
Set the decimal value to 15
Restart server.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.2351074