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.
Yes! Even we are seeing that issue after migrating to 7703. Earlier if anything like that occurs it used to show SQL-CODE: ORA-##### error. There should be some sort of setting to show the actual error instead of displaying the default "local" error.
WebFOCUS - ver8201 [ReportingServers: Windows 64bit; Client: tomcat and IIS on windows 2012 AppStudio
Posts: 104 | Location: Indianapolis | Registered: November 08, 2007
I had never seen "local" error before. I upgraded in Oct 2011 - but did not start seeing this error till April 2012. But interesting we are all on 7.7.03. I had to take one of the programs that has been in Focus code forever and make it an SQL passthru to make it work. I still have three others with this error too.
In Focus since 1993. WebFOCUS 7.7.03 Win 2003
Posts: 1903 | Location: San Antonio | Registered: February 28, 2005
Yes it is very inconsistant - exactly why I have not opened a case. Yes after making one a SQL pass thru it works. The others I have are pretty complicated and have not changed yet. Kamesh keep us posted if you get a result with IBI. Does sound like a bit of a bug crawling around out in 7.7.03.
Posts: 1903 | Location: San Antonio | Registered: February 28, 2005
Seeing the same thing in Data Migrator today, for routines kicked off from the web console. We've been running jobs like this from the web console for years.
03/01/2013 15:02:09.758 I disconnect FDS
03/01/2013 15:02:11.743 I validated t3rp9752 u=wfAdmin
03/01/2013 15:02:11.743 I processing gwrp720 u=wfAdmin,r=SRV
03/01/2013 15:02:11.758 I validated t3rp10776 u=wfAdmin
03/01/2013 15:02:11.758 I DM: agent started (dmid=C4, proc=dc_form1_stage/23_stage_b_to_testresult_2, active)
03/01/2013 15:02:11.758 I request by t3rp9752 to notify disconnect of sesid=23
03/01/2013 15:02:11.758 I disconnect gwrp720 tscomid=3,sesid=23
03/01/2013 15:02:11.758 I processing cmrpsh999998 u=wfAdmin,r=SRV
03/01/2013 15:02:11.758 E error: <NGXX> xxsec_init:unable to init NTLM, connect explicitly with no password
03/01/2013 15:02:11.758 I request by cmrpcm000004 for explicit connect to agent (DEFAULT)
03/01/2013 15:02:11.758 I connecting cmrpcm000004 tscomid=1,sesid=25
03/01/2013 15:02:11.758 I DM: connected agent dmid=C4 tscomid=1,sesid=25
03/01/2013 15:02:11.758 I request by cmrpcm000004 for explicit connect to agent (DEFAULT)
03/01/2013 15:02:11.758 I connecting cmrpcm000004 tscomid=2,sesid=26
03/01/2013 15:02:11.758 W (EDA13089) rejected t3rp10932 u=wfAdmin (password failure)
03/01/2013 15:02:11.790 I accepting FDS connection tcp=::1:56348
03/01/2013 15:02:12.024 I request by t3rp10776 to notify disconnect of sesid=24
03/01/2013 15:02:12.024 I disconnect cmrpsh999998 tscomid=4,sesid=24
03/01/2013 15:02:12.024 I disconnect FDS
03/01/2013 15:02:13.212 I accepting cmrpht000007 tcp=10.161.4.10:52624
03/01/2013 15:02:13.259 I request by cmrpht000007 for iwa connection
03/01/2013 15:02:13.259 I request by cmrpht000007 to exec <webconsole> u=wfAdmin, session=1362168092:1-1-0
Right now the error is very consistent for me, and its shown above. It's giving me a password failure for an admin account that provided the password on login. I had this problem a couple of weeks back and it disappeared, but now it's back.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I got this error today again, in an datamigrator process. I am going to dive a bit deeper in the details, maybe I can find more in the log file I will keep you informed and I wonder if after all these months if it is solved
Btw we are running 7.7.05
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006