[duxhelp] Re: Error on install
- From: "Peter Sullivan" <peter@xxxxxxxxxx>
- To: <duxhelp@xxxxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 15:10:43 -0500
Michael,
Thanks for following up.
You wrote:
> I would not let the installer silently succeed if an activation location
cannot be determined for some reason.
Do you mean to suggest an added error message when running "msiexec /a" or
when running the installer in the network image?
You also wrote:
> Personally I would not rely on a network assisted install to determine if
this location should be local or remote. This could result in some of these
errors.
It's probably too late for a major change in the way the network
installation is intended to work. That is, I cannot imagine going back now
and redesigning things to make it so that "msiexec /a" is the normal initial
procedure. We'd have to set back release by several weeks at least to get
that done. But I would like to be sure that we're making it easier to find
your way through the correct process -- and therefore harder to make an
error from which recovery is difficult.
When you did the installation initially, I gather that you did things in
this order:
1. Ran "msiexec /a" to create a network installation image.
2. Ran the network installation image on your server or master workstations.
3. Ran the network installation image on one or more workstatations.
Is that right? I'd simply like to be certain that I'm understanding your
experience correctly.
- Peter
-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Surato
Sent: Tuesday, March 28, 2006 2:33 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Error on install
Hi,
I think I understand a little more about what is happening. Out of habit, I
performed a few steps out of the prescribed order for the network install.
The first step was to run "msiexec /a" then perform all installations from
the network share. This made the activation location dialog unavailable.
This in turn did not result in a successful install of this component. I
attempted this both with and without entering a license string into the
installer. When I attempted this from the downloaded MSI, the install worked
properly. I have attached the requested files for all 3 install attempts.
With this in mind, I would not let the installer silently succeed if an
activation location cannot be determined for some reason. Personally I would
not rely on a network assisted install to determine if this location should
be local or remote. This could result in some of these errors.
This error will not allow for a "Network-Assisted Standalone Workstation
Installation" to succeed.
Now that I have a working copy, I will now perform the rest of the network
installation to see if that has further errors. Thank you very much!
+-------------------------------------------+
| Michael Surato |
| Resource Center for Persons |
| with Disabilities |
| Michigan State University |
| 120 Bessey Hall |
| East Lansing, MI 48824 |
| Voice: (517) 353-9643 Fax: (517) 432-3191 |
+-------------------------------------------+
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx
> [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of Peter Sullivan
> Sent: Tuesday, March 28, 2006 1:35 PM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Error on install
>
> Hello Michael,
>
> An install log is not normally created. You can have one created by
> using a command line the following:
>
> msiexec /i %TEMP%\dbt-1006beta2.msi /L*v %TEMP%\dbt-1006beta2.log
>
> Assuming that you've downloaded the .msi file to %TEMP%, this command
> will create a very detailed log, also in %TEMP%.
>
> You may need to remove the software before trying this.
> Otherwise the installer will want to maintain or repair DBT rather
> than installing it anew.
>
> I understand that you are likely to be trying installation on a
> network where you share a limited number of activations among a larger
> number of computers. That will be very helpful to us, because the
> method we use for doing this in DBT 10.6 is very different from what
> it was in DBT 10.5. You should also know these three things:
> 1. Setting things up this way just didn't work in beta 1.
> In fact, you'd get precisely the error you've reported if you tried
> it. The problem should be resolved for beta 2, though you've perhaps
> already proven me wrong about that.
> 2. With beta 2, it is important to follow the instructions given
> near the end of the beta web site.
> 3. The error that you have encountered should mean that there is a
> problem with a file called features.ini. So I'll be interested in
> having a look at that file. You may find features.ini in one or both
> of two places:
> C:\Program Files\Duxbury\DBT 10.6 (Beta 2)
> C:\Documents and Settings\All Users\Application
> Data\Duxbury\Activation\5369-8731-2729-7642-5710
>
> To get me a full look at what's going on, you should send me:
> 1. The installation log created using the procedure outlined above,
> 2. Features.ini (both copies, if you find a copy in both possible
> places), and
> 3. A file called version.txt from the DBT installation directory.
>
> - Peter
>
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx
> [mailto:duxhelp-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Surato
> Sent: Tuesday, March 28, 2006 12:04 PM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Error on install
>
> Hi,
>
> I just completed a custom install of beta 2. I selected launch
> application at the end of the install, and received an error that says
> "DBT license and activation failed: Error 0x8004105C". I have looked
> in the %temp% folder for install logs, but did not find any. Is there
> another location to look?
>
> I will try to launch and reinstall after lunch. Is there anything else
> I should look for?
>
> +-------------------------------------------+
> | Michael Surato |
> | Resource Center for Persons |
> | with Disabilities |
> | Michigan State University |
> | 120 Bessey Hall |
> | East Lansing, MI 48824 |
> | Voice: (517) 353-9643 Fax: (517) 432-3191 |
> +-------------------------------------------+
>
> * * *
> * This message is via list duxhelp at freelists.org.
> * To unsubscribe, send a blank message with
> * unsubscribe
> * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> * subscribe, unsubscribe, and set vacation mode and other subscription
> * options by visiting //www.freelists.org. The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
>
>
> * * *
> * This message is via list duxhelp at freelists.org.
> * To unsubscribe, send a blank message with
> * unsubscribe
> * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> * subscribe, unsubscribe, and set vacation mode and other subscription
> * options by visiting //www.freelists.org. The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
>
* * *
* This message is via list duxhelp at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
Other related posts:
