Hi,
I tried removing the "Run now" from the Finish dialog of the Official theme, but got into trouble. The installation always goes fine, but when uninstalling on one machine it works while on another it fails.
I reproduced this using the default .NET Setup project. It installs/uninstalls if not modified, but once I remove the "Run now" it gets into trouble.
To help you understand what I do, I captured my actions in the attached movie.
Any help would be appreciated.
Alexander
File Attached:
InstallAware.zip
Problem when removing \"Run now\" from the Finish dialoh
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
According to MSDN:
2755 Server returned unexpected error [2] attempting to install package [3].
Using logging might help - I haven't been able to reproduce this one.
2755 Server returned unexpected error [2] attempting to install package [3].
Using logging might help - I haven't been able to reproduce this one.
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: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Oh, I was able to see it while running inside the IDE. It doesn't happen when you run your setup outside the IDE, so shouldn't be a problem with production installs.
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/
You are right, it does not affect production installs. This was a failed attempt on our part to reproduce an annoying problem that we were having -- error 2755 was popping up, but strangely enough only on a specific machine.
Eventually we found out that this error was being caused by the batch file that we are running. This batch file changes the drive/folder before calling some executable. Modifying the batch file not to change drive/folder fixed this issue. I have idea why it was surfacing only on that specific machine.
Eventually we found out that this error was being caused by the batch file that we are running. This batch file changes the drive/folder before calling some executable. Modifying the batch file not to change drive/folder fixed this issue. I have idea why it was surfacing only on that specific machine.
Who is online
Users browsing this forum: No registered users and 119 guests