- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Status cannot be calculated because a Version ...
Server Management - Systems Insight Manager
1754228
Members
3504
Online
108812
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2011 10:00 PM
03-07-2011 10:00 PM
Status cannot be calculated because a Version Control Repository Manager has not been named.
I have Version Control Repository Manager 6.2.1.861 installed.
When I restart the VCRM service, it start to validate repository as expected and during this time version control agents can connect to repository and tell me that repository is busy.
But when the repository validation is complete, none of the clients can no longer connect to it. They give following error
"Status cannot be calculated because a Version Control Repository Manager has not been named. Click on change settings to specify a Version Control Repository Manager."
When I check VCA logs they say
Connection: close
Content-Length: 0
Content-Type: text/plain
Date: Mon, 07 Mar 2011 13:00:22 GMT
Server: CompaqHTTPServer/9.9 HP System Management Homepage
Set-Cookie: Compaq-HMMD=0003-e1c690ca-ccac-e447-b4bc-e64f383d033e-1299502822023838; path=/; Secure
Status: 500
VCRM log says
Failed request:
The specified module could not be found.
When I restart the VCRM service, it start to validate repository as expected and during this time version control agents can connect to repository and tell me that repository is busy.
But when the repository validation is complete, none of the clients can no longer connect to it. They give following error
"Status cannot be calculated because a Version Control Repository Manager has not been named. Click on change settings to specify a Version Control Repository Manager."
When I check VCA logs they say
Connection: close
Content-Length: 0
Content-Type: text/plain
Date: Mon, 07 Mar 2011 13:00:22 GMT
Server: CompaqHTTPServer/9.9 HP System Management Homepage
Set-Cookie: Compaq-HMMD=0003-e1c690ca-ccac-e447-b4bc-e64f383d033e-1299502822023838; path=/; Secure
Status: 500
VCRM log says
Failed request:
The specified module could not be found.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2011 01:20 AM
04-14-2011 01:20 AM
Re: Status cannot be calculated because a Version Control Repository Manager has not been named.
Hi
Had the same problem. Solved it by updating the "System Management Homepage" (SMH) to the latest version on the server, where the "Version Control Repository Manager" was installed.
Best regards
bent Buhl
Had the same problem. Solved it by updating the "System Management Homepage" (SMH) to the latest version on the server, where the "Version Control Repository Manager" was installed.
Best regards
bent Buhl
Best regards
Bent Buhl
Decentral teknik
JN Data A/S • Frichsvej 18 • 8600 Silkeborg
Telefon 63 63 63 63/ Fax 63 63 63 64
www.jndata.dk
Bent Buhl
Decentral teknik
JN Data A/S • Frichsvej 18 • 8600 Silkeborg
Telefon 63 63 63 63/ Fax 63 63 63 64
www.jndata.dk
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP