Cant connect visual vectors to server 1

[RFLundgren]

Hi there, have just been trying to connect visual vectors to the CMS server with no success at all. Continue to get the error cannot find server yet I can ping it.

I have also done a search here and tried all of the suggestions that people have put forward and still none have worked.

We are running CMS Rel 13, VV rel 13.1 so if anyone has any suggestions it would be most appreciated.

Cheers

Richard

 

[qz01gs]

You might want to look at PCN 1567? There is an issue with V13 CMS what base load are you on. The PCN covers:

The following CMS fixes have been addressed with this PCN:
• The SSH spatches with issues have been removed
• Support for R13 Visual Vectors Client software
• Solaris patch to support DST (Daylight Savings Time) change
• Support for Tivoli 5.3 client and server for LAN backup
• Support for new Netra 210 platform
• Includes new Daylight Savings Time Solaris patch
• Support for CM 3.1
• Support for Survivable CMS
• Full support of 2000 vector administration
• Backup script no longer excludes directories beginning w/n
• Backup script no longer fails due to UID/GID > 65535
• Negative values in real time VDN reports have been addressed
• When the link goes down and agents are logged in, CMS will recognize all agents when the link is back up.
• Up to 400 CMS Supervisors can be simultaneously logged in (previously 252 was the maximum).
• Customers with large amounts of data (~25GB) will see greater performance with their CMS Maintenance backups.
• Performance enhancements have been incorporated which especially affect larger systems.

 

[Stinney]

I had this issue and drove myself nuts with it.

First, have you verified that AOM has been started and that VV is actually running on the server?

If both are running, there is a file that can get corrupted on the CMS that controls the TCP/IP Sockets the VV needs

This can been fixed by removing all files in the following directory:

/opt/OrbixMT/config/Repositories/NamesRep

I can't remember if we had to reboot afterwards or not, but it fixed the problem. You can check out this information in the following thread690-1172944


- Stinney

Favorite all too common vendor response: "We've never seen this issue before.