Error running VLF-Windows to IBM i

[atostaine]

Awhile ago Hamad helped us setup a share on a file server so all of our users can run one copy of our app. It's basically the directories from the development machine copied to the server, and then we put an icon on each users desktop that points to the share. It's been working in V14 forever. I'm trying to duplicate that for testing V15 so I copied the directory structure over. I'm getting the following error once I press logon on VLF-Win. The IBM i starts a TX job for the app but it ends once I cancel the error.

Screenshot 2023-08-18 at 2.39.17 PM.png (91.48 KiB) Viewed 133134 times

Here is my x_Start. Is it necessary for me to define %basepath% anwhere?

%tit%PDSI
"%basepath%\X_Lansa\Execute\X_Run.exe"
CMTH=C
CDLL=C:\Freightblue_V15\X_WIN95\X_LANSA\Connect\lcomgr32.dll
UPGD=NO
FORM=DDS_EXEC
UPCD=AAA6B0EB-E6AD-450B-A255-3B4E21DA1DBE
PART=CCA
LANG=ENG
DBII=*NONE
DBID=*NONE
DBTC=Y
PSTC=NO
ASTC=NO
APPL=PDSI
DBID=*NONE
UPCF=CONTINUE
UPDF=CONTINUE
UPSI=YES
XENV=X_DOLLAR_SIGN_CHAR=$
XENV=X_GEN_AT_SIGN_CHAR=@
XENV=X_AT_SIGN_CHAR=@
XENV=X_HASH_SIGN_CHAR=#
SUDB=N
SUDB=N
INST=MSI
RNDR=M

This message appears in the dialog box after I click OK:

Fri Aug 18 14:39:18 2023
Version 15.0.0 Build 4403 Windows Server 2008 R2 Server Datacenter (Full InstallatioComponent : VF_SY160
CONNECT_SERVER V2
Statement : 17
Message : (1017) - Server must be running LANSA 11.0 or later when using DEFINE_ANY_SERVER or DBID=*ANY.
Routine : X_PDF_Determine_Client_Type

[MarkDale]

Hi Art,

The line where the connection fails in VF_SY160 is probably just where the built_in CONNECT_SERVER is invoked. So its probably nothing VLF specific.

For general CONNECT_SERVER problems, the technical guide
http://docs.lansa.com/14/en/Lansa015/in ... server.htm

suggests this:

That the same job description has LOG(4 00 *SECLVL) logging if you are trying to solve a problem. This will ensure any IBM i job the profile starts will produce an IBM i job log. This job log will almost always yield useful error information.

That might be worth a try.

I don't think you need to specify the base path, though I think your shortcut probably has to specify the whole path in the Target property and in the Start In property.

[atostaine]

I don’t think the IBM i is ending the job but I’ll take another look. Thanks

[atostaine]

I made some progress on this after installing all of the EPC's for V15. I'm getting a message that it can't find the message file DC@M01. Does anyone know what PC file contains the message file?

Thanks

[davidbalansa]

Hi Art,

This is the LANSA message file. In Windows it is located in the file LANSA internal file LX_MSG.

Screenshot 2023-08-31 063111.png (87.62 KiB) Viewed 132945 times

[atostaine]

Thanks David. I don't have a local database so I think it's supposed to be in a file in the PC Directory?

Art

[MikeRoyal]

Hi Art

It's a few years since I worked on the windows version of VLF, but I vaguely recall that you need to set the %PATH% environment variable on the windows client to include the path to your VLF folders.

Might be worth checking.

Regards

Mike

[caseywhite]

Hi Art.

Not sure if you resolved this yet but take a look at this help topic.
http://docs.lansa.com/14/en/lansa015/in ... ght=LX_MSG

Could be you just need to copy the .xq files from the v14 server directory to the v15 or maybe just rerun the *SYSEXPORT for the v15 system.

[atostaine]

Thanks Casey I’ll give it a try.

[atostaine]

Hi Casey: Copying the XQ files didn't work for me. I can't remember how to run *SYSEXPORT lol. How do I do that from the V15 system?

Art

[caseywhite]

Hi Art. I haven't tried it but here is a link to V15 documentation that explains how to run it using X_RUN.
https://docs.lansa.com/15/en/lansa015/C ... 3_0055.htm

[atostaine]

Thanks again Casey. I managed to do the *sysexport but moving those .LQ files didn't resolve my problem. I guess I'll submit an incident.

Art