Hi All,
I get the following error when I try to unistall:
Could not access network location for MyFolderName Where MyFolderName contains the value of the Folder where I am installing this application.
I searched the Help File and this forum and could not find anything about this error.
The installation is created using the Wizard.
If I rebuild the project and run that installation, it will remove the previous install with no problem.
Thanks.
Error testing unstalling feature
Error testing unstalling feature
Edhy Rijo
Thom Child and Family Services
Thom Child and Family Services
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Hi Edhy
It seems like you have an invalid path specified in your shortcut folders. All paths must be fully qualified.
It seems like you have an invalid path specified in your shortcut folders. All paths must be fully qualified.
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/
Hi Michael,
Well, created a new script accepting all default values for Target Folder ($PROGRAMFILES$\\$TITLE$) and Shortcut Folder ($TITLE$), installed this on a test computer with Windows XP-SP2. Then tried to unistall it and got the same Error.
I have not modified the script in any way, just accept all Wizard default options.
Keep in mind that I am testing IA using the demo version 5.12 (Build ponderosa_sp2.060222). If the uninstall does not work, I can not really make a decision on buying IA.
Well, created a new script accepting all default values for Target Folder ($PROGRAMFILES$\\$TITLE$) and Shortcut Folder ($TITLE$), installed this on a test computer with Windows XP-SP2. Then tried to unistall it and got the same Error.
I have not modified the script in any way, just accept all Wizard default options.
Keep in mind that I am testing IA using the demo version 5.12 (Build ponderosa_sp2.060222). If the uninstall does not work, I can not really make a decision on buying IA.
Edhy Rijo
Thom Child and Family Services
Thom Child and Family Services
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Hi Edhy!
The only time this is encountered is when running from VMware using the Shared Folders feature, which uses paths of the form \\\\.\\ that confuses the Windows Installer engine. Was this what you are trying? There really are no other known cases of this occuring.
Oh, and I believe if you install from a network path, Windows Installer expects that path to remain accessible during uninstall (ex: \\\\server\\share\\file.msi should be there during uninstall, if that is where you ran the install from).
So these wouldn't typically be concerns unless you are testing an uncompressed setup from a network share, and you are either removing the setup after installing, or you are using a VMware shared folder.
Hope that helps!
The only time this is encountered is when running from VMware using the Shared Folders feature, which uses paths of the form \\\\.\\ that confuses the Windows Installer engine. Was this what you are trying? There really are no other known cases of this occuring.
Oh, and I believe if you install from a network path, Windows Installer expects that path to remain accessible during uninstall (ex: \\\\server\\share\\file.msi should be there during uninstall, if that is where you ran the install from).
So these wouldn't typically be concerns unless you are testing an uncompressed setup from a network share, and you are either removing the setup after installing, or you are using a VMware shared folder.
Hope that helps!
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/
Hi Michael,
This is a bit frustrating and I do apprecitate the support provided by you and other members of this newsgroup to my testing.
I am testing on a Windows XP Pro SP2 from a local folder on drive C. The Build Type is Compressed Single .EXE file.
So far I am doing everything by the book and what bothers me is that if I build a new release of the same setup and run that, it will UNINSTALL the previous installation, but if I want to uninstall it manually it will generate the same error. I even send the test file to a friend and he installed and got the same error when try to uninstall it.
If you like and have some time I can create a small test of my setup and post here the download link for you to see if you can duplicate my findings.
Please note that I am not trying to get advantage of anybody here other than report my findings during my demo period before commit to the purchase of IA.
This is a bit frustrating and I do apprecitate the support provided by you and other members of this newsgroup to my testing.
I am testing on a Windows XP Pro SP2 from a local folder on drive C. The Build Type is Compressed Single .EXE file.
So far I am doing everything by the book and what bothers me is that if I build a new release of the same setup and run that, it will UNINSTALL the previous installation, but if I want to uninstall it manually it will generate the same error. I even send the test file to a friend and he installed and got the same error when try to uninstall it.
If you like and have some time I can create a small test of my setup and post here the download link for you to see if you can duplicate my findings.
Please note that I am not trying to get advantage of anybody here other than report my findings during my demo period before commit to the purchase of IA.
Edhy Rijo
Thom Child and Family Services
Thom Child and Family Services
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Hi Edhy!
I suspect something may have gone wrong in your script, maybe instead of calling Apply Uninstall, you are calling something else?
Before posting here, why not try with a standard template project in InstallAware and see if you can reproduce the same behavior. That way at least you can narrow the issue down.
I suspect something may have gone wrong in your script, maybe instead of calling Apply Uninstall, you are calling something else?
Before posting here, why not try with a standard template project in InstallAware and see if you can reproduce the same behavior. That way at least you can narrow the issue down.
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 188 guests