IT Process Automation

Has anyone installed PAM 4.3_01 on Windows server 2016?

Added my new Win2016 node to my cluster and when i try the CA Cluster test process, run script operator returns : 'hostname' is not recognized as an internal or external command,
operable program or batch file.

Had a look at the PATH variable. Everything looks fine.

Hostname works well if i type in in cmd manually.

At least, the new node works in the cluster

Thanks.

I have installed 4.3SP2 on Windows2016.  Just ran a "run script" operator with just "hostname" for the script and the process succeeded.

It doesn't look like 4.3SP1 was certified on Windows2016:

Platform Support and Requirements - CA Process Automation - 4.3.1 - CA Technologies Documentation 

not sure if that is the problem here or not but could be.  Maybe more information about the operator you are running such as the exact command that the script is running.  Is there a userid/password entered into the properties of the operator?  Is the operator running on a touchpoint?  etc.

Hi Andrew.

I'm running CA's test process to test clustering setup

Nothing fancy. It is the original one, never modified it.

And this process is call a specified number of time. Thus allowing you to see if the load balancing setup works.

Pam version :

Version: 4.3 HF01
Build: 4.3.50 HF01 - Aug 11, 2015 3:16:12 PM

I ran an old cluster test process I have in version 4.3SP2 and it worked fine.  But it uses the following script:

echo %computername%

Regardless, you are on a release that is not certified with Windows2016 so that may be the problem and there may be other problems that we are just not aware of.

Upgraded my 3 nodes on SP2.

Still have the same issue.

The only difference between my nodes, apart the OS version, is that 8dot3 naming is not activated on my new node. May it cause issues?

If you export the process you should be able to upload the XML to this post and then I can test the exact process you are using on my system.  

I do not want to upload it here. I had a look at the xml and it contains orchestrator server name and other informations.

Understood.  Feel free to open a support case and send it to us that way.