This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Version Manager checkout problem 8.4.0

I have Version Manager 8.4.0 installed on a Windows 10 SHB (Secure Host Baseline) laptop. I am attempting to checkout (Check out vice Get just to clarify) source objects directly from the GUI (from the PVCS server) onto my laptop. The objects copy to my laptop but the version manager sticks with the 'Checking out...' modal window. The process does create the semaphore for the object checked out but the process never finishes.
Any ideas would be much appreciated.
  • 0  
    Hello Mark,

    Some questions:
    [list=1]
    • Is there any chance an Event Trigger is defined for this project (database)?
    • If you perform a non-locking Get, does that complete?
    • If you perform a checkout to a different location, like your temp folder does that complete?
    • Is the behavior file specific? If not, is it project specific?

    Thanks in advance for clarifying.

    Kind regards,

    - Richard.
  • 0
    Thank you for the response Richard.
    1. There is no event trigger defined on this project.
    2. I can indeed perform a non locking get.
    3. I have attempted to checkout to various locations and folders and get the same behavior.
    4. This behavior is not specific to a specific file or project.
    By the way, I am trying to checkout via Version Manager directly because we cannot connect our PowerBuilder client to the project. We are using PB 12.5.1. This manifested itself after we moved to Windows 10 SHB.
    So, I am completely unable to successfully checkout any objects out from PVCS.
    Any help and / or suggestions would very much appreciated.
    Thanks again.
  • 0  
    Hello Mark,

    I don't know what changes the "SHB" edition of Windows 10 makes, but if it breaks the SCC connection from PB to VM then it's arguably secured a bit too tight, or needs configuration changes.

    Instead of checking out a file, what happens when you attempt to lock it? Similar lockup?

    Is there any chance you have Source Bridge installed? Look under the Tools menu and see if SourceBridge is greyed out or not. If it is not greyed out, select it and ensure the connection info is valid. While performing a checkout or lock, check if there's a ttsourcebridge icon on your Windows taskbar and press it to see if there's info.

    If SourceBridge is installed and not working it might be for the same reasons PB stopped working with VM after switching to Windows 10 SHB, given there's overlap in how the two communicate with VM. If so, try uninstalling SourceBridge from your PC and see if that solves the problem. If it does, and you need to use SourceBridge, a deep dive into the SHB features / limitations seems in order.

    Hope this helps!

    Kind regards,

    - Richard.
  • 0
    Hello Richard,
    Thanks again for the response.

    We do not install Source Bridge.

    Okay, so I get the same response when I attempt a lock. Also, we do not install Source Bridge.

    The crux of the issue seems to be finishing the lock. When I try a checkout, the affected file does indeed get copied to the folder I point to but the semaphore does not get deleted. At this point process has to be manually stopped via task manager. I'm assuming the sem gets deleted after the checkout/lock is finished right?

    Ideally I would prefer to have the PB / VM link fixed rather than focus on checking out directly from VM (as the later was a stop gap approach because of the PB / VM link is not working).

    By the way are now using version 8.4.6.0 build 037 which I'm thinking is not Win10 compatible. However, that is what I am stuck with for the time being. We are also dealing with HBSS/SHB constraints which may be an issue as well.

    I'm starting to believe you are correct in that we are secured a bit too tight and need some configuration loosening.

    Thanks again for you attention.
  • 0  
    Hello Mike,

    It's probably best to focus on the Lock operation, as that appears to be the step that is failing. Are you using VM File Server at all? (Click the File Server Status icon in the bottom-left corner of the GUI and see what it says.)

    Using VM 8.4.6 may have something to do with it, but that would be easily tested if you can temporarily install a newer VM release (even if it's not the corporate standard).

    Beyond that one more test: open the SampleDB Project Database (C:\ProgramData\Serena\VM\SampleDB) and attempt a checkout operation using one of the files in there. Same problem? If not, we could be looking at file system permission limitations on your production PDB, especially if the VM File Server is not being used.

    Kind regards,

    - Richard.
  • 0
    Hello again Richard,

    I suspect VM 8.4.6 is not the culprit in this case because we have several other developers that can check out directly from VM. This is localized to my work station.

    Also, we don't install the SampleDB Project Database (not sure why...it's a silent install and I never see that option). And, we don't use a file server.

    One more thing to add: Other developers can use my VM account from their machine and successfully perform check outs. However, on my machine I cannot check out using account logins that work on other machines...if that makes sense.

    It does appear the issue is with my work station....

    Any other ideas are most gratefully appreciated.

    -Mark
  • 0  
    Hi Mark,

    Could be a permissions thing, could be AntiVirus scanner related.

    It's probably best to create a support case at this time so you can submit the output of running the knowledgebase.serena.com/.../index