No information In Device center

Answered Question
Dec 28th, 2009

We have LMS3.2, CS3.3, RME4.3.1and  fully Integrated with ACS, Some devices are appared in device center without any information but they managed corrctly in RME.

Invetory poll job is succeed and  Sync Archive job is /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif"; mso-fareast-font-family:"Times New Roman";} succeed   for those devices.

Please see attached files

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 6 years 7 months ago

This means that there is some devices in the PIDM table which already are mapped to RME 4.3.1.  You need to get more tactical.  If you feel comfortable going through the table to change only the entries mapped to RME 4.3 which do not have a corresponding 4.3.1 entry, you can do that.  Else, talk to your TAC engineer again to get the SQL queries to do this.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
albatli1977 Tue, 05/11/2010 - 04:45

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;} I opened TAC and the problem is solved but now the problem back again for certain of devices as attached ... and when apply the SQL I get :

SQL Statement:

UPDATE PIDM_app_device_map SET app_version='4.3.1' WHERE app_name='RME' 

and app_hostname='sec5-12'




*** Error ***
Primary key for table 'PIDM_app_device_map' is not  unique (DBD: execute failed)

Attachment: 
Correct Answer
Joe Clarke Tue, 05/11/2010 - 21:24

This means that there is some devices in the PIDM table which already are mapped to RME 4.3.1.  You need to get more tactical.  If you feel comfortable going through the table to change only the entries mapped to RME 4.3 which do not have a corresponding 4.3.1 entry, you can do that.  Else, talk to your TAC engineer again to get the SQL queries to do this.

Actions

This Discussion

Related Content