Get free P3, P6, Project tips & tricks, register to our newsletter!
To be able to post message in forums, please login or register.
Registration is free (also spam-free)!
Posted By on 01 Jul 2009 04:33 PM We are troubleshooting this same HRESULT / FACILITY_ITF error which is being generated every 30 seconds (in one of our Primavera development environments).ÂWe also see the following TPGS error which appears to trigger the start of the HRESULT / FACILITY_ITF errors:ÂORA-01017: invalid username/password; logon denied This leads us to think we've got a mismatch somewhere with our Oracle username/passwords used by Primavera service accounts.ÂI will update if we find out more.ÂPete Wasielewski Pioneer Hi-Bred Internationalete.Wasielewski@Pioneer.com">Pete.W...ioneer.com
Posted By lakshmy on 04 May 2009 06:30 AM TimeSheet server after the installation of services in the system to generate a service name of TPGS, the corresponding path for the executable file "C: \ WINDOWS \ system32 \ TPGS.exe". But after the service to start every 30 seconds or 90 seconds, the application will generate an error, the specific error message is as follows: Exception error File:ConnectionMgr.cpp, Line:567, Error:8004b002, Description:HRESULT = 8004b002 FACILITY = FACILITY_ITF This is a FACILITY_ITF error that is specific to the interface that returned this error. See the documentation of the interface that returned this error for information about this HRESULT. CCache which is different from the corresponding content, such as: Context: CCache::RefreshUDFTypes CCache:: RefreshOpenedProjects CCache::RefreshDocStatusCodes CCache::RefreshUserList CCache::RefreshAppPreferences CCache::RefreshLicenseInfo CCache::RefreshNonWorkTypes
Last week we got this FACILITY_ITF error to stop being generated every 30 seconds after we reset the usernames and passwords for the Primavera pubuser and privuser accounts on both the Oracle database side and on the Primavera TPGS application side. We also made sure the user accounts were not locked on the Oracle database side (we unlocked something in there but I don't recall whether it was pubuser, privuser or something else). We also made sure the username and password were matching for the user account setup within Primavera to communicate with our LDAP server.
So we're now happy the error messages have gone away. Bottom line is that it appears to be caused by a mismatch between Primavera username and password settings between the Primavera TPGS application side and the Oracle database side. Hope this helps.
Pete Wasielewski; Pioneer Hi-Bred International; A duPont Company.