11-16-2012 05:54 PM - edited 03-18-2019 12:08 AM
Hi, All
Just finished TMS installation on an Windows 2003 VM, I'm trying to enable Cisco TMS Agent by Administrative Tools > Configuration > General Settings, but after enable that, the TMS Agent Diagnostics shown "Unable to connect to remote server", so I checked the TMSAgentService in Windows services, I found it's not started, and could not be started even I manually start the service.
There isn't any other configurations on the TMS yet, it just finished the intial installation.
Solved! Go to Solution.
11-19-2012 08:28 AM
Hey
I had a quick glance in logs provided and seems there is few issues there:
Result Code: 68 (ÌõÄ¿ÒÑ´æÔÚ)
Additional Information: The entry dc=provisioning cannot be added because an entry with that name already exists
When you uninstalling TMS you should remove OpenDS as well. So now I would do following:
Uninstall tms management suite (control panel, add remove programs) and restart pc
Uninstall opends C:\Program Files\TANDBERG\TMS\Provisioning\OpenDS-2.0
-uninstall.bat
-select all folders to remove
Manually delete folder C:\Program Files\TANDBERG\TMS\Provisioning\OpenDS-2.0
Install tms again.
Please try those steps. On side notes I would stick to Magnus recommendation and move to TMSPE, so you will not have to deal with issues like that
Cheers
Rafal
11-19-2012 05:16 PM
Hi, Rafal
Actually the TMS is built from an fresh windows 2003, instead of uninstall action and install again, so I really don't know what's problem there.
And I do ack you ideal of go TMSPE idea, but the issue I faced is really strange, I did installed .net framework 4.0 before TMS installation, why the log show up the .net is not found?
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide