Visual LANSA Forum

Hi Jorg

I recall this error from way back...
I don't believe the solution suggested by Dino will make any difference. As I recall it...V11.5 cannot be installed on to a 64-bit O/S. V11.5 was only available for 32-bit O/S.
If you still have a V12 on your IBM, you should be able to install V12 on ...

Hi Stefano,
The quickest way to fix this error is to clear the entire LX_FLG table, however you would end up losing all of your Host Monitor history. Alternatively you could open the table in a Database editor and look for the record where XLGDAT is '00000020', and delete that record only.

HTH
Bark

Given the various tests that were done on other environments, I would be looking more at the LANSA side of things. Also, I downloaded and tested it OK and even on a 7.2 O/S environment.
As Dino suggested, perhaps there is a LANSA object that isn't the correct version (locked during an upgrade or ...

Don, can you debug anything (forms/functions/web pages)?
Is the service started? Is the default port 51251 available?
The only thing I can think of in relation to the error is the langmap.txt file so perhaps its corrupted. Looking at my own vl environment, this langmap.txt is in the x_ppp partition ...

another thing I just though of...
If this is VLF-Win, then its using superserver. perhaps at the same time that one of the users is having issues logging in, you could use the lcoecho on the command line to make a connection and if thats OK, then you could focus on the user and their connection to ...

These intermittent connection issues are a nightmare to troubleshoot.
I would focus on any patterns that you can establish.
for example, this line: these issues are mainly happening at newer compared to older ones
You should try to get definite statements...is it definitely only new users? All ...

Hi

I just ran it OK in V14.2
The things that spring to mind would be
- look for the XMDSERVER server module to see if its in the repo.
- if not, the required imports may not have been done from the partition init button/screen
- if you are using Windows11, you might be affected by the issues ...

Bit late replying to this but have you checked the possibility (dated 11 July) here https://lansa.com/support/v14news/index.html
It only affects Windows 11 PCs but debug is listed as a feature affected.

cheers
bark

Is the blanked out server in the error message your JIT application server or your backend (IBM I assume) D/A server?

As this is JIT deployment, you shouldn't have to manually uninstall and reinstall a new version as this defeats the purpose of JIT.
We use JIT deployment model in our organization ...

I was told recently that its shipping in an upcoming EPC. You could ask your local rep when that is.
HTH
bark

The reply from Rene would be applicable if this was a consistent issue. That is, you cannot use the HM every time you try. And there are other things you can check, like the TP joblogs on the IBM for any relevant messages.

However, if its OK sometimes and then fails randomly, it could be a network ...

If I understand this correctly...you are logged into the IDE with task TSYS and you say you created a new RP BB11 in the IDE (by copying an existing RP AB11 I assume). And then you attempt to check this in for the first time and you get the error that the object is not allocated to Task Identifier ...

I found this page
https://docs.lansa.com/15/en/lansa010/content/lansa/ugub_30090.htm
that has a note at the bottom of the page:
This facility is NOT to be used to load a LANSA File. Instead, export/import the definition you want to use into the new partition. Do not compile the file. Set the user's ...

I may not be understanding your setup correctly but why not get a VLN for your own PC? You apply your VLN to your own PC and in the development license studio, set your host server to your own PC as the host type (not local), refresh and press the button to use licenses server <your PC>.
Or perhaps ...

Since a smaller list is OK, it would suggest a limit. Check the trace files generated by JSM to see if you can see a truncated/corrupted email address. If its always truncated on the same one, then it would suggest a limit. If you then remove that one address and all addresses after it and its OK ...

I think what you are saying is that the end users still have the same version of MS Word but the TypeLibID on your own dev PC has changed so when you build and deploy, it fails for the users. Correct?

So what has changed on your PC since this was last OK? Did you get a new update of Office 2016 ...

Some clarity required...for example, what do you mean by missing?
Is it that when you use the USE command in an RDML function, it isn't available? Or that the program bi@p129 doesn't exist?
is it an existing function that is falling over at runtime or are you developing?
and what version is this?

I endorse JYoungs approach. There's no getting away from the fact that if you are new to LANSA, you will have to do some learning and the tutorials would be the best way of gaining understanding and confidence. Get on the latest version of VL and go straight to vl web, which is what VLF-One piggy ...

In my experience, the only way of making headway with random IDE crashes is to zip up the (enormous) dump file and get it sent to the devs. Often, they can pinpoint the issue and provide a fix. So, that would be my suggestion for your random crashes (but if you don't like to apply hotfixes, you ...

I recall that this was not working OK and was fixed in V14SP2 so if you're not on that version, that might be the reason.