Generate Report in Win7 Crashes ATIH 2012
**My Prior Post was in the wrong thread I think**
Installed AHI 2012 & PP. Both fully licensed. I have successfully created both a NonStop and Scheduled BU (Image). However, anytime I try to run the Generate Report function, AHI crashes and closes. Running on Win7 Pro SP1. Here is the error from the Windows Event Viewer:
Faulting application name: TrueImage.exe, version: 15.0.0.6151, time stamp: 0x4ece2dab
Faulting module name: ti_managers.dll, version: 15.0.0.6131, time stamp: 0x4ebb4287
Exception code: 0xc0000005
Fault offset: 0x0080ca90
Faulting process id: 0xac4
Faulting application start time: 0x01ccb6713c3f3702
Faulting application path: C:\Program Files (x86)\Acronis\TrueImageHome\TrueImage.exe
Faulting module path: C:\Program Files (x86)\Acronis\TrueImageHome\Common\ti_managers.dll
Report Id: f655c8e7-2264-11e1-a94d-b8ac6f9d327a
So I cannot gerneate a system report. Any ideas?
There's not really a lot to be said that would be very helpful, GolfGeezer. Sometimes system components just don't like being accessed in the ways that diagnostic tools may access them, and that isn't specific to the Acronis system reporting tool's methods.
In general, exception code 0xC0000005 indicates an access violation error. Other possible causes could be anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and malware/adware installations. Not easy to pin down, and certainly not possible for any remote non-observer.
Richard,
Thanks for taking a look and commenting. I did send the same via email to Acronis Support, but based on the large amount of negative feedback about their services, I thought that maybe someone in the community might know something. I'll report whatever they do (assuming they do) respond with.
GG
Try booting from the TI bootable recovery CD and choose the create system report option.
GroverH,
While I appreciate that I may be able to run he report by booting from the CD, the issue remains that the program crashes doing a required support report function - and one that should NOT take the app down. Further, the fact that it orphans a memory-eating process that must be manually "killed" needs attention. This is certainly not not your issue to solve, so hopefully Support will respond to my mailed problem report.
GolfGeezer,
I agree with your assessment--just merely trying to provide a temporary workaround.
In my opinion, you would have a better chance of getting a response (and a quicker response) from support if you were to fill out an official support request. Good luck.