SCSI transport failed error
Hi,
I am getting SCSI transport failed error on my Solaris 10 servers. iostat is reporting Hard & Transport errors.
I am able to access to lun and able to write data to it without any problem.
Questions:
1. what does this error mean?
2. could this impact the performance?
3. possible fix?
/scsi_vhci/ssd@g60a98000486e5a75576f4e4949586c42 (ssd0):
Jun 1 20:59:20 APP001 SCSI transport failed: reason 'tran_err': retrying command
Jun 1 21:00:41 APP001 scsi: WARNING: /scsi_vhci/ssd@g60a98000486e5a75576f4e4949586c42 (ssd0):
Jun 1 21:00:41 APP001 SCSI transport failed: reason 'timeout': retrying command
Jun 1 21:00:41 APP001 scsi: WARNING: /scsi_vhci/ssd@g60a98000486e5a75576f4e4949586c42 (ssd0):
Jun 1 21:00:41 APP001 SCSI transport failed: reason 'tran_err': retrying command
=========================
root@STFEMAPAPP001 # iostat -En
c1t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: LSILOGIC Product: Logical Volume Revision: 3000 Serial No:
Size: 146.56GB <146561286144 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
c0t0d0 Soft Errors: 3 Hard Errors: 0 Transport Errors: 0
Vendor: TSSTcorp Product: CD/DVDW TS-T632A Revision: SR03 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 3 Predictive Failure Analysis: 0
c6t60A98000486E5A75576F4E4949586C42d0 Soft Errors: 2 Hard Errors: 648 Transport Errors: 659
Vendor: NETAPP Product: LUN Revision: 0.2 Serial No:
Size: 107.36GB <107357405184 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis:
Help appreciated.
Thanks.
it means that when the sun tried to send or recive data to the drive it could not. this could be cable or scsi controler. but the most likely proublem is your drive. i would get the data off and try a new drive be fore it fails.
Similar Messages
-
Solaris 10 SCSI transport failed reason 'tran err' on host level
Hello,
we are frequently getting below errors on host, can any one please help to solve this issue?
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 20:41:09 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 1 20:41:09 host SCSI transport failed: reason 'tran_err': retrying command
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::GPN_ID for D_ID=2e1400 failed
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 disappeared from fabric
Mar 2 00:30:16 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 reappeared in fabric
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 2 00:30:18 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 00:30:18 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Requested Block: 367501 Error Block: 367501
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B0
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:30:36 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,5 (ssd112):
Mar 2 00:30:36 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Requested Block: 201152 Error Block: 201152
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B5
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:31:40 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 2 00:31:40 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Requested Block: 10063136 Error Block: 10063136
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B2
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:32:31 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,4 (ssd113):
Mar 2 00:32:31 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Requested Block: 71274 Error Block: 71274
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B4
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 03:41:29 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,3 (ssd114):
Mar 2 03:41:29 host Error for Command: read(10) Error Level: Retryable
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Requested Block: 88112 Error Block: 88112
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B3
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 06:00:00 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,1 (ssd116):
Mar 2 06:00:00 host Error for Command: read(10) Error Level: Retryable
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Requested Block: 202608 Error Block: 202608
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B1
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 17:02:01 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 17:02:01 host SCSI transport failed: reason 'timeout': retrying command
Mar 4 02:07:11 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-1
Mar 4 02:07:21 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-2
Mar 5 02:06:47 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-1
Mar 5 02:06:57 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-2
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 5 10:02:55 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 5 10:02:55 host SCSI transport failed: reason 'timeout': retrying command
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 02:06:38 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-1
Mar 6 02:06:48 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-2
Mar 6 05:00:00 host explorer: [ID 702911 daemon.notice] Explorer started
Mar 6 05:02:49 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18043] core dumped: /ecmp/ecm/log/cores/luxadm.host.18043.core
Mar 6 05:02:50 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18046] core dumped: /ecmp/ecm/log/cores/luxadm.host.18046.core
Mar 6 05:02:54 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18331] core dumped: /ecmp/ecm/log/cores/luxadm.host.18331.core
Mar 6 05:03:46 host explorer: [ID 702911 daemon.notice] Explorer finished
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 12:27:02 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28834] core dumped: /ecmp/ecm/log/cores/luxadm.host.28834.core
Mar 6 12:27:33 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28839] core dumped: /ecmp/ecm/log/cores/luxadm.host.28839.core
Mar 6 15:24:11 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5006] core dumped: /ecmp/ecm/log/cores/luxadm.host.5006.core
Mar 6 15:30:52 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5699] core dumped: /ecmp/ecm/log/cores/luxadm.host.5699.core
Mar 6 15:31:57 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5975] core dumped: /ecmp/ecm/log/cores/luxadm.host.5975.core
Mar 6 15:32:39 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5987] core dumped: /ecmp/ecm/log/cores/luxadm.host.5987.core
Mar 6 15:36:16 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6274] core dumped: /ecmp/ecm/log/cores/luxadm.host.6274.core
Mar 6 15:36:38 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6286] core dumped: /ecmp/ecm/log/cores/luxadm.host.6286.core
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 18:23:44 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 6 18:23:44 host SCSI transport failed: reason 'tran_err': retrying command
Mar 7 01:43:47 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.139069 s
Mar 7 02:07:10 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-1
Mar 7 02:07:20 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-2
Mar 7 02:07:58 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.152342 s
Mar 7 07:23:29 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[24350] core dumped: /ecmp/ecm/log/cores/luxadm.host.24350.coreHello,
we are frequently getting below errors on host, can any one please help to solve this issue?
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 1 20:41:09 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 1 20:41:09 host SCSI transport failed: reason 'tran_err': retrying command
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::GPN_ID for D_ID=2e1400 failed
Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 disappeared from fabric
Mar 2 00:30:16 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 reappeared in fabric
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 2 00:30:18 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 00:30:18 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Requested Block: 367501 Error Block: 367501
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B0
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:30:36 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,5 (ssd112):
Mar 2 00:30:36 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Requested Block: 201152 Error Block: 201152
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B5
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:31:40 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 2 00:31:40 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Requested Block: 10063136 Error Block: 10063136
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B2
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 00:32:31 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,4 (ssd113):
Mar 2 00:32:31 host Error for Command: write(10) Error Level: Retryable
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Requested Block: 71274 Error Block: 71274
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B4
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 03:41:29 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,3 (ssd114):
Mar 2 03:41:29 host Error for Command: read(10) Error Level: Retryable
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Requested Block: 88112 Error Block: 88112
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B3
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 06:00:00 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,1 (ssd116):
Mar 2 06:00:00 host Error for Command: read(10) Error Level: Retryable
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Requested Block: 202608 Error Block: 202608
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B1
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
Mar 2 17:02:01 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 2 17:02:01 host SCSI transport failed: reason 'timeout': retrying command
Mar 4 02:07:11 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-1
Mar 4 02:07:21 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-2
Mar 5 02:06:47 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-1
Mar 5 02:06:57 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-2
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 5 10:02:55 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
Mar 5 10:02:55 host SCSI transport failed: reason 'timeout': retrying command
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 02:06:38 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-1
Mar 6 02:06:48 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-2
Mar 6 05:00:00 host explorer: [ID 702911 daemon.notice] Explorer started
Mar 6 05:02:49 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18043] core dumped: /ecmp/ecm/log/cores/luxadm.host.18043.core
Mar 6 05:02:50 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18046] core dumped: /ecmp/ecm/log/cores/luxadm.host.18046.core
Mar 6 05:02:54 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18331] core dumped: /ecmp/ecm/log/cores/luxadm.host.18331.core
Mar 6 05:03:46 host explorer: [ID 702911 daemon.notice] Explorer finished
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 12:27:02 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28834] core dumped: /ecmp/ecm/log/cores/luxadm.host.28834.core
Mar 6 12:27:33 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28839] core dumped: /ecmp/ecm/log/cores/luxadm.host.28839.core
Mar 6 15:24:11 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5006] core dumped: /ecmp/ecm/log/cores/luxadm.host.5006.core
Mar 6 15:30:52 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5699] core dumped: /ecmp/ecm/log/cores/luxadm.host.5699.core
Mar 6 15:31:57 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5975] core dumped: /ecmp/ecm/log/cores/luxadm.host.5975.core
Mar 6 15:32:39 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5987] core dumped: /ecmp/ecm/log/cores/luxadm.host.5987.core
Mar 6 15:36:16 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6274] core dumped: /ecmp/ecm/log/cores/luxadm.host.6274.core
Mar 6 15:36:38 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6286] core dumped: /ecmp/ecm/log/cores/luxadm.host.6286.core
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
Mar 6 18:23:44 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
Mar 6 18:23:44 host SCSI transport failed: reason 'tran_err': retrying command
Mar 7 01:43:47 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.139069 s
Mar 7 02:07:10 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-1
Mar 7 02:07:20 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-2
Mar 7 02:07:58 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.152342 s
Mar 7 07:23:29 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[24350] core dumped: /ecmp/ecm/log/cores/luxadm.host.24350.core -
Hello Guys, I'm trying to figure out if my harddrive is going bad in my system. I'm seeing a lot of SCSI transport error messages in the /var/adm/messages file. This only happens when our backups are running at night. We back up all our servers through the firewall using veritas's netbackup. Can someone help me sift thought this information in the messages file and let me know what all this means. Thanks
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 Cmd (0x2d37890) dump for Target 0 Lun 0:
Dec 6 18:53:22 cp-hqc2 Cmd (0x2d37890) dump for Target 0 Lun 0:
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 cdb=[ 0x2a 0x0 0x0 0x60 0xba 0x74 0x0 0x0 0x2 0x0 ]
Dec 6 18:53:22 cp-hqc2 cdb=[ 0x2a 0x0 0x0 0x60 0xba 0x74 0x0 0x0 0x2 0x0 ]
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 pkt_flags=0x4000 pkt_statistics=0x60 pkt_state=0x7
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 pkt_scbp=0x0 cmd_flags=0x1860
Dec 6 18:53:22 cp-hqc2 pkt_flags=0x4000 pkt_statistics=0x60 pkt_state=0x7
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 pkt_scbp=0x0 cmd_flags=0x1860
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 glm: [ID 401478 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6018]
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: Disconnected tagged cmd(s) (1) timeout for Target 0.0
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 glm: [ID 401478 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6018]
Dec 6 18:53:22 cp-hqc2 got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3 (glm0):
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
Dec 6 18:53:22 cp-hqc2 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'reset': retrying command
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'reset': retrying command
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0):
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'timeout': retrying command
Dec 6 18:53:22 cp-hqc2 SCSI transport failed: reason 'timeout': retrying commandHello, data is not being backed up locally. This server is our firewall. We have multiple dmz zones on our firewall. One of our dmz's host's the veritas master server which backs up other web servers in other dmz zones. When the backups kick off at night, these messages appear in the /var/adm/messages file. Does this mean the firewall cannot handle the load of traffic??
-
SCSI transport failed: reason 'aborted': retrying command
The /var/adm/messages it show as below:
does anyone knows what is this error message and how i can fix it??
dsu1b:/var/adm ROOT > more messages
Jul 30 05:53:04 dsu1b xntpd[313]: time reset (step) 0.134397 s
Aug 1 08:34:08 dsu1b xntpd[313]: time reset (step) 0.134628 s
Aug 1 10:48:25 dsu1b unix: LOMlite PSU 1 Input B restored
Aug 1 10:48:28 dsu1b unix: LOMlite PSU 1 Input B failed
Aug 2 11:15:42 dsu1b unix: WARNING: /pci@1f,2000/SUNW,ifp@1/ssd@w50020f230000878f,1 (ssd13):
Aug 2 11:15:42 dsu1b SCSI transport failed: reason 'aborted': retrying command
Aug 2 11:15:42 dsu1b
Aug 2 11:16:06 dsu1b unix: WARNING: /pci@1f,2000/SUNW,ifp@1/ssd@w50020f230000878f,0 (ssd12):
Aug 2 11:16:06 dsu1b SCSI transport failed: reason 'aborted': retrying command
Aug 2 11:16:06 dsu1b
Aug 2 11:16:14 dsu1b unix: WARNING: /pci@1f,2000/SUNW,ifp@1/ssd@w50020f230000878f,3 (ssd15):
Aug 2 11:16:14 dsu1b SCSI transport failed: reason 'aborted': retrying command
Aug 2 11:16:14 dsu1b
Aug 2 11:16:14 dsu1b unix: WARNING: /pci@1f,2000/SUNW,ifp@1/ssd@w50020f230000878f,0 (ssd12):
Aug 2 11:16:14 dsu1b SCSI transport failed: reason 'aborted': retrying command
Aug 2 11:16:14 dsu1b
Aug 2 11:35:33 dsu1b explorer: Explorer started
Aug 2 11:37:35 dsu1b unix: pseudo-device: lockstat0
Aug 2 11:37:35 dsu1b unix: lockstat0 is /pseudo/lockstat@0
Aug 2 11:38:32 dsu1b unix: /pci@1f,4000/scsi@3/st@4,0 (st4):
Aug 2 11:38:32 dsu1b <HP DDS-3 4mm DAT >
Aug 2 11:38:32 dsu1b unix: st4 at glm0:
Aug 2 11:38:32 dsu1b unix: target 4 lun 0
Aug 2 11:38:32 dsu1b unix: st4 is /pci@1f,4000/scsi@3/st@4,0
Aug 2 11:40:54 dsu1b explorer: Explorer finished
Aug 2 21:56:16 dsu1b xntpd[313]: time reset (step) 0.168668 s
Aug 4 13:04:00 dsu1b xntpd[313]: time reset (step) 0.144823 s
dsu1b:/var/adm ROOT >Hmm, if this was the first and last occourance of this message its probably safe to ignore it. If you have had it many times its about time that you start trouble shooting your SCSI chain; checking the cables, if possible move the disks to another controller/box etc.
The message basicly tells you that the system tried to communicate with the disks, but for some reason the command it sent to the disks was aborted.
7/M. -
Dell R610 "SCSI transport failed: reason 'reset': retrying command"
MY DELL R610 Server run 3 ~ 5 hours ,will display the message and the server is die.
Jul 1 00:48:50 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0 (mpt0):
Jul 1 00:48:50 JSxwmGS Disconnected command timeout for Target 0
Jul 1 00:48:51 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0/sd@0,0 (sd1):
Jul 1 00:48:51 JSxwmGS SCSI transport failed: reason 'reset': retrying command
Jul 1 00:50:01 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0 (mpt0):
Jul 1 00:50:01 JSxwmGS Disconnected command timeout for Target 0
Jul 1 00:52:02 JSxwmGS scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,2940@1c/pci1028,1f10@0 (mpt0):
Jul 1 00:52:02 JSxwmGS Disconnected command timeout for Target 0Use the same server install Centos5.4 , run the same java program on that , It is running ok.
use solaris 10 zfs file system ,it also have the question. -
Install from SCSI CD fails: ERROR: boot device didn't show up after 30
I have a x86 based server w/SCSI HD and DVD drive.
Install fails with following.
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201108
ERROR: boot device didn't show up after 30 seconds
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
sh: can't access tty; job contro turned off
[ramfs /]#
I hooked up a IDE DVD drive and using same CD installs OK. Then, once installed, I switch my DVD back to SCSI that failed the install, and guess what? Arch booted from my HD now recognizes the SCSI DVD drive, I can mount it and so on. Looks to me like the install kernel doesn't support my SCSI DVD drive but the installed kernel does.
I need the Arch install to work from the SCSI DVD drive on my system. I'm trying to develop an Arch distro for my particular system, which there are about a dozen of in the field, they all have SCSI DVD and no IDE drives. Will I have to add a SCSI driver to the boot kernel? Or is my problem something else?
I notice there is no /dev/disk/by-label (ther is a /dev/disk/by-id by-label and by-uuid).
I do a:
"[ramfs /]# lsmod | grep sr_mod"
sr_mod 14951 0
cdrom 36329 1 sr_mod
scsi_mod 131482 7 sg,sr_mod,sd_mod,libata,mptspi,mptscsih,scsi_transport_spi
[ramfs /]# lsmod | grep scsi
mptscsih 20040 1 mptspi
mptbase 63459 2 mptspi,pmtscsih
scsi_transport_spi 20059 1 mptspi
scsi_mod 131482 7 sg,sr_mod,sd_mod,libata,mptspi,mptscsih,scsi_stransport_spiscrath "I notice there is no /dev/disk/by-label (ther is a /dev/disk/by-id by-label and by-uuid)."
Should be: I notice there is no /dev/disk/by-label (there is a /dev/disk/by-id by-path and by-uuid). -
Hello Experts,
We are getting "Assemble failed" error message when we tried to assemble components. I have attached a CMS log file. You help and feedback is greatly appreciated.
David
Info:Starting Step Repository-export at 2008-10-08 05:34:02.0206 -4:00
Info:Component:alleghenyenergy/AE_IMPORTED_OBJECTS
Info:Version :JD1_XD1IR01_C.20081008093400
Info:1. PR is of type TCSSoftwareComponent
Info:the workspace will be read from XI
Info:OK : workspacedata added.
Info:Component:ivara.com/IVARA_EXP_ENTERPRISE
Info:Version :JD1_XD1IR01_C.20081008093401
Info:2. PR is of type TCSSoftwareComponent
Info:the workspace will be read from XI
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
:communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
com.sap.aii.utilxi.misc.api.ResourceException: Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.checkSwcvExistence(InternalRepTransportServiceImpl.java:316)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.createSupportPackage(InternalRepTransportServiceImpl.java:283)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.createSupportPackage(TransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:206)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
at com.sap.cms.tcs.client.XICommunicator.readWorkspaceData(XICommunicator.java:228)
at com.sap.cms.tcs.core.RepositoryExportTask.processRepositoryExport(RepositoryExportTask.java:226)
at com.sap.cms.tcs.core.RepositoryExportTask.process(RepositoryExportTask.java:324)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
at com.sap.cms.tcs.core.TCSManager.assemblePropagationRequests(TCSManager.java:677)
at com.sap.cms.pcs.assembly.manager.AssemblyManager.assemble(AssemblyManager.java:1510)
at com.sap.cms.pcs.assembly.AssemblyQueueHandler.execAssembly(AssemblyQueueHandler.java:818)
at com.sap.cms.pcs.assembly.AssemblyQueueHandler.startAssembly(AssemblyQueueHandler.java:133)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startAssembly(CmsTransportProxyBean.java:829)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl20.startAssembly(LocalCmsTransportProxyLocalObjectImpl20.java:1836)
at com.sap.cms.ui.wl.Custom1.startComponetAssembly(Custom1.java:14080)
at com.sap.cms.ui.wl.Custom1.assembleQueue(Custom1.java:4685)
at com.sap.cms.ui.wl.wdp.InternalCustom1.assembleQueue(InternalCustom1.java:2303)
at com.sap.cms.ui.wl.Worklist.handleAssemblyOptionsEvent(Worklist.java:1487)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2520)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:283)
at com.sap.cms.ui.wl.wdp.InternalWorklists.wdFireEventAssemblyOptionsEvent(InternalWorklists.java:388)
at com.sap.cms.ui.wl.Worklists.fireAssemblyOptionsEvent(Worklists.java:247)
at com.sap.cms.ui.wl.wdp.InternalWorklists.fireAssemblyOptionsEvent(InternalWorklists.java:328)
at com.sap.cms.ui.wl.AssemblyOptions.onActionStartAssembly(AssemblyOptions.java:276)
at com.sap.cms.ui.wl.wdp.InternalAssemblyOptions.wdInvokeEventHandler(InternalAssemblyOptions.java:339)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step Repository-export ended with result 'fatal error' ,stopping execution at 2008-10-08 05:36:32.0376 -4:00Hi,
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: Exception received:
ClientServerException exception:Software component version 58a66500336b11dd8387f3c70a53b4e5 has not yet been imported into the system and therefore cannot yet be assembled using CMS. You must execute a CMS- or file-based import of the software component version into the consolidation system first.
The error is saying that there might a communication issue with CBS to CMS. That's the reson the imported SCA version is not available in the current system to assemble. The NWDI restart may work some times.
Thanks
Krishna -
SQL Exceptions, transport-level errors on SharePoint 2010 App Server
SharePoint 2010 becomes inaccessible 2-3 times per day. It happens at approximately the same times: 8 PM, 1 AM and 1 PM. It is inaccessible for about 3-4 minutes and then comes back on its own.
During the time it is down, we see the following errors in the event viewer on the application server:
EventID: 5586 Task Category: Database -
Unknown SQL Exception 64 occurred. Additional error information from SQL Server is included below.A transport-level error has occurred when receiving results from the server.
(provider: TCP Provider, error: 0 - The specified network name is no longer available.)
EventID: 3 Task Category: None -
.Net SqlClient Data Provider: System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error:
0 - The specified network name is no longer available.)
EventID: 6398 Task Category: Timer -
The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID f9db48f1-f115-47ab-99b6-552460cbb782) threw an exception. More
information is included below. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
EventID: 8086 Task Category: Business Data -
The BDC Service application failed due to a SQL Exception: SQLServer host ums1spd1v. The error returned was: 'A transport-level error has occurred when sending the request to
the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)'
The SharePoint logs have errors during the same time period saying the same kinds of things: Sql exception raw message: A transport-level error has occurred when receiving results from the server,
The specified network name is no longer available, etc.
Our network administrator has looked at the issue and cannot find any network problems.
He setup a continuous ping from the app server to the database server.
Even during the times these errors are occurring, the app server is still able to reach the database server.
However, you cannot ping the app server itself during this time.
Our database administer cannot find any SQL Server issues.
There are no errors in the event viewer or the SQL logs on the database server.
In Central Admin, we can see that one or two jobs fail with SQL errors during the times these errors take place.
It is almost always the “User Profile Service Application – User Profile Language Synchronization Job” and often the “Health Statistics Updating” or “Crawl Log Report for Search Application Search Service Application”.
These jobs run successfully at many other times during the day.
Is there a good way to tell if the database, network or SharePoint itself is the root of these problems?
The database and network guys say there are no problems in their areas, but all I can find in the SharePoint logs is that it can’t reach the database server.
Thank you for any suggestions you may have!Since these seem to happen at very specific times, I would run a NetMon trace at that window to capture what is going back and forth (or perhaps the timer service is just unable to reach the SQL server).
Trevor Seward, MCC
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
Viewing Transport Log Errors in ECC
Dear SRM Experts,
System Info : ECC 6.0. and SRM 5.0
We moved transports from Dev to QA and some of the transports failed with Return codes of 8 and 12.
Where do we look up the transport errors that occured.
Points will be rewarded for answers.
Thanks in advance,
Bobby.Yann,
Thank you very much for your reply.
I went to SE10 and selected my released order and
clicked on the transport logs and drilled down. But I am not able to find the RC=8 and
RC=12 errors. The outer level for all the lines has a status of successfully completed(0).
Please let me know if I am missing any steps.
Thanks again,
Bobby. -
When transporting multiproviders and cubes transport failed.
HI Experts,
When transporting cubes and multiproviders in a request the transport failed with return code 8.
The described below as:
Start of the after-import method RS_CUBE_AFTER_IMPORT for obje
Error/warning in dict. activator, detailed log > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101078 has not been activated
Error when activating InfoCube 101078
Error/warning in dict. activator, detailed log > Detail
/BIC/L101077 (specify a primary key)
Table /BIC/L101077 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101077 has not been activated
Error when activating InfoCube 101077
Error/warning in dict. activator, detailed log > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101078 has not been activated
Error when activating InfoCube 101078
Error/warning in dict. activator, detailed log > Detail
/BIC/L101077 (specify a primary key)
Table /BIC/L101077 could not be activated
Return code..............: 8
DDIC Object TABL /BIC/L101077 has not been activated
Error when activating InfoCube 101077
Error/warning in dict. activator, detailed log > Detail
/BIC/L101078 (specify a primary key)
Table /BIC/L101078 could not be activated
Please let us know if anyone has come across similar kind of issue.
Regards,
Monalisa MohantyIssue seems to be with the aggregates maintained in the cube.
Is your aggregates were properly maintained in your Dev system when you have collected it in your transport?
Check the same and also use overwrite option when you are trying to import the transport in the target systems.
If the aggregates are properly maintained then check the import once again and see if that works fine with the overwrite mode. If not then you need to collect your objects again in a new transport.
Hope this helps.
Murali -
Transport Fail -com.sap.aii.utilxi.misc.api.ResourceException:Import
Hi Experts,
My Transports through Solution Manager is failing in Production PI. Transports are imported, deployed successfully in Test and Regression environments and working fine. Transport requests are of type Workbench and we are attaching '.tpz' files as Non abap objects. All contain ESR objects, no ID components. Import and Check version steps are good but failing at Deployment step in Production PI.
Please find the log which I can see in SE10. All the transports failed with the same below error description.
CTS Import Service - Version 0.94 04.04.2008
==============================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://ABC2159161:50000
Start import with id:4E8B872CA9F100F2E10080000A32109F
DeployProxy (patch level:0) called with followingparameters:
Deployable(0)
Deployable-Type:1
Deployable-Id:4E6E38F506B601AAE10080000A321063
Deployable-TransportContainerId:DI1K900677
Deployable-ContentLocator:/usr/sap/trans/data/DI1K900677/XI7_1
>>>63.tpz
Property(0)
Property-key:TARGETSYSTEMID Property-value:PI1
Begin CommunicationData-Type[0]:1
CommunicationData-Address:http://ABC2159161:50000/rep
CommunicationData-Host:ABC2159161
CommunicationData-Port:50000
CommunicationData-User:'filled'
CommunicationData-Password:'filled'
Importing archive:XI7_1_A_SAPPI_CM_1.0_of_ABC.com-objs_6
com.sap.aii.ibtransportclient.XiTransportException: caused by:
>>>rt failed: Internal error when importing object [Lcom.sap.a
>>>aused by: com.sap.aii.utilxi.misc.api.ResourceException: Im
>>>g object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d
>>>ethodFault: caused by: ClientServerException exception:Impo
>>>object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d c
>>>sourceException: Import failed: Internal error when importi
>>>IWorkspace;@7ffc92d
End CommunicationData-Type[0]:1
End import with returncode:'8'
Deployment
End date and time : 20111009003401
Ended with return code: ===> 8 <===
Thanks,
Nabendu.Hi,
I have already informed Basis about these. But do we have any way to check the exact reason for this failure?
All the above points can ensure the successful transport to Production or not, I am not sure.
Thanks,
Nabendu. -
Transport user error: invalid object name while starting CMS in CCM
Hi Experts,
I'm not able to start the CMS in CCM.It was working fine. Suddenly it went down due to some data base access failure. After that Iu2019m not able to start the CMS.
Kindly find the event viewer error and information.
Error: The root server reported an error Initialization Failure.
Error: Failed to register object.. Reason: Transport user error: invalid object name..
Information: Central Management Server stopped
Could you please tell me how to start the CMS in CCM? Since I can able to setup CMS Database and audit database successfully.
Regards,
SridharanHi ,
Thanks for the response.I have trace the CMS.I found some error in log file.any idea on the following errors,
trace message: CNSClientManager::VerifyConnection() : search fails(37) - Transport user error: object with the specified name not found.
trace message: CNSClientManager::VerifyConnection() : Failed to query for APSs. Empty cluster list returned.
trace message: TheAPSServer::RegisterApsInNameServer: Fail to register the current APS(Transport user error: invalid object name.)
trace message: CNSClientManager::ClusterInfo::InvalidateAPS: Removing APS from m_ActiveMembers and adding to m_InactiveMembers
trace message: SIServerController:run: Fail to initialize or uninitialize. Reason is The root server reported an error Initialization Failure.:
Regards,
Sridharan -
TMS Check Transport Tool Error
Hello Experts,
We have migrated the database from Informix(DEV old machine) to Oracle(DEV New machine) and found the system up and running fine except the DBconnect failed error when i run the STMS->system overview->select the system as DEV-->R3System->check->Transport tool.
Please find the error log herewith:
developertrace,0] Logon as OPS$-user to get SAPR3's password
developertrace,0] Connecting as /@DEV on connection 0 ...
developertrace,0] >oci_logon(con_hdl=0, user='', dbname='DEV')
dbsloci.,6405] *** ERROR => CONNECT failed with sql error '1019'
developertrace,0] Try to connect with default password
developertrace,0] Connecting as SAPR3/<pwd>@DEV on connection 0 ...
developertrace,0] >oci_logon(con_hdl=0, user='SAPR3', dbname='DEV')
dbsloci.,6405] *** ERROR => CONNECT failed with sql error '12705'
We have tried almost every option given in the SAP notes but couldnt figure out the issue. We are now not able to support PRD now as the DEV is not available. Can any one quickly help me in resolving the issue...
R3 -> 45B
OS: UNIX
Kernel: 45B_EXT
We are getting no error when we run R3Trans -x and R3Trans -d as well.
Please help us in resolving the issue ASAP...
P.S: If you could give your contact number, iam ready to call you and talk to you regarding the issue and can work upon this.
Thanks and Regards,
Mani
+91 934 749 6777Hi Ruchit,
Please find the trans.log file after I run R3Trans -x herewith:
4 ETW000 [developertrace,0] New connection 0 created 20 0.034731
4 ETW000 [developertrace,0] db_con_connect (con_name=R/3) 62 0.034793
4 ETW000 [developertrace,0] Got ORACLE_HOME=/oracle/DEV/920_64 from environment
4 ETW000 89 0.034882
4 ETW000 [developertrace,0] -->oci_initialize 23 0.034905
4 ETW000 [developertrace,0] Got ORACLE_SID=DEV from environment
4 ETW000 42 0.034947
4 ETW000 [developertrace,0] Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environme
nt
4 ETW000 29 0.034976
4 ETW000 [developertrace,0] Logon as OPS$-user to get SAPR3's password
4 ETW000 22 0.034998
4 ETW000 [developertrace,0] Connecting as /@DEV on connection 0 ...
4 ETW000 29 0.035027
4 ETW000 [developertrace,0] -->oci_logon(con_hdl=0, user='', dbname='DEV')
4 ETW000 31 0.035058
4 ETW000 [developertrace,0] Now I'm connected to ORACLE 62893 0.097951
4 ETW000 [developertrace,0] Got SAPR3's password from table SAPUSER
4 ETW000 1408 0.099359
4 ETW000 [developertrace,0] Disconnecting from connection 0 ...
4 ETW000 23 0.099382
4 ETW000 [developertrace,0] -->oci_logoff(con_hdl=0) 22 0.099404
4 ETW000 [developertrace,0] Now I'm disconnected from ORACLE
4 ETW000 1032 0.100436
4 ETW000 [developertrace,0] Try to connect with the password I got from OPS$-us
er
4 ETW000 25 0.100461
4 ETW000 [developertrace,0] Connecting as SAPR3/<pwd>@DEV on connection 0 ...
4 ETW000 22 0.100483
4 ETW000 [developertrace,0] -->oci_logon(con_hdl=0, user='SAPR3', dbname='DEV')
4 ETW000 22 0.100505
4 ETW000 [developertrace,0] Now I'm connected to ORACLE 40345 0.140850
So as this is not giving any error, i dont think this is a problem with sapr3 password.
Apart from that we suspect that there is some problem with the env variable ORA_NLS33... but couldnt get to the bottom of the problem...
Please find the trace file we got when we ran tp command:
[developertrace,0] db_con_connect (con_name=R/3) 64 0.058188
[developertrace,0] Got ORACLE_HOME=/oracle/DEV/920_64 from environment
85 0.058273
[developertrace,0] -->oci_initialize 23 0.058296
[developertrace,0] Got TNS_ADMIN=/oracle/DEV/920_64/network/admin from environment
42 0.058338
[developertrace,0] Got ORACLE_SID= from environment 43 0.058381
[developertrace,0] Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment
29 0.058410
[developertrace,0] Logon as OPS$-user to get SAPR3's password
21 0.058431
[developertrace,0] Connecting as /@DEV on connection 0 ...
28 0.058459
[developertrace,0] -->oci_logon(con_hdl=0, user='', dbname='DEV')
30 0.058489
[dbsloci.,6405] *** ERROR => CONNECT failed with sql error '1019'
2235 0.060724
[developertrace,0] Try to connect with default password 18 0.060742
[developertrace,0] Connecting as SAPR3/<pwd>@DEV on connection 0 ...
23 0.060765
[developertrace,0] -->oci_logon(con_hdl=0, user='SAPR3', dbname='DEV')
22 0.060787
[dbsloci.,6405] *** ERROR => CONNECT failed with sql error '12705'
60464 0.121251
[ ,597] ***LOG BY2=>sql error 12705 performing CON 48 0.121299
[ ,597] ***LOG BY0=> 17 0.121316
[tpsqlora.c,1104] end: tp_connect 13 0.121329
Any help in this way is very much appreciative.
Best Regards,
Mani -
Failed to send email report ,The transport failed to connect to the server
HI i have to automate my report using sub
1.I have configured SMTP server in the configuration settings
2. I have created subscitption using my report,But i here i will found one error.
Please find the
failed to send email report ,The transport failed to connect to the server
and can u please help me out for this
when i check in the loge files it will show this error below
No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;I have change the settings as u suggested but still not able to send the mail .
its shows me the same error mesg
<Header>
<Product>Microsoft SQL Server Reporting Services Version 2009.0100.1600.01 ((KJ_RTM).100402-1539 )</Product>
<Locale>English (United States)</Locale>
<TimeZone>W. Europe Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\Logfiles\ReportServerService__02_10_2015_03_44_06.log</Path>
<SystemName>WEGDACM1</SystemName>
<OSName>Microsoft Windows NT 6.1.7601 Service Pack 1</OSName>
<OSVersion>6.1.7601</OSVersion>
<ProcessID>10420</ProcessID>
<Virtualization>Hypervisor</Virtualization>
</Header>
rshost!rshost!28d0!02/10/2015-03:44:06:: i INFO: Currently registered url http://+:80/ReportServer_MSSQLSERVEREPORT/ on endpoint 2
rshost!rshost!28d0!02/10/2015-03:44:06:: e ERROR: Failed to register url=http://+:80/Reports/ for endpoint 3, error=b7.
rshost!rshost!28d0!02/10/2015-03:44:06:: w WARN: Endpoint 3 is enabled but no url is registered for vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportManager.
servicecontroller!DefaultDomain!28f4!02/10/2015-03:44:06:: e ERROR: Error creating HTTP endpoint. System.Runtime.InteropServices.COMException (0x800700B7): Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)
at Microsoft.ReportingServices.HostingInterfaces.IRsUnmanagedCallback.CreateHttpEndpoint(RsAppDomainType application, String[] urlPrefixes, Int32 cPrefixes, String[] hosts, Int32 cHosts, Boolean wildCardPresent, String virtualDirectory, String
filePath, Int32 authType, Int32 logonMethod, String authDomain, String authRealm, Boolean authPersist, Int32 extendedProtectionLevel, Int32 extendedProtectionScenario, Boolean enabled)
at Microsoft.ReportingServices.Library.ServiceAppDomainController.SetWebConfiguration(RunningApplication rsApplication, Boolean enabled, String folder)
rshost!rshost!28d0!02/10/2015-03:44:06:: i INFO: Endpoint 4 is disabled and no url is registered vdir=/ReportServer_MSSQLSERVEREPORT/ReportBuilder, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportServer\ReportBuilder.
rshost!rshost!28f4!02/10/2015-03:44:06:: i INFO: Derived memory configuration based on physical memory as 16776696 KB
servicecontroller!DefaultDomain!28f4!02/10/2015-03:44:06:: i INFO: Recycling the service from the default domain
rshost!rshost!28f4!02/10/2015-03:44:17:: i INFO: Application domain type WindowsService statistics: created: 10, unloaded: 10, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!28f4!02/10/2015-03:44:17:: i INFO: Appdomain:12 WindowsService_10 started.
library!WindowsService_10!28f4!02/10/2015-03:44:17:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. ;
servicecontroller!WindowsService_10!28f4!02/10/2015-03:44:17:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
error.
resourceutilities!WindowsService_10!28f4!02/10/2015-03:44:18:: i INFO: Reporting Services starting SKU: Enterprise
servicecontroller!WindowsService_9!28f4!02/10/2015-03:44:18:: i INFO: Service controller exiting.
appdomainmanager!DefaultDomain!28f4!02/10/2015-03:44:18:: i INFO: Appdomain:11 unregistered.
appdomainmanager!DefaultDomain!28f4!02/10/2015-03:44:18:: i INFO: Appdomain:11 WindowsService_9 unloading.
appdomainmanager!DefaultDomain!e24!02/10/2015-03:44:18:: i INFO: AppDomain:11 0 pending unload(s)
library!WindowsService_10!19f0!02/10/2015-03:44:18:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. ;
library!WindowsService_10!19f0!02/10/2015-03:44:18:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
error.
library!WindowsService_10!19f0!02/10/2015-03:44:18:: e ERROR: ServiceStartThread: Attempting to start service again...
library!DefaultDomain!1ca8!02/10/2015-10:55:23:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. ;
This is my Logfile can u pls go through it and resolve my issue. -
I’m running MS SQL Server 2005, Express Edition, SP3 on Windows XP. Local connections only.
In preparation to restore a database, I use IWSQLDMOServer::KillProcesses() to allow the database restore. (IWSQLSMOResore::SQLRestore()) The restore is successful and I appear to be able to connect OK. (No error indication on the
connect) However, the first time I try to use the database via an ExecuteQuery() the call fails and the connection state is changed to Closed. I also get the “Transport-level error has occurred...No Process is on the other end of the pipe” exception.
Closing and restarting the application fixes the problem.
Also, disconnecting and reconnecting twice before the ExecuteQuery() call also fixes the problem.
So, I can hide the problem by connecting twice, but I am hoping there is a better solution.
Walter EykelIt appers when you connect for the restore process, you are opening a different session than that of the original one, with a different database context.
The first time you try to execute a query, you attempt to use the session that was open BEFORE the KillProcesses() call and therefore was killed. By the time you run the first time, your client is informed that the previous session is no longer available.
In the second time, as your client was informed that the original session was killed, it opens a new one.
Its the same behavior as in SSMS.
As a workaround, you could change your database context of your
current session to a base that wont be restored, call the restore methods, and then switch back to the original database context.
Maybe you are looking for
-
Can't download free app purchased under another account once Family Sharing is enabled
I "purchased" Onedrive for iPhone years ago. Then I turned on family sharing on my daughters phone. She couldn't update Onedrive because she hadn't purchased it, so I deleted it as I had for others and tried to download it again. However, this fails
-
I Think I Messed Up...Can You Help?
Ok, so I thought I could drag my "applications" into the dock and make a stack. I guess i was wrong. Once I did the click, drag and drop to the right side of the dock.....POOF!! my applications folder was gone in a cloud of dust. It's not in my trash
-
Need help with a workflow that will restrict resize to 720x540
I need help constructing a workflow that will resize any image I choose to 720x540. I want this to be restrictive to this size, in other words I don't want 720x468 or etc. I have tried this too many times, will no success so now I am reaching out for
-
Passing a parameter in the query string
When a string containing a �+� is passed as a parameter in the URL in the query string through a POST request, it is interpreted as two strings separated by a �+� and thus when the string is retrieved through a request.getParameter (),it returns the
-
Dell 2405FPW 24" display problem. Please help
Can anyone help me with this, I can't seem to get an answer from either Dell tech support nor from Apple. I just received my dell 2405FPW 24" display. Connected it to DVI port 1 on my powermac G5. It started to work just fine for the first hour or so