Jump to content

Assertion failure at "tmemory.cpp.622" during backup


Recommended Posts



I'm running Retrospect Single Server 6.5.336 on a Windows NT V4.0 SP 6a system; this system is backing up 5 Windows XP systems. While doing a backup, my customer told me that the following error occurred:


"Retrospect has encountered a serious error


Assertion failure at "tmemory.cpp.622"


A log has been written to the file "assert_log.utx"


Please tell Dantz about this problem."


Here's the top part of assert_log.utx"


OS: Windows NT version 4.0 (build 1381), Service Pack 6

Application: C:\Program Files\Dantz\Retrospect\Retrospect.exe, version 6.5.336

Exception occurred on 11/16/2003 at 9:50:32 PM

Error info: Assertion failure at "tmemory.cpp-633"


Exception code: E0000000 ASSERTION

Fault address: 77F1D642 0001:0001C642 KERNEL32.dll



I did some searching in the Dantz Support section, and I'm now guessing that my backup server ran out of memory while backup up a system with many files. One article suggested that I "see the Defining Subvolumes Tutorial". Does this sound like I'm on target?




Link to comment
Share on other sites

Another possibility is that when Retrospect performs a large number of local backups over an extended period of time without quitting, you may experience this error. Configure Retrospect to Quit the backup when done to avoid this error.


How much memory do you have?

How many files on the largest volume?

Are these client or local volumes?

Are you using the client software to backup network volumes?


Making sure Retrospect is quit regularly, using subvolumes, and/or adding additional memory to your computer should help alleviate these issues.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...