startup.aliases file corrupted on power loss on cFP 2220

[GeneHancock]

We have had an issues several times with our cFP 2220 where the startup.aliases file is being corrupted presumably on shutdown and startup.  I was unable to grab the corrupted file but I believe that the system name was lost as it would explain my symptoms which were that my application which loads the addresses for the application does so from a file.  the system had been delivered for service and on initial boot up the application ran fine except none of the IO was available.  I see the exact same symptoms when I there is an error in my address file that provides an incorrect address to a module that is not at that slot. I do know it was this file as I saw it's size was different than the one I built so I replaced it via ftp and rebooted and all is well now

Is there a problem with he 2220 having power removed at any time?  Is there reason why this file would get corrupted?

[Aldo_A]

Hi Gene,

An applications engineer has replied to your question via email. Let me know if you have additional concerns. Thanks!

[Matthew_Williams]

What was the resolution?  We have quite a few FieldPoint controllers deployed and I would like to know if there is an issue we should be aware of.

Thanks.

Matt

[Aldo_A]

Hi Matthew,

One of our AEs responded to your question and followed up with you if the issue was reproducible or just a one-time occurrence. As he stated, the startup.aliases files contains information on where to look for shared variables. The file is not being written to while deployed so there shouldn't be a problem with turning off the power. If the issue is reproducible, please post the details of your application to troubleshoot the issue. Thanks!

[Matthew_Williams]

HI Aldo.  I wasn't the original poster, just an interested passer-by, curious about the potential for a problem with our installed base.  Were the .aliases files being corrupted once the units were deployed and operational?

Matt

[Aldo_A]

Hi Matthew,

I apologize for the mix-up, the issue was that the startup.aliases was being corrupted when the cFP 2220 was powered down. When the system was in the initial boot up stage, it was discovered that the startup.aliases was corrupted. The units were being deployed and were operational. However, it seems that it was just a one-time occurance.

[Matthew_Williams]

Thanks Aldo.

Matt