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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-20T17:57:54+00:00

    The STOCKHISTORY function is currently not working correctly. I update every Saturday. It was okay Aug 10, 2024, but not Aug 17 (or today). Hope they fix it soon.

    I discovered if I open the workbook and wait 5 or 10 minutes, eventually formulas with STOCKHISTORY(...) will randomly update. It takes a lot of patience.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-08-20T14:42:34+00:00

    I am on the same boat! Please get this fix asap

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-08-20T13:05:00+00:00

    Hi Scott Laudeman,

    Thanks for your post in Microsoft Community.

     

    STOCKHISTORY function relies on specific external service providers, so in this regard, it is an online service. The special function in Excel may occasionally fail to return results due to temporary server issues at the data source. However, please rest assured that these issues usually do not last too long.

    Furthermore, we have already reached out to Microsoft development team and the external data provider as quickly as possible, hoping they can complete the fix promptly.

     

    I hope the information above is helpful to you!

     

    Best Regards,

    Thomas C - MSFT | Microsoft Community Support Specialist 

    Hi Thomas C,

    Is anyone doing follow up to this issue with some sense of URGENCY? I am now at a complete standstill because STOCKHISTORY is not working as it should. "Hoping" for a fix is NOT ACCEPTABLE when users are paying for 365 to be working as it should. Microsoft needs to set up QUALITY and PERFORMANCE conditions with these specific external service providers, and in the service agreement there needs to be included penalties for non-performance.

    I am waiting (along with ALL other 365 subscribers being impacted) for an Estimated Time to Resolve this issue. Please follow up with the MSFT development team and insist on getting an ETA to get this resolved ASAP.

    I am sure if there was a similar incident impacting the internal operations at Microsoft, Upper Management would be jumping all over it.

    As Subscriber Users, we are expecting same attention to this issue.

    Please advise if there is a timeline to get STOCKHISTORY back online and working as it should.

    Best,

    Ray F

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-08-20T04:42:46+00:00

    Hi Scott Laudeman,

    Thanks for your post in Microsoft Community.

    STOCKHISTORY function relies on specific external service providers, so in this regard, it is an online service. The special function in Excel may occasionally fail to return results due to temporary server issues at the data source. However, please rest assured that these issues usually do not last too long.

    Furthermore, we have already reached out to Microsoft development team and the external data provider as quickly as possible, hoping they can complete the fix promptly.

    I hope the information above is helpful to you!

    Best Regards,

    Thomas C - MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments