VoigtWorld :: Family and Friends

Start :: PostNuke :: pnTNG :: pnTNG 2.16 error: Error accessing TNG information.
Moderated by: Wendel, admin

	pnTNG 2.16 error: Error accessing TNG information.
dnuttall	Posted: 08.08.2006, 15:05
registered: Mar. 2006 Posts: 1 Status: offline last visit: 08.08.06	I have a pristine/clean install of both PN 0.762 and TNG 5.1.4. Both work fine separately, so we activated the pnTNG and that works too. Added a Block/menu link and that works fine with TNG accepting the PN guest or validated PN user. However, the subject error continues to display even though everything seems to work OK. My guess is it comes from pntng.php in the PN root directory. Since PN 762 changed the table prefix from nuke_ to pn_, is there some residue in the module that doesn't find the right PN users table? That's the only explanation I can conjure up, but drawing social security seems to have softened my brains, so it could be something else. Any ideas (Wendel) or others? I haven't asked Darrin, but he'd tell me that its NOT TNG and I think he would be on solid ground there. TIA and best regards from San Antonio, TX Dave


Wendel	Posted: 08.08.2006, 23:15
registered: Jun. 2005 Posts: 82 Status: offline last visit: 03.05.08	Dave, Can you check your pnTNG settings in the Administration section of PN. Does it give you any errors? This error does come from pntng.php. It means that it had trouble creating/validating the user information with TNG. pnTNG uses the standard PN call to get the PN user id. pnTNG does not access any of the PN tables directly -- so I don't think that is the problem. In this case, either it a) can't get to the TNG config.php file (the configuration is not right) b) it couldn't read TNG's user table (as found in the TNG config.php file) It would be a MySQL error. c) or it couldn't create a user ID in TNG tables. Again a MySQL error. I've never really seen b or c happen, but there is always a first time. Have you installed any of the blocks? Do you get similar errors? If so, I would suspect the pnTNG configuration settings. That seems to be a common problem area with pnTNG. - Wendel edited by: Wendel, Aug 08, 2006 - 10:17 PM