Object won't compile

alphabeta13 · Post by **alphabeta13** » Fri Mar 20, 2020 7:53 am

I am new to Lansa and I am taking over a project from someone that's no longer with the company.

There's an object that runs okay, but when I check the source there's an error message which is causing it not to compile.
I know it's probably because the source that's in our system does not match the object.

The error message is:
Component #cmzGeocodedMap is remotely located. It needs to be checked out before this component can be built.

The object is to show the map of location based on an address/postal code.

Where can I check it from? and how to do it?

Thanks in advance.

Regards,
Taufik

JamesDuignan · Post by **JamesDuignan** » Fri Mar 20, 2020 8:31 am

Hi Taufik,

I believe this message is because you do not have the object "cmzGeocodedMap" checked out.

If you look for the component in the repository, it should appear greyed out. Meaning there is a copy on the master, but not locally.

Right-click cmzGeocodedMap and select checkout.

Regards,
James

alphabeta13 · Post by **alphabeta13** » Sat Mar 21, 2020 7:14 am

James:

Thanks for the response. I found the object under widgets group.
However I could not check it out and getting some error messages:

- Object could not be processed
- Task Tracking has restricted work that can be performed on object
- The object is lock to Task xxxx by PC xxxx with description ( )

I tried checking it out as read-only, compiled the object successfully, but then receiving the same messages when checking it back in.

Any ideas on how to resolve or get around these messages?

Regards,
Taufik

René Houba · Post by **René Houba** » Mon Mar 23, 2020 9:01 pm

Hi Taufik,

When you start your VL development environment in Windows, you also select a Task. Let's say TASKA.

The error message you get is:
- The object is lock to Task xxxx by PC xxxx with description ( )

So for example the error message says:
The object is lock to Task TASKB by PC xxxxx ......

What is the exact message?

What you can do for example is start the VL Windows environment with TASKB.

Does that solve your problem?

Kind regards,
René

atostaine · Post by **atostaine** » Tue Mar 24, 2020 1:51 am

alphabeta13 wrote: Sat Mar 21, 2020 7:14 am
I tried checking it out as read-only, compiled the object successfully, but then receiving the same messages when checking it back in.

Any ideas on how to resolve or get around these messages?

Regards,
Taufik

If you checked it out as read only you don't need to/can't check it in.

alphabeta13 · Post by **alphabeta13** » Tue Mar 24, 2020 2:15 am

René:

I have verified that I was using the same task: TDEM0001.

Art:

The issue is I am getting error messages when checking out normally.

Thanks,
Taufik

atostaine · Post by **atostaine** » Tue Mar 24, 2020 5:34 am

If you are sure that the other user checked in all of his changes, I would close that task and create a new one.

In green screen housekeeping, work with tasks, just change the status of the task to CLS, press enter, then FIN.

Create another task, and refresh your PC tasks and then use that new task to check it out.

caseywhite · Post by **caseywhite** » Tue Mar 24, 2020 5:41 am

It could be that the object is locked to the same task but to a different PC.

Instead of closing the whole task you could just drop the task lock for that one object. To do that in green screen:
1. Housekeeping
2. Work with Tasks
3. Find your task and 5 r
4. 5 to Review Task History
5. Find the object and put a 9 next to it and press enter to change the task
6. Just leave everything blank and press enter

Now the object is not locked to the task. So you can check the object out for read only which will refresh the task lock in the IDE. Now check it out to your task.

atostaine · Post by **atostaine** » Tue Mar 24, 2020 6:23 am

That didn’t work for me so I went nuclear

Sounds like OP is a one man shop as long as everything is checked in go crazy!

alphabeta13 · Post by **alphabeta13** » Tue Mar 24, 2020 10:41 pm

Thank you all for your responses.

I have reached out to Lansa and was advised to close the task and then check the objects out using a new task.
It worked.

Regards,
Taufik

atostaine · Post by **atostaine** » Wed Mar 25, 2020 12:35 am

alphabeta13 wrote: Tue Mar 24, 2020 10:41 pm Thank you all for your responses.

I have reached out to Lansa and was advised to close the task and then check the objects out using a new task.
It worked.

Regards,
Taufik

Sounds familiar

René Houba · Post by **René Houba** » Thu Mar 26, 2020 12:27 am

Hi Taufik,

Attached a document I created some time ago for one of our customers. It explains the PC name locking a little bit more.

Kind regards,
René

soa · Post by **soa** » Fri Mar 27, 2020 4:49 pm

Just to get a start - you can always try logging into the IDE as the partition security officer which will ignore such considerations.

Visual LANSA Forum