can you duplicate the issue using the webtier url and add tracesoap=true like
click on the attachment and when you see error=null, send the debugtrace for analysis. The null points to non existing links, need to find out what is preventing it from opening.
I suffixed my URL with: ?tracesoap=true, but didn't know where to find the debug trace to send to you.
Note: I currently have tracing turned off in my sm.ini file as it fills up the logs...
At the root of Tomcat - or sometimes inside /bin - there is a specific webtier sm.log. That should also contain data from when the problem occurs. Following Rama's suggestion reproduce the problem and send in that specific sm.log.
Also, we were wanting to know what applications version is being used? We're assuming 9.40, but just want to be sure.
Is this the doc you're testing "#UpgradeTasks.docx"? If so try removing the # in front of the file name and see if it works (Reattach without the #). I can now reproduce the issue if I attach a file with a # at the beginning of the filename for a text/log file.
That was it - Thanks Jason!
I remember such restrictions in the past, but I thought they were fixed in later versions - oh well.
You're welcome. It was a group effort with Rama, Steve, Jason and myself.
Glad the issue is resolved, can you verify in your old system if you still had the # or not? We need this info to continue working on this internally 🙂
Interestingly, it also happens on our 9.30.201 Webtier.
Thanks again - Larry!