Home All Groups Group Topic Archive Search About
Author
31 May 2009 4:03 PM
peleg
i used this code
http://computerperformance.co.uk/vbscript/wmi_event_log_administrator.htm
to search for a content inside the Message property (which show that data in
the Description part fo the event).
the problem is that on winXP there is no problem and i recive the value,
but on win2003 i get empty data
any idea why?
btw : i work as an admin on the server.

Thanks i nadvance
Peleg

Author
31 May 2009 4:40 PM
Cor Ligthert[MVP]
Be aware that there are 4 ways you can use Visual Basic

As VBA like you see in office
As VBS like you use as a system administrator or in a Classic ASP
environment
As VB for Com
Ad VB For Net

The persons in this newsgroup are especially biased on VB for Com, no
problem, but you are asking a question for VBS a different culture, you get
probably a better answer in a newsgroup for VBS Visual Basic Scripting.

Cor

Show quoteHide quote
"peleg" <pe***@discussions.microsoft.com> wrote in message
news:2769A3F3-B120-4576-B8CF-645F4F54693D@microsoft.com...
>i used this code
> http://computerperformance.co.uk/vbscript/wmi_event_log_administrator.htm
> to search for a content inside the Message property (which show that data
> in
> the Description part fo the event).
> the problem is that on winXP there is no problem and i recive the value,
> but on win2003 i get empty data
> any idea why?
> btw : i work as an admin on the server.
>
> Thanks i nadvance
> Peleg
Author
31 May 2009 5:22 PM
Rick Rothstein
Why would you say "especially biased on VB for Com", with an emphasis on the
words "especially biased"? I find it hard to believe that you are not aware
this newsgroup was set up WELL before VB.NET was a gleam in Bill Gates' eye.
As such, it was intended to serve VB for Com users. When VB.NET was
introduced to the market place, Microsoft, recognizing that the Com and .NET
environments were significantly different enough from each other in
programming approach and style, specifically set up newsgroups to handle
VB.NET questions... those newsgroups are where Microsoft intended VB.NET
questions to be asked. By doing that, Microsoft was trying to insure that
this (and the other VB for Com newsgroups) would be kept free of off-topic
questions (that is, free of question that did not pertain to VB for Com).
When VB.NET advocates come into this (and other VB for Com newsgroups) and
encourage posters to continue posting their questions here by answering any
VB.NET questions that they post here rather than redirecting these posters
to the newsgroups Microsoft specifically set up for them (as the volunteers
here regularly attempt to do), then those VB.NET advocates do a grave
disservice to those programmers who have chosen to remain programming in the
VB for Com language. Oh, and yes, I know you (and other VB.NET advocates)
think VB for Com is limited in what it can do by comparison to VB.NET and,
in addition to answering VB.NET questions here, regularly try to point this
out. But so what? The people posting their VB for Com questions here simply
want an answer to their questions, not a sales pitch for a different
language. By the way, all the same arguments VB.NET advocates make for
switching to VB.NET could have been made by C/C++ programmers across the
years... do you think those who asked their VB for Com questions here in
past years would have wanted to see that have happened back then (would you
have)? I think not... and it is for the same reasons VB.NET advocates who
come here pointing out the advantages of VB.NET are not welcome. All such
posts (either answering VB.NET questions in the VB for Com newsgroups or
advocating VB.NET as offering a better solution) do nothing more than create
"noise" for those coming here looking for specific answers to specific
questions for their programming tool of choice... VB for Com (whether you or
other VB.NET advocates think their choice is a wise one or not).

--
Rick (MVP - Excel)


Show quoteHide quote
"Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> wrote in message
news:u06$P6g4JHA.4632@TK2MSFTNGP02.phx.gbl...
> Be aware that there are 4 ways you can use Visual Basic
>
> As VBA like you see in office
> As VBS like you use as a system administrator or in a Classic ASP
> environment
> As VB for Com
> Ad VB For Net
>
> The persons in this newsgroup are especially biased on VB for Com, no
> problem, but you are asking a question for VBS a different culture, you
> get probably a better answer in a newsgroup for VBS Visual Basic
> Scripting.
>
> Cor
>
> "peleg" <pe***@discussions.microsoft.com> wrote in message
> news:2769A3F3-B120-4576-B8CF-645F4F54693D@microsoft.com...
>>i used this code
>> http://computerperformance.co.uk/vbscript/wmi_event_log_administrator.htm
>> to search for a content inside the Message property (which show that data
>> in
>> the Description part fo the event).
>> the problem is that on winXP there is no problem and i recive the value,
>> but on win2003 i get empty data
>> any idea why?
>> btw : i work as an admin on the server.
>>
>> Thanks i nadvance
>> Peleg
>
Author
31 May 2009 6:58 PM
Cor Ligthert[MVP]
"Rick Rothstein" <rick.newsNO.SPAM@NO.SPAMverizon.net> wrote in message
news:OieSoRh4JHA.4272@TK2MSFTNGP04.phx.gbl...
> Why would you say "especially biased on VB for Com", with an emphasis on
> the words "especially biased"?

I would have said exactly the same about VB for Net as it was post in the
Net newsgroups.

But I did not feel the need to say something extra about Net in this
newsgroup.

I hope this explains the reason why I did it?

Cor
Author
31 May 2009 5:56 PM
Richard Mueller [MVP]
Show quote Hide quote
"peleg" <pe***@discussions.microsoft.com> wrote in message
news:2769A3F3-B120-4576-B8CF-645F4F54693D@microsoft.com...
>i used this code
> http://computerperformance.co.uk/vbscript/wmi_event_log_administrator.htm
> to search for a content inside the Message property (which show that data
> in
> the Description part fo the event).
> the problem is that on winXP there is no problem and i recive the value,
> but on win2003 i get empty data
> any idea why?
> btw : i work as an admin on the server.
>
> Thanks i nadvance
> Peleg

The script works fine on Windows Server 2003. Most likely no one has logged
onto the local machine. If the machine is joined to a domain, no one should
log on locally. Most likely everyone authenticates to the domain, so there
are no events with number 680.

--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--
Author
31 May 2009 6:47 PM
peleg
Hi Richard
i changed 680 to my owne source id.
the server is not in a domain, and i have looged to the server as an admin.
the source id that i have indicated does appear in the event viewer and i
see all the properties of that event using that script.
more then that : on XP i got the Message content, but not on win 2003

Thanks
Peleg

Show quoteHide quote
"Richard Mueller [MVP]" wrote:

>
> "peleg" <pe***@discussions.microsoft.com> wrote in message
> news:2769A3F3-B120-4576-B8CF-645F4F54693D@microsoft.com...
> >i used this code
> > http://computerperformance.co.uk/vbscript/wmi_event_log_administrator.htm
> > to search for a content inside the Message property (which show that data
> > in
> > the Description part fo the event).
> > the problem is that on winXP there is no problem and i recive the value,
> > but on win2003 i get empty data
> > any idea why?
> > btw : i work as an admin on the server.
> >
> > Thanks i nadvance
> > Peleg
>
> The script works fine on Windows Server 2003. Most likely no one has logged
> onto the local machine. If the machine is joined to a domain, no one should
> log on locally. Most likely everyone authenticates to the domain, so there
> are no events with number 680.
>
> --
> Richard Mueller
> MVP Directory Services
> Hilltop Lab - http://www.rlmueller.net
> --
>
>
>
Author
31 May 2009 7:51 PM
mayayana
You're in the wrong newsgroup. This group is for
VB, which is not the same thing as VBScript (which
is not the same thing as WMI).

    If the other answers already posted didn't answer your
question then try reposting it in the right group.

A lot of people use WMI through VBScript, so that group
might be good:

microsoft.public.scripting.vbscript

You can also post in the WMI group, since
your question is primarily about WMI:

microsoft.public.win32.programmer.wmi

   It's a little bit awkward because there's no 1-to-1
correspondence between WMI and a given language.
WMI can be accessed a number of ways. So people
in the WMI group -- like people in the general Win32 API
groups -- always seem to assume that everyone is
using whatever programming or scripting language they
themselves happen to be using. :)  But WMI is mainly used
by network admins, and they're typically using VBScript.

Show quoteHide quote
> i used this code
> http://computerperformance.co.uk/vbscript/wmi_event_log_administrator.htm
> to search for a content inside the Message property (which show that data
in
> the Description part fo the event).
> the problem is that on winXP there is no problem and i recive the value,
> but on win2003 i get empty data
> any idea why?
> btw : i work as an admin on the server.
>
> Thanks i nadvance
> Peleg