Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Package refuses to replicate to Distribution Point

Status
Not open for further replies.

BarryTheSprout

IS-IT--Management
Jan 11, 2005
2
GB
In use - SMS 2.0 SP5 running on W2K Advanced Servers in a three tier heirarchy (Primary <=> Primary <=> Secondary), I have full rights over the second and third tier servers but none at the top level (which serves multiple child sites). SQL is SQL 7.0.

On occasion SMS packages provided by the top level site refuse to replicate to my primary child site. They will, however, replicate to a subsequent (secondary) child site. The Package Status is shown as correct (i.e. Targetted = 2 yet Installed = 1) and if I look at status messages for that package I get the following constantly repeating:

2300 - SMS Distribution Manager is beginning to process...
2342 - SMS Distribution Manager is starting to distribute.
2301 - SMS Distribution Manager successfully processed...

The package does not appear in the SMSpkgG$ directory although .NAL, .ICO and .PKG entries are created in the pkginfo.box directory and do get copied to the CAP. I notice though that the .NAL file doesn't appear to contain any data when others (when viewed in Notepad) contain something along the lines of "MSWNET:["SMS_SITE=XXX"]\\XXXSMS001\SMSPKGG$\TOP001A2\"

Recreating the package at the top level server is not an option as other sites are distributing the package successfully. I have been told that this can be fixed by some judicious editing of the SQL database but am obviously reticent to do this without knowing exactly what to edit and if I'd also need to do any file manipulation within SMS.

Any ideas gratefully received.
 
Update:

I've now looked through the most likely tables in the SMS DB, three of which show inconsistencies for this package when compared to others. Namely PkgServers, PkgStatus and SMSPackages.

Should I manually amend/add the relevant records in these tables? I'm somewhat worried about referential integrity and whether this would confuse the relationship between database and SMS file structure.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top