Thanks chirrupowner, but I believe your problem, although it has similar symptoms, was different than the one reported in this thread.
This is evidenced by the fact that the problem persisted for you even when Mcaffee was disable or unistalled. In the problem we are all dealing with, disableling Mcaffee DOES fix the probem.
The solution you posted appears to simply disable the VS JIT debugger - which in your case, was running even when there was no bug.
Our (still unresolved) issue is related to a bug found by the JIT debugger, which is:
"Validlink_google is invalid".
This problem was clearly caused by the Mcaffee update. Turning off the debugger may stop the messages (I haven't tried it yet) but in this case I think it would be the equivelent of saying "If I don't go see the doctor, I'm not sick"
Mcafee we are patiently awaiting a resolution
HELLO???? Where are we at now? This has been going on since the 6th of January today is the 14th. Enough is Enough, McAfee is suppose to protect me from this kind of stuff not give it to me. Time for an update please!!!!
yes, I think this is enough time. You need to roll this back, give us some options here or find a new line of work Mcaffee. Patience now gone!
Hello everyone! I just wanted to update you on the status of the fix for this issue. McAfee just finished posting a fix, remotely, to my system to see if it would fix the problem and, I am happy to say, that it has. They said that they will now include the fix in an update and systems that have been affected will be automatically fixed with the update. Timeframe is still the same, by the end of the week. Dinesh, thank you for your time and help with this matter, it is greatly appreciated!
Thank you Diminutives!! We appreciate your feedback. I request you all to test the below mention steps and update us.
Step 1 - Disable Access Protection
Step 2 –
Step 3 -
Enable Access Protection
RegardsMessage was edited by: BalaSGS on 1/19/11 12:40:17 PM GMT-06:00
Bala, should we cosnider this to be the actual fix; or is it more of a diagnostic thing, to help you pinpoint the specific script causing the problem?
Would still like a response to the question that I asked last week:
Bala, should we consider this to be the actual fix; or is it more of a diagnostic thing, to help you pinpoint the specific script causing the problem?