(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

Hi Matt,

In a multi-customer environment I don't think you could use a "shared credentials" where the ACS assumes the user ID and password is the same across all of your systems.

I'm personally on 1.1.9.7 as well and running IBM Semeru Runtime Open Edition 21.0.4.1 (build 21.0.4+7-LTS). No issues similar to yours and using the "Use default user name and prompt once for each system" options because the "prompt every time" would kill me.

Do you use just the .jar file from the extracted .zip archive or do you install the ACS through the installer, and run the .exe file? Could you try one or the other?

I'm personally set to run the .jar only from a cloud with the ACS set as a portable installation so I can have my settings everywhere I go.

Cheers, Michael

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

Thanks all.

I was able to change the Java version and am now using Semeru 21 and no longer have that issue when I use the 'Use default user name to prompt for password once per system"

I don't have administration access to my PC, so I had to add the -vm option to the start commands. At least I was able to prove that the Java version was the culprit and will have desktop support make it more permanent. 

Matt

Hi Matt,

In a multi-customer environment I don't think you could use a "shared credentials" where the ACS assumes the user ID and password is the same across all of your systems.

I'm personally on 1.1.9.7 as well and running IBM Semeru Runtime Open Edition 21.0.4.1 (build 21.0.4+7-LTS). No issues similar to yours and using the "Use default user name and prompt once for each system" options because the "prompt every time" would kill me.

Do you use just the .jar file from the extracted .zip archive or do you install the ACS through the installer, and run the .exe file? Could you try one or the other?

I'm personally set to run the .jar only from a cloud with the ACS set as a portable installation so I can have my settings everywhere I go.

Cheers, Michael

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

You may want to try, if not yet done, this interesting feature which is to place a java installation inside the iACS installtion folder (https://www.ibm.com/support/pages/java-options-ibm-i-access-client-solutions):

---------------- quote ----------------

IBM i ACS can also directly define the Java runtime to be used by the acslaunch program.  One of the benefits of this approach is that this allows IBM i ACS to use a Java runtime that may not be available to the entire client workstation.  There are also several ways to do this and here are a couple:

• Place the Java JRE folder next to the acslaunch program that is being used.

---------------- quote ----------------

Here is how I did it:

PowerShell 7.5.0
PS C:\Users\Marco> cd C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64
PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64> dir

    Directory: C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          25/11/2024    16:49                jdk-23.0.1+11-jre
-a---          25/11/2024    16:39        1555792 acslaunch_win-64.exe
-a---          25/11/2024    16:39        2948944 acsnative.dll
-a---          25/11/2024    16:39         146256 acspcoc.exe

PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64>

Thanks all.

I was able to change the Java version and am now using Semeru 21 and no longer have that issue when I use the 'Use default user name to prompt for password once per system"

I don't have administration access to my PC, so I had to add the -vm option to the start commands. At least I was able to prove that the Java version was the culprit and will have desktop support make it more permanent. 

Matt

Hi Matt,

In a multi-customer environment I don't think you could use a "shared credentials" where the ACS assumes the user ID and password is the same across all of your systems.

I'm personally on 1.1.9.7 as well and running IBM Semeru Runtime Open Edition 21.0.4.1 (build 21.0.4+7-LTS). No issues similar to yours and using the "Use default user name and prompt once for each system" options because the "prompt every time" would kill me.

Do you use just the .jar file from the extracted .zip archive or do you install the ACS through the installer, and run the .exe file? Could you try one or the other?

I'm personally set to run the .jar only from a cloud with the ACS set as a portable installation so I can have my settings everywhere I go.

Cheers, Michael

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

Good call, Marc, to mentioned it here. This trick becomes quite handy when you just want to temporarily test some other JDK/JRE (so you paste it in the ACS "run" folder without any installation steps), all without needing the current (properly installed) JDK/JRE to be uninstalled first. The JDK/JRE placed in the ACS "run" folder just takes a precedence during ACS runtime. I have seen IBM Support folks themselves using this trick for ACS troubleshooting.

You may want to try, if not yet done, this interesting feature which is to place a java installation inside the iACS installtion folder (https://www.ibm.com/support/pages/java-options-ibm-i-access-client-solutions):

---------------- quote ----------------

IBM i ACS can also directly define the Java runtime to be used by the acslaunch program.  One of the benefits of this approach is that this allows IBM i ACS to use a Java runtime that may not be available to the entire client workstation.  There are also several ways to do this and here are a couple:

• Place the Java JRE folder next to the acslaunch program that is being used.

---------------- quote ----------------

Here is how I did it:

PowerShell 7.5.0
PS C:\Users\Marco> cd C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64
PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64> dir

    Directory: C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          25/11/2024    16:49                jdk-23.0.1+11-jre
-a---          25/11/2024    16:39        1555792 acslaunch_win-64.exe
-a---          25/11/2024    16:39        2948944 acsnative.dll
-a---          25/11/2024    16:39         146256 acspcoc.exe

PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64>

Thanks all.

I was able to change the Java version and am now using Semeru 21 and no longer have that issue when I use the 'Use default user name to prompt for password once per system"

I don't have administration access to my PC, so I had to add the -vm option to the start commands. At least I was able to prove that the Java version was the culprit and will have desktop support make it more permanent. 

Matt

Hi Matt,

In a multi-customer environment I don't think you could use a "shared credentials" where the ACS assumes the user ID and password is the same across all of your systems.

I'm personally on 1.1.9.7 as well and running IBM Semeru Runtime Open Edition 21.0.4.1 (build 21.0.4+7-LTS). No issues similar to yours and using the "Use default user name and prompt once for each system" options because the "prompt every time" would kill me.

Do you use just the .jar file from the extracted .zip archive or do you install the ACS through the installer, and run the .exe file? Could you try one or the other?

I'm personally set to run the .jar only from a cloud with the ACS set as a portable installation so I can have my settings everywhere I go.

Cheers, Michael

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

And I see another advantage, if you place the iACS installation folder in a network shared folder available to all users. This way, you do not have to install any java software on the personal device (which could be problematic within some organizations), and you update iACS and its java installation, on a one shot basis, no need to update it everywhere.

Good call, Marc, to mentioned it here. This trick becomes quite handy when you just want to temporarily test some other JDK/JRE (so you paste it in the ACS "run" folder without any installation steps), all without needing the current (properly installed) JDK/JRE to be uninstalled first. The JDK/JRE placed in the ACS "run" folder just takes a precedence during ACS runtime. I have seen IBM Support folks themselves using this trick for ACS troubleshooting.

You may want to try, if not yet done, this interesting feature which is to place a java installation inside the iACS installtion folder (https://www.ibm.com/support/pages/java-options-ibm-i-access-client-solutions):

---------------- quote ----------------

IBM i ACS can also directly define the Java runtime to be used by the acslaunch program.  One of the benefits of this approach is that this allows IBM i ACS to use a Java runtime that may not be available to the entire client workstation.  There are also several ways to do this and here are a couple:

• Place the Java JRE folder next to the acslaunch program that is being used.

---------------- quote ----------------

Here is how I did it:

PowerShell 7.5.0
PS C:\Users\Marco> cd C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64
PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64> dir

    Directory: C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          25/11/2024    16:49                jdk-23.0.1+11-jre
-a---          25/11/2024    16:39        1555792 acslaunch_win-64.exe
-a---          25/11/2024    16:39        2948944 acsnative.dll
-a---          25/11/2024    16:39         146256 acspcoc.exe

PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64>

Thanks all.

I was able to change the Java version and am now using Semeru 21 and no longer have that issue when I use the 'Use default user name to prompt for password once per system"

I don't have administration access to my PC, so I had to add the -vm option to the start commands. At least I was able to prove that the Java version was the culprit and will have desktop support make it more permanent. 

Matt

Hi Matt,

In a multi-customer environment I don't think you could use a "shared credentials" where the ACS assumes the user ID and password is the same across all of your systems.

I'm personally on 1.1.9.7 as well and running IBM Semeru Runtime Open Edition 21.0.4.1 (build 21.0.4+7-LTS). No issues similar to yours and using the "Use default user name and prompt once for each system" options because the "prompt every time" would kill me.

Do you use just the .jar file from the extracted .zip archive or do you install the ACS through the installer, and run the .exe file? Could you try one or the other?

I'm personally set to run the .jar only from a cloud with the ACS set as a portable installation so I can have my settings everywhere I go.

Cheers, Michael

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst

I've been testing that and is seems really slow to load when the java is on the share. Additionally, the documentation advises that if the share drive gets disconnected with the Java there the application will quit working. If the Java is local and the ACS is on a share then you can still use it as long as it was active before ACS share dropped. 

Just ran some tests:

• G= IFS share to /QIBM/Userdata/Access/ACS (IBM i remote hosted)
• K=Intel server share (AWS)
• C=Local C: drive

Java=K, ACS=K took 1:40 to load

Java- C, ACS=K tool :20

Java=C, ACS=G took :46

Java=G, ACS = G took 2:45

Java=C, ACS=C took :09

Not sure why the ifs share took longer than an Intel file share.

And I see another advantage, if you place the iACS installation folder in a network shared folder available to all users. This way, you do not have to install any java software on the personal device (which could be problematic within some organizations), and you update iACS and its java installation, on a one shot basis, no need to update it everywhere.

Good call, Marc, to mentioned it here. This trick becomes quite handy when you just want to temporarily test some other JDK/JRE (so you paste it in the ACS "run" folder without any installation steps), all without needing the current (properly installed) JDK/JRE to be uninstalled first. The JDK/JRE placed in the ACS "run" folder just takes a precedence during ACS runtime. I have seen IBM Support folks themselves using this trick for ACS troubleshooting.

You may want to try, if not yet done, this interesting feature which is to place a java installation inside the iACS installtion folder (https://www.ibm.com/support/pages/java-options-ibm-i-access-client-solutions):

---------------- quote ----------------

IBM i ACS can also directly define the Java runtime to be used by the acslaunch program.  One of the benefits of this approach is that this allows IBM i ACS to use a Java runtime that may not be available to the entire client workstation.  There are also several ways to do this and here are a couple:

• Place the Java JRE folder next to the acslaunch program that is being used.

---------------- quote ----------------

Here is how I did it:

PowerShell 7.5.0
PS C:\Users\Marco> cd C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64
PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64> dir

    Directory: C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          25/11/2024    16:49                jdk-23.0.1+11-jre
-a---          25/11/2024    16:39        1555792 acslaunch_win-64.exe
-a---          25/11/2024    16:39        2948944 acsnative.dll
-a---          25/11/2024    16:39         146256 acspcoc.exe

PS C:\Users\Marco\IBM\ClientSolutions\Start_Programs\Windows_x86-64>

Thanks all.

I was able to change the Java version and am now using Semeru 21 and no longer have that issue when I use the 'Use default user name to prompt for password once per system"

I don't have administration access to my PC, so I had to add the -vm option to the start commands. At least I was able to prove that the Java version was the culprit and will have desktop support make it more permanent. 

Matt

Hi Matt,

In a multi-customer environment I don't think you could use a "shared credentials" where the ACS assumes the user ID and password is the same across all of your systems.

I'm personally on 1.1.9.7 as well and running IBM Semeru Runtime Open Edition 21.0.4.1 (build 21.0.4+7-LTS). No issues similar to yours and using the "Use default user name and prompt once for each system" options because the "prompt every time" would kill me.

Do you use just the .jar file from the extracted .zip archive or do you install the ACS through the installer, and run the .exe file? Could you try one or the other?

I'm personally set to run the .jar only from a cloud with the ACS set as a portable installation so I can have my settings everywhere I go.

Cheers, Michael

(Posted in IBM i Global before I found this group...)

I recently installed the latest version of ACS and the only option for password prompting that works is "Prompt for user name and password every time". The other options give me the "MSGGEN005 - Internal error. (java.lang.NullPointerException)" message. 

I'm running on Windows 11 Enterprise 24H2. Oracle java 1.8.0_111. I have seen issues online with 24H2, and that issue is with using shared credentials..

When I use prompt every time, I get 2 login screens where I have to put in my password. The second time it pops up my user id is filled in with all upper case. After I enter my password for the second time, I get the IBM i 5250 login screen, so in effect I have to log in 3 times to get into my system. 

Has anyone else come across this? And does anyone know of a solution?

1. Can I stop the MSGGEN005 error when using "Use default user name and prompt once for each system"?
2. Can I stop getting 2 login screens?

Thanks,

Matt Hopkins

IBMi Programmer/Analyst