HP Integrity rx5670 Windows Integrity nPartition Guide - Page 151

Using WMIOP.EXE to pinpoint problems

Get HP Integrity rx5670 PDF manuals and user guides View all HP Integrity rx5670 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 151 highlights

Troubleshooting Using WMIOP.EXE to pinpoint problems Using WMIOP.EXE to pinpoint problems When relying on multiple software components that are running simultaneously, locating the source of a problem can sometimes be difficult. In cases where an error message does not adequately describe the source of the problem, or when the error could have multiple causes, using the "wmiop.exe" utility that is included with the WMI Mapper component can help track the problem down. Wmiop.exe is installed in the %PEGASUS_HOME%\bin directory. Since this directory is added to the PATH during installation, wmiop can be executed from any directory. If it cannot, that is your first indication that something is wrong, most likely that your PATH environment variable is not set correctly. Syntax for the wmiop utility is described below (an abbreviated usage explanation can also be viewed from the command line by running wmiop with no options): Usage: wmiop [arg, ...] Implemented operations (not case sensitive) are: getClass|gc enumerateClassNames|ecn [ ] getInstance|gi [ list ] enumerateInstances|ei enumerateInstanceNames|ein getProperty|gp { ask | list } [ ] setProperty|sp { ask | list } [ [ ] ] deleteClass|dc createInstance|ci modifyInstance|mi [ list ] deleteInstance|di [ list ] Examples: wmiop ecn wmiop enumerateinstancenames Win32_OperatingSystem wmiop gi Win32_Process list wmiop ei Win32_ComputerSystem Environment variables: Chapter 6 151

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Troubleshooting
Using WMIOP.EXE to pinpoint problems
Chapter 6
151
Using WMIOP.EXE to pinpoint problems
When relying on multiple software components that are running simultaneously,
locating the source of a problem can sometimes be difficult. In cases where an error
message does not adequately describe the source of the problem, or when the error could
have multiple causes, using the “wmiop.exe” utility that is included with the WMI
Mapper component can help track the problem down.
Wmiop.exe is installed in the %PEGASUS_HOME%\bin directory. Since this directory
is added to the PATH during installation, wmiop can be executed from any directory. If it
cannot, that is your first indication that something is wrong, most likely that your PATH
environment variable is not set correctly.
Syntax for the wmiop utility is described below (an abbreviated usage explanation can
also be viewed from the command line by running
wmiop
with no options):
Usage:
wmiop <cimoperation> [arg, ...]
Implemented operations (not case sensitive) are:
getClass|gc <class>
enumerateClassNames|ecn [ <class> ]
getInstance|gi <class> [ list ]
enumerateInstances|ei <class>
enumerateInstanceNames|ein <class>
getProperty|gp <class> { ask | list } [ <propnam> ]
setProperty|sp <class> { ask | list } [ <propnam> [ <value> ] ]
deleteClass|dc <class>
createInstance|ci <class>
modifyInstance|mi <class> [ list ]
deleteInstance|di <class> [ list ]
Examples:
wmiop ecn
wmiop enumerateinstancenames Win32_OperatingSystem
wmiop gi Win32_Process list
wmiop ei Win32_ComputerSystem
Environment variables: