Home > Retrospect Error > Retrospect Error 102

Retrospect Error 102

A faulty driver or an incompatible application is just two of the countless factors why Retrospect Error 102 Trouble Communicating occur. Update the drivers and firmware for your SCSI card and update the firmware for your device if possible. Anybody have any thoughts on this? Low Virtual Memory Once you run out of RAM space for your computer files, this error will come your way. weblink

Home Products Solutions Online Store Support Company News/Articles Blogs Contact Us SitemapPrivacy Policy Products Solutions Contact Us How to Buy Support Company Reseller List Blogs News/Articles Warranty Sitemap Privacy Policy © thanks Mike Back to top #2 Lennart Thelander Lennart Thelander Digital Master Members 454 posts Gender:Male Location:Helsingborg, Sweden Posted 28 June 2011 - 04:59 AM The same tape failed twice ...!Trouble Recent Msgs:issues.maven.apache.org/2016-11/msg00880.htmlfedora-virt-maint/2016-12/msg00001.htmlcentos-devel/2016-12/msg00000.htmlissues.maven.apache.org/2016-11/msg00878.htmlscm-fedora-commits/2016-12/msg00014.htmldev-poi.apache.org/2016-12/msg00001.htmlubuntu-bugs/2016-12/msg00014.htmlgeneral/2016-12/msg00118.htmlwp-svn/2016-12/msg00006.htmlcore-libs-dev/2016-12/msg00003.html Latest News Stories: Linux 4.0 Kernel Released Google Lets SMTP Certificate Expire Open Crypto Audit Passes TrueCrypt CIA 'tried to crack security of Apple devices' Xen Security Bug: Amazon, Changing the advanced tab settings will allow you to do this. https://www.retrospect.com/en/support/kb/troubleshooting_error_102_trouble_communicating

If there are still errors, it is an indication that there is a problem with the device. I cannot get the tape backups to work because I keep getting this error 102 message. This is simply an indication that something needs to be done in your personal computer so be free from worries. Last Update: February 14, 2012 About Us Press Support Privacy Downloads Upgrade Buy Try Facebook Twitter LinkedIn Spiceworks YouTube Kiva Blog Choose your language: Deutsch English English-AU English-UK Español Français

Has anyone else experienced this? Changing the computer immediately is not a smart move, try to troubleshoot the problems first. Retrospect Search Products Support Partners Buy Free Trial Support Support and Maintenance Downloads Knowledge Base Documentation Register Contact Us Error -102 Trouble Communicating Resources Troubleshooting USB/Firewire devices: Make sure the connection Since 1994 Back to top Back to Networking and Clients 1 user(s) are reading this topic 0 members, 1 guests, 0 anonymous users Reply to quoted postsClear Retrospect Forum →

And have you found a solution? Try the device on a second computer. One G5 iMac volume took 5 hours, while a comparable size volume on a Jaguar machine took about one hour. http://forums.retrospect.com/index.php?/topic/23445-error-102-trouble-communicating/ What you should do is to find the main cause of the error to take necessary troubleshoot.

Jump to content Windows | Mac | iPhone & iPad | Buy | Buy Try Upgrade Partners | Support Sign Tudor Road, Suite 1 Anchorage AK 99507 907-562-7372 [email protected] Previous Message by Thread: error 102 trouble communicating I have a Windows 2000 Adv Server with the latest version of Retrospect installed Alter the size of your Pagefile up to 1.5 to double of your RAM�s memory. OSDir.com sysutils.retrospect.general Subject: RE: error 102 trouble communicating Date Index Thread: Prev Next Thread Index Boy, do I have some experience with this error! (Been having an intermittent -102

Please only post your question one time. Troubleshooting Fibre Channel devices: Try different fibre channel cards and cables and make sure the cable is connected securely. Could be a bad tape drive, a bad tape, a bad SCSI card, a hardware problem, etc... In rare cases, the firmware for the USB Bridge (part of the external USB drive case) may need to be updated.

These are always generated by the destination device (e.g., Personal Storage 5000) and reported by Retrospect. have a peek at these guys I am running Retrospect server (6.0.204) on a G4 tower, OS 10.2.8, 400 MHz processor, 256 RAM. Sorry if this has been posted out before. I had a possible power brown out one night, but no known power or network issues last night.

Copyright © 2016 Retrospect, Inc. Installing a new and also updated good antivirus will do well for you. Make sure the USB 2 devices are being used with a USB 2 port for best performance. http://fiftysixtysoftware.com/retrospect-error/retrospect-error-505.html This is not solved with a simple ESC or Ctrl + Alt + Del.

Just do not forget to check out the supplier of the RAM whenever you plan to get one. Connect devices directly the computer. Update the firmware for the device.

You can switch between NT Passthrough and ASPI by going to Configure>Preferences>Media>Handling and toggling the option to "Use ASPI to communicate with devices".

Lost DLL Files If there is a program trying to be run and suddenly stopped, there might be a missing file causing this Retrospect Error 102 Trouble Communicating. Connect devices directly the computer. Provide feedback Please rate the information on this page to help us improve our content. The common reason for these errors are virus.

Please re-enable javascript to access full functionality. Can Bad Media Cause Error -102? I had a possible power brown out one night, but no known power or network issues last night. Most devices are qualifed on the Macintosh using ATTO UL3 and UL4 SCSI cards. this content Note: Adaptec has dropped support for the Mac OS as of 10.3.x.