A
Alex
We're pushing out SP2 for Office 2003 via WSUS. The update on only one
client kept failing. In the clients application log were two events from the
MsiInstaller, Event ID: 11311 followed by 1024. The 11311 error was:
Product: Microsoft Office Professional Edition 2003 -- Error 1311. Source
file not found(cabinet): D:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\O1561403.CAB. Verify that the
file exists and that you can access it.
I copied the specified .cab file to the client from another machine and
reran the update. Same problem ensued; however, I found that the file I
copied over had been deleted by the update process. The failing client only
had ~61-62 (can't remember exactly) objects in the MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9 folder compared to 96 objects in
the same folder on a successfully updated clients. So, I renamed the old
folder on the bad client, copied the entirety of the 96 object folder from
the good client. The trick was changing the permissions on the folder. I
only allowed read & execute permissions for the System and Administrator
groups on that folder and sub-items. I believe the system account is what's
used by the update, but figured it wouldn't hurt. Sure enough, worked like a
charm. The update ran through successfully, after which I left the new,
copied folder, but restored the permission. Hope this helps someone, and I'd
be curious to get a comment on this from someone at Microsoft.
client kept failing. In the clients application log were two events from the
MsiInstaller, Event ID: 11311 followed by 1024. The 11311 error was:
Product: Microsoft Office Professional Edition 2003 -- Error 1311. Source
file not found(cabinet): D:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\O1561403.CAB. Verify that the
file exists and that you can access it.
I copied the specified .cab file to the client from another machine and
reran the update. Same problem ensued; however, I found that the file I
copied over had been deleted by the update process. The failing client only
had ~61-62 (can't remember exactly) objects in the MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9 folder compared to 96 objects in
the same folder on a successfully updated clients. So, I renamed the old
folder on the bad client, copied the entirety of the 96 object folder from
the good client. The trick was changing the permissions on the folder. I
only allowed read & execute permissions for the System and Administrator
groups on that folder and sub-items. I believe the system account is what's
used by the update, but figured it wouldn't hurt. Sure enough, worked like a
charm. The update ran through successfully, after which I left the new,
copied folder, but restored the permission. Hope this helps someone, and I'd
be curious to get a comment on this from someone at Microsoft.