I have installed an upgrade to my app, which appeared to complete successfully.
The 1st time I went to launch it, I got a message saying "Please wait while Windows Installer configures Best Authority" (Best Authority is my app). This was followed by a message box: "Error 1706: No valid source could be found for product Best Authority. Windows Installer cannot continue."
This setup kit has worked on other machines.
How can I find out what file WI thinks is in need of repair?
I did a logged boot -- I've zipped & attached the log, in case it might help.
Application Launches Windows Installer -- why?
-
- Posts: 32
- Joined: Mon Mar 13, 2006 3:36 pm
- Location: Leesburg, VA
- Contact:
Application Launches Windows Installer -- why?
Fletcher James
-
- Posts: 32
- Joined: Mon Mar 13, 2006 3:36 pm
- Location: Leesburg, VA
- Contact:
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
That's very strange - should only happen if you are using advertised shortcuts and/or filetypes, and if the target of a shortcut and/or filetype has become compromised (missing, corrupt, moved, etc)
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
-
- Posts: 32
- Joined: Mon Mar 13, 2006 3:36 pm
- Location: Leesburg, VA
- Contact:
Mystery most likely solved
This was a machine (VM) on which we had installed several prior versions of our product. Some of those kits were built with "Product W", at a time when the developer didn't have coherent instructions for setting Package Code and Upgrade Code. Examining the Control Panel | Add/Remove Programs list, I found two products listed as "Best Authority".
Uninstalling both of those products, and then re-installing our current kit solved the problem.
We are now approaching a release candidate, and have no more than 100 people who have installed the earlier betas. They should not have any problem if we tell them that they should uninstall any prior release before installing our RC build.
Uninstalling both of those products, and then re-installing our current kit solved the problem.
We are now approaching a release candidate, and have no more than 100 people who have installed the earlier betas. They should not have any problem if we tell them that they should uninstall any prior release before installing our RC build.
Fletcher James
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Thanks for your pro-active involvement in resolving this issue.
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Who is online
Users browsing this forum: No registered users and 154 guests