BSI 10.0.k

We had a similar issue when testing our upgrade to BSI 10.0.j.

After consulting with BSI they stated that it was an INFOR issue and referred us to install the below CTPs. These are all for Lawson 9.0.1.

JT-440566 - KB 1510934 9.0.1_patch_100734
JT-641574 - KB 1544802 9.0.1_patch_102015
JT-657347 - KB 1548539 9.0.1_patch_102154
JT-669375 - KB 1573174 9.0.1_patch_102506
JT-741675 - KB 1607589 9.0.1_patch_103984

I am not sure what version of Lawson you are using but we are already on 10.0.0.

Below are the Lawson 10 equivalent of the above CTPs.

CTP100735 found in KB 1510925
CTP102226 found in KB 1549987
CTP104627 found in KB 1633353
CTP104821 found in KB 1623593
CTP105885 found in KB 1642889

We were recommended to install all of these and upon re-testing it resolved our issue.

Note:

We are also looking to move to BSI 10.0.k soon but received a notice that BSI had pulled it from the site after originally having made it available. Makes us wonder if there could be issues with this particular cyclic needing attention.

Since you already have it installed, it might be worth checking to see if you have the above CTPs applied and if not apply them then re-test the issue.

Thank you so much. We are also testing our Lawson 10 upgrade at the same time and did not have the issue there so I guessing it was part of the latest service pack.

FYI - BSI reposted 10.0.k later the same day that they pulled it.

You are welcome.

Thanks for the heads up on 10.0.k. The business gets the notifications from BSI at my employer.

I will be sure to let them know it should be available again.

Did anyone have an issue installing the 10.0.k client? I found out that Tomcat, Java, and ODBC all need to be 64 bit now.

We can get to the login page, but once we login, we get an Application error:
Exception is: java.lang.NoClassDefFoundError: Could not initialize class com.bsi.tf.jni.TF10APIJNI

jeff, ran into same issue.
had to completely uninstall client, remove server registry key, and re-install.

Thanks John. I've tried uninstalling and installing everything, I've tried making everything 32 bit, making everything 64 bit. Trying Apache/Tomcat6 and Apache Tomcat 7. And still no luck. Thanks for the registry tip. I will give that a try.

John,

Sorry, where is the server registry key that I'm looking for?

Hi Jeff - you can register your host, and request a new key on the BSI Support site (mybsiconnect.force.com). Then download the *.lic file, and import it from the BSI10 directory location when the tflic command to load it is executed:  tf10lic -i yourlicense.lic

Then it may indicate there is a critical file folder missing in the Tomcat directory that’s needed. During the client install, a file named ‘lib’ is placed in the folder “lib” in the Tomcat environment directory. If the folder is not there to receive the file, the file is placed in the folder anyway, but it won’t work without the complete path. See the steps below to correct.

After the PRD (or applicable environment) folder is opened, there should be a sub-folder “lib”. The lib folder here is where the new tf10apiJNI.dll is placed. If this folder does NOT exist, then create a new one named lib and rerun the client install.

Ronnie,

BSI already sent me the Word document with this verbiage, and this did not resolve my issue. I'm receiving the Application Error message, but the Error itself is different.

Error Message
Exception is: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (IO Error: NL Exception was generated)

Jeff, I am curious to know if you were able to get this running. We can't even get the login screen to load. We too are getting the tomcat, ODBC, java error but all three are 64 bit. After numerous emails and phone call, I have not been able to get anyone to respond from BSI. I talked to one person on the phone and he said he would have to send it to the tier 2 people. He sent me a form to fill out which I immediately did and nothing for two days. Ann

We did finally get this to work. Our problem ended up being the way that we copied the tnsnames.ora entry into the box during configuration. If we copied the tnsnames.ora entry from the tnsnames.ora file itself, it would not work. Once we copied the tnsnames.ora entry from the tnsping results, it worked like a champ. I still don't understand that one. They both had the same information, but the spacing was different.

What I would recommend is to uninstall everything....Tomcat, and all of your Tax Factory 10 installations.

I would install the 64bit Java JRE first, then Tomcat 7, and then your TF10.0.k installation(s).

I hope that helps.
Jeff