FATAL ERROR: Unhandled Access Viloation Writing 0x6b046550

[coralie.jacobi]

Looking for any help or insight on where to look. We have a .NET application that reads MS ACCESS database files. It creates temporary files on the local machine, so there is writing files involved, not just reading. The application runs great on AutoCAD2013. We now have some users that have ugraded to AutoCAD2014. All but one of us the applicaton runs just as it did. One user get's this error. Not necessarily at the same point in the process, but once it hits, he must reboot his machine to get things cleared out.

He still has AutoCAD 2013 on his machine. Once he reboots, he can run the applicaton with no issues in 2013.

Any suggestions on where to look would be greatly appreciated.

[augusto.goncalves]

If these errors are not consistent, I would suggest you check if all used files are available and accessible (permissions). You may also check for objects not disposed, such as Transactions and Databases (read from file).

[coralie.jacobi]

Thanks Augusto.

The wierd part of this whole thing is it ran fine on the machine with AutoCAD 2013. Now after he has installed 2014, it crashes only in 2014. He can reboot his machine and then run it fine in 2013. We use this application throughout the company, so the issue is definaetly on his manchine.

[mzakiralam]

Try to debug the code. Find out where code stop to work and through exception. It also happened to me that code works fine in AutoCAD 2010 but does not work in 2011. If the error is always in the same line then better to review the code.