C:\Documents and Settings\agkc\Desktop>ipv6 install
Installing...
Failed to complete the action.
Error 0x800704b8
C:\Documents and Settings\agkc\Desktop>
It on a newley built SP2 system
Thanks
Andy
strange that no one has an idea how to fix that problem. I get
C:\Dokumente und Einstellungen\chaostrooper>ipv6 install
Installation wird durchgeführt...
Vorgang konnte nicht abgeschlossen werden.
Fehler 0x800704b8
and the gui interface also gives an "extended error"
Emanuel
Andy Clark schrieb:
I gave up and reinstalled the system as it was a new build and it work , we
did not do anything different as far as we can remember
Andy
This is technically not an IPv6 error; it is coming from the setup
subsystem. So the likely causes are that another network GUI is open...
Things to try:
Are they logged in as an administrator, do they have permissions to the
registry specifically HKLM\System\CCS\Services and
HKLM\System\CCS\Services\6to4 etc...
Run esentutl /g to check the integrity of the security database
%windir%\security\Database\secedit.sdb
Stewart.
http://research.microsoft.com/ur
http://www.microsoft.com/ipv6
"Andy Clark" <an...@agkc.freeserve.co.uk> wrote in message
news:ewQCqKVN...@tk2msftngp13.phx.gbl...
netsh> interface ipv6 install
An extended error has occurred.
6to4 doesn't exist in services and security database integrity seems to
be Ok. System Restore didn't even help, also restored an old SYSTEM
registry hive and didn't help either... I can't figure out what caused
the problem. If there is no idea I think I will install XP on VMWare
just to try to reproduce it again (with snapshots) and tell what
modification it didn't like.
Any answers will be really appreciated!
- database is not up-to-date
Then ran the same command with on recovery option - esentutl /r
%windir%\security\Database\secedit.sdb and it turned out to have some
trouble, citing:
- Operation terminated with error -1003 (JET_errInvalidParamater, Invalid
API paramater)
Thus ran the tool again in repair mode - esentutl /p
%windir%\security\Database\secedit.sdb, which was a success shown by the
following intergrity check. Thereafter installed IPv6 via the command line.
Thanks Stewart for the tip, though MS might think about a KB article as
few guys out there facing the same trouble but having a hard time to find
a solution.
Cheers
---
"km" <k...@go.com.jo> wrote in message
news:op.soru9...@ooik-2994207698.vtol.gov.mil...
Charles
"km" <k...@go.com.jo> wrote in message
news:op.soru9...@ooik-2994207698.vtol.gov.mil...