one device shows "contains no device alarms"

[DCIM_Support]

DCE 7.5.0

I have one device, a Netbotz rack Appliance 250, that for my account, the device Alarm Configuration reports that it "contains no device alarms".

At least two other accounts I checked both see the correct information when I logon with the same computer.

I have both device and server administrators rights, the same as the other accounts that work.

Hovering the pointer over the device shows 1 threshold and 92 device alarms

How do I fix it?

(CID:143760134)

[DCIM_Support]

Hi Mark, thanks for posting - and sorry to leave you hanging.

Are you still seeing this issue?

Thanks,

Stine

(CID:144313680)

[DCIM_Support]

Mark,

This may be an issue with the local configuration files on your computer for the desktop client.  Please try to clear your local configuration files, which contain client configuration, such as: DCE IP list, column configurations, language settings, etc.

NOTE: As an alternative, you can try to login using your user on another system that has the desktop client installed.

Delete the following directory on your computer: C:\Users\\.isxc

NOTE: You can instead cut and paste the directory to a different location on your computer and if removing the directory does not correct the issue, you can delete the new .isxc folder and restore the original.

Once the file is no longer available, the client will generate a new one when it is started.  You can then login and test to see if the issue is still present.

Kind Regards,

Cory

(CID:144313888)

[DCIM_Support]

The problem seems to show up intermittently on different devices.

Exiting and restarting the client doesn't make it go away - I have tried up to 5 times, but eventually it does, or just moves to a different device..

Currently on v7.5.0 with an upgrade to v7.6 planned.

 It didn't show up with a different logon on the same computer.

I'll try the user folder removal suggestion and see if the problem shows up again.

(CID:144868342)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.