Problem opening attached files (expecially TIFF files) from inside SAP on windows 2000
Hi Experts,
this is going to be a long explanation: we are running SAP on a windows 2000 SP 4 architecture, using it also for document management. The problem is that sometimes our users cannot open attached files and get an error (# 26172) "Cannot create file xxxx" (This is my translation from a localized non-english version); this happens with a whole variety of file-types: e.g. PDF, .doc, .xls, .jpg, but expecially with .TIF images and always on a RANDOM base. This means that the same file might be impossible to open on a machine, while being opened on another, but also on the same computer after a random number of unlucky tries. We tried to resolve the problem disabling temporarily our anti-virus software, which seemed to help sometimes, but not always and not for all files; we also tried to change the location of the temporary folder where Internet Explorer 6 SP1 opens it, (guided by a SAP support suggestion), but to no avail. Hardware seems to have no relevance to the problem and all software has been updated to the latest service packs and patches. SAP GUI version is 6.20, if you need any further information, just feel free to ask. I really hope somebody has a sound solution for this question, which is going to become a nightmare...
Many thanks in advance.
this is going to be a long explanation: we are running SAP on a windows 2000 SP 4 architecture, using it also for document management. The problem is that sometimes our users cannot open attached files and get an error (# 26172) "Cannot create file xxxx" (This is my translation from a localized non-english version); this happens with a whole variety of file-types: e.g. PDF, .doc, .xls, .jpg, but expecially with .TIF images and always on a RANDOM base. This means that the same file might be impossible to open on a machine, while being opened on another, but also on the same computer after a random number of unlucky tries. We tried to resolve the problem disabling temporarily our anti-virus software, which seemed to help sometimes, but not always and not for all files; we also tried to change the location of the temporary folder where Internet Explorer 6 SP1 opens it, (guided by a SAP support suggestion), but to no avail. Hardware seems to have no relevance to the problem and all software has been updated to the latest service packs and patches. SAP GUI version is 6.20, if you need any further information, just feel free to ask. I really hope somebody has a sound solution for this question, which is going to become a nightmare...
Many thanks in advance.
ASKER
In our case, every user has an own temporary folder, on his PC, which in fact is located in
\\%PCNAME%\c$\Documents and Settings\%USERNAME%\Local Settings\Temp.
Actually, we even tried to use another folder (C:\SAP_temp), to shorten the path, but it did not resolve the issue.
\\%PCNAME%\c$\Documents and Settings\%USERNAME%\Local Settings\Temp.
Actually, we even tried to use another folder (C:\SAP_temp), to shorten the path, but it did not resolve the issue.
ASKER
Just as an afterthought, using Sysinternals' FileMonitor revealed a 'Sharing violation' condition only on the files which cannot be correctly opened and, immediately after, a 'Name collision'. Actually, I think this is a standard error message for a corrupted file, but it might also be the right giveaway to the problem.
Anyway, thanks a lot to all who might give advice on this question.
Anyway, thanks a lot to all who might give advice on this question.
did you debug it ? what is the function block or class that creates the error message ?
ASKER
No, I did not and I do not think I could easily debug a copyrighted software like SAP. Can you explain what you mean? Thanks.
YES you can debug sap and watch every single step it is doing. (of course you need the right user profile, e.g. sap_all and sap_new) To debug it, just at any point type /H into the command field (where you normally enter the transaction code). then your next action will take you to debugging mode and you can proceed step by step there.
in your case, I recommend that you set a breakpoint (under tools menu in debugging) for the message command. That will make SAP stop at all "message" commands. Then you just jump from breakpoint to breakpoint (f10) and will end up at the message you are actually getting (# 26172) and from there you can work backwards to see what caused the problem.
This sounds more complex than it is. if you can read abap coding, debugging will be easy for you.
good luck !
J
in your case, I recommend that you set a breakpoint (under tools menu in debugging) for the message command. That will make SAP stop at all "message" commands. Then you just jump from breakpoint to breakpoint (f10) and will end up at the message you are actually getting (# 26172) and from there you can work backwards to see what caused the problem.
This sounds more complex than it is. if you can read abap coding, debugging will be easy for you.
good luck !
J
ASKER
I am currently doing as you suggested, but it doesn't seem to give any useful information. I will give some details later.
Hi,
I think its some thing to check with your TIFF file, if its not properly identified by GUI, then it will not be opened...
check out TIFF file attached...
R.K
I think its some thing to check with your TIFF file, if its not properly identified by GUI, then it will not be opened...
check out TIFF file attached...
R.K
ASKER
Could you please explain what you mean by "properly identified"? In my case, files which SAP is unable to open are always saved with the right extension in Temp directory, if this is what you mean, but they cannot be opened by other applications, since they are not "complete". Usually, the file size of unreadable files is 64 Kb, though, when the same file opens correctly in SAP, its size is displayed as it really is (normally about 100 Kb) and I am also able to open it directly from the Temp directory.
ASKER
I changed the type of attachment to PDF and many users still have problems, now I am tracing HTTP routing between content server and SAP production server, but it doesn't seem to help.
ASKER
Since i resolved this problem thanks to a local consultant who had to work on my network for more than 15 hours, I'll ask to have this question deleted in a few days. Thanks to all of you for trying: I was confirmed this was a really tough and unusual problem, related to a mulfunctioning SAPhttp program, about which we filed a bugcheck to SAP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have had a somewhat similar problem, but maybe I need more details from you. In our case, the problem was that all temporary files were created on a network drive, and then we had conflicts there with similar filenames when many users were active. How have you configured your viewer? In my case at the end we now set the temp path to a user-specific network drive, and had no more problems (we have to do it on the network because we are using dumb citrix terminals).
J