Troubleshooting
Problem
When reusing an existing server (that has been running earlier versions of Controller) it is possible that the server has been configured to force all .NET assemblies to run in 32 bit mode (using the “ldr64 setwow” command). This in turn causes problems for especially the FAPNTService.exe and the CCRBatch.exe service that as of 10.2 will need to run in 64 bit mode in order to function properly.
Symptom
In the case of the FAPNTService running in 32 bit mode the most common error is that the service will not be able to log on to TM1. This can be seen as a log message in the FAP log.
The easiest way to check if the services are running in 32 bit mode (which they should not be) is to start the Windows Task Manager and then locate the services in the list (you may have to tick the “show processes from all users” checkbox to see all services. If there is a “*32” text after the name of the service this means that the service is running in 32 bit mode.
Resolving The Problem
Remove any batch scripts that you may have defined to force the server to run .NET assemblies in 32 bit mode. Then start a command prompt (as administrator) and navigate to C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\. Then type and run the command “ldr64 set64”. You should then get a confirmation that the “Current status is 0x00000001” which mean that the setting was correctly applied.
Restart the server and verify that the services run in 64 bit mode (ie no presence of the text “*32” after the service name.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21673225