Over the past several days I have been configuring multiple systems with multiple Peopletools versions and I think my mind snapped somewhere.  This 32/64 bit thing is so frustrating.  Basically 8.54 is almost completely 64 bit, but 8.53 is still a 50/50 chance.  When it comes to Crystal with 8.54 you need to make sure you use the 64 bit run time library where as 8.53 and down use the 32 bit run time.  However if you have the full install of crystal so that you can develop reports, you need to put the CrystalExePath to the the full install win32_x86 32 bit directory.

I found this absolutely helpful case on Support:  1540788.1:

PeopleSoft PeopleTools 8.53+ uses the SAP Crystal Reports runtime engine for .NET Framework 4, (Crystal Reports version for Visual Studio 2010), as the runtime for running SAP Crystal Reports. This must be downloaded from the SAP website. Link

Download the Runtime:  PeopleTools 8.53 – 32bit and PeopleTools 8.54 – 64 bit.

When configuring the process scheduler set the CrystalEXEPath to:

8.53:  CrystalEXEPath = C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86

8.54:  CrystalEXEPath = C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_x64

If you have Crystal Reports 2008 installed as well as the runtime set the CrystalEXEPath to:

CrystalEXEPath = C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86

Note:  This are the default install paths and maybe different depending on how you installed them.

The other day I ran into a situation where all Crystal’s were going to error, after working fine. Doing a little research on My Oracle Support I found that this error:

Warning: ORB::BOA_init: hostname lookup returned `localhost’ (127.0.0.1/::1)
Use the -OAhost option to select some other hostname

is actually related to the IPv6 being disabled. On the servers were this occurred the odd thing appears to be that IPv6 was disabled prior to the error occurring. So it is possible that some patch or fix or another change the administration team did started this error to occur. After re-enabling the IPv6 the error went away. This appears to occur with PeopleTools 8.5x with Crystal 2008 running in the Windows 2008 environment.

Windows 2008 non-R2:
Control Panel > Network > Manage Network Connections > highlight Local Area Connection > Advanced > Advanced Settings > Bindings for Local Area Connection.
1) If IPv6 is not enabled, enable it, then retest.
2) If enabled, try switching the order, then retest.

Windows 2008 R2:
Control Panel > Network > double-click on Local Area Connection > Properties >
1) If IPv6 is not enabled, enable it, then retest.
2) If enabled, try switching the order, then retest.

When trying to execute a crystal check on one of my development systems I found a problem after trying to fix another problem.  All the crystals were going to error status and the message was coming up:

File: SQL Access ManagerSQL error. Stmt #: 2  Error Position: 0  Return: 404 – ORA-01017: invalid username/password; logon denied  (200,0)

It turns out that the PSACCESSPRFL table had an extra entry which was invalid for the environment.  Once I removed the invalid entry from the PSACCESSPRFL table the problem was resolved.