Internal Error Occurred : The request is not supported

[Guest]

Working with a new Asus A8V d/l system with networking and internet access
initially working fine. During a reinstallation of some software a system
restart was required and suddenly networking and internet access were
unavailable. No restore points work. When I try to repair the network
connection I get a message that TCP/IP cannot be queried. When I try to run
"Cmd" then "ipconfig/release" I am given the message " An internal error
occurred : The request is not supported Please contact Microsoft Product
Services for further help" "Additional information : Unable to query host
name".

Running the Home networking wizard again to establish Computer Name and
Workgroupd does not resolve this, neither does removing and subsequently
re-installing Windows Networking Services through Add/Remove Windows
components.

I was originally working with the built in motherboard networking
connection, and suspected a hardware problem, but exactly the same symptoms
occur with a new Belkin PCI network card and with a USB wireless networking
adapter (one at a time). The network hub etc have been tested and are fully
linked and operational, so the problem must presumably lie with the
networking configuration on my new computer. It is running Windows XP SP2
MCE 2005 with all updates current to just before Christmas.

Any ideas to help resolve this would be much appreciated.
DaveJ

 

[Steve Winograd [MVP]]

Working with a new Asus A8V d/l system with networking and internet access
initially working fine. During a reinstallation of some software a system
restart was required and suddenly networking and internet access were
unavailable. No restore points work. When I try to repair the network
connection I get a message that TCP/IP cannot be queried. When I try to run
"Cmd" then "ipconfig/release" I am given the message " An internal error
occurred : The request is not supported Please contact Microsoft Product
Services for further help" "Additional information : Unable to query host
name".

Running the Home networking wizard again to establish Computer Name and
Workgroupd does not resolve this, neither does removing and subsequently
re-installing Windows Networking Services through Add/Remove Windows
components.

I was originally working with the built in motherboard networking
connection, and suspected a hardware problem, but exactly the same symptoms
occur with a new Belkin PCI network card and with a USB wireless networking
adapter (one at a time). The network hub etc have been tested and are fully
linked and operational, so the problem must presumably lie with the
networking configuration on my new computer. It is running Windows XP SP2
MCE 2005 with all updates current to just before Christmas.

Any ideas to help resolve this would be much appreciated.
DaveJ

Type this line at a command prompt to reset the TCP/IP stack, then
reboot:

netsh winsock reset catalog
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Thanks Steve :

I note at
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/netsh.mspx
that this command is stated as valid for Windows Server 2003 Sp1. Is it
also valid for Windows XP MCE 2005 with SP2 ? (not at home right now so can't
try this until this evening). Possibly an issue with MS Antispyware beta ?

DaveJ

 

[Steve Winograd [MVP]]

Thanks Steve :

I note at
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/netsh.mspx
that this command is stated as valid for Windows Server 2003 Sp1. Is it
also valid for Windows XP MCE 2005 with SP2 ? (not at home right now so can't
try this until this evening). Possibly an issue with MS Antispyware beta ?

DaveJ

You're welcome, DaveJ. I don't have access to MCE 2005, but I believe
that it uses the same TCP/IP stack as XP.

The best way to find out if the command is valid is to try it and see.
It will either work, or give an error message saying that it isn't
recognized.

Removing spyware can cause TCP/IP stack corruption if a removed
program had created an entry in the LSP chain. The "netsh" command
that I gave repairs the LSP chain. Please see this Microsoft
Knowledge Base article:

After you run Microsoft Windows AntiSpyware (Beta), you have
network-related problems, or you receive an error message
http://support.microsoft.com/kb/892350/en-us
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Hi Steve : Tried the netsh command and it executed as expected saying it went
to completion and reset the config. However, this did not resolve the
problem. I was unable to post this information here last night as the
"service here was temporarily unavailable" (at least from where I live !!)

I tried a Windows installation repair and that gave several error messages,
ran to completion, but returned the system to the same state and did not
resolve the problem. During the Windows repair I got the following two error
messages just before it got to "Installing Start Menu Items" :
ngen.exe - Entry Point Not Found : The procedure entry point
GetRequestedRuntimeVersion could not be located in the dynamic link library
mscore.dll (this later happened again with 18 instances of reappearance at
one point)
.Net Framework Initialization Error
c:\Windows\Microsoft.Net\Framework\v2..0.50727\mscorwks.dll could not be
loaded (this also happened again with one instance at the time the first
error message reappeared.)

Following the Windows "repair", which appears to have changed/resolved
nothing, I still have the following :
When I try to repair the connection :
"Windows could not finish repairing the problem because the following action
annot be completed. Failed to query TCP/IP settings of the connection.
Cannot Proceed."

Again the netsh command was executed, ran to success but did not resolve the
problem. I get the error message when I try to start WIndows Firewall :
"Windows firewall cannot be displayed because the associated serice is not
running" When I let it try and start the service from this error message it
fails to start.
DaveJ

 

[Guest]

Further to the above :

Under "Services", if I attempt a manual start of the Windows Firewall/
Internet Connection Sharing (ICS) service, I get "Error 2 : The system cannot
find the specified file." I will need help to determine what the missing
file might be (can copy from another system if it is a standard Windows XP
file).

I also noted that a number of other servvices were not started :
Network location Awareness
Peer Name Resolution Protocol
Peer Networking
Attempting to start each manually resulted in the error message "Error 1068
The dependency service or group failed to start"
All appear to need Peer Networking Identity Manager, which seems to have all
teh services it needs but also depends on "Microsoft IPv6 Protocol driver"
which needs TCP/IP Protocol driver and IPSEC driver. I have no idea if these
are functioning correctly but I did try to remove, reboot and reinstall the
"Microsoft TCP/IP Version 6" Windows networking component - this had no
affect. I also tried unchecking the "Microsoft TCP/IP version 6" box on the
network connection, intending to rely only on "Internet Protocol (TCP/IP)"
but this had no affect either.

I would conclude that either there is a damaged file which is not being
replaced during uninstalls/ reinstalls and repairs, else something is
blocking some key processes.

Full scans with both Norton AntiVirus and Microsoft AntiSpyware Beta, latest
definitions in each, revealled nothing malevolant as identifeied on the
system. Both have since been uninstalled in case they were in any way
interfering with / actively causing the problem to persist.

One additional piece of information that may or may not be relevant -
attempts to install teh component "RIP Listener" lead to an error "One or
more services for the RIP Listener component took longer that their allotted
time to start. Installation will continue but services will not be available
until they have started completely". I assume this is another clue to
potential dependencies that for some reason are damaged or blocked.

Would be nice to be able to repair this given the time it will take to
reconfigure the system with all needed software, but I am rapidly reaching
the conclusion that only a clean install of Windows XP will resolve this.
Willing to give it a few more atempts if any additional ideas come to mind.
DaveJ

 

[Guest]

Finally concluded that the configuration could not be salvaged - no repair
pathway that I could find resolved the problem, I even for a time thought it
might be a hardware issue, but it was not.

Resolved the issue by deleting the partition on drive C: and going through
an entire clean install of Windows XP MCE, only minor hassle was the time it
takes to re-activate your copy of Windows XP over the phone having been
backed into a corner like this. Perhaps one day MS will come up with a way
of saving a valid activation so that we do not have to go through the
time/trouble it takes to reactivate over the phone. Nevertheless, the system
is operational again on the network and internet albeit it will take a while
yet to re-install and patch all the installed software to the latest versions.

DaveJ