Jump to content

7.5.387 Released


Recommended Posts

Hello,

 

EMC Insignia has released an update to Retrospect and Retrospect Express 7.5 to address several issues reported by users of Retrospect 7.5.370. The new update is version 7.5.387.

 

To read a list of changes in this update, please visit:

 

http://kb.dantz.com/article.asp?article=8331&p=2

 

 

This update can be downloaded from:

 

http://www.emcinsignia.com/updates or by using the Automatic Updates feature in Retrospect 7.5.

 

 

 

Thank you for using Retrospect

Link to comment
Share on other sites

It fixes the buffer overrun issue, but introduces a new one for me:

 

OS: Windows Server 2003 version 5.2 (build 3790), Service Pack 2, (32 bit)

Application: C:\Program Files\Retrospect\Retrospect 7.5\Retrospect.exe, version 7.5.387

Driver Update and Hot Fix version 7.5.11.100

Exception occurred on 5/15/2007 at 1:29:13 PM

Error info: Assertion failure at "elem.cpp-1000"

 

Exception code: e0000000 ASSERTION

Fault address: 77e4bee7 0001:0000aee7 (null)

 

 

Thread ID: b3c, Name: Backup server source polling

 

EAX:02d9517c CS:22b001b EIP:77e4bee7 EFlags:00000206

EBX:00b74e02 SS:0023 ESP:02d95178 EBP: 02d951cc

ECX:00000000 DS:0023 ESI:02d9520c FS: 181003b

EDX:00000001 ES:506f0023 EDI:02d9520c GS: 61410000

 

 

Module Fn (symbol or seg:offset in DLL) Args

=============== ================================= =======================================================================

kernel32.dll 0001:0000aee7 e06d7363 1 3 2d95200 2d95414 1814efc e06d7363 1

bdrock20.dll __CxxThrowException +34 0 0 2d95414 1814efc b74e02 1 2d9521c 2d94db8

bdrock20.dll DebugHandler::Throw +7C e0000000 1 1 2d95270 2d95370 600550d3 e0000000 1

bdrock20.dll assertLog +16 e0000000 1 2d95270 'essA' 'oitr' 'af n' 'ruli' 'ta e'

bdrock20.dll Debug +63 6007be6c 3e8 2d9618c b74e78 614298ef 1d1a 180ecf8 b74e78

bdrock20.dll ElementSpace::LmGet +D5 180ec84 1d1a '_psp' 180ecf8 16f1 180ecf8 1e6e704 2d953e0

TYCE.DLL tyceKGetItem +41 180ec84 1d1a '_psp' 180ecf8 16f1 2d96154 6060c1cc 180ec84

TYCE.DLL tyceKThreadGet +4A 180ec84 1d1a '_psp' 2d9617c 1d1a 188648 188648 2d961ac

meson.dll ModuleData::send +79C 180ec84 'TSHG' 1d1a '_psp' 2d9617c 1d1a 188648 188648

TYCE.DLL proGetProv +6B 1885b4 1d1a 0 0 188648 0 60640e08 -1

TYCE.DLL proDoEnumList +51 1885b4 1d1a 1 0 1d1a 188648 2d96f40 6060c1cc

TYCE.DLL proDeepList +89 1885b4 1d1a 2d98480 1c0 180 0 a 0

meson.dll ModuleData::send +79C 1885b4 'PoDL' 1d1a 2d98480 1c0 180 0 a

windbvol.rpx remdbGetVolList +43C 22b7d94 1d1a 2d9c644 0 -3 1 0 2

meson.dll ModuleData::send +79C 22b7d94 'VGtL' 1d1a 2d9c644 0 -3 1 0

PCVOL.DLL vttkGetVolList +52B 18c5a7c 16f1 2d9c644 0 -3 1 2d9c338 2d9c560

meson.dll ModuleData::send +79C 18c5a7c 'VGtL' 16f1 2d9c644 0 -3 1 2d9c338

ENGINEHI.DLL extcSourceCheck +42F 18cff64 16f1 16f1 -3 2d9c604 2d9c644 0 0

ENGINEHI.DLL extcCheckItem +9F1 18cff64 d5aa -3 15acb40 2d9e780 0 0 0

ENGINEHI.DLL extcPollOne +440 18cff64 18d0000 2d9f528 6060c1cc 18cff64 0 2d9fee0 6063862e

ENGINEHI.DLL extcPoll +68 18cff64 0 2d9fee0 6063862e 18cff64 0 0 19bca4

meson.dll ModuleData::send +79C 18cff64 'TgPl' 0 2d9fee0 6063862e 18cff64 0 0

meson.dll doTask +299 'Msg ' 0 18cff64 'TgPl' 2d9fa24 2d9fa24 299a2e0 2d9fa28

meson.dll TThread::TaskSend +23 22d840c 'Msg ' 18cff64 'TgPl' 0 2d9fee0 6063862e 18cff64

ENGINEHI.DLL extgSourcePoll +2B 18cff64 0 0 19bca4 0 0 299a834 299a834

meson.dll doTask +21E 'Task' 1570be0 0 0 2d9ff18 2d9ff18 '``EF' 2d9ff84

meson.dll TThread::TaskCall +21 22d840c 'Task' 1570be0 18cff64 0 0 19bca4 0

meson.dll modThreadRoot +15B 299a30c 0 0 b74e78 1 2d9ff90 8085005e 2d9ffdc

MSVCR71.dll 0001:00008565 b74e78 0 0 b74e78 0 2d9ffc4 8085065d -1

kernel32.dll 0001:00023829

Link to comment
Share on other sites

I can see this specific assert mentioned as fixed in regard to two updates, both of which are old. Since I'm running the latest update, whatever is happening on my system, it is something not listed in the knowledge base. Besides, I had no such error before updating to 7.5.370. I cannot exclude the possibility of some change in the environment that coincided with the Retrospect upgrades, but regardless of the cause I still have no leads on how to resolve the problem.

Link to comment
Share on other sites

While you didn't get this specific error in prior versions, you did get the buffer overflow. Retrospect was trying to report the assert error but was unable to do so, due to the wrong error being reported. Retrospect is now reporting the correct error.

 

The KB doc I pointed to should give the needed troubleshooting steps.

Link to comment
Share on other sites

Quote:

OS: Windows Server 2003 version 5.2 (build 3790), Service Pack 2, (32 bit)

Application: C:\Program Files\Retrospect\Retrospect 7.5\Retrospect.exe, version 7.5.387

Driver Update and Hot Fix version 7.5.11.100

Exception occurred on 5/15/2007 at 1:29:13 PM

Error info: Assertion failure at "elem.cpp-1000"

 


 

In general, the most likely cause for an assertion is a bug in Retrospect. That doesn't mean it's specific cause in this case, but I would consider it the prime suspect.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...