Greetings,
Every time we try to use AppVerifier we get huge log files that essentially
can't be opened.  Start our app, shut it down and AppVerifier says there's 7
errors and 26 warnings.  Hit 'view' and the XML file is so big it can't be
opened by IE.  This is on a dual core AMD with 2 Gig of memory.

What are we doing wrong?

Thanks for any advice,
-Michael Viking

Hi Michael,
How big is the log file? 
You can covert the binary log file to XML format using AppVerifier command 
line as well. Can you try that and see if it works? the logs are stored in 
%USERPROFILE%\AppVerifierLogs.
Can you also let us know what version of AppVerifier you are using and what 
checks you enabled on your app.
Thanks you,
Prasad

"Michael Viking" wrote:

> Greetings,
> Every time we try to use AppVerifier we get huge log files that essentially
> can't be opened.  Start our app, shut it down and AppVerifier says there's 7
> errors and 26 warnings.  Hit 'view' and the XML file is so big it can't be
> opened by IE.  This is on a dual core AMD with 2 Gig of memory.
> 
> What are we doing wrong?
> 
> Thanks for any advice,
> -Michael Viking
> 
> 
>

Thanks for the reply.  The log file that had 7 errors and 26 warnings was
about 10 megabytes.  I tried both hitting the view button in AppVerifier,
and exporting to XML.  The fact seems to be that IE cannot handle an XML
file that big.  The only thing I enabled was LuaPriv.  No changes were made
anywhere, everything defaults.  Just add my app, click on LuaPriv to turn it
on and unclick Basics to turn them off.  Start my app, quit my app.  That's
all.  This is version 3.3 of AppVerifier, the latest, I believe.
-Michael Viking


"Prasad Kakulamarri [MSFT]"
 wrote in message
news:4AF7A3E5-48FF-403C-9E33-BD1F21B84798@microsoft.com...
> Hi Michael,
> How big is the log file?
> You can covert the binary log file to XML format using AppVerifier command
> line as well. Can you try that and see if it works? the logs are stored in
> %USERPROFILE%\AppVerifierLogs.
> Can you also let us know what version of AppVerifier you are using and
what
> checks you enabled on your app.
> Thanks you,
> Prasad
>
> "Michael Viking" wrote:
>
> > Greetings,
> > Every time we try to use AppVerifier we get huge log files that
essentially
> > can't be opened.  Start our app, shut it down and AppVerifier says
there's 7
> > errors and 26 warnings.  Hit 'view' and the XML file is so big it can't
be
> > opened by IE.  This is on a dual core AMD with 2 Gig of memory.
> >
> > What are we doing wrong?
> >
> > Thanks for any advice,
> > -Michael Viking
> >
> >
> >

Hi,
I am not sure why IE is not able to open the XML file. Have you tried 
manually opening this file from IE rather than AppVerifier? Can you open this 
XML file using notepad? I won't be able to tell what the problem is without 
looking at the log file. 
Thanks,
Prasad

"Michael Viking" wrote:

> Thanks for the reply.  The log file that had 7 errors and 26 warnings was
> about 10 megabytes.  I tried both hitting the view button in AppVerifier,
> and exporting to XML.  The fact seems to be that IE cannot handle an XML
> file that big.  The only thing I enabled was LuaPriv.  No changes were made
> anywhere, everything defaults.  Just add my app, click on LuaPriv to turn it
> on and unclick Basics to turn them off.  Start my app, quit my app.  That's
> all.  This is version 3.3 of AppVerifier, the latest, I believe.
> -Michael Viking
> 
> 
> "Prasad Kakulamarri [MSFT]"
>  wrote in message
> news:4AF7A3E5-48FF-403C-9E33-BD1F21B84798@microsoft.com...
> > Hi Michael,
> > How big is the log file?
> > You can covert the binary log file to XML format using AppVerifier command
> > line as well. Can you try that and see if it works? the logs are stored in
> > %USERPROFILE%\AppVerifierLogs.
> > Can you also let us know what version of AppVerifier you are using and
> what
> > checks you enabled on your app.
> > Thanks you,
> > Prasad
> >
> > "Michael Viking" wrote:
> >
> > > Greetings,
> > > Every time we try to use AppVerifier we get huge log files that
> essentially
> > > can't be opened.  Start our app, shut it down and AppVerifier says
> there's 7
> > > errors and 26 warnings.  Hit 'view' and the XML file is so big it can't
> be
> > > opened by IE.  This is on a dual core AMD with 2 Gig of memory.
> > >
> > > What are we doing wrong?
> > >
> > > Thanks for any advice,
> > > -Michael Viking
> > >
> > >
> > >
> 
> 
>

Hi Prasad,

Thanks for the response.  I have tried manually opening the file.  Let me be
clear that it does eventually open after taking up huge amounts of memory
and time.  Perhaps after 5 minutes or so it will finally open.

Is there any way I can send you an XML file to look at?

Thanks,
-Michael


"Prasad Kakulamarri [MSFT]"
 wrote in message
news:7950EDB3-C931-45C2-9A90-799080EEF8E8@microsoft.com...
> Hi,
> I am not sure why IE is not able to open the XML file. Have you tried
> manually opening this file from IE rather than AppVerifier? Can you open
this
> XML file using notepad? I won't be able to tell what the problem is
without
> looking at the log file.
> Thanks,
> Prasad
>
> "Michael Viking" wrote:
>
> > Thanks for the reply.  The log file that had 7 errors and 26 warnings
was
> > about 10 megabytes.  I tried both hitting the view button in
AppVerifier,
> > and exporting to XML.  The fact seems to be that IE cannot handle an XML
> > file that big.  The only thing I enabled was LuaPriv.  No changes were
made
> > anywhere, everything defaults.  Just add my app, click on LuaPriv to
turn it
> > on and unclick Basics to turn them off.  Start my app, quit my app.
That's
> > all.  This is version 3.3 of AppVerifier, the latest, I believe.
> > -Michael Viking
> >
> >
> > "Prasad Kakulamarri [MSFT]"
> >  wrote in message
> > news:4AF7A3E5-48FF-403C-9E33-BD1F21B84798@microsoft.com...
> > > Hi Michael,
> > > How big is the log file?
> > > You can covert the binary log file to XML format using AppVerifier
command
> > > line as well. Can you try that and see if it works? the logs are
stored in
> > > %USERPROFILE%\AppVerifierLogs.
> > > Can you also let us know what version of AppVerifier you are using and
> > what
> > > checks you enabled on your app.
> > > Thanks you,
> > > Prasad
> > >
> > > "Michael Viking" wrote:
> > >
> > > > Greetings,
> > > > Every time we try to use AppVerifier we get huge log files that
> > essentially
> > > > can't be opened.  Start our app, shut it down and AppVerifier says
> > there's 7
> > > > errors and 26 warnings.  Hit 'view' and the XML file is so big it
can't
> > be
> > > > opened by IE.  This is on a dual core AMD with 2 Gig of memory.
> > > >
> > > > What are we doing wrong?
> > > >
> > > > Thanks for any advice,
> > > > -Michael Viking
> > > >
> > > >
> > > >
> >
> >
> >

I would suggest you use the "Standard User Analyzer" (part of Application 
Compatibility Toolkit 5.0 on Microsoft download) to analyzer your app for 
LUA issues. It will take care of the big log file issue and will make the 
result more readable by categorizing them and filtering out unnecessary 
entries.

Thanks,
Yu
-- 
This posting is provided "AS IS" with no warranties, and confers no rights.


"Michael Viking"  wrote in message 
news:Oz04fdGXHHA.4872@TK2MSFTNGP03.phx.gbl...
> Hi Prasad,
>
> Thanks for the response.  I have tried manually opening the file.  Let me 
> be
> clear that it does eventually open after taking up huge amounts of memory
> and time.  Perhaps after 5 minutes or so it will finally open.
>
> Is there any way I can send you an XML file to look at?
>
> Thanks,
> -Michael
>
>
> "Prasad Kakulamarri [MSFT]"
>  wrote in message
> news:7950EDB3-C931-45C2-9A90-799080EEF8E8@microsoft.com...
>> Hi,
>> I am not sure why IE is not able to open the XML file. Have you tried
>> manually opening this file from IE rather than AppVerifier? Can you open
> this
>> XML file using notepad? I won't be able to tell what the problem is
> without
>> looking at the log file.
>> Thanks,
>> Prasad
>>
>> "Michael Viking" wrote:
>>
>> > Thanks for the reply.  The log file that had 7 errors and 26 warnings
> was
>> > about 10 megabytes.  I tried both hitting the view button in
> AppVerifier,
>> > and exporting to XML.  The fact seems to be that IE cannot handle an 
>> > XML
>> > file that big.  The only thing I enabled was LuaPriv.  No changes were
> made
>> > anywhere, everything defaults.  Just add my app, click on LuaPriv to
> turn it
>> > on and unclick Basics to turn them off.  Start my app, quit my app.
> That's
>> > all.  This is version 3.3 of AppVerifier, the latest, I believe.
>> > -Michael Viking
>> >
>> >
>> > "Prasad Kakulamarri [MSFT]"
>> >  wrote in message
>> > news:4AF7A3E5-48FF-403C-9E33-BD1F21B84798@microsoft.com...
>> > > Hi Michael,
>> > > How big is the log file?
>> > > You can covert the binary log file to XML format using AppVerifier
> command
>> > > line as well. Can you try that and see if it works? the logs are
> stored in
>> > > %USERPROFILE%\AppVerifierLogs.
>> > > Can you also let us know what version of AppVerifier you are using 
>> > > and
>> > what
>> > > checks you enabled on your app.
>> > > Thanks you,
>> > > Prasad
>> > >
>> > > "Michael Viking" wrote:
>> > >
>> > > > Greetings,
>> > > > Every time we try to use AppVerifier we get huge log files that
>> > essentially
>> > > > can't be opened.  Start our app, shut it down and AppVerifier says
>> > there's 7
>> > > > errors and 26 warnings.  Hit 'view' and the XML file is so big it
> can't
>> > be
>> > > > opened by IE.  This is on a dual core AMD with 2 Gig of memory.
>> > > >
>> > > > What are we doing wrong?
>> > > >
>> > > > Thanks for any advice,
>> > > > -Michael Viking
>> > > >
>> > > >
>> > > >
>> >
>> >
>> >
>
>

Hi Yu Chen,

Thanks for the response.

May I bill you for the time I've spent on this non-functioning tool that
Microsoft recommends for getting an application logo certified?  :-)

-Michael Viking?

"Yu Chen [MSFT]"  wrote in message
news:AA13A7E6-C988-4F9F-B13D-20DE98263315@microsoft.com...
> I would suggest you use the "Standard User Analyzer" (part of Application
> Compatibility Toolkit 5.0 on Microsoft download) to analyzer your app for
> LUA issues. It will take care of the big log file issue and will make the
> result more readable by categorizing them and filtering out unnecessary
> entries.
>
> Thanks,
> Yu
> -- 
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Michael Viking"  wrote in message
> news:Oz04fdGXHHA.4872@TK2MSFTNGP03.phx.gbl...
> > Hi Prasad,
> >
> > Thanks for the response.  I have tried manually opening the file.  Let
me
> > be
> > clear that it does eventually open after taking up huge amounts of
memory
> > and time.  Perhaps after 5 minutes or so it will finally open.
> >
> > Is there any way I can send you an XML file to look at?
> >
> > Thanks,
> > -Michael
> >
> >
> > "Prasad Kakulamarri [MSFT]"
> >  wrote in message
> > news:7950EDB3-C931-45C2-9A90-799080EEF8E8@microsoft.com...
> >> Hi,
> >> I am not sure why IE is not able to open the XML file. Have you tried
> >> manually opening this file from IE rather than AppVerifier? Can you
open
> > this
> >> XML file using notepad? I won't be able to tell what the problem is
> > without
> >> looking at the log file.
> >> Thanks,
> >> Prasad
> >>
> >> "Michael Viking" wrote:
> >>
> >> > Thanks for the reply.  The log file that had 7 errors and 26 warnings
> > was
> >> > about 10 megabytes.  I tried both hitting the view button in
> > AppVerifier,
> >> > and exporting to XML.  The fact seems to be that IE cannot handle an
> >> > XML
> >> > file that big.  The only thing I enabled was LuaPriv.  No changes
were
> > made
> >> > anywhere, everything defaults.  Just add my app, click on LuaPriv to
> > turn it
> >> > on and unclick Basics to turn them off.  Start my app, quit my app.
> > That's
> >> > all.  This is version 3.3 of AppVerifier, the latest, I believe.
> >> > -Michael Viking
> >> >
> >> >
> >> > "Prasad Kakulamarri [MSFT]"
> >> >  wrote in message
> >> > news:4AF7A3E5-48FF-403C-9E33-BD1F21B84798@microsoft.com...
> >> > > Hi Michael,
> >> > > How big is the log file?
> >> > > You can covert the binary log file to XML format using AppVerifier
> > command
> >> > > line as well. Can you try that and see if it works? the logs are
> > stored in
> >> > > %USERPROFILE%\AppVerifierLogs.
> >> > > Can you also let us know what version of AppVerifier you are using
> >> > > and
> >> > what
> >> > > checks you enabled on your app.
> >> > > Thanks you,
> >> > > Prasad
> >> > >
> >> > > "Michael Viking" wrote:
> >> > >
> >> > > > Greetings,
> >> > > > Every time we try to use AppVerifier we get huge log files that
> >> > essentially
> >> > > > can't be opened.  Start our app, shut it down and AppVerifier
says
> >> > there's 7
> >> > > > errors and 26 warnings.  Hit 'view' and the XML file is so big it
> > can't
> >> > be
> >> > > > opened by IE.  This is on a dual core AMD with 2 Gig of memory.
> >> > > >
> >> > > > What are we doing wrong?
> >> > > >
> >> > > > Thanks for any advice,
> >> > > > -Michael Viking
> >> > > >
> >> > > >
> >> > > >
> >> >
> >> >
> >> >
> >
> >
>

Hi Michael,
LUAPriv is not a required for logo. LUAPriv logs informational messages by 
default along with warnings and errors. This is the reason you are seeing 
huge log files even though the number of errors and warnings is small. You 
can turn off logging for informational messages by configuring the verifier 
stop options for LUAPriv. Right click on LUAPriv, click on Verifier Stop 
Options and go through each verifier stop and turn off logging and stack 
trace for those stops that are informational.
We will consider changing this default logging behavior.

Thank you,
Prasad

"Michael Viking" wrote:

> Hi Yu Chen,
> 
> Thanks for the response.
> 
> May I bill you for the time I've spent on this non-functioning tool that
> Microsoft recommends for getting an application logo certified?  :-)
> 
> -Michael Viking?
>

Hi Prasad,

Thanks for the information and the clarification.  We definitely thought
LUAPriv was required.

Would you also consider fixing the dialog for verifier stop options?  It
should a) be multi-select for verifier stop numbers, and b) I shouldn't have
to hit "OK" for every change I make.  For example, if I pick a verifier stop
number, make a change, choose a new verifier stop number, then go back to
the original verifier stop number, my changes are gone!!  These two combined
make for a very poor user experience.

Thanks,
-Michael

"Prasad Kakulamarri [MSFT]"
 wrote in message
news:E7CA0110-26BD-4866-88A6-2D2C645B141C@microsoft.com...
> Hi Michael,
> LUAPriv is not a required for logo. LUAPriv logs informational messages by
> default along with warnings and errors. This is the reason you are seeing
> huge log files even though the number of errors and warnings is small. You
> can turn off logging for informational messages by configuring the
verifier
> stop options for LUAPriv. Right click on LUAPriv, click on Verifier Stop
> Options and go through each verifier stop and turn off logging and stack
> trace for those stops that are informational.
> We will consider changing this default logging behavior.
>
> Thank you,
> Prasad
>
> "Michael Viking" wrote:
>
> > Hi Yu Chen,
> >
> > Thanks for the response.
> >
> > May I bill you for the time I've spent on this non-functioning tool that
> > Microsoft recommends for getting an application logo certified?  :-)
> >
> > -Michael Viking?
> >
>

Michael,
Thank you for the feedback. A few other folks also complained about these 
same issues. I will add them to my list of work items.
Thank you,
Prasad

"Michael Viking" wrote:

> Hi Prasad,
> 
> Thanks for the information and the clarification.  We definitely thought
> LUAPriv was required.
> 
> Would you also consider fixing the dialog for verifier stop options?  It
> should a) be multi-select for verifier stop numbers, and b) I shouldn't have
> to hit "OK" for every change I make.  For example, if I pick a verifier stop
> number, make a change, choose a new verifier stop number, then go back to
> the original verifier stop number, my changes are gone!!  These two combined
> make for a very poor user experience.
> 
> Thanks,
> -Michael
> 
> "Prasad Kakulamarri [MSFT]"
>  wrote in message
> news:E7CA0110-26BD-4866-88A6-2D2C645B141C@microsoft.com...
> > Hi Michael,
> > LUAPriv is not a required for logo. LUAPriv logs informational messages by
> > default along with warnings and errors. This is the reason you are seeing
> > huge log files even though the number of errors and warnings is small. You
> > can turn off logging for informational messages by configuring the
> verifier
> > stop options for LUAPriv. Right click on LUAPriv, click on Verifier Stop
> > Options and go through each verifier stop and turn off logging and stack
> > trace for those stops that are informational.
> > We will consider changing this default logging behavior.
> >
> > Thank you,
> > Prasad
> >
> > "Michael Viking" wrote:
> >
> > > Hi Yu Chen,
> > >
> > > Thanks for the response.
> > >
> > > May I bill you for the time I've spent on this non-functioning tool that
> > > Microsoft recommends for getting an application logo certified?  :-)
> > >
> > > -Michael Viking?
> > >
> >
> 
> 
>