May 21, 2009 8:39 AM
Failed to install service winexesvc
-
Like (0)
_______________________________________________
Hi
Was wondering if anyone could help? We were trying to pick up SNMP data from process from windows servers and were coming across this error:
ERROR: Failed to install service winexesvc - NT code 0x00000424
This is the command we used to try and install the win exe service:
/usr/local/zenoss/common/bin/winexe -U OURDOMAIN/monitoring%secretpasswd //192.168.1.2x "ipconfig /all"
Any help would be much appreciated with this one! :? :?
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users
"gmiller" wrote:
Hi
Was wondering if anyone could help? We were trying to pick up SNMP data from process from windows servers and were coming across this error:
ERROR: Failed to install service winexesvc - NT code 0x00000424
This is the command we used to try and install the win exe service:
/usr/local/zenoss/common/bin/winexe -U OURDOMAIN/monitoring%secretpasswd //192.168.1.2x "ipconfig /all"
Any help would be much appreciated with this one! :? :?
ERROR: Failed to install service winexesvc - NT code 0x00000424
I was able to get this working as per the instructions on another post.
Although the service failed to register the winexesvc binary was sucessfully copied to my target machine, and it was simply a matter of registering the service manually on this machine with the following 2 commands.
sc create winexesvc binPath= C:\WINDOWS\WINEXESVC.EXE start= auto DisplayName= winexesvc
sc description winexesvc "Remote command provider for Zenoss monitoring"
There's a bug in winexe/service.c file. Get the fresh source from SVN (see below), then find and change the line:
#define NT_STATUS_SERVICE_DOES_NOT_EXIST NT_STATUS(0xc0000424)
into:
#define NT_STATUS_SERVICE_DOES_NOT_EXIST NT_STATUS(0x00000424)
in winexe/service.c then recompile and enjoy :-)
The error code 0x00000424 is explained here for example:
http://infosys.beckhoff.com/content/1031/tcdiagnostics/html/tcdiagnostics_win32_errorcodes.htm
Instructions how to get fresh winexe and compile are:
cd /usr/src
mkdir winexe
cd winexe
svn co http://dev.zenoss.org/svn/trunk/wmi/Samba/source
cd source
./autogen.sh
./configure
make proto bin/winexe
cp -f bin/winexe /usr/local/bin
They're slightly modified from http://ubuntuforums.org/showpost.php?s=cf38d6cc32f1d06db1f02d437f198e03&p=9098595&postcount=8
HTH
Has this been incorporated into any existing distribution, either of Zenoss or an RPM or such of winexe 0.9? Or must we compile it ourselves?
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University
The trunk code still contains the bug:
http://dev.zenoss.org/svn/trunk/wmi/Samba/source/winexe/service.c
(in the block of #includes and #defines near the top).
I have to throw my shoe into the ring here. I have a bunch of WMI systems that are not polling into Zenoss. I'm running the WMI Data Source and the zenfperfwmi log file is chalk full of IO_TIMEOUT errors. However, I try and run this stript:
winexe -U domain/username%password //system 'typeperf -q'
I hoped to confirm the WMI was connecting. The results of that command were.
[winexe/winexe.c:120:on_ctrl_pipe_error()] ERROR: Failed to install service winexesvc - NT code 0x00000424
Almost all of my systems only have partial information from WMI. The services/filesystem/CPU etc information populates but I don't have the freespace information or the status of the services. As such I can't monitor the services or free space since none of that information is working. The default Zenoss graphs are populating, however.
My WMI environment are 32 and 64 bit servers running 2k3 and 2k8. There is no correlation between an OS and it working or not working.
You're not going to make progress unless you fix this bug and recompile it yourself according to my instructions above. For an unknown reason authors still haven't fixed that bug (see http://dev.zenoss.org/svn/trunk/wmi/Samba/source/winexe/service.c near the top). Maybe they're not aware of it.
Thanks.
I've updated the source and made the changes you suggest. I recompiled and restarted Zenoss instance just to be sure. However my WMI script is still producing the same error.
Hi there
following the instructions above I get the following error
-su: ./autogen.sh: No such file or directory
it looks like some of the files are missing is anyone able to help?
cheers
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||