/build/static/layout/Breadcrumb_cap_w.png

Installer error 2753

One of the user’s experiences an error which i am not able to replicate during testing. I have a CA to set permissions using cacls.exe. However one user generating a 2753 error on calcs.exe.
2753 The File '[2]' is not marked for installation.
Fixed the problem by changing the permissions manually. Just wanted to know what could trigger this error?

Thank you.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: Coriolus 13 years ago
Orange Belt
0
I would duplicate the problem and during the procedure have PROCMON running to capture the error, this way you will get a more accurate look at what is going on.
Posted by: jonaman_17 12 years ago
Yellow Belt
0
will the windows cleanup utility be able to resolve this issue?
will tha patch be able to delete the previous windows install
Posted by: anonymous_9363 12 years ago
Red Belt
0
ORIGINAL: jonaman_17
will the windows cleanup utility be able to resolve this issue?
will tha patch be able to delete the previous windows install
If you had used the tools available here on AppDeploy, in this case the 'MSI Error's look-up page http://itninja.com/question/help-with-msi-132779,you would see that the error is connected with the installation packge, not Windows, so any clean-up exercise would be pointless.
Posted by: ihudson 10 years ago
Yellow Belt
0
Got error 2753 the file 'swdnld.exe' is not marked for installation when trying to manually install shockwave player version 11.5.9. I renamed the file swdnld.exe to swdnld.exe.old then rebooted and reinstalled Shockwave.msi Player w/o issues.
Posted by: P4Packager 9 years ago
Yellow Belt
0
Issue:: Error 2753 the file 'xxx.exe' is not marked for installation
Scenario:: Your machine has application X version 1.0 (x_1.0)already installed and you are trying to reinstall it or upgrading it with application x version 1.2(x_1.2)
Cause:: In above scenario it is possible that application x_1.2 is trying to overrite xxx.exe but cud not do so.
Investigation:: install and uninstall x_1.0 and check for xxx.exe getting removed or not.(In my case it was not getting removed.Hence I was receiving err 2753)
Solution:: Write a custom action to delete folder containing xxx.exe and make this as Immediate/Deffered custom action (Synchronous ignore exit) and put this custom action Just after Costinitialize Custom action. (NB.this is important)

I solved this error in above scenario.[8D]

[8|]Please note , scenario may differ .above error is linked to Custom action .In my case it was linked to Custom action related to XXX.exe.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ