This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Program update - Error 1706
Started by
SergeyP
, Apr 17 2008 08:45
8 replies to this topic
SergeyP
-
- Full Members
- 6 posts
Posted 17 April 2008 - 08:45
Hello colleges, I have the following question.
With the following scenario some of our clients have problems:
1. Install our product version 1 from folder1.
2. Erase folder1.
3. Install our product version2 from folder2.
4. A question "Enter valid path to sources" appears and then - Error 1706.
I've turned on detail logging fro msi and saw the following.
We redistribute SQLServer2005_ADOMD.MSI with our product and install it if it was not installed earlier. So we have a custom action(nested msi) for running it installation.
So the mentioned error occurs when this custom action starts.
Are there some ideas how to avoid this error?
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 21 April 2008 - 18:13
Deleting a folder doesn't uninstall the application. Windows Istaller will try to repair the deleted files. Tell users to uninstall proeprly.
Stefan Krüger
InstallSite.org twitter facebook
SergeyP
-
- Full Members
- 6 posts
Posted 22 April 2008 - 14:39
| QUOTE (Stefan Krueger @ 2008-04-21 18:13) |
| Deleting a folder doesn't uninstall the application. Windows Istaller will try to repair the deleted files. Tell users to uninstall proeprly. |
But user does not delete folder with installed application. He deletes folder with installation files only!
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 23 April 2008 - 10:56
In this case: how are you installing version 2? Is this a minor or major upgrade (did the ProductCode change)?
Does it work properly if they delete folder 1 *after* updating to version 2?
Does it work properly if they delete folder 1 *after* updating to version 2?
Stefan Krüger
InstallSite.org twitter facebook
SergeyP
-
- Full Members
- 6 posts
Posted 27 May 2008 - 12:51
Sorry for a long delay, I had a vacation.
So, here is more detail description.
The product is distributed with SQLServer2005_ADOMD.MSI and installs it to target computers.
So the installation contains custom action(nested msi) which installs SQLServer2005_ADOMD.
This action cause the problem. Any ideas?
So, here is more detail description.
The product is distributed with SQLServer2005_ADOMD.MSI and installs it to target computers.
So the installation contains custom action(nested msi) which installs SQLServer2005_ADOMD.
This action cause the problem. Any ideas?
SergeyP
-
- Full Members
- 6 posts
Posted 28 May 2008 - 17:35
One more note.
I have 2 msi packages:
- With custom action(InstallNestedAction) which installs nested msi.(product version 1)
- Without this custom action.(product version 2)
So, I install version 1, erase folder with installation, install version 2.
During version 2 installation, I was asked for the sources of version 1. I have looked to log file.... the question was during executing InstallNestedAction! But this action does not present at product's version 2 msi! What is wrong?
I have 2 msi packages:
- With custom action(InstallNestedAction) which installs nested msi.(product version 1)
- Without this custom action.(product version 2)
So, I install version 1, erase folder with installation, install version 2.
During version 2 installation, I was asked for the sources of version 1. I have looked to log file.... the question was during executing InstallNestedAction! But this action does not present at product's version 2 msi! What is wrong?
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 30 May 2008 - 11:55
You didn't answer my questions.
Is this a Major or a Minor upgrade?
Double check the condition on the nested install custom action.
In general, this type of custom action is deprecated.
Is this a Major or a Minor upgrade?
Double check the condition on the nested install custom action.
In general, this type of custom action is deprecated.
Stefan Krüger
InstallSite.org twitter facebook
SergeyP
-
- Full Members
- 6 posts
Posted 02 June 2008 - 07:51
| QUOTE (Stefan Krueger @ 2008-05-30 11:55) |
| You didn't answer my questions. Is this a Major or a Minor upgrade? Double check the condition on the nested install custom action. In general, this type of custom action is deprecated. |
It's Major upgrade.
Looks like the condition on nested install is always true.
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 03 June 2008 - 11:53
So it probably tries to re-run the nested install again but it's no longer present in its location. Do you really need to re-run the nested install? If not, it might be best to change the condition.
Of course this depends on what the uninstall of the old version is doing with the nested install.
Of course this depends on what the uninstall of the old version is doing with the nested install.
Stefan Krüger
InstallSite.org twitter facebook