Skip to main content

We are running Apps8 Sp1+. About every 9 months or so, our client user PCs receive Microsoft Office updates that put the file “msoshext.dll” back on the workstation.  This is an Office DLL that corrupts the operation of IFS browsing within the Doc Management browser. We usually end up renaming the DLL so it doesn’t interfere and all works well again.

Has IFS ever addressed this issue?

Does this issue cause IFS application to close when the user tries to view an doc attachment?  We are currently experiencing this now.  Cannot figure out why


Yes, it does. When we get Windows updates pushed down to our local machines, we look to see if this file has been put back in. If so, we just rename it so it isn’t used. This will correct the doc attachment issue. I don’t think IFS will address this, since it’s a Windows issue.


Yes, it does. When we get Windows updates pushed down to our local machines, we look to see if this file has been put back in. If so, we just rename it so it isn’t used. This will correct the doc attachment issue. I don’t think IFS will address this, since it’s a Windows issue.

That is probably a correct assumption. We also do not release patches from R&D for Apps 8 anymore. Our support dept. might of course be able to help out anyway.

By the way, are you using the web client or IFS Enterprise Explorer? And, what file types do you use when you get the problem? Perhaps the problem can be worked around using a macro that “starts” the document in some other way.

 

 


Reply