I am IT support person for one of our clients and they are complaining about InDesign crashing every time they try to copy text from Ms Office or Open Office. I checked the event logs I found the following error is thrown many times:
Faulting application name: InDesign.exe, version: 7.0.4.553, time stamp: 0x4d890440
Faulting module name: MSVCR90.dll, version: 9.0.30729.4940, time stamp: 0x4ca2ef57
Exception code: 0xc0000005
Fault offset: 0x0003b36a
Faulting process id: 0x9a8
Faulting application start time: 0x01cd36dcfcee3866
Faulting application path: C:\Program Files (x86)\Adobe\Adobe InDesign CS5\InDesign.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCR90.dll
Report Id: 482cfdbe-a2d0-11e1-8bdb-bcaec5e1a2cd
Would appreciate any help you could provide.
It's very hard to debug crashes under Windows 7 (well, anything post-XP); the event log errors don't give enough information to meaningfully point to the problem with any reliability.
Snce this seems to involve MSVCR90, do you have Visual Studio or .NET installed? It may be worth reinstalling one or both of those.
The right way to track these down is to install WinDBG and run InDesign under WinDBG and get a stack trace. Unfortunately this is not a step most people are willing to take, but it will give you insight into what's going wrong.
But feel free to give it a shot and we'll help you out with interpretation.
Is the error reliably reproducible?
Good to see you're running 7.0.4.553 though; that's the latest CS5 update.
What version of Visual Studio I should install and is it available freely on the web?
I'm not suggesting you should install a version of Visual Studio if you don't have it installed already. But the MSVCR90 dll is associated with Visual Studio and/or .NET. If you have one or both of those installed on the machine in question, you should try reinstalling them. For that matter, you might also try reinstalling InDesign.
That said, I do think Visual Studio [Express?] is available for free. (As is WinDBG. I suppose WinDBG probably comes with Visual Studio. I'm not a microsoft development tools expert.)
For debugging, I would recommend this Wiki entry:
http://en.wikipedia.org/wiki/WinDbg
Begin with the first link in the list at the bottom.
Take care, Mike
Tangent:
I would recommend this Wiki entry: http://en.wikipedia.org/wiki/WinDbg
Begin with the first link in the list at the bottom.
OK, Mike, you've got me. Why would you recommend a Wikipedia entry only to say that someone should start with the first link at the bottom? Why not link directly to whatever it is you want to link to?
I'm also kind of confused...are you recommending How to install Windbg and get your first memory dump, blogs.msdn.com/b/johan/archive/2007/01/11/how-to-install-windbg-and-g et-your-first-memory-dump.aspx?
If so, you have me puzzled. It's not wrong information, but we don't want a memory dump. We just want a stack trace. That's the 'kp' command, I believe. I don't have a nice fancy URL to recommnd, so maybe I shouldn't nitpick yours, but it doesn't look very helpful for the problem at hand.
p.s.: it also seems to recommend loading a bunch of extensions that are not helpful here. Like SOS. All that's needed is the core WinDBG.
First off, MSVCR90.dll is installed by the ID installer, so probably has nothing at all to do with viusal studio, so I think that's a red herring.
While the real tools might work better, this sounds like it's probably text related, probably a font issue. Is your user trying to paste formatted, or unformatted content?
North America
Europe, Middle East and Africa
Asia Pacific