FRED database problems

[amrsherif]

Hello,

We are using EViews 12, the Nov 4 2022 build. We have been having issues connecting to FRED since Friday. I am attaching a screenshot. This is on our server version. The database works fine on the desktop (or standalone) versions of EViews. Not sure if this is a licensing issue or something else.
I know there have been some issues in the past with FRED, that were fixed with patches, but i am not sure about this one.

Sorry i was not sure if this question belongs in programing or licensing.

[EViews Jason]

Nothing has changed with the code pertaining to FRED in quite some time. The fact that it used to work and that we cannot replicate the issue on our end would imply an issue with the FRED servers.

Rather than performing a query, can you try running the following 2 commands in EViews:

Code: Select all

create u 10
fetch gdp

Did this work?

If it still fails with the COM component error, try entering the regcom command into EViews. Then press Yes(all). A dialog should appear after roughly 20 secs indicating all registration were successful. Next restart EViews and try fetching again. Did this work?

[amrsherif]

Thanks for this. Both querying the DB and fetching from it fail.
I tried regcom and restarted but still getting the same COM error.

I may have misunderstood, but if there is an issue with the FRED servers, as you implied is a possibility, wouldn't fetching fail on our PCs as well (the standalone versions)?

[amrsherif]

Another potentially important clue is that when i try to check for updates i get this error (attached):

Unable to connect to http://wwww.eviews.com/
(null)(12175)

[amrsherif]

Yet i can fetch from other databases like the IMF SDMX database. I can also connec tto EViews.ocm in the browser.
Very puzzling

[EViews Gareth]

Possibly a network firewall type issue?

[amrsherif]

According to our IT department, there are no logs that indicate that this could be a firewall issue.
However, if you do not know of anyone else having this issue (using the server licnese) then most likely, the problem is on our end.
Please let me know if you see/hear of any others with the same problem.