<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable To Schedule Flow using SAS DIP service in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318804#M6784</link>
    <description>&lt;P&gt;Hi Juan,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for the reply, Want to ask you that node name mention in SID file is different from the node name of the machine then will it be an issue for SAS DIP scheduling?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As you have suggested have gone through&amp;nbsp;the logs, I was able to find warning only which is as given below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;| WARN | Transport Connection to: tcp:IP:53067 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///IP:53067@61616&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Kaushal&lt;/P&gt;</description>
    <pubDate>Wed, 14 Dec 2016 10:47:57 GMT</pubDate>
    <dc:creator>kaushalsolanki</dc:creator>
    <dc:date>2016-12-14T10:47:57Z</dc:date>
    <item>
      <title>Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318778#M6782</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am not able to schedule a flow using SAS DIP Service, Error screenshot is attached.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for the help in advance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://communities.sas.com/t5/image/serverpage/image-id/6361iA0762B95D1A5B830/image-size/original?v=v2&amp;amp;px=-1" border="0" alt="Schedule Flow.JPG" title="Schedule Flow.JPG" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Kaushal&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 08:44:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318778#M6782</guid>
      <dc:creator>kaushalsolanki</dc:creator>
      <dc:date>2016-12-14T08:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318783#M6783</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;did you find some time to read the documentation?:&amp;nbsp;&lt;A href="http://support.sas.com/documentation/cdl/en/scheduleug/68697/HTML/default/viewer.htm#p1j3p8f1tqg8ann1odi1fww2mlcw.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/scheduleug/68697/HTML/default/viewer.htm#p1j3p8f1tqg8ann1odi1fww2mlcw.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Otherwise, I would start by checking the logs of the DIP and JMS services, the command line generated (it should call a java process), and your limitations (no sub-flows are allowed).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If anything of this works for you, please share with us and/or SAS Technical Support your logs and findings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Juan&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 08:55:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318783#M6783</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2016-12-14T08:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318804#M6784</link>
      <description>&lt;P&gt;Hi Juan,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for the reply, Want to ask you that node name mention in SID file is different from the node name of the machine then will it be an issue for SAS DIP scheduling?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As you have suggested have gone through&amp;nbsp;the logs, I was able to find warning only which is as given below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;| WARN | Transport Connection to: tcp:IP:53067 failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///IP:53067@61616&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Kaushal&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 10:47:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318804#M6784</guid>
      <dc:creator>kaushalsolanki</dc:creator>
      <dc:date>2016-12-14T10:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318892#M6788</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for your question: not sure if I can understand what are you exactly asking for, but my answer at this moment would be: no, that should not be a technical problem (although it might be a problem if you receive a security audit).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for the log, please read this SAS note:&amp;nbsp;&lt;A href="http://support.sas.com/kb/54/066.html" target="_blank"&gt;http://support.sas.com/kb/54/066.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 12:34:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318892#M6788</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2016-12-14T12:34:04Z</dc:date>
    </item>
    <item>
      <title>Re: Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318899#M6790</link>
      <description>&lt;P&gt;Hi Juan,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The SAS note you have suggested, I have already gone through that but it is not working for me.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Kaushal&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 12:40:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318899#M6790</guid>
      <dc:creator>kaushalsolanki</dc:creator>
      <dc:date>2016-12-14T12:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318909#M6794</link>
      <description>&lt;P&gt;And did you already contacted SAS Technical Support. Did you extended the logs to a DEBUG level?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2016 12:53:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/318909#M6794</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2016-12-14T12:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unable To Schedule Flow using SAS DIP service</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/321274#M6867</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Found the solution, It was because of SSL certificate implementation so if we are trying to schedule flow from client machine we need to copy&amp;nbsp;&lt;SPAN&gt;SSL files “cacerts” and “jssecacerts”:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;lt;SASHOME&amp;gt;/&lt;WBR /&gt;SASPrivateJavaRuntimeEnvironme&lt;WBR /&gt;nt/9.4/jre/lib/security&lt;BR /&gt;&lt;BR /&gt;Replaced the files of the same name with the mid tier versions, in the following location on local machine:&lt;BR /&gt;&lt;BR /&gt;C:\Program Files\SASHome\&lt;WBR /&gt;SASPrivateRuntimeEnvironment\&lt;WBR /&gt;9.4\jre\lib\security&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Kaushal&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2016 09:36:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Unable-To-Schedule-Flow-using-SAS-DIP-service/m-p/321274#M6867</guid>
      <dc:creator>kaushalsolanki</dc:creator>
      <dc:date>2016-12-27T09:36:43Z</dc:date>
    </item>
  </channel>
</rss>

