Unable to use APC website for updating DDF files

[DCIM_Support]

I'm managing multiple DCE installations (physical and virtual) and I'm having issues to update DDF files using the APC website method. When I try to update I'm getting a NULLPointer execption in the client. Please see screenshot. There is no entry created in the server log and the information provided in the error dialog is very minimal.

Since we had to manually allow unauthorized access to the domain "updates.apc.com" in our proxy servers in order to get the firmware updates working, I'm expecting a similair issue for the DDF update process. Which domain and communication protocol is used for this update process ? Is this server side or client side ?

(CID:137105613)

[DCIM_Support]

Dear Michel Gerritse,

From your question:

I'm managing multiple DCE installations (physical and virtual) and I'm having issues to update DDF files using the APC website method. When I try to update I'm getting a NULLPointer execption in the client. Please see screenshot.

I do not recommend using this feature at all. The reason is irrelevant (obsolete) versions of DDF-files, that may be located there. I have already paid attention =SE= to this several times (see for example ). Perhaps in the future =SE= it will finish this function to a working state and will keep the list of available DDF-files up to date.

...Which domain and communication protocol is used for this update process ? Is this server side or client side ?

Two years ago I already studied this topic in my post . As a result, changes were made to the FA293307 "Data Center Expert | Firmware updates are not available within the Firmware Update window after che..., for example:

Resolution:

Data Center Expert reaches out to updates.apc.com to obtain the latest available firmware. Using HTTPS to navigate to the URL (http and then FTP on older versions) to download the catalog file.

Therefore, to update the DDF-files you need:

I.e., successful execute update DDF files from the APC website requires to open outgoing connection from the DCE client PC to production update URL: https://updates.apc.com:443/. Notice: only one HTTPS (443) protocol, but not HTTP and not FTP.

...and, for device firmware updates you need:

And, I solved the last problem quickly, as I understood, that for successful execute check Firmware Updates it is required to open outgoing connection from the DCE server to production update URL: https://updates.apc.com:443/. And practically only it is already enough for successful execute check Firmware Updates from the DCE client.

Hope this helps you.

With respect.

(CID:137105642)

[DCIM_Support]

Dear Michel Gerritse,

Tell us please, did you solve this problem or not?

With respect.

(CID:137109224)

[DCIM_Support]

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