SMS Deployment Error 1335
Hi,
I m trying to deploy MS Visio 2003 using SMS. It gives me an error related to a particular cab file which also appears in the source. I can only guess that the error reported is due to the fact that the said file is corrupted.
Could you guys help me if any one of you have faced similar problems. Or is it a typical case with a typical solution for MS applications.
Cheers :)
I m trying to deploy MS Visio 2003 using SMS. It gives me an error related to a particular cab file which also appears in the source. I can only guess that the error reported is due to the fact that the said file is corrupted.
Could you guys help me if any one of you have faced similar problems. Or is it a typical case with a typical solution for MS applications.
Cheers :)
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
dunnpy
17 years ago
India_Repackaging,
It does appear that the installation file/s may be corrupted looking at the error provided.
Microsoft offer a couple of suggestions below:
Error message during Office 2000 or Office XP installation: "Error 1335 - Cannot Copy Cab File Office1.cab"
As you're using SMS to deploy, did it all work correctly when you were developing your transforms file? Assuming you are using a transforms file to customise your installation.
Basically my question is "does it work outside of the SMS environment?"
Could it be that a corrupt copy of the files was copied up to the SMS server, or the SMS has corrupted the installation files when copying them to the distribution points (very unlikely, but a possibility all the same)?
Hope that gives you somethings to consider,
Thanks,
Dunnpy
It does appear that the installation file/s may be corrupted looking at the error provided.
Microsoft offer a couple of suggestions below:
Error message during Office 2000 or Office XP installation: "Error 1335 - Cannot Copy Cab File Office1.cab"
As you're using SMS to deploy, did it all work correctly when you were developing your transforms file? Assuming you are using a transforms file to customise your installation.
Basically my question is "does it work outside of the SMS environment?"
Could it be that a corrupt copy of the files was copied up to the SMS server, or the SMS has corrupted the installation files when copying them to the distribution points (very unlikely, but a possibility all the same)?
Hope that gives you somethings to consider,
Thanks,
Dunnpy
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
