Two other things to verify:

1. Make sure "MOUNTWaitfordata" is set to yes.
   Enter this command:
      tdpsqlc set MOUNTWaitfordata=yes

2. Make sure that the program waits for tape mounts.
   Add this option to the backup commands in the script file:
      /MOUNTWait=Yes

If the ideas above do not help and Richard's ideas do not help,
you should consider calling IBM support to help you.
They can gather the TSM Server traces necessary to
find out what is causing the internal server error.

Thanks,

Del

----------------------------------------------------

>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to ADSM-L
>
> I have read the act log of a scheduled backup and I found this
>
> 28/05/09 01:13:50 AM COT ANR0530W Transaction failed for session
> 195942 for node XXXX_SQL (TDP MSSQL Win32) - internal server error
> detected. (SESSION: 195942)
>
> 28/05/09 01:33:52 AM COT ANE4993E (Session: 195941, Node: XXXX_SQL)
> TDP MSSQL Win32 ACO3002 Data Protection for SQL: full backup of
> database HAP from server HDDES1 failed, rc = 418.(SESSION: 195941)
>
> 28/05/09 01:33:52 AM COT ANE4991I (Session: 195941, Node: XXXX_SQL)
> TDP MSSQL Win32 ACO3000 Data Protection for SQL: Starting full
> backup of database HAQ from server HDDES1.(SESSION: 195941)
>
> 28/05/09 02:53:18 AM COT ANE4991I (Session: 195941, Node: XXXX_SQL)
> TDP MSSQL Win32 ACO3001 Data Protection for SQL: full backup of
> database HAQ from server HDDES1 completed successfully.(SESSION: 195941)
>
> 28/05/09 02:53:31 AM COT ANE4991I (Session: 195941, Node: XXXX_SQL)
> TDP MSSQL Win32 ACO3008 Data Protection for SQL: Backup of server
> HDDES1 is complete. Total SQL backups selected: 2 Total SQL backups
> attempted: 2 Total SQL backups completed: 1 Total SQL backups
> excluded: 0 Total SQL backups inactivated: 0 Throughput rate: 41,
> 293.15 Kb/Sec Total bytes transferred: 270,897,340,728 Elapsed
> processing time: 6,406.59 Secs(SESSION: 195941)