Cory,
> I realize that 'communication error' is supposed to indicate a disconnect
> between the backup machine and the backup device but backups from a Mac
> running Retrospect client to this same machine and drive succeeds just fine.
That's basically what this error means, even if the drive works OK
elsewhere. Sounds like this PC/drive combination is having problems,
especially with the hanging problem. Off the top of my head:
Update SCSI card drivers.
Uninstall any extraneous drivers Windows or other software may have
installed.
Make sure ASPI is installed by running ASPICHK (installed into the
Retrospect Program Files directory).
Try a different tape in your drive.
Try the drive connected to a different PC with a different card.
If these don't help, please call us.
Matthew Tevenan
Technical Support Specialist
Dantz Development Corporation
925.253.3050
[EMAIL PROTECTED]
> From: Cory Rau <[EMAIL PROTECTED]>
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Thu, 10 Aug 2000 17:51:00 -0400
> To: retro-talk <[EMAIL PROTECTED]>
> Subject: Re: NT Backup Failing
>
> Though I'm new to this list, I've been using many flavors of Retrospect for
> a long time but have never encountered the problem I'm having now.
>
> I've got Retrospect 5.11 installed on an NT Workstation machine (sp 6a) and
> Retrospect client (most recent version downloaded from the Dantz web site
> yesterday) on an NT Server (sp 5) file server (all Intel-based logic
> boards). We have a 10Base-T network which runs great in every respect.
> I've been using this basic configuration for a long time but recently, the
> parallel port on the machine running Retrospect took a dirt nap. No
> problem, I thought, I can install this HP Colorado Travan External 8MB
> (parallel port connect) tape drive on another machine and just run the
> backup from there. Well, now, whenever we try to backup the NT Server,
> Retrospect on the workstation freezes up at varying points in the backup.
> Many times, I get a communication error (I believe it's -102). Other times,
> Retrospect just hangs and the drive ceases all activity. My only choice at
> that point is to bring up the task manager and force the task to end.
>
> I've updated all appropriate drivers and respective Retrospect products on
> all machines and rebooted them all. No go.
>
> I realize that 'communication error' is supposed to indicate a disconnect
> between the backup machine and the backup device but backups from a Mac
> running Retrospect client to this same machine and drive succeeds just fine.
> Admittedly, the backup on the Mac side is far smaller than the one on the NT
> Server but still...
>
> Anyone experienced this before? I swear I have but I can't remember for the
> life of me how we got it solved. We've been running with this configuration
> successfully for over a year. All machines seem to be in tip-top shape.
> The NT Server runs like a champ 24/7.
>
> Thanks in advance for any help...I'm anxious to stop this file-transfer type
> manual backup.
>
> Regards,
>
> ----------------------------
> | Cory Rau |
> | Stimpson Co., Inc. |
> | 631-472-2000 x 306 |
> | [EMAIL PROTECTED] |
> ----------------------------
>
>
>
>
> --
> ----------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://list.working-dogs.com/lists/retro-talk/>
> Problems?: [EMAIL PROTECTED]
>
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://list.working-dogs.com/lists/retro-talk/>
Problems?: [EMAIL PROTECTED]
