Class not registered

idan

unread,

Jan 28, 2004, 4:01:10 PM1/28/04

to

hi

on a minlogon command prompt runtime, while trying to run:
C:\>netsh interface ip set address name="Local Area Connection" source=static addr=...

istead of "OK" I got "Class not registered".
i monitored the registry access and found a "not found" CLSID\4950F811-1D3A-11D0-891F-00AA004B2E24
in my XP pro I searched for it in the registry and found the text "WBEN Locator". there is no such component in TD.

does anyone know what component am I missing?

thanks,
idan

KM

unread,

Jan 28, 2004, 6:02:44 PM1/28/04

to

idan,

Have you done "rundll32 netshell.dll HrRenameConnection" command?

Make also sure to include "Network Command Shell Interface Context" and "IP
Router Monitor Library" components.

--
KM,
BSquare Corporation

idan

unread,

Jan 29, 2004, 2:16:17 AM1/29/04

to

yep. so far I have included:
- NetShell
- Network Command Shell
- Network Command Shell Context
- IP Router Monitor Library
- Credential Management User Interface

anything else?

idan

unread,

Jan 29, 2004, 8:01:13 AM1/29/04

to

things so far:

The registry key I found has a subkey with the file Wbemprox.dll. This file is contained in "WMI Core" which is over 6MB, too big for my platform. Therefore I Added it to the configuration, but disabled all the files except: esscli.dll, fastprox.dll and all wbem*.*. This did NOT solve the problem.
The class GUID is there but netsh is looking for values that are not registered.

any other suggestions?

KM

unread,

Jan 29, 2004, 1:55:39 PM1/29/04

to

idan,

Only thing I can tell you now is that a while ago I ended up writing my our
C++ app to change/set ip address manually. The app is pretty simple, it
takes a few parameters and enumerates ip interfaces in registry to set up
what's needed. This way I did not even have a need for netsh.

However, as being mentioned in this NG, some folks made netsh to work on
minlogon image with pretty small footprint. I guess they have not included
WMI Core.

Have you run "rundll32 netshell.dll HrRenameConnection"? I guees you did.
So, your local area network interface is named properly now?

--
KM,
BSquare Corporation

Slobodan Brcin (eMVP)

unread,

Jan 29, 2004, 2:39:02 PM1/29/04

to

As long as you have resolved all your dependencies it should work since you
have included more components than required.
I'm using minlogon and it is working perfectly. Also you don't need "WMI
Core".

Try going step by step.

Type from command prompt:

netsh
netsh>interface
netsh interface>ip
netsh interface ip>?

You can use ? to see what features are present at any level, so use this to
see at what level you will get "Class not registered"
Then we will know exactly what to look at.

KM

unread,

Jan 29, 2004, 3:09:17 PM1/29/04

to

I take my hat off to you :-)
I have not seen more detail message on netsh in this NG!

--
KM,
BSquare Corporation

idan

unread,

Feb 2, 2004, 4:56:07 AM2/2/04

to

thanks for the replies.

one thing I can say for sure... I did include more components than needed.
It actually was a free space problem. XPe needed more than 12MB free on the drive to do it's magic in the FBA phase.

now I have a problem with shares, but that's for a different thread...

idan