Custom Actions using cached vbs file... I can't find it - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Speebs
Posts: 4
Joined: Thu Aug 06, 2009 7:18 am

Custom Actions using cached vbs file... I can't find it

Please help me! I am incredibly frustrated.

I had a package that was working just fine a few days ago. I have a custom action set to run, and it's a simple VBS script that deletes leftover registry keys. The script works fine when run outside of the installation package.

Today, I made a change to the EULA and product code, and tried to run through the installer, and suddenly it wasn't able to complete and I got the message "A script required for this installation cannot be found". I verified that the VBS script works, changed some text in the dialog it displays, and recompiled the MSI. IT CONTINUED TO RUN THE OLDER VERSION OF THE VBS FILE. I deleted the custom actions, looked in the AIP file to see if there were any references to VBS files (there weren't), and recompiled again. It is still running the old VBS! I can't imagine where it is coming from. I am pulling my hair out. Does anyone have any ideas? I need this to work because the update I made to my software is crucial, and right now I can't send out the update.

Thanks,
Doug
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Custom Actions using cached vbs file... I can't find it

Hi,
It is still running the old VBS! I can't imagine where it is coming from
You can try deleting the cache file created by the previous builds and then rebuild the package.
"A script required for this installation cannot be found".
This error also occurs when you try to run from a custom action a script that is going to be installed on the target computer. If you try to run it before the installation has copied the script and the other files to their destination folder the error will rise.

However, for deleting e registry key you don't need a VBscript, you can use the New Value Removal option offered by AI from the Registry page.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Speebs
Posts: 4
Joined: Thu Aug 06, 2009 7:18 am

Re: Custom Actions using cached vbs file... I can't find it

Thanks- I forgot to mention that I did delete all of the cache folders and continued to have the problem. I copied the AIP file and compiled it on another computer, and it worked fine. AI is clearly using a cached copy from SOMEWHERE, but I can't find it referenced and don't know where it could be hiding. I'm not sure what else to try as the problem machine is my main development computer.

Also, I am running a separate script for the registry keys because I need to ask the user whether to delete them or leave them there.

Thanks again,
Doug
Speebs
Posts: 4
Joined: Thu Aug 06, 2009 7:18 am

Re: Custom Actions using cached vbs file... I can't find it

After testing with another machine, I've decided that AI is compiling the MSI file just fine, and it's Windows that is using a cached MSI when I try to run it. I can't for the life of me find the MSI it is actually using though. Does anyone have any ideas? This sucks!
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Custom Actions using cached vbs file... I can't find it

Hi,

You can try using Windows Installer Cleanup Utility or the "MsiZap.exe" tool from the Windows SDK to remove any traces of your program installation.

Please note that these tools remove only the Windows Installer information for the package, the installed resources must be removed manually.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Speebs
Posts: 4
Joined: Thu Aug 06, 2009 7:18 am

Re: Custom Actions using cached vbs file... I can't find it

Bogdan wrote:Hi,

You can try using Windows Installer Cleanup Utility or the "MsiZap.exe" tool from the Windows SDK to remove any traces of your program installation.

Please note that these tools remove only the Windows Installer information for the package, the installed resources must be removed manually.

Regards,
Bogdan
_______________
Mitrache Bogdan
Advanced Installer Team
http://www.advancedinstaller.com/
Thanks... I actually tried that this morning before remembering this thread, and it worked. I'm not sure why I hadn't thought of that before. I'm all set now. Thanks all!

Return to “Common Problems”