sdeevers
Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Faulting module name: MSVCP140.dll
Hey All, this is a little weird, but all of the sudden R-API 3.53.0 is not loading my projects upon startup today. From the event viewer, I was able to glean the following and thought I'd ask for maybe some insight Faulting application name: ReadyAPI.exe, version: 3.53.0.1, time stamp: 0x6377c6fe Faulting module name: MSVCP140.dll, version: 14.32.31332.0, time stamp: 0x8b64702c Exception code: 0xc0000005 Fault offset: 0x00000000000132f8 Faulting process id: 0x3e74 I'm hoping someone can help me out StuRe: Fixed User licenses cannot be used on virtual machines or with docker containers
ihorstep - Unfortunately, we have been put on hold till our IT department can determine the "best" user ID we should use for that VM instance (the associated email will need to be public facing to receive the link to create the SB License server account). Once IT lets us know, we will update our CI/CD plans to use the associated "accessKey" information and let you know if all is fine."cannot open git-upload-pack" although Git account in place
Wondering if anyone has a possible solution for an issue we are seeing. From R-API, a user has successfully established a connection for "Git" in the preferences with their credentials. When they go to "Test Connection", and enter a valid repository, they receive an error, "cannot open git-upload-pack". Since they are unable to get a connection to a repository, they cannot pull down updates to the associated project or run specific test steps which requires a Git credential.Re: Fixed User licenses cannot be used on virtual machines or with docker containers
If you are moving to the ID based license, this link explains how to use the accessKey in the testrunner script executed on the VM. We are going to give this a shot later today and will let you know if that is a viable option.Re: Fixed User licenses cannot be used on virtual machines or with docker containers
We are potentially facing the same dilemma. We are currently using a fixed license on our VM which runs our daily CI/CD tests without any issues. I am in the process of evaluating an upgrade to a current release, but do not want to jeopardize losing the benefit of those tests running daily if we must / be required to have a floating license for a VM.SmartBear License Manager question
Does anyone know how long your license will last before it expires when you are using the "SmartBear License Manager"? The license associated is good through 3/31/2026 ... This was not a "good experience" as we had tests running when that error generated and when they selected "Yes", the tests immediately stopped. I guess we should not select anything when that message appears until after the tests have completed.
