J
jjmphildav
We have machines in our company that are suddenly experiencing the "looking
for sku011.cab" error when opening Office files. I do not understand why
these machines are suddenly getting errors since they have been using Office
2003 SP1 for almost a year now and I know for sure the LIS was enabled during
the installation ( I even did a random check that the MSOCACHE folder was
created on the root of C:\).
The most frustrating thing for me is that when I went to Google this problem
I found out that there are sooooooooo many people experiencing this (even
with their LIS enabled) and Microsoft does not really have any explanation as
to why this problem is happening randomly. I went to Microsoft website and
found a documentation on how to enable the MSOCACHE using the listool.exe but
no explanation as to why MSOCACHE gets deleted or corrupted.
I hope Microsoft will look into this problem. We have hundreds of in-house
and remote users and I'm just afraid that we are going to get a lot of
Helpdesk calls for this. We do Microsoft updates on our machines on a regular
basis and I hope this is not what is causing the problem. Honestly, this is
the only thing I can think of that is causing it since our users do not have
permission to install on their machine. I have also read that other users
started having this problem after doing Office updates.
for sku011.cab" error when opening Office files. I do not understand why
these machines are suddenly getting errors since they have been using Office
2003 SP1 for almost a year now and I know for sure the LIS was enabled during
the installation ( I even did a random check that the MSOCACHE folder was
created on the root of C:\).
The most frustrating thing for me is that when I went to Google this problem
I found out that there are sooooooooo many people experiencing this (even
with their LIS enabled) and Microsoft does not really have any explanation as
to why this problem is happening randomly. I went to Microsoft website and
found a documentation on how to enable the MSOCACHE using the listool.exe but
no explanation as to why MSOCACHE gets deleted or corrupted.
I hope Microsoft will look into this problem. We have hundreds of in-house
and remote users and I'm just afraid that we are going to get a lot of
Helpdesk calls for this. We do Microsoft updates on our machines on a regular
basis and I hope this is not what is causing the problem. Honestly, this is
the only thing I can think of that is causing it since our users do not have
permission to install on their machine. I have also read that other users
started having this problem after doing Office updates.