AutoCAD MEP 2010 2011 : Asks for Installation media when launching a different program
Source: Autodesk Technical Support
I understand that when you launch Carrier HAP, Titus Teams, or Cook Compute-A-Fan, you get a message saying to “Please wait while Windows configures AutoCAD MEP 2011”, and on one computer you get the message “Please wait while Windows Configures Autodesk Revit MEP 2010”, that “The feature you are trying to use is on a CD-ROM or other removable disk that is not available”, and after you put the installation disk in the drive, it gives an error “1334 The file “REVSYP201000F_EL_Adlm.asr” cannot be installed because the file cannot be found in cabinet file x86.cab.”
When this configuration behavior happens at any time other than the initial launch of AutoCAD MEP that configures the user’s account, it indicates that there is some missing file or other change on the system that Windows thinks is affecting MEP. For information about this behavior and suggestions on how to fix it, read the document on our website, located at the link below:
Windows Installer displayed unexpectedly
The 1334 error indicates some problem with reading the installation media. This could be compounded by whatever is calling up the installer in the first place, so once you get the first one fixed and it does not ask for installation media, you will not get the 1334 since you are not calling the process that requires the files. If you ever get the 1334 during a repair install or some other normal installation process outside of this issue, that would be a separate troubleshooting issue to submit for a different troubleshooting process.
Resolution Steps: from Autodesk technical support
To review the steps we took, I checked the event logs just after the install dialogs were launched (and then cancelled) and searched for any messages, either warnings or errors with MSIEXEC as the ‘Source’. When I found the error, I searched to see if there was a particular file or registry key that was being referenced in the error.
After that, when verifying that the file in the error was not present, we initiated the Repair from the Add Remove Programs. To be certain, when the prompt came up to reference the original install media, I browsed out to the mep.msi file on the install media.
Once the Repair had completed, we verified that the secondary installer no longer was triggered when launching the third party applications.
Tech Solutions 