Hi,
I have two servers, one is the site server and has a few roles inc MP, another also has a few roles inc MP
I'm seeing the above error for both servers - where to start looking?
Peter
Technology Tips and News
Hi,
I have two servers, one is the site server and has a few roles inc MP, another also has a few roles inc MP
I'm seeing the above error for both servers - where to start looking?
Peter
Seeing things like this in that log:
***Where server.domain has replaced by actual server name***
Warn>: The Site Object "["Display=\\server.domain\"]MSWNET:["SMS_SITE=GLB"]\\server.domain\" on "["Display=\\server.domain\"]MSWNET:["SMS_SITE=GLB"]\\server.domain\" has not been accessable for 168 hours. It will be deleted. The role of the site object is
omGetServerRoleAvailabilityState could not read from the registry on server.domain; error = 6:
No obvious errors when using configmgr, but would like to get to the bottom of this.
Have 1 Primary server with following roles:
A Second server with the following roles:
Two SUP servers behind a Load balancer, and our DB is on a dedicated SQL cluster (2 nodes)
Have you manually troubleshot connectivity from the site server to these site systems? Things like pining them by FQDN, connecting to admin shares, etc.?
Hi Peter,
We are seeing the same warning and error messages in our SCCM 2012 infrastructure.
The first warning message "Site System Status Summarizer has not been able to access the storage object \\FQDN..." is only on the site server with the MP role.
We are seeing the "could not read from the registry on FQDN; error = 6" on all of our DPs.
Did you resolve either of these?
Davis
Same any found a solution?
SCCM2012
Site System Status Summarizer has not been able to access the storage object "siteserver" on Site Object "SITEServer" for 168 hours.
Site System Status Summarizer will now assume that you no longer intend to use the storage object and will no longer monitor the storage object.
This product appears to have more issues tham SMS 2.0
I'm having the same exact information status messages Master_Cheif. It would be greate to know if Peter or anyone else ever found out the issue.
I ended up opening a case with MS and they said there was a registry key missing and had me manually create it. Using the DP role as an example, the reg key would be:
HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\SMS Distribution Point
Name: Availability State
Type: REG_DWORD
Data: 0
That fixed it for me.
Sorry it's been a while since I've been here but this sort of worked for me. It did and it didn't. I now get the same old error of not able to access the storage for my one DP that I applied this RegKey to but it also reports that it detected the storage object and it's low on space. Do I need to reboot the DP or can you confirm the regkey I've created below is correct syntax.
HKLM\SOFTWARE\MICROSOFT\SMS\OPERATIONS MANAGEMENT\SMS SERVER ROLE\SMS DISTRIBUTION POINT\Availability State
REG_DWORD = 0
I don't know as I don't think I've distributed anything since I added this Reg key. I will have to get back with you on Tuesday as I've left the office. Thank you BrianG for your quick replies and I look forward to following up next week.
I'm seeing this error on a productive SQL Cluster Node in connection with Reporting Services at the moment.
I've got a CAS - PRI - SEC environment with the Databases for CAS and PRI hosted on an SQL Cluster. The problem is originating from the CAS trying to access a drive on it's respective SQL Cluster Node hosting the reporting services.
I've checked the following things:
- Ports (80, 135, 443, 445, 1433, 4022)
- Permissions (Computer Account has full permissions in SQL and local Admin on all Cluster Nodes, Reporting Services Account has rights on DB and the folder)
- RegKey mentioned in this thread (for reporting services of course ;-)) (Regkey is there on the Node hosting the reporting services)
I've currently no idea what else to look at. It's not impacting the Default reports, but custom made reports cannot be run, showing an error for the shared datasource/Sharepoint Website.
Any ideas what else I could check?
Cheers,
Fred
Spot on!: When I added the registry key the log showed the following message:
Site System Status Summarizer detected that the availability of the "Distribution point" role on server "<Servername>" has changed to Online.
Maybe it is only for reporting purpose in the SCCM console, distribution was no issue before in my case.
Wow! That registry entry seems to have fixed a similar problem for me too, and we're running R2 SP1!
Out of the blue, I could not update a software updates package on any DPs, and saw the "Site System Status Summarizer has not been able to access the storage object" message in the DP status messages.
After adding the registry entry to both my DP's and rebooting them, they immediately began to download the package.
What was frustrating was that distmgr.log, and status messages for Content Distribution Manager gave no indication of a problem. Also, the "not able to access the storage object" status messages were only classified as "Information",
so a glance at the status of all the components and roles gives no indication of any problem.
I see there is a CU1 for R2 SP1 which hopefully contains a fix for this bug.