ssh.connect returns The message store has reached EOF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 08:22 PM
When I call ssh.connect to try and send a file to an SFTP server I get an exception of "The message store has reached EOF".
Unable to find any help with this issue.
I have an export set scheduled job that creates the file properly then I am executing a javascript probe that is calling a mid server script include to do the work.
I can't get past this error. I have verified that the credentials I am using are correct (connect save/delete, etc using FileZilla).
Any assistance would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2016 03:17 AM
I think for that error it is better if you open a case with ServiceNow support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2016 07:09 AM
Unfortunately, ServiceNows response was:
ServiceNow will only create the file on the MID sever machine. You will need to configure out how to get it to the final directory. You may want to check our community page and post the question. https://community.servicenow.com/welcome
So basically, no help there.
KEVIN MAURIELLO
Sr. Technical Consultant
INSOURCE | 565 E. Swedesford Road, Suite 220 | Wayne, PA 19087
P. 1 610 592 0800 | C. 1 484 695 3645 | F. 1 610 592 0817
kevin.mauriello@insourcenow.com<mailto:michael.hallman@insourcenow.com> | www.insourcenow.com<http://www.insourcenow.com/> | Connect on LinkedIn<https://www.linkedin.com/in/kjmdeveloper>
INSOURCE: Facebook<https://www.facebook.com/insourceinc/> | Twitter | LinkedIn<https://www.linkedin.com/company/insourceinc/>
ServiceNow Silver Services Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2016 09:26 AM
There is a internal PRB under investigation within ServiceNow for same error received by a MID server. Unfortunately the error comes from J2SSH library and is hard to troubleshoot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-27-2016 09:43 AM
That's actually good news.
If there is any way I can get on the watch list for that problem I would appreciate it.
Thanks for the update
KEVIN MAURIELLO
Sr. Technical Consultant
INSOURCE | 565 E. Swedesford Road, Suite 220 | Wayne, PA 19087
P. 1 610 592 0800 | C. 1 484 695 3645 | F. 1 610 592 0817
kevin.mauriello@insourcenow.com<mailto:michael.hallman@insourcenow.com> | www.insourcenow.com<http://www.insourcenow.com/> | Connect on LinkedIn<https://www.linkedin.com/in/kjmdeveloper>
INSOURCE: Facebook<https://www.facebook.com/insourceinc/> | Twitter | LinkedIn<https://www.linkedin.com/company/insourceinc/>
ServiceNow Silver Services Partner