Test Case 32: Sign up for windows error reporting via winqual.microsoft.com
Hello,
My application failed the very last logo test case. I guess the reason is that we haven't sighed up for the windows error reporting.
Here is the question:
1. Do I have to sign up a company account to pass this test even if we don't want to get error reporting from online services? (our user may warry about the security issue such as stealing user info via online error reporting.)
2. If the sigh up is a must, I can see that it goes to VeriSign. However, our code signing certificate is from Comodo (not arrived yet). So, is there any conflict if I got code signing from Comodo, and error reporting from VeriSign?
Thanks for the answer in advance!
haiying
[718 byte] By [
haiying] at [2008-1-4]
Hi,
Thanks for the reply.
I repeated the test again, here is what happened:
After I run threadhijacker, command windows message shows:
********************************************************
Found Process, ID 5184<dec>, Ox1440<hex>
Attempting to hijack thread 2528
Causing access violation exception
Found Process, ID 5184<dec>, Ox1440<hex>
Code injected to 00150000, code injected from 000FEBEC
******************************************************
But I didn't see any application error or window error reporting in event viewer. There are some "information" and "warning", but none from this process ID (5184). So I think that means "test failed".
Please let me know if I did anything wrong and what is the right way.
Many thanks in advance!
haiying
What the elevation level of
1. Threadhijacker
2. Your application
I were running both threadhijacker and my application as logouser1.
Now I tried running both as administrator (using elevation by right click "run as Administrator"), but still didn't get any error or info in event viewer as required. Could you please let me know what is the right steps except those shown in the "certified for windows vista test cases" documents. I didn't see anywhere mentioned elevation level.
Would appreciate if microsoft can update the documents if anything changed. I.e., I see lots of users have quesiton on TC15 &23
about the image tool. The setup13 at the "machine setup and configuration" session is too vague to follow.
Thanks!
haiying
In essence Winqual requires a basic certificate from verisign. This is not the full blown one so the cost is less.
Signing with Comodo is for your application is ok, at long it is on the list.
How is the failure Test Case 32 stated? Did you get this back from the test authority?
Thanks for the reply.
I'm doing internal tests before submit to the test authority. Our current situation is: applied code signing certificate from Comodo (not arrived yet), has not get basic certificate from verisign, thus not registered in Winqual for error reporting.
Back to my original question:
1. Do we have to register for window error reporting in WinQual to pass test case 32?
2. Is that ok to use Comodo code signing other than verisign?
Test Case 32 verification says:
1. All the applications's executables must display the WER dialog message in order to pass this test case.
2. There must be both an Error message with "Source" listed as application error and an information message with "source" losted as Window Error Reporting to pass this test cases.
With my current application (without verisign certificate and winqual registration), I would fail both verifications. But, will the WER registration do the trick? Is there any confliction with Comodo code signing certificate and VeriSign basic certificate?
Haiying
1. Note that even if you do not map your application in WinQual, your user will still have the opportunity to send the info to WinQual in the event of a crash.
2. Using a specific code signing authority is not required for the signing of your application.
I tried threadhijacker.exe to windows media player and notepad. Both behaves exactly the same as our application. I.e., no WER dialog pop up, no error or WER information message in event viewer.
Please explain. Thanks!
haiying
Notepad works fine for me, make sure you syntax is correct
threadhijacker /av /ui /pid:<your pid number>
You should check the settings in Control Panel | Problem Reports and Solutions | Change Settings | Advanced Settings. It's possible that it is turned off on your machine.
Still, no good luck.
I have checked the setting before, it is "On".
Now I also changed the other two options:
For all useres , turn WPR from "All each user to choose settings" to "On"
For All users..., from "Allow each user to choose reporting settings" to "Auto check for solutions (default)".
However, I still did not see application error and WER info message in the event viewer while testing notepad.
Notepad did crash after the execution of threadhijacker, so I assume the command was correct.
When you saying notepad works fine on your machine, what did you see in Event viewer?
Sorry to keep asking, but I'm very flustrated by this test case. Thanks!
haiying
