Jump to content

agblugano

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About agblugano

  • Rank
    Newbie
  1. Problem solved, it was a corrupted backup set catalog. I think that on startup retrospect is doing a integrity check of some kind on catalog files... but a crash with no warnings shouldn't be an option in case of files corruption in my opinion. Not in an enterprise grade software in any case.
  2. Hi everybody, I have recently purchased the 7.7 upgrade on my 7.6 installation. For 1 week and a half it run fine, but this morning I closed it after noticing that 2 scripts were waiting for backup sets that weren't locked by any activity. Retrospect closed correctly, then I reopened it, recycled one of my backup sets and CRASH! It closed unexpectedly. Then I tried to open it up again, but after 15 seconds from the startup it closed again without notice. This happens every time I try to open it, with no error notification or assert log creation whatsoever. I've tried to recover the config.dat file from the .bak, but to no avail, the application stays on longer but crashes nonetheless. I didn't purchase the ASM with my upgrade, I have never had the need to do it, but this is a SERIOUS issue I'd like to solve. Have you experienced something similar and be of help in solving it? Do you have any idea why this is happening? Thanks. Alberto
  3. agblugano

    Error -540

    Ciao everybody, any news on the situation? I have the same problem to and would like to have an official solution. Even the last update (Retrospect version 7.5.508) didn't fix it. Anyway, may i install the .pdu file in this thread with no worries till a fix is provided?
×