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.
MSGV0002 appears to be related to the length of the schedule name. I tried reducing the length to less than 64 characters, but I still got the error. This suggests that the error could have been for the Schedule Name or Title, the Task Name, the Distribution Name, the email Notification Subject...
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
In 7705 I found that accidentally using the en-dash punctuation in the Subject line causes garbage characters in the subject line of the distributed report email. Using MS Word, I had typed in all the information (text) I was going to use in preparation for setting up a RC job. For the Subject (and Description, for that matter) I had typed some text followed by a followed by some more text. MS Word turns the into an en-dash and as it turns out RC sees this as some sort of unprintable character set, hence the garbled subject line in the email. After manually editing the Subject in the RC job, problem solved.
I just bumped into this in 8.2 so the problem remains. And what is odd is that it appears that once you've fouled the connection you can't undo it, as I removed all non-alpha characters and continued to get the error. So if you hit this you likely want to start from scratch.
I restarted, and also took out the reference to an EDASERVE routine and proxied the request through an MRE unit. May have helped, don't know if that was important, but I was able to save the new one.
Thanks for the help, and thanks for leaving this marked NOT CLOSED as that is exactly what it is.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007