Solution for Tally Memory Access Violation

Solution: Four Steps to repair Tally Tally Memory Access Violation - (Software Exception 0xC0000005 If you have been working with Tally for sometime, you might have come accross 'Memory Access Violation' error with some code - '0!000000"'# This usually s$ells doom to many users# %uckly, there are somethings you can do to attem$t to solve the $roblem#

Step !: E"it t#e Tally$ini Confi%uration File There is a setting that tells Tally to automatically load a com$any# &u$$osing the com$any file is corru$ted, you might never start Tally# Tally# &o disable it# i t# The 'T ' Tally#ini' ally#ini' file is in Tally directory# 

Set "default companies from 'yes' to 'no'

&ave the file, close and start Tally# If Tally starts without issues, then your default com$any file is corru$ted and you will need to carry out re$air outlined later in this article#

Step &: A"'ust Screen esolution Tally has issues when being used with fewer colours# Additionaly, different versions of Tally has windows have different minimum reuirements# Access (is$lay &ettings in the control $anel and change (is$lay &ettings as follows)

Windows 2K/XP/Vi 2K/XP/Vista/Win7: sta/Win7:  

Screen Resolution : 1024 by 768 pixels olor !uality : i#$est %&2 bit

Windows 98:  

Screen Resolution : 1024 by 768 pixels olor !uality : 16 bit i#$ olor 

*or +indows , ensure that *ont &i.e is set to '&mall *onts' otherwise Tally may goof# /nce this has been done, restart you com$uter and start Tally# If you still have $roblems, try the net ste$#

Step ): emo*e+,elete rinters es, sometimes Tally has a thing with $rinters1 Make sure you have $rinter installation !(s nearby# (elete the configured $rinters 2including vitual $rinters3# 4o to &tart 5 !ontrol 6anel 5 6rinters 7 *aes# Try to fire tally# If it works, re-install only $rinters that you use and you should be fine#

Step .: Contact Tally Support  At this $oint, you $robably have a more com$le $roblem - this should not make you give u$# !ontact Tally solutions for more hel$#

/ow to epair ,ama%e" Company File Restore older backup

In '&te$ 8' above, you might have established the $roblem to be a corru$t com$any file# 8# !hange to directory to the location where data is stored, usually '(ata' in the tally folder# 9# !om$any files are named using numbers - eg) 8008, 9009 e#t#c# !o$y the corru$t com$any folder to a safe $lace# :# (elete contents of the corru$t com$nay folder# ;# &tart Tally and restore your latest backu$#
f you encounter 1Memory Access1 error w#ile e"itin% a recor" &ometime everything works well so long as you are not deleting or modifying a record# I noticed that, for some unknown reasons this $roblem arises when I try to delete a certain record# I have tried to re-$roduce this scenario without success# =ere is what you can do if you have this kind of $roblem) 8# !arry out instructions outlined in '=ow to >e$air (amaged !om$any *ile' above# 9# &tart Tally and $ress '!T>%?A%T?>' :# ou will be asked to rewrite the com$any file# &elect the $roblematic com$any and acce$t to re-write# ;# /nce the $rocess is com$lete, eit tally#

&tart Tally and edit your records without# If you still have difficulties, then contact Tally &olutions#