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.
What does this error mean? The server I am trying to deploy to is a regular Maintain server running in private mode. No agents were busy while I deployed the program. It was a test server with noone on it.
Details: (FOC3839) AppServer command :COMPILE: invalid in state :MAINTAIN CALL SERVER:This message has been edited. Last edited by: Kerry,
Sandbox Version: 8.1.04 Sandbox Platform: Windows 2008 R2 Testing Version: 7.7.02M Testing Platform: Windows Server 2008 R2 WF Production Version: 7.7.02M Production Platform: Windows Server 2008
Posts: 57 | Location: Philadelphia, PA | Registered: June 19, 2007
Richard Are there any non-Maintain commands in the code? Something before the MAINTAIN statement or after the END statement? The only thing I can recommend is to change the server to: Agent_refresh = 1 in edaserve.cfg If that doesn't work please let me know if all Maintains fail or just this one.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
Sandbox Version: 8.1.04 Sandbox Platform: Windows 2008 R2 Testing Version: 7.7.02M Testing Platform: Windows Server 2008 R2 WF Production Version: 7.7.02M Production Platform: Windows Server 2008
Posts: 57 | Location: Philadelphia, PA | Registered: June 19, 2007
Richard I believe it has to do with Maintain trying to reuse an agent that may or may not be in the ready state. This issue was fixed in later releases (V7.5) but we still recommend that our users call their Maintain procedures with a random value or timestamp to ensure no agent or caching issues.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003