Did you determine whether the file is being corrupted when written or retrieved? Maximo doesn't really process the file contents so I don't think Maximo corrupted it and I've never seen where it has corrupted a file. Knowing whether what is on the server is corrupt or if it's being corrupted only during retrieval is important for you to triage the issue with your IT team.As for secured attachments system property not working, I believe your issue there is you have misconfigured your doclinks without realizing it. When you use a web server to render attachments it's more flexible because Maximo isn't the one exposing your attachments. When you enable this property, because Java is case sensitive, you need to ensure that your naming structure matches on the DOCTYPES, DOCINFO, and the doclink system properties. For example, my mxe.doclink.doctypes.defpath, mxe.doclink.doctypes.topLevelPaths, & mxe.doclink.path01 system properties are set to c:\DOCLINKS (lowercase C, uppercase everything else) in my local VM. When I'm not using secured attachments, my doctypes could be C:\DOCLINKS or c:\doclinks (or any combination thereof) and it would work. But now that I'm using secured attachments, they all must match exactly. Ensure the defaultfilepath on DOCTYPES (which you can also modify in an application like WOTRACK by using the Attachment Library/Folders->Manage Folders dialog) matches the same case on each of your folders.
For DOCINFO you really need to do this from a database perspective unless you have only a few documents. If you're on a case sensitive database platform (DB2/Oracle) you can run a query like this to identify documents with issues (replacing with your actual path in the case that you need it to be):SELECT * FROM docinfo WHERE urltype='FILE' and urlname not like 'c:\DOCLINKS%';If you're on SQL Server it won't return results that are only due to case differences (though would find other issues like pointed to a different path). While this may not solve your problem, you should make a plan to switch to utilizing secured attachments anyways. Exposing documents through the web server can cause confidential information to be leaked to unauthorized individuals. Even if only people inside your organization can access your Maximo environment, your technician would potentially be able to access purchasing documents for example that they shouldn't have access to view. It's better to have Maximo enforce the security.
Join CommunityInvite ColleaguesLearn MoreGet Started on MORE