As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
If the distribution server were not on, then you would not see any error at all. You would get an error something like this after the procedure has completed but it unable to be distributed due to one of the following reasons:
The destination is not reachable (bad IP/DNS) Unable to log in to destination (bad username/password) Bad characters in or invalid name for the destination file Insufficient write privilege for the destination location/directory
Check out all of these things. RC also has trace files that you can turn on to see what is happening. You might also check any system/server logs at the destination to see if you are getting security or authentication violations.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
I assume you are distributing the xls file via FTP. The broken pipe errors are typically generated from the destination FTP server. Make sure you can access the FTP site with the userid/password before running ReportCaster. We had some issues with too many FTP's at once causing the broken pipe errors. This was resolved by a registry setting on the destination FTP server for the number of allowed concurrent connections.
Dev- WF 7.68 on Windows Server 2003: DB2, SQL Server 2K, SQL Server 2005, SQL Server Anaysis Services 2005. Test- WF 7.67 on Windows Server 2003: DB2, SQL Server 2K, SQL Server 2005, SQL Server Anaysis Services 2005. Prod - Dev- WF 7.65 on Windows Server 2003: DB2, SQL Server 2K, SQL Server 2005, SQL Server Anaysis Services 2005