Excel STOCKHISTORY() function repeatedly encounters #CONNECT! error.

Anonymous
2024-08-19T21:41:33+00:00

Hi Team,

I spent over 2 hours troubleshooting this issue with an advocate in Office support (7*********0). He worked very hard to understand and resolve the issue.

We tried numerous resets: the network, uninstalling and reinstalling office, updating office, powering down, and restarting the computer. Nothing helped.

The issue occurs in approximately 20% of the values for a list of stocks and one date. It occurs in a similar percentage of dates for a single stock.

Ultimately we discovered that creating a new spreadsheet and typing or pasting the formula into an empty cell will not result in the #CONNECT! error. But this does not work in previously created spreadsheets.

Please check on this as soon as possible. This is a critical function for applying Excel to stock research.

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

54 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-24T06:22:35+00:00

    Hi Scott and everyone who has replied in this thread:

    Thank you all for your active participation in this thread. Without our collective effort, I doubt Microsoft would have addressed this issue so quickly. All of your responses have helped strengthen and grow this community.

    If anyone encounters further issues in the future, please feel free to ask questions here in the community. Our support team will do its best to help resolve problems, whether they originate from Microsoft development teams or other external data providers. I will also gather your feedback to push them to expedite solutions.

    Lastly, Scott, please select "Yes" or "No" under my initial response regarding the STOCKHISTORY() function.
    Image
    Making it easier for users who are unaware that the function has been fixed to find it through search engines.

    Wishing everyone a happy and productive day.

    Thomas

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-08-27T21:29:20+00:00

    Hi Thomas,

    The issue with STOCKHISTORY() persists, albeit in a slightly different way. There are several replies regarding the new issue at the end of this thread. Should we start a new thread or use this one?

    Thank you for your help.

    Scott

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-08-27T21:49:30+00:00

    The STOCKHISTORY() issue persists, but in a different form.

    As of 6 pm PDT on August 25, I receive #CALC! errors sporadically for calculations that use STOCKHISTORY(). I also receive repeated and consistent error warnings that are rendering Excel unusable: "Excel ran out of resources while attempting to calculate one or more formulas. As a result, these formulas cannot be evaluated."

    I ran Task Manager and there are no memory issues, nor have there ever been.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-08-28T00:21:27+00:00

    Hello

    I am getting exactly the same problem you described, this time is worst since the "not enough resources error window" keeps popping up and thus, cannot use the file.

    Did you notice whether an upgrade was installed? In my case, I restarted my computer and an upgrade did install, thus going back to the initial problem of all this happening after an upgrade.

    Microsoft, please help resolve this issue

    Thanks

    Mario

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-08-28T02:26:58+00:00

    I manually did a separate update of Excel 365 on my Mac today - even though it is supposedly set for automatic updates. After that, for a while, the STOCKHISTORY function worked fine. Then it deteriorated again into the same #CONNECT!, #CALC!, #SPILL!, #UNKNOWN! and other #N/As as before, including the Alerts for lack of resources etc.

    On the phone waiting 45 minutes for Microsoft support but had to give up owing to work pressures.

    Was this answer helpful?

    0 comments