Office 2013 with Service Pack 1 installation error about "search path"

Question

I have an automated installation technique that has worked fine with Office 2010 Pro Plus (32-bit), incorporating the latest Service Pack into the network administrative installation point (under \updates), adding 10 foreign languages to the network administrative
installation point, creating a custom .msp with the OCT (that goes into \updates too), editing the config.xml files, and then running setup.exe from that network administrative installation point. This works on 32-bit Windows XP clients and on 32- and 64-bit
Windows 7 clients.
For Office 2013 Pro Plus, I have built the network administrative installation point exactly the same way (original DVD files + languages + SP1 updates + config.xml updates), but the installation is failing with every type of client, all with
the same error message. The network administrative installation point is readable by the normal installing account, but I even get the same error when I login as me and initiate setup.exe manually, and I have all rights to this point.
Here's the critical point from a log file:
2014/03/11 11:53:49:691::[2372] DistributionPoint parsed.  The distribution point is now set to: \\archive.ads.college.edu\archive\KBOXalt\Office2013
2014/03/11 11:53:49:691::[2372] COMPANYNAME specified in config.xml.
2014/03/11 11:53:49:691::[2372] USERNAME specified in config.xml.
2014/03/11 11:53:49:800::[2372] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
2014/03/11 11:53:49:910::[2372] Searching for default versions of resource files under the folder [\\archive.ads.college.edu\archive\KBOXalt\Office2013].
2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
Type: 34::InvalidDirectory.
2014/03/11 11:53:50:019::[2372] WER element [SuppressModal] is set to value [true]
2014/03/11 11:53:50:019::[2372] WER element [P4] is set to value [InvalidDirectory]
2014/03/11 11:53:50:019::[2372] Catalyst execution finished: 03/11/2014 11:53:50.  Return code: 30034.  Exception caught: InvalidDirectory.
2014/03/11 11:53:50:019::[2372] PERF: TickCount=894821 Name=RunSetup Description=End function
I cannot find any references to this exact error anywhere on the Internet. Can anyone tell me what this means, and how I fix it?

Answer 1

As automated, the utility that runs setup.exe maps a drive letter to
\\archive.ads.college.edu\archive\KBOXalt using a kboxmap AD account, which has read access to the whole \KBOXalt tree. I used that same kboxmap AD account manually to simulate what the utility does, and hit the same problem. But here's what's
odd: right next to that
\\archive.ads.college.edu\archive\KBOXalt\Office2013 directory is an
\\archive.ads.college.edu\archive\KBOXalt\Office2010 directory, both created the same way, and the Office 2010 installation has always worked perfectly using the kboxmap AD account. I don't understand why Office 2013 is only working for an account with
read/write access, where Office 2010 worked fine for an account with only read access. Especially when the Office 2013 resource kit documentation clearly states that the account running the installation should only have read access, nothing more. (All this
KBOX stuff comes from the fact that our deployment environment is a Dell KACE KBOX 1000. However, that plays no part in the problem: ignoring the KBOX 1000, I can manually recreate the problem every time.)