Greetings,
I'm a SysAdmin working on our BSI 8.0 upgrade (yes, I know we're late to the party) and am having some major issues with an error that just won't go away. I'm running Windows Server 2003 SP1, Lawson Environment 8.0.3.7 ESP7, and trying to go from TaxFactory 7.0k to 8.0g. I have an Oracle 10g DB.
Basically, when we run our PRTF and try to run any of the tests, the app bombs out with this error:
Error: 173
BSIProcessTaxesNC8
Called program file not found in drive/directory
I basically have gone through all the troubleshooting:
-I checked the environment variables - we have a DATA SET variable set to DEFAULT, matching the 8.0 setting. I have a TF80_STRING_CONNECT with the correct parameters matching my ODBC configuration
-I checked my PRTFX settings, line 699 is calling TF80 as expected.
-I checked permissions on the libtfxiface8.dll file - SYSTEM has full permissions and so does my group of Lawson Users. The dll is in the right place - %GENDIR%/BIN
-The tf8api.dll is in the system32 folder with the right permissions
-I patched the environment and the application with the appropriate PT's (166922 and 51432)
-I tried recompiling the programs attached to the patches
-I tried rebooting the server to ensure settings took
-I tried reinstalling the 8.0 client
I looked on here and found a great procedure for the UNIX installation. The only thing I deviated from was that the initial installation, including creating the tablespace and user, populating it, and installing the client, was done prior to applying the PT's. I havent tried backing all the way out of the installation, but I can't imagine that was the issue.
Anyone else have something I can try? Lawson support is stymied by this issue and from a technical standpoint the problem seems simple - it can't find the file to run - I just don't know where else to look to make sure it's looking in the right spot. It's worthy to note I still ahve TF 70 installed on the machine, but supposedly with the changes made they shouldn't have a problem with one another. Am I missing something?
Thanks in advance for the help.
Sorry if I'm putting you through some more questions but are you able to connect via the TF app?
Ok, apparently there is very small window in which you can edit your original posts...arrgghh
Here's what I was trying to add:
Sorry if I'm putting you through some more questions but are you able to connect via the TF app? Did you check the event viewer to see if there was more information?
Hey, check this out. After my post I just did a check on the error message in google, and it came up with this a
Cobol problemor
this one| QUOTE |
173 Called program file not found in drive/directory (Fatal)
You have tried to call a program which is not present on your current logged-in drive or directory, or in a directory pointed to by the COBPATH environment variable, or to send a message to a class which cannot be loaded.
Resolution:
Once your program has terminated you should copy the relevant file into your logged-in drive or directory. If insufficient space is available, you should set the COBPATH environment variable to search the directory or drive on which the file is present when your program calls it.
If the error was caused by a class which could not be loaded, find out whether or not the filename for the class (listed in the Class-Control paragraph) is a separate executable file, or contained in a .dll or .lbr file. If it is a separate executable file, the resolution is as above. If it is part of a .dll or .lbr file, ensure that the containing file has been loaded with a CALL statement before sending messages to any of the classes. If the program not found is P2emgr, you need to load the GUI Class Library, with a CALL "APIGUI" statement.
|
I don't if that really offers any solution for you but see if that might be your issue.
I can connect via the TF app. I checked the event viewer and there are indeed COBOL errors, but they basically report the same thing as the PRTF app, which doesn't quite help.
After working with the company, they themselves appear to have told us that we are the only ones experiencing this issue. I hope we can get it resolved somehow and I'm pursuing all avenues to get some kind of resolution. I just feel like I've tried everything short of starting over from scratch and still have these problems.
Well, it appears we fixed our problems. For information's sake for anyone else desperately looking for info, the cause of our problem was the presence of another labcobrts.dll file located in the Micro Focus COBOL installation directory. I am unsure how that file got there but it definitely was a different version than the one we had in %GENDIR%/bin. Once we moved this file we were able to run our PRTF with no problems.
Thanks for the help!