Deploying Office 2003 via Task Sequence fails but advertisement of same app works

All Replies

• Friday, October 12, 2007 9:49 PMCathy Moya [MSFT]

   
  

  0

  Sign In to Vote

  I am moving this to the OSD forum because it installs OK with regular software dist. There will probalby be someone here who can parse the log and help you.

   

   

   

  • Reply
  • Quote

   
• Saturday, October 13, 2007 1:53 PMTroyM

   
  

  0

  Sign In to Vote

  The "hash" that is being verified between the two examples above are different.  If these were in-fact the same package, I would expect the hashes to be the same.

   

  Also, is it possible you modified the package "directly" on the DP, without modifying the "source" first and then updating all the DP's, generating a new version?

   

  Are you sure these are the same package?  Verify again that your task sequence is running the same package...

  • Reply
  • Quote

   
• Monday, October 15, 2007 7:14 AMRisk01

   
  

  0

  Sign In to Vote
  Thanks for your response.
  
  I will pass the comments on to my colleagues and get them to verify the details you mentioned.

   

  • Reply
  • Quote

   
• Tuesday, October 16, 2007 6:34 AMRisk01

   
  

  0

  Sign In to Vote

  My colleagues tested the process again and the same results occured:-

   

  the behaviour is still the same and the logs contain the same error messages…

  I double checked task sequence and advertisement: they are both using the same program and package.

   

  Any suggestions would be extremely welcome.

   

  Thanks

  • Reply
  • Quote

   
• Monday, October 29, 2007 12:05 AMkwacky1

   
  

  0

  Sign In to Vote

  In the lines above that log snippet you should be able to see what account the task manager is using to connect to the source.

   

  Is it using http, the computer account or the network access account?

   

  • Reply
  • Quote

   
• Monday, October 29, 2007 10:22 AMRisk01

   
  

  0

  Sign In to Vote

   

  The TS manager appears to be using HTTP to connect to the source. I've pasted some lines from the log file. It appears to download the package using HTTP, completes 100% but then states that the hashes are different. The log file then tries to resolve the source and fails. This is not something odd like when booting with PXE, it cannot resolve the DP, but on the otherhand, at some point it can resolve the server because it downloaded the source - confused???
  
  <![LOG[Downloaded file from http://tstmsm01.t-axa-de.intraxa:80/SMS_DP_SMSPKGD$/DE100017/Office2003_Standard_MFI.MST to C:\_SMSTaskSequence\Packages\DE100017\Office2003_Standard_MFI.MST ]LOG]!><time="13:12:55.284+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="downloadcontent.cpp:1167">
  <![LOG[Downloaded file from http://tstmsm01.t-axa-de.intraxa:80/SMS_DP_SMSPKGD$/DE100017/PRO11.MSI to C:\_SMSTaskSequence\Packages\DE100017\PRO11.MSI ]LOG]!><time="13:12:56.187+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="downloadcontent.cpp:1167">
  <![LOG[Downloaded file from http://tstmsm01.t-axa-de.intraxa:80/SMS_DP_SMSPKGD$/DE100017/README.HTM to C:\_SMSTaskSequence\Packages\DE100017\README.HTM ]LOG]!><time="13:12:56.207+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="downloadcontent.cpp:1167">
  <![LOG[Downloaded file from http://tstmsm01.t-axa-de.intraxa:80/SMS_DP_SMSPKGD$/DE100017/SETUP.HTM to C:\_SMSTaskSequence\Packages\DE100017\SETUP.HTM ]LOG]!><time="13:12:56.247+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="downloadcontent.cpp:1167">
  <![LOG[Downloaded file from http://tstmsm01.t-axa-de.intraxa:80/SMS_DP_SMSPKGD$/DE100017/SETUPPRO.EXE to C:\_SMSTaskSequence\Packages\DE100017\SETUPPRO.EXE ]LOG]!><time="13:12:56.337+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="downloadcontent.cpp:1167">
  <![LOG[Download done setting progress bar to 100]LOG]!><time="13:12:56.337+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="downloadcontent.cpp:1172">
  <![LOG[Hash could not be matched for the downloded content. Original ContentHash = 1BE2E22A418C44ED167C3211EF01453610593718, Downloaded ContentHash = 74895D7BC10FB5E4F8BF1C17842FAD2A3580F5EE]LOG]!><time="13:13:54.419+-120" date="10-11-2007" component="InstallSoftware" context="" type="3" thread="3736" file="downloadcontent.cpp:1336">
  <![LOG[0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2268)]LOG]!><time="13:13:54.419+-120" date="10-11-2007" component="InstallSoftware" context="" type="0" thread="3736" file="resolvesource.cpp:2268">
  <![LOG[DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, sDestination, dwFlags, L"", 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2336)]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="0" thread="3736" file="resolvesource.cpp:2336">
  <![LOG[DownloadContentLocally(pszSource, sSourceDirectory, dwFlags), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2422)]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="0" thread="3736" file="resolvesource.cpp:2422">
  <![LOG[TS::Utility::ResolveSource(pszPkgID, sContentLoc), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,144)]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="0" thread="3736" file="installsoftware.cpp:144">
  <![LOG[Failed to resolve the source for SMS PKGID=DE100017, hr=0x80091007]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="3" thread="3736" file="installsoftware.cpp:144">
  <![LOG[GetContentLocation(pszPkgID, m_bPkgContainSrcFiles, sContentLocation), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,704)]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="0" thread="3736" file="installsoftware.cpp:704">
  <![LOG[Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\DE100017]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="1" thread="3736" file="resolvesource.cpp:2687">
  <![LOG[The user tries to release a source directory C:\_SMSTaskSequence\Packages\DE100017 that is either already released or we have not connected to it]LOG]!><time="13:14:01.219+-120" date="10-11-2007" component="InstallSoftware" context="" type="2" thread="3736"

  • Reply
  • Quote

   
• Monday, October 29, 2007 10:16 PMkwacky1

   
  

  0

  Sign In to Vote

  I was comparing that log snippet to my own TS, where I am also deploying Office 2003.

   

  Download done setting progress bar to 100

  Content successfully downloaded at D:\_SMSTaskSequence\Packages\...

  SMS PkgID '...' resolved to location D:\_SMSTaskSequence\Packages\...

   

  What download settings is set on your package, are you using Binary Differential Replication for example?

  • Reply
  • Quote

   
• Tuesday, October 30, 2007 11:24 AMRisk01

   
  

  0

  Sign In to Vote

   

  Settings that have been set for the package are:-

   

  Package contains source files

  Always obtain files from the source directory

  enable binary differential replication

   

  Access the distribution folder through common ConfigMgr package share

   

  Automatically download content when packages are assigned to BDP's

  Make this package available on protected DPs

   

  Use package properties for status MIF matching

   

   

  Thanks for the assistance!

   

  • Reply
  • Quote

   
• Tuesday, October 30, 2007 11:44 PMkwacky1

   
  

  0

  Sign In to Vote

  Would you be able to test without 'binary differential replication'?

  In one of the TechEd presentations for SCCM there was mention the 'binary differential replication' was not recommended for packages that contain small files and office 2003 contians a lot of small files.

   

  regards,

   

  Simon

  • Reply
  • Quote

   
• Wednesday, October 31, 2007 7:50 AMRisk01

   
  

  0

  Sign In to Vote
  I can ask the team to test this, but surely would the same problem not also occur for the normal advertisement as well, seeing that it uses the same package?
  
  When the package is used by the advertisement. it installs successully and its using the same settings.

   

  • Reply
  • Quote

   
• Wednesday, October 31, 2007 1:19 PMMikaelP

   
  

  0

  Sign In to Vote

  Hi,

   

  We are getting the same kind of error in a task sequence.

  This is in an osd build TS for xp and vista.

  A normal adv./distr. works in the same environment.

   

  /Mikael

   

  Part of the smsts.log:

   

   

  "<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,566)]LOG]!><time="14:55:15.070+-120" date="10-31-2007" component="TSMBootstrap" context="" type="0" thread="1588" file="ccmxml.h:566">
  <![LOG[PackageHash.SDMPackage node not found in the policy assignment property PRG_Requirements.]LOG]!><time="14:55:15.070+-120" date="10-31-2007" component="TSMBootstrap" context="" type="0" thread="1588" file="tspolicy.cpp:1924">"

   

   

   

  • Reply
  • Quote

   
• Wednesday, October 31, 2007 10:33 PMkwacky1

   
  

  0

  Sign In to Vote

  Is the normal Office advertisement set to Download and Run or does it run from the distribution point.  If it is running from the distribution point then you would defenitely get a different result, possibly the result we're looking for.

   

  I'm just trying to understand why Office in your environemnt is performing hash verification during the TS, whereas in my environment it does not.

   

  regards,

   

  Simon

  • Reply
  • Quote

   
• Monday, November 05, 2007 12:45 PMMikaelP

   
  

  0

  Sign In to Vote

  Hi,

   

  This was an OSD build TS.

   

  However was the problem solved when this environment could be updated with CM AD schema.

  Earlier was only Wins used.

   

  • Reply
  • Quote

   
• Monday, November 05, 2007 3:08 PMRisk01

   
  

  0

  Sign In to Vote

  The Advertisement is configured to download the package and run locally, so I don't think it's that causing a problem.

  • Reply
  • Quote

   
• Monday, November 05, 2007 3:09 PMRisk01

   
  

  0

  Sign In to Vote

  This particular problem is with my german colleagues. I believe that they have upgraded the AD schema but I will double check with them.

  • Reply
  • Quote

   
• Tuesday, November 06, 2007 8:54 AMRisk01

   
  

  0

  Sign In to Vote
  The schema was updated before we installed ConfigMgr so again, I don't think it is this causing the problem.

   

  • Reply
  • Quote

   
• Wednesday, April 02, 2008 3:23 PMEric Krause

   
  

  0

  Sign In to Vote

   

  Did you ever find the answer, we are experiencing the same problem.

   

  Eric

  • Reply
  • Quote

   
• Wednesday, April 02, 2008 6:08 PMMikaelP

   
  

  0

  Sign In to Vote

  When you get the "packagehash" error in smsts.log it is usually solved by updating the DP again

   

  • Reply
  • Quote

   
• Wednesday, April 02, 2008 6:17 PMEric Krause

   
  

  0

  Sign In to Vote
  The package deploys fine and a single advertisement, but when added to a task sequence I start getting the hash error.

   

  • Reply
  • Quote

   
• Thursday, April 03, 2008 7:10 AMRisk01

   
  

  0

  Sign In to Vote

  In our situation, even though the package deployed fine on its own when it was advertised, the problem was something odd with the package on the distribution point.
  
  We tried refreshing the package and also updating the package but neither of these made any difference. In the end, we had to delete the package from the DP, so it was completely removed and then re-distributed the package out to the DP again.
  
  This resolved the problem for us. We didn't find out what the underlying problem was, apart from an issue with the package integrity. I don't know why the refresh or update didn't fix the problem, but the issue was resolved and we haven't seen the problem since.

  • Reply
  • Quote

   
• Friday, September 05, 2008 8:51 AMVyacheslavS

   
  

  0

  Sign In to Vote
  At me precisely same problem. The package deploys fine and a single advertisement, but when added to a task sequence I start getting the hash error. (Source for Package Office 2003 Administrative Install)
  • Reply
  • Quote

   
• Monday, September 08, 2008 9:54 AMVyacheslavS

   
  

  0

  Sign In to Vote
  Problem resolved.
  Create new package. Source from administrative install distributive. No other from default settings package. Create new program. Create DP.
  
  TS complete no errors.
  

  • Marked As Answer byNathan BarnettMSFT, ModeratorMonday, February 23, 2009 10:46 PM
  •  
  • Reply
  • Quote

   
• Friday, September 12, 2008 2:05 PMKeith H

   
  

  0

  Sign In to Vote
  This is quite annoying and affecting us also.  Yes recreating the package works, but wastes a lot of time during testing.  Surely there should be a fix for this?  Wally??

   

  • Reply
  • Quote

   
• Friday, September 12, 2008 2:53 PMMikaelP

   
  

  0

  Sign In to Vote

  One thing.

  Make sure that the under the Program-"Advanced" that the setting "Allow this program to be run within a tasksequence" is set.

   

  • Marked As Answer byNathan BarnettMSFT, ModeratorMonday, February 23, 2009 10:46 PM
  •  
  • Reply
  • Quote

   
• Friday, November 06, 2009 4:46 PMBatmanInTheHood

   
  

  0

  Sign In to Vote
  I am having the same problem.  Let me make sure I have your steps right.
  
  1. Create a new package from Enterprise CD
  2. Create an administrative installation with the service packs
  3. Create the install with no transforms and take defaults....
  
  I don't understand "No other from default settings package."
  
  Does this mean don't install settings besides the default settings?  Can I still use an MST file?
  
  My package works, but when I run in a task sequence, it fails... It doesn't even run the install command....  On our other test boxes it works, but when you start Office it is asking for the MSI and can't find it.
  
  • Reply
  • Quote