Valerie,

Would you have some more information on the Operating system, we have seen a few clients with this issue, but have not been able to identify it.  As well have not been able to replicate.

Sage 300 version, OS version, Excel version?

we were Window 10, 32bit 0365 excel we are now windows 11, 64bit 0365 excel - both have the same issue.  The VM was not upgraded we spun up a new one and I was kinda hoping the error would be left behind but no such luck.  I current have not see the issue and I work direct on the RDP server.

And this is SI 8.0 on both Windows 10 and 11.

good point sorry.   No it's Sage 2024 BI.

The below is what we got back from SI Team.  They say it is environmental, I have been arguing that it is not.  I think something needs to change in the Excel addin, but I have no means of proving it.

A "subscript out of range" error occurs when a program tries to access an item in a list, array, or collection using an index (or "subscript") that is outside the valid range of available positions. This is a common error in programming, particularly in languages like VBA, and means the requested item number does not exist. It can happen because an array was declared without a size, the specified index is too high or too low, or a collection member was referenced by a name that doesn't exist. 

then why do i get it just loading License manager?  I agree it doesn't make sense.  

Just adding some detail about what we saw with this error over the past week. The client reached a point where no BI component would load at all—not the BI icon, License Manager, Viewer, or Manager. The error appeared instantly every time. Previously, they could try a couple of times and eventually get in, but this time nothing worked.  Usual things like Office quick repair didn't work even uninstalling and re-installing BI didn't help.   This is a virtual machine. 

With IT’s help, we found that several Windows updates had not fully completed. Those updates were finished, but the error still persisted. However, once we opened Excel first, then launched BI, everything worked after the windows updates were complete.  This was not the case before the windows updates were completed.

I’ve now had two other users report the same thing:
open Excel first (confirm the Office 365 login is fine), then open BI—and the error disappears.

Not sure if this helps anyone else, but wanted to share in case it does.

Usually , i would try to perform a general repair on BI if there is anything not working well. Below is the step i used, let me know if that worked.

From within Excel, go to File, then Options > Trust Center > Trust Center Settings button > Trusted Locations and Add new
location to browse to add C:\Program Files (x86)\Common Files.  Be sure to select the box for the subfolders.

After adding that location, exit out of Excel and all Office applications, and run a “Quick Repair” on MS Office from the Control Panel. 

thanks for posting this - I have never checked the trust center before - I have done a general repair of BI and gotten errors - uninstalled and re-installed.   this could be helpful.    I almost always try the quick repair first.    The weird thing is i only have one site that every has this issue.  I have lots of users of BI.

Hi Ron,

We have several clients with this issue and can replicate it. Let me know if you would like to connect at some point. Either Darby or myself can connect you to one of the many instances where the issue is happening. 

Doug B.

Equation Technologies 

The problem is getting Alchemex to look at the issue, they said they cannot replicate it and therefore will not look further into the issue.  This being an environment issue.  They refused to engage.  I would need Equation tech to push your account manager, support has nowhere to go with this.

Thanks Ron

This is the response I received this morning from my account manager: 

Hi ValerieH , Did you manage to resolve this issue , i am also expereiencing the same issue on terminal server  with BI 8.0 ,  2023 Sp2 . Any suggesstion ?

I did manage to solve and I believe in the end what happened was there was a OS upgrade that was "pending' half installed something along those lines.  Once all users were forced off the RDP server and all MS updates were on, I did a MS office quick repair the problem was resolved.