An unhandled win32 exception occurred in Offi

October 29, 2010 at 09:01:11
Specs: Windows XP Professional v2002 SP3, Inte(R) Core(TM) 2 CPU 6600 @ 2.40GHz/1.99 BG
Running Windows XP Prof V2002 SP 3 with Office 2007.

Recently, whenever I close Excel 7 or Word 7, I get a pop-up (Visual Studio Just-In-Time Debugger) which states "An unhandled win32 exception occurred in OfficeLIveSignIn exe[4452]".

When I engage the debugger VS returns a pop-up with the following:
"Unhandled exception at 0x01003ce4 in OfficeLIveSignIn.exe:0XC0000005: Access violation reading location 0x00000018."

Anybody recognize this problem


See More: An unhandled win32 exception occurred in Offi

Report •

#1
October 29, 2010 at 09:17:38
THis is Michael Dean again...

I've located the instruction where the fail is occurring:
01003CE4 mov ecx,dword ptr [eax]


Report •

#2
October 29, 2010 at 10:03:09
Google found this site:

http://msdn.microsoft.com/en-us/lib...

where it states:

"This message indicates that Just-In-Time debugging failed because you do not have proper access permissions. For information on the required permissions,"

I do not use Visual Studios, so have no other ideas.

MIKE

http://www.skeptic.com/


Report •

#3
October 29, 2010 at 10:08:43
I may not have been clear about the scenario:

The Debug window opens in response to an access violationi (apparenlty) by OfficeLiveSign.exe. The perplexing part: the violation occurs whenever I close Office 2007 Excel or Word...I'm not sure why OfficeLiveSIgnIn.exe would be triggered by close activities.


Report •

Related Solutions

#4
October 29, 2010 at 10:19:17
You could try a Diagnostic and see if that catchs anything.


Running Microsoft Office Diagnostics from within Excel/Word

Click the Microsoft Office button
Click on the Excel/Word Options button to bring up the Excel/Word Options dialog box (at the bottom of window)
Click on the Resources button in the left hand pane
Click on the Diagnose button in the right hand pane
Click Continue
Click Run Diagnostics

Running Microsoft Office Diagnostics from the Start Menu

Click on the Start button
Click All Programs
Click Microsoft Office folder
Click Microsoft Office Tools
Click Microsoft Office Diagnostics
Click Continue
Click Run Diagnostics

MIKE

http://www.skeptic.com/


Report •

#5
June 19, 2011 at 07:44:32
this file show you that how we can stop runtime debugging on other application and browser

we can enable and disable 3 option in asp.net

goto tool

and open option

after this go on runtime bebugging

disable all 3 option and click OK

we can stop this problem


Report •

#6
June 19, 2011 at 08:45:06
if you have any problem about just in time debugging then you can see my video

how to solve this problem

my video on
http://www.facebook.com/video/video...


Report •

Ask Question