04-09-2013 09:05 AM - edited 03-18-2019 12:54 AM
Friends,
i have a challenge in adding Tandberg Profile 52 dual to TMS and getting the Error "object reference not set to an instance of an object".
TMS is running on 13.X
Profiel is on Tc3.1.1
but we have the Same Combination of Devices added in TMS already.
Thanks
Solved! Go to Solution.
04-09-2013 10:54 AM
I have seen this stack trace once before, and that was when trying to add a system that had been pre-registered, and then deleted (not purged). Could you have a look and see if someone has tried to pre-register it to TMS?
And as Mahesh says: As soon as you have migrated to TMSPE, consider upgrading to TMS 14.1.1, where we have improved error handling when adding systems.
Regards,
Kjetil
04-09-2013 09:19 AM
Hi Thivakaran, Let us know the exact TMS software version installed in your environment. Can you also perform backup of the TMS SQL database [TMSNG folder] and try upgrading TMS version 14.1.1 from
Upgrading to latest TMS version will also help to perform upgrade of the database to fix if there is any unknown problems.
BR, Mahesh Adithiyha
04-09-2013 09:23 AM
Thanks Mahesh:
We are Using TMS 13.2.2 and performing upgrade to 14.X have dependency on the Provisioning Agent, as we are using legecy mode.
However, My concern is that we have similar systems operating with same version is already added in TMS.
04-09-2013 09:38 AM
Hi Thivakaran, The problem could also be that the Microsoft URLScan utility is running on the TMS server OS and blocking the requests.
If Microsoft URLScan is installed you will see in Windows Add/Remove programs. Can you uninstall and try re-adding the profile device in TMS.
BR, Mahesh Adithiyha
04-09-2013 10:29 AM
No MS URL Scan uttility is not running on our system.
04-09-2013 10:08 AM
Hi,
What is the full stack trace (if any) in the log-web file?
-Kjetil
04-09-2013 10:30 AM
the below is the Complete error message form the Log file.
"20:32:42,413 [39] ERROR ASP.tandberg_tms_ui_systemnavigator_folderpage_addsystem_ascx -
System.NullReferenceException: Object reference not set to an instance of an object.
at Tandberg.TMS.UI.SystemNavigator.FolderPage_AddSystem.AddSystem(String systemIPAddress, String systemIdFromList, String isdnLoc, String ipLoc, String timeLoc, Int64 folderId, IFolderService systemFolderService, Boolean addOnlySupportedSystems, Boolean addNonSNMPSystems, String snmpCommunityNames)"
04-09-2013 10:54 AM
I have seen this stack trace once before, and that was when trying to add a system that had been pre-registered, and then deleted (not purged). Could you have a look and see if someone has tried to pre-register it to TMS?
And as Mahesh says: As soon as you have migrated to TMSPE, consider upgrading to TMS 14.1.1, where we have improved error handling when adding systems.
Regards,
Kjetil
04-09-2013 11:06 AM
Excellent, the system was listed in the pre-register. Now i have purged and could able to add successfully.
Thanks Kjetil and Mahesh for hte Help
04-10-2013 01:29 AM
For future reference: I captured the problem as defect CSCug26342. The issue has been resolved in TMS 14.1.
-Kjetil
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