PowerBuider target locked

[awheeler]

I am using Agent Git with PowerBuilder 12 and the target file has recently become locked. I cannot check it out again to add new pbls to the project. I know I checked the target out several months ago and checked it back in. Now I can no longer check the target out.

[jussij]

You should be able to fix this by deleting the Agent Git lock file.

So could you try the following:

1. Backup your current project folder just in case something goes wrong.
2. Make sure PowerBuilder is not running.
3. Find the .git folder found in the root of the project folder. Note: This is a hidden folder so you may need to adjust Windows Explorer so that it displays this folder.
4. Inside that .git folder find and delete the following Agent Git lock file:

   Code: Select all

   agentgit.db

5. Start Power Builder and all Agent Git locks will now be gone.

If the checkout still fails could you then do the following:

1. Make sure PowerBuilder is not running.
2. Open the Agent Git configuration utility and turn on the debug option.
3. Use the View Debug Log File button to open the log file, taking note of its location (that will be shown on the last line of the log file).
4. Trim the log file down to nothing.
5. Start Power Builder and try to do the check-out.
6. Go back to the log file and send it though as an e-mail attachment, or alternatively add it as a file attachment in reply to this post.

Cheers Jussi

[awheeler]

Deleting the database file did not help. I have created the debug log file. What email do I send the log file to?

[jussij]

Inside the jussij user profile found at the top of this post contains a send e-mail option. Just click on the jussij link.

You could also try the following:

1. Again make sure you backup the project folder just in case.
2. If not already installed, install Tortoise Git: https://tortoisegit.net/
3. With PowerBuilder not running, go to the project folder and do a Commit as shown in the image below:

   

   commit-folder.png (43.73 KiB) Viewed 4086 times

   In the image above, Tortoise Git is being used to commit (i.e. check in) all changes made in the GitTest folder. In your case this will be the PowerBuilder project folder.
4. Now start PowerBuilder and do an undo checkout inside of the IDE. But because all changes from this folder were committed in the step above, this undo checkout should mean not changes will be lost.

IMPORTANT: Obviously step 4 has the potential to cause the loss of changes if things are not done correctly or if something unexpected happens, hence the need for the good backup.

Even if this latest suggestion works, could you still send through the log file as it would be interesting to learn why the other suggestion failed to work and what is actually going wrong.

Jussi

[awheeler]

Hi Jussi,

I see no option for "send email" in your profile. Is there a setting I need to add to my profile to see email addresses?

I do use Tortoise Git and I attempted the commit as suggested but, as I have no objects checked out, I get the message "No files were changed or added since the last commit".

I did try modifying the target file using Notepad and was able to add two pbls to the library. I went in to PowerBuilder and they were there along with the objects I had created in these pbls. Is it possible to now add these pbs to source and then check in them into the repo using Agent Git, then do as you suggest and commit the target file in Tortoise Git?

Your thoughts?

[jussij]

Your thoughts?

It is very difficult to tell what is going wrong as I have so little information to go on.

I have sent you an e-mail. Please send though the log file using that e-mail address.

Is it possible to now add these pbs to source and then check in them into the repo using Agent Git, then do as you suggest and commit the target file in Tortoise Git?

The Agent Git check-in action is exactly the same as the commit found in Tortoise Git.

You can see this by doing the following:

1. Check out a file in PowerBuilder.
2. Make a change in PowerBuilder and save the changes.
3. Using the Tortoise Git Diff menu to see these differences in that file:

   

   git-diff.png (204.64 KiB) Viewed 4067 times

4. Check the file in using PowerBuilder and now there will be no more differences.

Cheers Jussi

[jussij]

Unfortunately the log file attachment that was sent through did not highlight any errors in the Agent Git plug-in, instead it appeared to be working as expected.

For an understanding of how the Agent Git MS-SCCI plug-in works consider the following description: viewtopic.php?t=8368

Jussi