mastercam Posted October 19, 2006 Report Share Posted October 19, 2006 Has anyone come across this error? Thanks - Gary Link to comment Share on other sites More sharing options...
RonaldL Posted October 19, 2006 Report Share Posted October 19, 2006 Is there any more information after the error number? That error isn't showing up on the error code list. Link to comment Share on other sites More sharing options...
mastercam Posted October 19, 2006 Author Report Share Posted October 19, 2006 That's my point. Retrospect has encountered a serious error Assertion failure at "tmemory.cpp-1176" Link to comment Share on other sites More sharing options...
Lennart_T Posted October 20, 2006 Report Share Posted October 20, 2006 Quote: That's my point. Retrospect has encountered a serious error Assertion failure at "tmemory.cpp-1176" 1176 isn't an error, it's a line number in the source code. "Assertion failure" is an error and you omitted that vital information in your first post. Link to comment Share on other sites More sharing options...
mastercam Posted October 23, 2006 Author Report Share Posted October 23, 2006 Thanks! I didn't notice the obvious. Have you seen the this type of error before? Link to comment Share on other sites More sharing options...
Lennart_T Posted October 23, 2006 Report Share Posted October 23, 2006 I say you (or rather Retrospect) is running out of memory (RAM). How many files are you backing up? What are your hardware specs? What software version are you running? Link to comment Share on other sites More sharing options...
mastercam Posted October 24, 2006 Author Report Share Posted October 24, 2006 Quote: I say you (or rather Retrospect) is running out of memory (RAM). How many files are you backing up? What are your hardware specs? What software version are you running? Retro: 7.5.258 Server/catalog files: Dell PE 2650 2 gig ram Array/storage: EMC CX 300 Files: It varies - but under 4 million I cannot seem to pin point when this happens. Some times it's before certain jobs - then sometimes it's after. I know how to get more 'log' information - I just don't know which log information to focus on getting! Also - we are running only 1 job at at time - not mutli-threading. Also also - most times when this occurs I notice Retrospect memory use get's to over 200 meg in task manager. I don't know what normal specs are for memory usage. Thanks!!! Link to comment Share on other sites More sharing options...
mastercam Posted November 1, 2006 Author Report Share Posted November 1, 2006 106 views - I bet others have this error! Link to comment Share on other sites More sharing options...
Mayoff Posted November 1, 2006 Report Share Posted November 1, 2006 How much free space do you have on the C drive when this happens? What else runs on this computer during the backup? You may want to call TS directly so we can help more directly with this error. Link to comment Share on other sites More sharing options...
nekr0phage Posted November 1, 2006 Report Share Posted November 1, 2006 Mastercam - You may also want to update Retrospect. There was a fix for assertion 'tmemory.cpp-1709' which is not the same error, but may share similar sources. You can see the contents of the update here: http://kb.dantz.com/article.asp?article=9496&p=2 Link to comment Share on other sites More sharing options...
mastercam Posted November 2, 2006 Author Report Share Posted November 2, 2006 Mayoff, Nothing else is runnning on the server. As far as free space 'whenn' this happens...I'm not sure...right now it's 3 gig. Foster, I saw that link and may try it later. Thanks. It seems I get this error mainly when a database/exchange is being backed up...BUT...I'm not sure which log settings to change to see exactly where this error resides. Link to comment Share on other sites More sharing options...
mastercam Posted November 8, 2006 Author Report Share Posted November 8, 2006 I updated Retrospect and still have this issue. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.