SMS 2003 SP3 Dist Points missing

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SMS 2003 SP3 Dist Points missing

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> SMS 2003 SP3 Dist Points missing

Page: [1]

Message

<< Older Topic Newer Topic >>

SMS 2003 SP3 Dist Points missing - 7/30/2008 6:18:58 PM

mh958

Posts: 23
Score: 0
Joined: 7/9/2007
Status: offline

Ok, I think I am on the verge of quitting my job :( More sarcasm then not, but I am to losing my mind.

We are running 2 SMS servers but they are both in the same office, MSPSMS01 and MSPSMS02. The 01 server holds the SQL database, and is just there for that reason, everything else runs on the MSPSMS02 server. About 2 months ago we upgraded both servers to SP3, and I am pretty sure the Distribution Points have the SP3 version of the client running on them.

We have a total of 15 distribution points (1 for each of our main offices) but over the coarse of the past month all the distribution points have disappeared from the "Site Status" under the "System Status" area. MSPSMS02 is there along with 3 other distribution points that somehow managed to survive whatever is not happy.

MSPSMS02 won't push any new packages that I create to the missing distribution points, but it replicates fine to the 3 remaining distribution points that still show up in "Site Status".

I have tried removing the DP role on all the distribution points, and waiting 15 minutes, and then re-adding them, I have even let one sit over night, but that doesn't seem to help.

The distmgr.log file shows the following...

Used 0 out of 5 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    6020 (0x1784)
Starting package processing thread,thread ID = B20    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    6020 (0x1784)
Sleep 3600 seconds...    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    6020 (0x1784)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=MSPSMS02 SITE=MP1 PID=4236 TID=2848 GMTDATE=Wed Jul 30 22:13:45.602 2008 ISTR0="Prospect-Max-1-0-R2" ISTR1="MP1001C8" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MP1001C8"    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
No action specified for the package MP1001C8.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
No action specified for the package on server ["Display=\\NTSUNRISE2\"]MSWNET:["SMS_SITE=MP1"]\\NTSUNRISE2\.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
Start adding package to server ["Display=\\NTPHOENIX2\"]MSWNET:["SMS_SITE=MP1"]\\NTPHOENIX2\...    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
No action specified for the package on server ["Display=\\MSPSMS02\"]MSWNET:["SMS_SITE=MP1"]\\MSPSMS02\.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    4928 (0x1340)
Will wait for 1 threads to end.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
Thread Handle = 1468    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    2848 (0x0B20)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=MSPSMS02 SITE=MP1 PID=4236 TID=4928 GMTDATE=Wed Jul 30 22:13:45.649 2008 ISTR0="Prospect-Max-1-0-R2" ISTR1="["Display=\\NTPHOENIX2\"]MSWNET:["SMS_SITE=MP1"]\\NTPHOENIX2\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MP1001C8" AID1=404 AVAL1="["Display=\\NTPHOENIX2\"]MSWNET:["SMS_SITE=MP1"]\\NTPHOENIX2\"    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:45 PM    4928 (0x1340)
Cannot establish connection to ["Display=\\NTPHOENIX2\"]MSWNET:["SMS_SITE=MP1"]\\NTPHOENIX2\    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    4928 (0x1340)
Error occurred, performing error cleanup prior to returning.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    4928 (0x1340)
DP thread with array index 0 ended.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
DP thread with thread handle 1468 and thread ID 4928 ended.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
Updating package info for package MP1001C8    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
The package and/or program properties for package MP1001C8 have not changed, need to determine which site(s) need updated package info.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
StoredPkgVersion (0) of package MP1001C8. StoredPkgVersion in database is 0.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
SourceVersion (2) of package MP1001C8. SourceVersion in database is 2.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=MSPSMS02 SITE=MP1 PID=4236 TID=2848 GMTDATE=Wed Jul 30 22:13:46.181 2008 ISTR0="Prospect-Max-1-0-R2" ISTR1="MP1001C8" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MP1001C8"    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
Failed to process package MP1001C8 after 0 retries, will retry 100 more times    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    2848 (0x0B20)
Used 0 out of 5 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:50 PM    6020 (0x1784)
Sleep 1826 seconds...    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:50 PM    6020 (0x1784)
Used 0 out of 5 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:55 PM    6020 (0x1784)
Sleep 1821 seconds...    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:55 PM    6020 (0x1784)

I have been trying to find help with the part that says

Cannot establish connection to ["Display=\\NTPHOENIX2\"]MSWNET:["SMS_SITE=MP1"]\\NTPHOENIX2\    SMS_DISTRIBUTION_MANAGER    7/30/2008 5:13:46 PM    4928 (0x1340)

but everything people say to try doesn't seem to help. Why are 3 DP's working fine, but the other 12 have this error?

We are running advanced security, and the MSPSMS02 (SMS Server) is a Domain Admin.

Any ideas?
Please help my sanity :)

-Mike

Post #: 1

RE: SMS 2003 SP3 Dist Points missing - 7/30/2008 7:04:16 PM

skissinger

Posts: 2167
Score: 135
Joined: 9/13/2001
From: Sherry Kissinger
Status: offline

"Cannot establish connection to " .... what have you tried? My first suggestion would be to confirm that the Primary site server is in the local Administrators group on NTPHOENIX2

I know, I know, MSPSMS02 is a domain admin. But add it in there individually as well. We're troubleshooting, right?

_____________________________

mofmaster@smsexpert.com (version 2007) | http://www.smsexpert.com | http://www.sccmexpert.com
My Blog
Microsoft MVP - ConfigMgr

(in reply to mh958)

Post #: 2

RE: SMS 2003 SP3 Dist Points missing - 7/30/2008 9:28:37 PM

mh958

Posts: 23
Score: 0
Joined: 7/9/2007
Status: offline

Both servers are in the local admin group on the servers/dp's

Here is another error, the dp's show up in Site Status every once in a while with a critical icon next to them.

SMS Site System Status Summarizer still cannot access storage object "\\NTCHICAGO2" on site system "\\NTCHICAGO2". The operating system reported error 2147942464: The specified network name is no longer available.

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 "7/30/2008 8:01:04 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 am pretty sure it is a rights issue. It is just strange that security is the same on all the dp's and that 3 still talk while the rest don't anymore.
If I open the SMS Admin console, and open Site Hierarchy, Site Settings, Connection Accounts, there is an account under "Client" that is used for client pushes, but there is no account under "Site System" is there supposed to be a SMSNetworkAccess type account in there, or do some installations not have one in there?

Thanks for the help BTW.

(in reply to skissinger)

Post #: 3

RE: SMS 2003 SP3 Dist Points missing - 8/1/2008 9:57:51 AM

mh958

Posts: 23
Score: 0
Joined: 7/9/2007
Status: offline

Another thing I tried today, after searching for others that have similar problems.
I went to the physical server and did ( at time /interactive cmd )
and mapped a drive letter to a distribution point that is still functional, and I can access the smspkgd$.
If I map a drive letter to a DP that no longer is showing up in my Site Status, I get
"The specified network name is no longer available" and I can't access the drive.
They are both Domain Controllers, and if I look at the security on the smspkgd$ share on both
servers they are the exact same.

< Message edited by mh958 -- 8/1/2008 10:18:12 AM >

(in reply to mh958)

Post #: 4

RE: SMS 2003 SP3 Dist Points missing - 8/20/2008 2:48:39 PM

mh958

Posts: 23
Score: 0
Joined: 7/9/2007
Status: offline

This thread is closed, and I found my issue is permission related.
Quite possibly service pack related.

New thread is here

http://www.myitforum.com/forums/m_184570/mpage_1/key_/tm.htm#184570

-Mike

< Message edited by mh958 -- 8/20/2008 3:06:23 PM >

(in reply to mh958)

Post #: 5