Actually, it seems to say "system error occurred (174)", not "system
error 174".  Which leads me to believe that it may be saying that the
NBU error was 174 (media manager - system error occurred), not Solaris
error number 174 (which I suppose you'd find in
/usr/include/sys/errno.h if there was a 174).

Anyway, try "bperror -r -S 174".  This error is almost always caused
when media is written using a tape drive with anincorrectly configured
st.conf entry.

Jason Ahrens writes:
> I've tried this duplication a few times. Each time I get the same error...
> (24, socket write failed, Solaris system error 174)
> 
> 17:18:42 INF - host veritasmedia1 backup id CA10044311-a_1007878381 read
> failed, socket write failed (24).
> 
> 17:18:44 INF - host veritasmedia1 backupid CA10044311-a_1007878381 write
> failed, media manager - system error occurred (174).
> 
> 17:18:45 INF - Duplicate of backup id CA10044311-a_1007878381 failed,
> media manager - system error occurred (174).
> 
> I don't know and I can't seem to find what system error 174 is.. This is
> on a Solaris 7 server, running NB DC 3.4.1 NB 2.
> 
> Any ideas?
> 
> Thanks
> 
> Jason
> 
> --
> Jason Ahrens, Systems Analyst
> TELUS Enterprise Solutions
> http://www.telus.com
> The Future is Friendly
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
Larry Kingery 
      Don't use a big word where a diminutive one will suffice.