SMSNomad: Hash code errors on MS Update scan package

SMSNomad: Hash code errors on MS Update scan package (Full Version)

All Forums >> [Vendor Forums] >> 1E Products

Message

spence03 -> SMSNomad: Hash code errors on MS Update scan package (11/5/2007 11:25:55 AM)
Has anyone seen a tendency for hash code errors (8293) in any specific circumstances, particularly on the MS Update scan package (~10MB)? Some of our sites are getting these errors, and seem to be ok at the beginning of the MS Update scan package but then part way into the P2P distribution process, machines start failing with the 8293 error. This is not happening at all sites, just one or two. The distribution of an empty 30 MB file (made with createfil.exe) works fine under the same conditions. We are using Nomad v 2.2.0.9.

ealdrich -> RE: SMSNomad: Hash code errors on MS Update scan package (11/5/2007 11:41:51 AM)
what are you seeing reported in the Nomad log(s)? There is absolutely NO chance that there was any sort of refresh, update, or anything else remotely close to this that may have occurred on one of the SMS DP's being used as the source for the download? Which machine(s) reported the hash error: The local master or peer client(s)? Possible that local AV client may be scanning the locally cached SNO file(s) causing a hiccup?

spence03 -> RE: SMSNomad: Hash code errors on MS Update scan package (11/5/2007 12:22:51 PM)
The peer clients are reporting the errors. The initial master gets the file from the DP just fine, and starts distributing it ok, but eventually the initial master becomes unavailable. It is only after the Master role has moved to a 2nd or 3rd machine that we are seeing the problem. From the SMSNomad.log file on one of the peer client machines: 10/24/2007 03:05:54.562: Calculating Package Hash 10/24/2007 03:05:54.655: PackageHash failed (WMI)97A0A185EF9E6A34692AF3C239F3F7B3A96413B3!=(Calc)874648047E8837716544D3EC6D753417E57F5D59 10/24/2007 03:05:54.655: FFFChecks5 (0007) 10/24/2007 03:05:54.655: All selected FFF checks completed 10/24/2007 03:05:54.655: Initiating Policy Update.... 10/24/2007 03:05:54.655: CYCLESMS Advanced Client (2.50.4253.3000) 10/24/2007 03:05:54.874: "Request & Evaluate User Policy" result=0 10/24/2007 03:05:54.921: "Request & Evaluate Machine Policy" result=0 hEvtWindoze 10/24/2007 03:05:56.296: LastTriggerTime 20071024030309.375000+000 10/24/2007 03:03:09 10/24/2007 03:05:56.296: Waiting for Policy Update ...never seems to get policy update... 10/24/2007 03:11:02.982: fed up with waiting 10/24/2007 03:11:08.013: Set done "00000002"(5) 99.990% ERROR - (00002065) Package Hash does not match 10/24/2007 03:11:08.278: Returning 00002065 Package Hash does not match 10/24/2007 03:11:08.278: Copy Thread has exitted 8293 10/24/2007 03:11:08.294: Exit returns 00002065 ... I'll be applying one of the updates to try and resolve the policy update issue, and I'm hoping that may help. The DP was refreshed with a new package source version, and the clients caches were deleted prior to the advert, but there was no refresh/update that happened during the distribution. I've re-created the error a few times. Absolutely possible that te local AV client could be scanning the locallyt cached files. Should I exclude the whole nomad cache from the virus scanner? This is happening at one of the larger sites (about 220 active clients) but it is not happening at other larger ones. We are not, and cannot use multicast at any site unfortunately. Thanks!

ealdrich -> RE: SMSNomad: Hash code errors on MS Update scan package (11/5/2007 12:34:01 PM)
This is something that should be directed to our support team ASAP. In the short term I would also exclude the Nomad cache folder from AV scanning to eliminate this as a potential source of problem (unlikely as it is, however! :-( )

bmason505 -> RE: SMSNomad: Hash code errors on MS Update scan package (8/18/2008 1:07:36 PM)
Was a fix ever found for this?

rlauder -> RE: SMSNomad: Hash code errors on MS Update scan package (8/20/2008 4:27:43 AM)
We were running SNOB v2.0.4.1 when we found this issue and (as usual) were advised that the bug was fixed in the latest version. We have been gently rolling out v2.2.1.0 (I wouldn't advise rolling out the latest versions of 1E products too agressively unless you like repeating the process :-( ) and it seems to be doing the job.

SMS_Chan -> RE: SMSNomad: Hash code errors on application (8/21/2008 10:06:56 PM)
SNOmad v 2.5.4.4 still i m getting the Error 8293 ************************************ 21/08/2008 19:52:23.611: Calculating Package Hash 21/08/2008 19:54:01.656: PackageHash failed (WMI)5995304550E58398129F43D9F35041D8D4899E98!=(Calc)0C0C7F46C2AF7DA7A59421008A481DE519DBC68E 21/08/2008 19:54:01.781: All selected FFF checks completed 21/08/2008 19:54:01.796: Initiating Policy Update.... 21/08/2008 19:54:01.796: CYCLESMS Advanced Client (2.50.4160.2000) 21/08/2008 19:54:02.093: "Request & Evaluate User Policy" result=0 21/08/2008 19:54:02.156: "Request & Evaluate Machine Policy" result=0 21/08/2008 19:54:04.827: LastTriggerTime 20080821195318.516000+000 21/08/2008 19:53:18 21/08/2008 19:54:04.890: Delaying 5 seconds 21/08/2008 19:54:09.984: Set done "KOS01D63"(1) 99.990% ERROR - (00002065) Package Hash does not match 21/08/2008 19:54:10.499: Returning 00002065 Package Hash does not match 21/08/2008 19:54:10.515: Copy Thread has exitted 8293 21/08/2008 19:54:10.593: Exit returns 00002065 **************************************************** Could someone help me out ...... Thanks Chan

haga147 -> RE: SMSNomad: Hash code errors on application (8/29/2008 8:48:37 AM)
Update package from source. The error ususally happens when there is a change in the package source. I would also run cachecleaner on your clients if not downloading from DP.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.265625