Jump to content

sjmike

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sjmike

  • Rank
    Occasional forum poster
  1. We're running version 7.0.249 on a Windows 2003 Server, Exchange Server 2003
  2. We're running Exchange Server 2003 with all the latest patches and Retrospect 7.0. When backing up certain mailboxes we get these error messages. It has been ongoing for about over a month now and we've never had this problem in the past. T-52: PtSend: cmd MbeF/msg RdBg: byte count 1261 exceeds maximum of 1024 Trouble reading files, error -523 (service transaction error) T-635: PtSend: cmd MbeF/msg RdBg: byte count 1261 exceeds maximum of 1024 Trouble reading files, error -523 (service transaction error) Unfortunately the 2 mailboxes that it occurs on are the President and VP of the company Any idea what might be causing these errors?
  3. For a few of our mailboxes we're getting these errors when backing them up. T-349: MBDataInputStream::PrepareLongProperty: Failure (winerr = 0x80004005) to read long property 0x1009. and its typically followed up by this error: File "Mike\Files\00000000e57f71d18b2c1d4593b10a8e2ef7f7360700826a18112673de47a30de8e99e5da2020000000033a500002e7872176a215849aad5cf0f0d762d130000437a0ee00000": can't read, error -1012 (feature unsupported) Any suggestions on how to resolve these errors? Running Exchange Server 2003. Using Retrospect 7.0 MultiServer with the 7.0 client
  4. sjmike

    SQL Server not seen

    Hi Amy, I registered the Sqldmo.dll like the link said, and deleted the client from Retrospect and re-added it afterwards and still have the same problem. The Enterprise Manager can access the SQL instance without any problems. Even the the SQL Server Service Manager can access / see it on all 3 systems. Just Retrospect can't see it on the newest system. Any other suggestions?
  5. sjmike

    SQL Server not seen

    For some reason retrospect does not want to see the SQL container on one our newest networked computers. However it recognizes it on the old system. The 2 systems with SQL Server 2000 running are using the 7.0.106 client. The backup system is running Retrospect 7.0.249 with a Multi Server License and the SQL Backup Add-on. All 3 systems are on Windows 2003. I even attempted to install Retrospect server locally on the problem system and it didn't see the SQL container either. Any suggestions?
×