- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 08:24 AM
Hi
I've just installed LMS 4.1 in my demo lab. Everything is working fine except for the Topology maps. When I click on the topolgy from configuration
I get
I've tried doing what its asked a number of times but with no success and was wondering if anyone else has had this problem and know the fix.
I'm running windows 7 with Java version 1.6.0_26 . Also this is the virtal appliance installation of Cisco LMS 4.1.
Regards
Solved! Go to Solution.
- Labels:
-
Network Management
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 11:35 AM
Your problem looks similar to one I have seen with incompatible Java versions. I suggest two things to check it out:
1. Launch Topology directly when logging in from the server desktop itself (via RDP is fine). Does it work there? If so, the issue is client-based.
2. Uninstall Java compeltely on the client. Then launch LMS in a browser. When you navigate to Topology tools you should be redirected to the CiscoWorks server's own Java distribution which is packaged to be the precise version (1.6.0_24) that it prefers. Download and install that version and check if the problem is fixed.
One can work around the Java issues in some cases but it's ugly. This, combined with Sun / Oracle's predeliction to want to upgrade Java to the latest version automatically makes this one of the trickier tools in the LMS toolbag to use consistently from diverse remote clients.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2011 01:17 AM
It is also important that it is possible to write in the program files\java\lib\endorsed directory of the client.
During the situation you show above it tries to write some jar files in that directory.
If you are sufficiently admininstrator on your machine this is possible. Anyway if you open a java console and work your way through the errors you see the write fail in that directory.
Cheers,
Michel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 04:51 AM
That is in fact the "normal" situation.
I have no idea why cisco has decided to give this process a different status. Historical stuff surely
Cheers,
Michel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2011 12:04 AM
Hi Gavin,
I had the same problem on my LAB server.
You can edit your hosts file in C:\Windows\System32\drivers\etc on your local machine.
In this file you add the ip and then the name of the server on which lms is installed.
Example
196.xxx.xxx.xxx GavinsLMS (Name of server)
Perhaps you can try this as it solved my issue, however i am not connecting to any DNS servers.
Bezinga
Jaques
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2011 11:35 AM
Your problem looks similar to one I have seen with incompatible Java versions. I suggest two things to check it out:
1. Launch Topology directly when logging in from the server desktop itself (via RDP is fine). Does it work there? If so, the issue is client-based.
2. Uninstall Java compeltely on the client. Then launch LMS in a browser. When you navigate to Topology tools you should be redirected to the CiscoWorks server's own Java distribution which is packaged to be the precise version (1.6.0_24) that it prefers. Download and install that version and check if the problem is fixed.
One can work around the Java issues in some cases but it's ugly. This, combined with Sun / Oracle's predeliction to want to upgrade Java to the latest version automatically makes this one of the trickier tools in the LMS toolbag to use consistently from diverse remote clients.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2011 01:17 AM
It is also important that it is possible to write in the program files\java\lib\endorsed directory of the client.
During the situation you show above it tries to write some jar files in that directory.
If you are sufficiently admininstrator on your machine this is possible. Anyway if you open a java console and work your way through the errors you see the write fail in that directory.
Cheers,
Michel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 03:54 AM
I have now fixed this issue by giving myself full right to my machine and copying all the relavent files. So thanks you all for you help.
But it still doesn't work - saying that I've got a DNS issue or an issue with my ANIServer
My ANIServer which says it is running with a busy flasg. Have tried to stop/start and reboot it but no luck.
Any suggestions would be more than welcome.
Regards
Gavin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2011 04:51 AM
That is in fact the "normal" situation.
I have no idea why cisco has decided to give this process a different status. Historical stuff surely
Cheers,
Michel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2011 12:04 AM
Hi Gavin,
I had the same problem on my LAB server.
You can edit your hosts file in C:\Windows\System32\drivers\etc on your local machine.
In this file you add the ip and then the name of the server on which lms is installed.
Example
196.xxx.xxx.xxx GavinsLMS (Name of server)
Perhaps you can try this as it solved my issue, however i am not connecting to any DNS servers.
Bezinga
Jaques
