"Cannot find perfmon object in array returned by perfDLL, index=0"
Thanks in advance,
Herbert
I have exactly the same problem.
Same configuration.
Peter
"H. Sprang" <h.sp...@gmx.net> wrote in message
news:b7j2f8$8jo$1...@london.vmware.com...
obviously nobody else has these problems (or they don't look in their
eventlogs :-)).
I think it is a bug in the authentication DLL. There are also no VM-objects
in the Performance Monitor.
Greetings
Herbert
"Peter" <petern...@yahoo.com> schrieb im Newsbeitrag
news:b7op3j$2fj$1...@london.vmware.com...
paulo mourão
"H. Sprang" <h.sp...@gmx.net> wrote in message
news:b7uocp$59s$1...@london.vmware.com...
Hi all!
Similar Problem here on Win2k SP3.... :o(
The error-description of error-source "vmauthd":
"Cannot find perfmon object in array returned by perfDLL, index=1"
This Error is logged about 60 times per minute...
Regards,
Matthias
60 times per minute is a very high frequency.
On my computer the event is logged once every 5 minutes for every missing
index (four indexes, 0 - 3). So i have 4 events every 5 minutes.
Greetings
Herbert
"Matthias Branzko" <Matthias...@web.de> schrieb im Newsbeitrag
news:b807pq$atb$1...@london.vmware.com...
my solution so far:
Stop the service and set the starttype to manual. As far as i know you don't
need this service if you hve no user restrictions.
My Vmware works fine without vmauthdservice :-)
Greetings
Herbert
"Paulo Mourão" <paulo....@dataweb.pt> schrieb im Newsbeitrag
news:b7vseo$25s$1...@london.vmware.com...
regards,
paulo mourao
"H. Sprang" <h.sp...@gmx.net> wrote in message
news:b81eeb$b9t$1...@london.vmware.com...
"Workgroup" is a security model.
"TCP/IP" is a network protocol.
So you can't switch between the two...they aren't the same type of
thing.
On Fri, 2 May 2003 23:23:36 +0800, "l" <temp...@21cn.net> wrote:
>my vm4 too.at the same time,the guest os cant access host with workgroup but
>can with tcpip .
>
----
Chuck Gladu
Please note: I am not a VMware employee and I do not
provide VMware support or answer VMware questions via
e-mail. Please limit your replies/questions to the
VMware newsgroups rather then e-mailing me directly.
As you mentioned. I am running VMWARE 4 without vmauthd service started.
So far no problems-:.)
Bur next one is already there, and well know as well.
VMWARE 4 running on hosts Win XP SP1 /W2K SP3 with USB 2.0 hardware are not
always able to use the USB features in the client OS.
VMware 4.0.0-4460 is really a DOT ZERO buggy product.
This release is useless and VMWARE should pay back the money to the
customers who already upgraded to VMWARE 4.
VMware 3.2.0-2230 is running fine on Win XP SP1.
I am NOT willing to spend more time to do beta testing on a released
product.for VMWARE.
Shame on VMWARE!
Peter
"H. Sprang" <h.sp...@gmx.net> wrote in message
news:b7uocp$59s$1...@london.vmware.com...
I had been troubled by the same error for a long while, and recently I
finally found out the cause and got it fixed. In case you are still
interested in a solution to this problem, here is my solution that fixed
the same error on my machine.
It turned out that for some reason the performance counters in
PerfOS.DLL were disabled. Once they were enabled, vmauthd has no problem
to retrieve those perfmon objects it needs, and the error goes away.
To see whether your performance counters in PerfOS.DLL you will need a
program called Extensible Performance Counter List (exctrlst.exe). It
can be found in the Support Tools folder on Windows XP Pro CD, or the
Windows 2000 Resource Kit CD. If you don't have the proper CD, you can
download it from
http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=7ff99683-b7ec-4da6-92ab-793193604ba4.
After you install the program, run it and set the "Sort Order" to
"Counter ID". You should see "PerfOS" near the top of the list. Click on
it, and its status will be displayed at the bottom part of the dialog
window.
If the "Performance Counters Enabled" checkbox is unchecked, that means
your PerfOS counters are diabled. You can simply check the box and press
the "Refresh" button.
Now start or restart your "VMware Authorization Service", and watch the
"Application Event Log" to see whether the vmauthd error stops.
Hope it helps.
Kochin Chang