Jump to content

Recommended Posts

assert_log.utx is growing rapidly on exchange server, retrospect client only. Retrospect client latest version.

 

Anyone a suggestion?

 

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

Application: C:\Program Files (x86)\Retrospect\Retrospect Client\pcpds.exe,

Exception occurred on 3/9/2009 at 10:25:59 PM

Exception code: c0000005 ACCESS_VIOLATION

Fault address: 100018b7 0001:000008b7 (null)

 

 

Thread ID: 1624, Name: Unknown

 

EAX:00000000 CS:0023 EIP:100018b7 EFlags:00010212

EBX:00000000 SS:002b ESP:0012fbf4 EBP: 0012fc58

ECX:1000f9f4 DS:002b ESI:00000001 FS: 0053

EDX:0000000f ES:002b EDI:1000f9f4 GS: 002b

 

 

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

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

ex2k7bridge.dll 0001:000008b7 'epiP' 60054f00 644775e0 8 f 64415c0b 2795c0 12fcd4

pcpds.exe 0001:706f7453 0 0 0 0 0 0 50005 8012b

0001:00242780 249468 21c920 217c78 214198 296be8 218668 27a6f8 27a6f8

0001:00242478 0 0 0 0 0 0 50053 1001a6

 

 

etc, etc, etc....

Share this post


Link to post
Share on other sites

This is a bug reported by other users. You can delete the assert log but the problem may come back again. We are working on a fix.

Share this post


Link to post
Share on other sites

We often have problems with our retrospect 7.5 server accessing our exchange 2007 store .

The error we get is : "Can't access backup client exch01, error -505 (backup client reserved)"

 

Yesterday we got the same error again . So i restarted the restrospect client service on the exchange machine , it restarted (it often does not and hangs) . So i thought it would be OK .

Now , 1 hour after i restarted the service we get a full disk on exchange (0kbyte free) . 1 file was the culprit : assert_log.utx .

The file could not be deleted , even after stopping the restrospect client service and the restrospect server service . The file was locked by the process pcpds.exe*32 . I killed the process and removed the assert_log.utx from the exchange disk .

 

I have to say , 700mbyte in 2 days is nothing . Our file was going at 44gbyte per hour .

 

I kept the file for reference . Mayoff , if you need it I can put it on our ftp for you to download .

 

 

Share this post


Link to post
Share on other sites

If you contact technical support we may be able to provide you with a test version that we believe fixes the problem. The issue is logged as bug 20611. Before we can provide the test version, our engineers will need to confirm you have the problem addressed in that bug.

Share this post


Link to post
Share on other sites

Fix was suplied to me and indeed it stopped producing massive assert_log.utx files. However still there are a few errors logged in the assert_log.utx file.

The assert_log.utx file was sent back to your technical support representative for further analysis.

Thanks for your help.

Share this post


Link to post
Share on other sites

I Have the Same Issue

Client on Exchange Server 2007/Server 2003 x64 SP2

Assert_log.utx Grew to 99GB and Halted the Server

Killed the Process responsable & Restarted the Agent

 

Is the FIX Available Yet

 

Tony

Share this post


Link to post
Share on other sites
Is the FIX Available Yet

 

If you contact technical support we may be able to provide you with a test version that we believe fixes the problem. The issue is logged as bug 20611. Before we can provide the test version, our engineers will need to confirm you have the problem addressed in that bug.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×