Skip to main content

Hi Team,

I have a customer who gets an error message when try to open any attachments in TST environment. This error message occurs only for one User and not for other users in same IFS App10 window. This is the error message:

 

 

Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index

   at Ifs.Fnd.Feature.FndBackgroundWorker.bw_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)

   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)

   at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)

   --- End of inner exception stack trace ---

 

Thank you for your help.

BR Marina

Hi Marina.

We are seeing the same issue since Apps 10 Update 20 was applied, specifically on the Purchase Order screen but it has cropped up elsewhere. I am thinking it may be profile related as not everyone sees the error. Did you ever find a fix for it? We also get this error presented on the Landed Cost tab on the PO screen:

Any help would be very appreciated

Thanks, Andrew

Hi @Marina_Moor,

We suggest applying IFS Apps 10 UPD 22 or higher version.
Single patch ID : 167578 

Have you tried clearing the .NET cache and forcing a new download of the application?

​

@Marina_Moor  did you get a solution for this? we’re facing the same error when attempting to use the “incomplete” status on IFS MWO (IFS Cloud). But the message does not happen when changing the status in IFS Cloud Web

​

Hi all,

 

I am contacting you, as I have this issue : “Index was out of range ...” on one of our Lobby elements in one of the 4 environments we are using : 

None of the 3 other environments face this issue, therefore I am completely lost regarding this issue.

Note : All 4 environments have the same version : IFS APPS 10 UPD 10 _ therefore I don’t see how this works for the 3 other environments.

@mwilson where do you go to clear the .NET cache in the Middleware ? 

 

Did you have any update on this issue? 

 

Best regards,

 

Clearing cache is for the client end of things not the middleware.

To clear cache do the following:

On the user’s local PC, open the Windows Start menu.  In the Search box paste the following and press enter
rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache
 

Next remove these two folders, located on the user’s local PC in C:\users\userid\:
AppData\Local\IsolatedStorage\osome item name]
AppData\Local\Apps\2.0

Usually the Apps\2.0 folder is all that is needed to be removed.

Warning this will remove all click once installed applications.

Hi, 

Thank you for your reply,  I had cleared the cache as well but nothing is happening on my lobby elements.

Would you have any other suggestions ? 


Best regards; 

 

Lobby elements, I must have missed that somewhere above.  If you have lobbies that are invalid then that usually means you have a problem with the lobby.  Either you have invalid code or columns or you are referencing objects that do not exist.

Thank you for the very quick reply htat is very much appreciated : 

Yes I forgot to mention that in all 3 other environment we use with the exact same sql request embedded in the lobby elements, same references to same tables etc. it works :/

Have you checked all of the code to make sure it returns a value?  For instance, do you have one element referencing another element?  I would assume if you do and the first element is null you would get this error.

Does the stack trace give any hint as to what object it is failing on?

Reply


Terms & ConditionsCookie settings