| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Visual C++ Error message |
From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_0604_01C75B83.33DB1E30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The error simply means that the application in question called =
abort() directly or indirectly. There is an ambiguity in the message. =
The title is the name of the EXE in the process containing the C = runtime.
It may not be the caller of abort(). In other words, this may = not be a
problem with MSIEXEC but instead with the component being = installed.
Then again, it might be MSIEXEC but if you installed the = latest release
of 3.1 I would expect it to be this. It could be = something weird like
geo suggested with a far future date that causes = some CRT functions to
appropriately call abort().
Rich
"Glenn Meadows" wrote in message =
news:45e5d0f7$1{at}w3.nls.net...
Done yesterday, no joy. I'll read the thread and see if any other =
helps are=20
available. Since the laptop is actually being cleaned off from the =
prior=20
user, I might just grab the original Toshiba Restore CD, and let it =
wipe=20
everything and start it again from square one.
Sure would like to fix it though, for adding to troubleshooting =
library.=20
.
Rich, you have any thoughts on this one?
--=20
Glenn M.
"Rich Gauszka" wrote in message=20
news:45e5cbcb$1{at}w3.nls.net...
>
> "Glenn Meadows" wrote in message=20
> news:45e5c743{at}w3.nls.net...
>> OK, need some help with this one.
>>
>> I've now got a laptop that has started throwing the error listed =
below no=20
>> matter how I try to apply updates. Either from our WSUS server, or =
from=20
>> Windows or Microsoft Update. The Laptop is a Toshiba, and is an =
OEM, so=20
>> it passes WGA validation properly.
>>
>> The error displayed is:
>>
>> Microsoft Visual C++ Runtime Library.
>>
>> Program C:\Windows\system32\msiexec.exe
>> This application has requested the Runtime to terminate it in an =
unusual=20
>> way. Please contact the Application Support Team for more =
information.
>>
>> That's it, total.
>>
>> Any clues, pointers on what I might need to download/re-install to =
clear=20
>> this error/problem?
>>
>> Thanks.
>>
>> --=20
>>
>> Glenn M.
>>
> not sure if it's applicable as the answer below was for a similar =
error=20
> in 2003 server.
>
> =
http://groups.google.com/group/microsoft.public.windows.server.update_ser=
vices/browse_thread/thread/607fc5e67677121c/bd4c375299c675a9%23bd4c375299=
c675a9
>
> Download the current version of Windows Installer 3.1v2 from the =
Microsoft
> Download Center and (re)install it on this system.
> ---------------
>
> A Google Groups search shows others have experenced the error
>
> =
http://groups.google.com/groups?q=3Dwindows+update+msiexec.exe++terminate=
+it+in+an+unusual+&hl=3Den&sa=3DX&oi=3Dgroups&ct=3Dtitle
>=20
------=_NextPart_000_0604_01C75B83.33DB1E30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The error
simply means =
that the=20
application in question called abort() directly or indirectly. =
There is an=20
ambiguity in the message. The title is the name of the EXE in the
= process=20
containing the C runtime. It may not be the caller of =
abort(). In=20
other words, this may not be a problem with MSIEXEC but instead with the =
component being installed. Then again, it might be MSIEXEC but if = you=20
installed the latest release of 3.1 I would expect it to be this.
= It could=20
be something weird like geo suggested with a far future date that causes = some=20
CRT functions to appropriately call abort().
Rich
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 5030/786 @PATH: 379/45 1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.