Error 1719 - Windows Vistsa Home Premium

It drives me crazy that every post about this error in the "Vista community"
is about XP. None of the XP "solutions" work for me and I've found nothing
that addresses this error for Vista. Please help.

I have a Toshiba laptop with Vista premium installed. After installing MS
Office Standard 2007 I can no longer install or uninstall anything, getting
the 1719 error. I've surfed the web and this problem based on MSI problems
seems to have been around for months but I can find no solution to it.
Attempting to uninstall anything hangs the process, which can't be stopped
even through the task mgr. Installs are the same way - using Windows Update
simply hangs the computer.

I could really use some help.

(cross-post added to Vista Perf & Maint)
"Charlie" <> wrote in message
news:24DC9880-3393-4A91-A379-
....
> [Subject: Error 1719 - Windows Vistsa Home Premium]

> It drives me crazy that every post about this error in the "Vista community"
> is about XP.


That's because the web interface to newsgroups that you are using
misleads you into thinking that all the links it offers are Vista-specific
newsgroups. Some of them are common to more than one OS.
In fact this one is common to all OS and typically there is more knowledge
about XP in here than about Vista.


> None of the XP "solutions" work for me and I've found nothing
> that addresses this error for Vista. Please help.

Error codes by themselves are relatively useless.
For example here is what that one may mean on XP.

<cmd_output OS="XPsp2">
F:\>net helpmsg 1719

There are no protocol sequences.
</cmd_output>

Is that what Vista shows for net helpmsg 1719 too?
As you can see it doesn't tell you much about anything. ; )


Try to find some context for them in any log files that the update
created. BTW the code that you are quoting is a decimal code
and in general you may find more references to its hex equivalent
(0x0687) instead. In fact, you might find those hex nibbles in a
longer hex code such as 0x80070687. Etc.


>
> I have a Toshiba laptop with Vista premium installed. After installing MS
> Office Standard 2007 I can no longer install or uninstall anything, getting
> the 1719 error. I've surfed the web and this problem based on MSI problems
> seems to have been around for months but I can find no solution to it.
> Attempting to uninstall anything hangs the process, which can't be stopped
> even through the task mgr. Installs are the same way - using Windows Update
> simply hangs the computer.


If you are having more general problems with WU you should try using
its log. Ref. KB902093.


>
> I could really use some help.


In case there is something different about Vista's production of this symptom
I've cross-posted this reply to a Vista-specific newsgroup.


HTH

Robert Aldwinckle
---

I am also getting the same and being a newbie and one with no experience find
it very hard to get decent help on the matter. I have no experience in
writing scripts so I need some very simple fix.
If it is true that this has been happening for so LONG why hasn't it been
fixed by Microsoft???????????



"Robert Aldwinckle" wrote:

> (cross-post added to Vista Perf & Maint)
> "Charlie" <> wrote in message
> news:24DC9880-3393-4A91-A379-
> ....
> > [Subject: Error 1719 - Windows Vistsa Home Premium]
>
> > It drives me crazy that every post about this error in the "Vista community"
> > is about XP.
>
>
> That's because the web interface to newsgroups that you are using
> misleads you into thinking that all the links it offers are Vista-specific
> newsgroups. Some of them are common to more than one OS.
> In fact this one is common to all OS and typically there is more knowledge
> about XP in here than about Vista.
>
>
> > None of the XP "solutions" work for me and I've found nothing
> > that addresses this error for Vista. Please help.
>
> Error codes by themselves are relatively useless.
> For example here is what that one may mean on XP.
>
> <cmd_output OS="XPsp2">
> F:\>net helpmsg 1719
>
> There are no protocol sequences.
> </cmd_output>
>
> Is that what Vista shows for net helpmsg 1719 too?
> As you can see it doesn't tell you much about anything. ; )
>
>
> Try to find some context for them in any log files that the update
> created. BTW the code that you are quoting is a decimal code
> and in general you may find more references to its hex equivalent
> (0x0687) instead. In fact, you might find those hex nibbles in a
> longer hex code such as 0x80070687. Etc.
>
>
> >
> > I have a Toshiba laptop with Vista premium installed. After installing MS
> > Office Standard 2007 I can no longer install or uninstall anything, getting
> > the 1719 error. I've surfed the web and this problem based on MSI problems
> > seems to have been around for months but I can find no solution to it.
> > Attempting to uninstall anything hangs the process, which can't be stopped
> > even through the task mgr. Installs are the same way - using Windows Update
> > simply hangs the computer.
>
>
> If you are having more general problems with WU you should try using
> its log. Ref. KB902093.
>
>
> >
> > I could really use some help.
>
>
> In case there is something different about Vista's production of this symptom
> I've cross-posted this reply to a Vista-specific newsgroup.
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>

http://www.microsoft.com/communities...9-90d206228997

10/20/2007 11:32 AM PST

"Chezza53" <> wrote in message
news:1F388C26-D79E-48B1-97E6-...
>I am also getting the same and being a newbie and one with no experience find
> it very hard to get decent help on the matter. I have no experience in
> writing scripts so I need some very simple fix.


Before you ask for "a fix" you have to be prepared to provide details,
which supplement this extremely vague symptom description.


So, are you a Vista user? What do you see if you enter (in a cmd window):

net helpmsg 1719


> If it is true that this has been happening for so LONG why hasn't it been
> fixed by Microsoft???????????


Probably because nobody is providing sufficient details about it. ; }


HTH

Robert
---

....
>> Try to find some context for them in any log files that the update
>> created. BTW the code that you are quoting is a decimal code
>> and in general you may find more references to its hex equivalent
>> (0x0687) instead. In fact, you might find those hex nibbles in a
>> longer hex code such as 0x80070687. Etc.
....

poor, very poor excuse! for an answer to a problem that seams to be very
popular! I have spend days and hours trying to fix this problem. Have read
everything under the sun. all information is not help.

I am trying to run a business and can not run my programs. Dead Losing money.

Get the problem fix and stop making excuses that there is not enough
information. The problem is wide spread.

Unbeleiveable.

Get with it Microsoft.

"Robert Aldwinckle" wrote:

>
> http://www.microsoft.com/communities...9-90d206228997
>
> 10/20/2007 11:32 AM PST
>
> "Chezza53" <> wrote in message
> news:1F388C26-D79E-48B1-97E6-...
> >I am also getting the same and being a newbie and one with no experience find
> > it very hard to get decent help on the matter. I have no experience in
> > writing scripts so I need some very simple fix.
>
>
> Before you ask for "a fix" you have to be prepared to provide details,
> which supplement this extremely vague symptom description.
>
>
> So, are you a Vista user? What do you see if you enter (in a cmd window):
>
> net helpmsg 1719
>
>
> > If it is true that this has been happening for so LONG why hasn't it been
> > fixed by Microsoft???????????
>
>
> Probably because nobody is providing sufficient details about it. ; }
>
>
> HTH
>
> Robert
> ---
>
> ....
> >> Try to find some context for them in any log files that the update
> >> created. BTW the code that you are quoting is a decimal code
> >> and in general you may find more references to its hex equivalent
> >> (0x0687) instead. In fact, you might find those hex nibbles in a
> >> longer hex code such as 0x80070687. Etc.
> ....
>
>
>

On Thu, 10 Jul 2008 02:32:09 -0700, Dakota1510
<> wrote:

>Get with it Microsoft.

Microsoft neither lives here nor works here. It doesn't even check
here.

We are all a bunch of computer users who gather to share our miseries
and successes.

Dakota1510 wrote:

> poor, very poor excuse! for an answer to a problem that seams to be very
> popular! I have spend days and hours trying to fix this problem. Have read
> everything under the sun. all information is not help.

You're responding to a very old thread. What exactly is your problem? What
makes you think it is common? What have you done to try to correct it?

(Please start a new thread rather than responding to this one.)

Harry.

"Charlie" wrote:

> It drives me crazy that every post about this error in the "Vista community"
> is about XP. None of the XP "solutions" work for me and I've found nothing
> that addresses this error for Vista. Please help.
>
> I have a Toshiba laptop with Vista premium installed. After installing MS
> Office Standard 2007 I can no longer install or uninstall anything, getting
> the 1719 error. I've surfed the web and this problem based on MSI problems
> seems to have been around for months but I can find no solution to it.
> Attempting to uninstall anything hangs the process, which can't be stopped
> even through the task mgr. Installs are the same way - using Windows Update
> simply hangs the computer.
>
> I could really use some help.

"Charlie" wrote:

> It drives me crazy that every post about this error in the "Vista community"
> is about XP. None of the XP "solutions" work for me and I've found nothing
> that addresses this error for Vista. Please help.
>
> I have a Toshiba laptop with Vista premium installed. After installing MS
> Office Standard 2007 I can no longer install or uninstall anything, getting
> the 1719 error. I've surfed the web and this problem based on MSI problems
> seems to have been around for months but I can find no solution to it.
> Attempting to uninstall anything hangs the process, which can't be stopped
> even through the task mgr. Installs are the same way - using Windows Update
> simply hangs the computer.
>
> I could really use some help.

Charlie:

I can relate with you. I am experiencing the same problem with Microsoft
Office Enterprise 2007 and Vista. I can't uninstall it, I can't repair it, I
can't reinstall it. And unfortunately, I need my computer for school so I'm
really screwed now.

Robert:

This deals with Microsoft Office Enterprise 2007 and Vista as Charlie
already mentioned in the first post. We get a popup box with an error code,
1719, and it says that the "Windows Installer Service could not be reached"
and to contact our support department. That is Microsoft's answer to every
error - to contact our support. Well, hello, most of us are having problems
with personal computers and don't have a support - we are it. I like Vista,
but I'm tired of having problems every time I download something on my
laptop. I haven't converted my desktop over yet and probably won't because of
this very problem. Things work well with XP already, so why change it to
something that doesn't work half the time?

pennyfmhvn wrote:

>> It drives me crazy that every post about this error in the "Vista community"
>> is about XP. None of the XP "solutions" work for me and I've found nothing
>> that addresses this error for Vista. Please help.

(For the record, this isn't a Vista Community, it's a Windows Update Newsgroup.)

> I can relate with you. I am experiencing the same problem with Microsoft
> Office Enterprise 2007 and Vista. I can't uninstall it, I can't repair it, I
> can't reinstall it. And unfortunately, I need my computer for school so I'm
> really screwed now.

You're responding to a very old thread. Please start a new thread about your
problem, with a bit more detail - including exactly you were doing when the
popup box appeared, which edition of Vista you have and whether or not service
pack 1 is installed. It would probably be more sensible to post it in one of
the Vista newsgroups, since this problem doesn't relate to Windows Update.

> This deals with Microsoft Office Enterprise 2007 and Vista as Charlie
> already mentioned in the first post. We get a popup box with an error code,
> 1719, and it says that the "Windows Installer Service could not be reached"
> and to contact our support department. That is Microsoft's answer to every
> error - to contact our support. Well, hello, most of us are having problems
> with personal computers and don't have a support - we are it.

Microsoft Office Enterprise is only sold to enterprise customers, not to
individuals, so it doesn't seem unreasonable for it to assume you have a support
department. I presume you got it from your school; do they not provide any sort
of support for it?

Harry.