Server Management - Systems Insight Manager
1833883 Members
2407 Online
110063 Solutions
New Discussion

Invalid or not reachable version control repository manager

 
Erhard Pütz
Advisor

Invalid or not reachable version control repository manager

Hello,

I tried to install the System Management Homepage (7.30) on a HP PC along with the latest version of Repository Manager. Then I populated the repository from an existing one.

I created a local account to be used in the client's agent config.

Then I set up a server's Version Control Agent to access that PC, but it said:

The specified repository is invalid or not reachable.

I could however ping the pc, sesolve the name and even access shares.

What does a Version Control Agent need to communicate with a VCRM (http, other ports, snmp or what else)?

Regards, Erhard
4 REPLIES 4

Re: Invalid or not reachable version control repository manager

Hi Erhard,

i think a snmp communication is good to start of with. I guess you need a lokal account on your SIM Server. Then you configure your VCA to use this account. What Protokoll VCA is using i dont know really.

Mike
TechGuru
Trusted Contributor

Re: Invalid or not reachable version control repository manager

You can try Repository IP for connect from VCA. VCA use HTTP for communicating to VCRM.
Erhard Pütz
Advisor

Re: Invalid or not reachable version control repository manager

Hi Michael, Logapriyan,

when I tested things that day, I tried both computer name and IP address and neither worked.

However when I tried things again today to implement your hints, believe it or not - it worked at once.

On the VCRM there is no SNMP installed.

Checking the settings again, I guess I put the account used by the VCA to authenticate against the VCRM in the local administrators group on the VCRM host.

I just counterchecked things removing the group and I got the error I got before.

The local administrators group is always member of the Systems Management Homepage (SMH) administrators group - that's probably why it works now.

I checked further:

One cannot assign a local windows account to the SMH's security groups.

One can only assign local windows groups to the SMH's security groups.

The account used by the VCA needs to be member of a local windows group which is at least member of the SMH's Operator group.

The Version Control User Guide has got one and a quarter pages about security and I do not see it mentions things.

Regards, Erhard
Erhard Pütz
Advisor

Re: Invalid or not reachable version control repository manager

I found the solution myself (see above).

Regards, Erhard