Over the past few days, some readers have encountered a well-known error code where the specified repository is invalid or unavailable 7.2. This problem can occur for several reasons. We will review them below.
Recommended: ASR Pro
I often had problems with version 7.3 of the Version Control Manager repository. None of my version control agents can contact him. When I try to view these VCA settings to register the creation VCRM, I get the message “The repository specified by email, servername.domainname.com, is invalid and unavailable”.
This appears to have started after HP upgraded the SIM card from version 7.2 to version 7.3 on top of that VCRM, though I can’t pinpoint exactly what happened at the time it all broke down. Show that it is used to work in a certain way in the past, as well as in a stationary state.
HP SIM 7.3 and VCRM 7.3 are definitely installed on the same R2 09 server. Ideally, all agent servers will communicate with HP SIM. I am using username/password authentication for VCA and have verified that the account has the administrative privileges that the VCRM server OS should have.
To solve these problems, I even built a brand new server based on HP SIM 7.3 and VCRM 7.3 (from scratch) from scratch, and in fact it has the same problem.
P.S.This topic has been moved from ITRC ProLiant servers (ML, DL, SL) to the HP Systems Insight Manager forum. – HP Forum Moderator
As a self-taught system administrator, I tend to learn by trial and error. And son, I’ve been fiddling around a bit lately, in the last few weeks I’ve been able to connect HP VCA to HP In vcrm :
It seemed that no matter what I knew about the information on the screen above, they would never see each other again. Credentials checked, permissions checked, but every time I filled the screen and clicked “Next”, I inevitably got a phone message “The specified repository, servername.domainname.com, is invalid or may not be available.” in a doomed downward spiral to restore my sanity.
So I was EXTREMELY excited when I found this gem on the HP Systems Insight Manager support forums in a post about upgrading from 18.104.22.168 to 22.214.171.124:
I received a response from an HP technician regarding HP VCA 126.96.36.199 working with HP VCRM 188.8.131.52
I didn’t fully answer the root cause, including this issue, but the form command is listed. I suspect this is usuallybut with the SSL encryption setting.
These commands solved the problem for me.
Try the following commands on a server running HP VCRM 184.108.40.206:
C:HPhpsmhbin>smhconfig.exe -Z ALL:!ADH:!EXPORT56:!EXPORT40:DES-CBC3-SHA:RC4-MD5:RC4-SHA:RC4+RSA:+HIGH:+ MEDIUM:-SSLv2:+EXP:LOW:!eNULL:!aNULL
For me, each of these commands solved the problem.
Unfortunately, I wasn’t sure if this would solve my problems, as I could never get VCA and VCRM to speak to begin with, so of course my problems weren’t due to other users’ approval. However, some of the most common connectivity issues mirrored those I’ve experienced. I applied most of the troubleshooting as a batch file (copy/paste the instructions in a text file to avoid greasy fingers, save as a .BAT file, command line output “both run as administrator”) and voila! So I can combine the two!
Unfortunately, I don’t show more details about exactly what the commands do or how they reach a solution, but it has been found that the problem is related on with the direct SSL encryption configuration, which apparently actually removed some of the ciphers that were predicted by VCRM 7.3.xx preventing communication between vca agents.
append -p path -d directory [-n [-l [-c] commitmsg]] [-u
Stores the extension of the new file in the working copy of the policy. Use the -p option to specify a specific file path (relative to all top-level directories in the policy) to create. Use the -d option to specify the content’s working directory. The -n option sends vibrations to the repository. If you use the -n option, you can use the -l option to get the commit log message. When individual users use -n without -l, the new command interactively prompts them for the current commit log message
[-c] [-r ]
If the address list does not exist, it will be created. If the selected catalogIf exists, the most recent content will be overwritten. By default, the latest full copy is retrieved; Use the specific -r option to check out a specific major revision. Can you specify a different version using the SVN DATE format, the HEAD keyword and usually the version numbers.
The date format specified without specifying the time is 00:00:00 by default.
The initial time that you can use to determine a particular version is the time you would normally commit that version. For example, if you fully committed revision 2 at 12:00:00 PM, you must specify a creation time of 12:00:01 AM or later to checkout revision 2. Example:
Speed up your computer today by downloading the software here.