WinRM and openPegasus

"Pierre Pacchioni" <[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <007701cd39c2$e73f0cc0$b5bd2640$@com>
Hello,

 

I've been trying to connect a Pegasus server running on Windows with WinRM
(on the same machine).

 

The openPegasus version is the 2.11.1

 

E:\workspace\DCNS\DORIS\openPegasus\pegasus-2.11.1\bin>cimserver.exe

Logs Directory = E:\workspace\DCNS\DORIS\openPegasus\pegasus-2.11.1/./logs

CIM Server 2.11.1

Listening on HTTP port 5988.

Started.

 

I can connect the server using the OpenPegasus client (cimcli.exe) without
any problem.

But I systematically received the bad request status 400 when I tried to
connect winRM with openPegasus server:

E:\workspace\DCNS\DORIS\openPegasus\pegasus-2.11.1\bin>winrm get
winrm/config -machine:localhost:5988

WSManFault

    Message = The WinRM client received an HTTP bad request status (400),
but the remote service did not include any other information about the cause
of the failure.

Error number:  -2144108175 0x80338171

The WinRM client received an HTTP bad request status (400), but the remote
service did not include any other information about the cause of the
failure.

 

Interesting enough I received the same error when I tried to connect
cimcli.exe with WinRM:

E:\workspace\DCNS\DORIS\openPegasus\pegasus-2.11.1\bin>cimcli niall -n
root/cimv2 -l localhost:5985

cimcli Pegasus Exception: HTTP Error (400 Bad Request).. Cmd = niall Object
=

 

So the question is shouldn't WinRM and OpenPegasus be compatible? And if so
how does it work?

I retrieved an old post on exactly the same subject:

http://osdir.com/ml/network.open-pegasus.general/2007-08/msg00028.html

But today OpenPegasus and WinRM (should) support WS-Management.

 

I have another question on the traceLevel. Using cimconfig I changed the
traceLevel to 5 (the max) but I was not able to retrieve/check where the
trace are written?

 

Thanks for your help,

Pierre.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.