| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| I got an error when I try to send a file to a remote SFTP |
« View previous topic :: View next topic » |
| Author |
Message
|
| pepitopepito45 |
 Posted: Thu Sep 03, 2015 3:32 am Post subject: I got an error when I try to send a file to a remote SFTP |
 |
|
Newbie
Joined: 03 Sep 2015
Posts: 1
|
| Code: |
ExceptionList
RecoverableException
File:CHARACTER:/build/slot1/S900_P/src/DataFlowEngine/MessageServices/ImbDataFlowNode.cpp
Line:INTEGER:1155
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmFileInputNode
Name:CHARACTER:MF_I009_A011_SCDPI_MOVE_FILES#FCMComposite_1_1
Label:CHARACTER:MF_I009_A011_SCDPI_MOVE_FILES.File Input
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
Insert
Type:INTEGER:14
Text:CHARACTER:MF_I009_A011_SCDPI_MOVE_FILES.File Input
RecoverableException
File:CHARACTER:/build/slot1/S900_P/src/DataFlowEngine/TemplateNodes/ImbOutputTemplateNode.cpp
Line:INTEGER:326
Function:CHARACTER:ImbOutputTemplateNode::processMessageAssemblyToFailure
Type:CHARACTER:ComIbmFileOutputNode
Name:CHARACTER:MF_I009_A011_SCDPI_MOVE_FILES#FCMComposite_1_3
Label:CHARACTER:MF_I009_A011_SCDPI_MOVE_FILES.File Output
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
Insert
Type:INTEGER:14
Text:CHARACTER:MF_I009_A011_SCDPI_MOVE_FILES.File Output
RecoverableException
File:CHARACTER:AbstractFileOutputNode.java
Line:INTEGER:828
Function:CHARACTER:locateOutputFile
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:2
Number:INTEGER:3314
Text:CHARACTER:
Insert
Type:INTEGER:5
Text:CHARACTER:File Output
Insert
Type:INTEGER:5
Text:CHARACTER:MF_I009_A011_S_MOVE_FILES
Insert
Type:INTEGER:5
Text:CHARACTER:/inter/cap/pi/de_tal[/b] |
|
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Sep 03, 2015 4:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
BIP3314W: File node 'insert1' in message flow 'insert2' cannot write to output directory 'insert3'.
The FileOutput node cannot write to the output directory because the file system prevents suitable access, which should include the
abilities to: read and write files; move, create and delete files; and create subdirectories with the same properties.
Check that a suitable directory exists and that the file system permits the required processing.
See the IBM Integration Bus online documentation section "FileOutput node" for more information. |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 03, 2015 4:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fjb_saper wrote: |
| Quote: |
BIP3314W: File node 'insert1' in message flow 'insert2' cannot write to output directory 'insert3'.
The FileOutput node cannot write to the output directory because the file system prevents suitable access, which should include the
abilities to: read and write files; move, create and delete files; and create subdirectories with the same properties.
Check that a suitable directory exists and that the file system permits the required processing.
See the IBM Integration Bus online documentation section "FileOutput node" for more information. |
|
Or if you've not figured out the secret formula yet:
BIP3314W: File node 'FileOutput' in message flow 'MF_I009_A011_S_MOVE_FILES' cannot write to output directory '/inter/cap/pi/de_tal'.
The FileOutput node cannot write to the output directory because the file system prevents suitable access, which should include the
abilities to: read and write files; move, create and delete files; and create subdirectories with the same properties.
Check that a suitable directory exists and that the file system permits the required processing.
See the IBM Integration Bus online documentation section "FileOutput node" for more information.
Next time at least have the courtesy to ask a question rather than just posting an exception tree and looking expectant.
It would also be helpful (and polite) to offer some context of the circumstances of the error; as a minimum the version of the software is probative.
You're also more likely to get help if you do this, and show some indication that you've tried to resolve this yourself before posting. Clearly in this instance you didn't make any attempt to resolve this yourself, but you might want to try that in future.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
