Well, before making any assumptions, let's review the obvious.. you have a program running another program, and something fails. You need to add some diagnostic output to the outer (kix) script to know what it's doing. This way you can tell what part is failing.
You map a drive to I:, but don't use I: in your commands. Instead you use UNC paths to launch the installers. While the installer may launch, it may not be able to find any other installation files it needs via UNC. Always CD into the folder where your installer is so it can find any required files.
After the USE I: command, add something like this:
If Not Exist('I:\isdept\jre.msi')
'ERROR! Cannot find a required file on the I: drive!'
; Connect to the mapped drive / CD to the install folder
$Cmd = '.\jre.msi /quiet /lew+ I:\logs\logi.log'
About to run $Cmd
; repeat as needed for additional install commands
Also - RUN "\\Server07159\OFCSCAN\AUTOPCC.EXE"
Is "OFCSCAN" a different share, with the AUTOPCC.EXE in the root? Or are you missing the share?
Again - defining the command in a var, displaying the var before you run it might help make those kind of mistakes more apparent, along with the If Exist() to validate that the file exists before you run it.