Suggested Articles
Search found 10 matches
- Wed Mar 16, 2011 3:21 pm
- Forum: Common Problems
- Topic: Licensed AI still shows trial pop up
- Replies: 4
- Views: 5691
- Jump to post
Re: Licensed AI still shows trial pop up
I guess our fix was only temporary. The dialog that says the installer was built with a trial version of AI is being displayed when the installer is run again. The account set up for the automated build does have a "license80.dat" file in "AppData\Local\Caphyon\Advanced Installer".
- Mon Mar 14, 2011 9:58 pm
- Forum: Common Problems
- Topic: Licensed AI still shows trial pop up
- Replies: 4
- Views: 5691
- Jump to post
Re: Licensed AI still shows trial pop up
We solved the problem by uninstalling AI, installing it for a specific user set up for the automated build, and registered it under that user.
- Fri Mar 11, 2011 9:00 pm
- Forum: Common Problems
- Topic: Licensed AI still shows trial pop up
- Replies: 4
- Views: 5691
- Jump to post
Licensed AI still shows trial pop up
We were testing AI as part of an automated build process running it as command line commands. We were happy with the results and purchased a Professional license. We went through the process registering the install of AI on the build server with the license key sent to us but when the installer is ...
- Fri Mar 11, 2011 3:37 pm
- Forum: Common Problems
- Topic: InstallUtilLib.dll on Windows XP
- Replies: 5
- Views: 8957
- Jump to post
Re: InstallUtilLib.dll on Windows XP
Unfortunately I don't have the old email chain.
- Thu Mar 10, 2011 11:02 pm
- Forum: Common Problems
- Topic: InstallUtilLib.dll on Windows XP
- Replies: 5
- Views: 8957
- Jump to post
Re: InstallUtilLib.dll on Windows XP
Sorry for digging up an old(er) thread, but has there been a solution to this? We have an Advanced Installer installer that works on Vista and Windows 7, but is also seeing problems on XP.
- Mon Sep 13, 2010 4:57 am
- Forum: Common Problems
- Topic: InstallUtilLib.dll on Windows XP
- Replies: 5
- Views: 8957
- Jump to post
InstallUtilLib.dll on Windows XP
My installer works in both Vista and Windows 7, but when run on Windows XP SP3 a pop up appears while "Copying files" that says something like "InstallUtilLib.dll: unkown error". Any ideas on why this may be happening?
- Fri Dec 18, 2009 4:11 pm
- Forum: Common Problems
- Topic: Updater, Auto Close, and MS Office
- Replies: 3
- Views: 3274
- Jump to post
Re: Updater, Auto Close, and MS Office
That doesn't entirely answer my question. I'm not sure what to put in the Edit Auto-Close Application Dialog to find and close Outlook.
- Thu Dec 17, 2009 5:59 pm
- Forum: Common Problems
- Topic: Updater, Auto Close, and MS Office
- Replies: 3
- Views: 3274
- Jump to post
Updater, Auto Close, and MS Office
Is it possible to use the Auto Close functionality to close an MS Office app, such as Outlook?
I have created an Outlook add in and am using Advanded Installer to deploy it. Now I want to add updater functionality to it and need to close Outlook before applying the update. When I stumbled upon the ...
I have created an Outlook add in and am using Advanded Installer to deploy it. Now I want to add updater functionality to it and need to close Outlook before applying the update. When I stumbled upon the ...
- Mon Dec 07, 2009 4:39 pm
- Forum: Common Problems
- Topic: Installer not updating when custom action DLL changes?
- Replies: 13
- Views: 13372
- Jump to post
Re: Installer not updating when custom action DLL changes?
That worked perfectly, thanks for clearing up my confusion.
- Fri Dec 04, 2009 9:49 pm
- Forum: Common Problems
- Topic: Installer not updating when custom action DLL changes?
- Replies: 13
- Views: 13372
- Jump to post
Re: Installer not updating when custom action DLL changes?
Hi Cosmin,
I have tried to create a custom action that is run on install and creates a file (just like what is being done in this thread) to test out the use of custom actions. Unfortunately, I have not gotten this to work yet. You suggested setting the Source Path to <AI_CUSTACTS>dotNetCustAct.dll ...
I have tried to create a custom action that is run on install and creates a file (just like what is being done in this thread) to test out the use of custom actions. Unfortunately, I have not gotten this to work yet. You suggested setting the Source Path to <AI_CUSTACTS>dotNetCustAct.dll ...