the report RSCMSTH0 gives error
HTTP/1.0 401 Unauthorized
content-type: text/html; charset=utf-8
content-length: 2135
sap-system: MU1
www-authenticate: Basic realm="SAP NetWeaver Application Server [MU1/800]"
sap-client: 800
~remote_addr:
~uri_scheme_expanded: NONE
Daniel
bom dia
Obrigada por retornar.
Entramos em contato com o Banco, a melhor solução foi modificar a carteira de cobrança, sendo assim banco emitirá o boleto e enviar para o cliente.
Desta forma conseguiremos utilizar o "standard" sem investimento do BARCODE.DLL ou Smartforms.
Estou realizando os testes para validação.
At,
Hello Adrien,
you might want to repost this question in Space http://scn.sap.com/community/ecm, as that Space is more relevant to the Content Server topic - and people might be able to answer this question faster there.
Best regards,
Laszlo
Hi Raneetha,
Did you solve this requirement. I have same requirement and would greatly appreicate if you found any standard solution other than custom.
Thx,
shyam
We have a Device LOCL-UL in SPAD.
Device type is ZHANWIN
Host Spool Access Method: F
Host Printer: __DEFAULT
Users are complaining that when they print labels, sometime the print is getting delayed, even for 5 minutes, nothing is happening. Even restarting Print Spooler does not help.
Network team suggests that there is no issue from their side.
Please help to resolve.
Hello,
Please notice that:
SAPLPD will only be supported for frontend printing in Releases < 4.6C.
For all other Releases, please note the following:
_________________________Front-end printing___________________________
- For frontend printing, customers should use access method 'G'
instead of access method 'F'. See SAP note 821519 for more details.
Also fully review SAP note: 128105 Frontend printing (collective note).
___________________________________________________________________
_______________________Server based printing___________________________
- For server-based printing via access method 'S' or 'U', customers should use SAPSprint instead of SAPLPD. SAP Note 894444 has all the details. This is valid for ALL Releases.
Also be aware that SAPSprint should not be installed on frontend PCs!
It is a server tool only.
Acess method 'G' should be used instead of 'F' as mentioned.
_______________________________________________________________________
Please also have a look at the SAP note:
85469 Options for the SAPSprint print server tool
Regards,
David
Hello,
"HTTP Error: 401 Unauthorized" generally occurs when you try to access
an External Content Server but the content Server doesn't validate the
Signature. There may be two reasons for this - either the Content Server
does not receive the signature or the Certificate corresponding to that
signature is not active. If this is the case, you will need to carry out
the relevant Customizing and then re-try.
Transaction OAHT is used to send the certificate to the external Content
server and Transaction CSADMIN can be used to administer the SAP
Content server.
Seems like the certificate on the content Server is not correct.
For each repository the SAP Content Server maintains two files that keep
the system certificates in order to verify signatures. Both are named
as the repository, one with extension ".cert" and one with ".pse".
These certificates and pse files are stored in the "Security" Directory
below the server installation directory(S:\SAP\Content Server\Security).
To resolve the issue, remove this files from the Security directory
for the repository Z1 and make sure that the Security directory
has access rights "full control" for everyone.
After that, distribute a new certificate to the content server for the
repository in transaction CSADMIN and activate it.
This should produce two files Z1.cert and Z1.pse.
Also, please ensure that a green bauble is associated with the system
PSE in transaction STRUST.
Regards,
David
Hi Ashutosh,
Could you let me know how this was solved. We are facing the same problem with Chinese language.
Would appreciate your help on this.
Thanks,
Tianyan
Hello,
as David already said: do NOT use SAPlpd and access method F (I think it is unreliable for production purposes like printing labels for shipments/goods) but reconfigure your printer in SPAD to use access method G. All the code for G is integrated in SAPgui and should work immediately.
Regards,
Alex
The driver program is a custom one. The settings to trigger the output as pdf are if the delivery gets PGI'd.
I'm not sure why the driver program would be causing the issue because it's code. The code itself never changed. It was working for a while and then all of a sudden stopped working.
I just got word yesterday that it was working again. So it's really not an issue anymore but very perplexing because if it comes up again I don't know what exactly to look for.
Thanks,
Tamara
Ok, that is really fancy. Maybe you could have a look in the transports.. perhaps you humble over someone's transport which cause and fix the error.
I also don't think that code can change.. execpt there is a transport
Maybe, just maybe someone has changed something and wasn't awre that it also hit's your output.
~Florian
Hello All,
This is my issue.
After SAP version upgrade EHP-7 I am facing some issues in purchase order printout.
font size in the purchase order is changed. fort size becomes smaller than the normal correct font.
We are using same form for both Po print out and fax.
for PO print out words are printed correctly. But for the fax I could see small fonts instead of normal one.
same form is used for both the medium. But I could see small fonts for Fax.
I want to know why fonts are showing smaller even same output form is used?
Where we need to check this problem.
Thanks
Regards
Subbu.
hi，
I also get this problem and find the solution now.It is because the size of our picture which we imported by t-code se73 is too big.So we change a small one and we also load fonts,graphics into printer memory.Then it works out.
Hope it can help you！
Hi Friends,
In VL32N, Some times user entered the value on qty field(LFIMG) without decimal point. Now I want to print that how it's displayed in VL32N.
ie without decimal values.
Thanks with Regards,
Vallamuthu M.
The problem we're facing is to be able to print a PDF spool through frontend printing.
When we try to print a PDF spool directly to frontend from transaction FIWTIT_CU, the PDF spool is correctly created and we can see it in SP01 as PDF spool type, but the concurrent output is a list of ASCII chars, similar to the one you get when you use the wrong driver.
The preview on SP01 works fine and, as a workaround, we can actually print the PDF throught the print option on the preview, but, of course,
it's quite time expensive.
Searching on SCN and sapnotes we found out that we cannot use SAPWIN/SWIN device type, but a PCL, PS or ZPL device type.
We tryed PDF1, POST2 and XFP with no luck.
Does anybody knows which device type can we use?
Should we use report RSPO0022 to check the device type we can use and just try them 'till we find the right one?
Thanks
I think my blog will be helpful to you - To Postscript or to not Postscript
Have you verified the printer you are sending it to supports known printer languages?
Thank you very much!
This is a possibility I din't think about, I'll check the printer configuration and let you know.
Stefano
Hello,
Perhaps this is simply a problem with the Sapscript buffers. You can run the report RSTXDELL on the system to clear the Sapscript buffers.
It is a good idea to do the refresh procedures after any updates concerning font metrics, device types etc...
To do this you can use RSTXDELL report with default settings except it
is better to have * instead of the current client number in the Client field.
After this you can create some new spools and the problem should be resolved. It will not work to reprint an old spool as the contained data is already incorrect.
Regards,
David
Hi Stefano,
With device type PDF1, you probably need to install SAPPDFPRINT into the Frontend windows PC.
See SAP note 1444342 about installing SAPPDFPRINT. If you don't have SAPDPFPRINT installed the file is printed as RAW. You should install SAPPDFPRINT. SAPPDFPRINT installs its own set of fonts and might also use the Windows Fonts.
Regards,
Aidan
in EHP7 PO output condition, in send status tab, options are different from EHP4, what is the impact?
in EHP4
send status:
Requested status options are:
1. A Return all statuses
2. E only error statuses are to be returned
3. N no status is to be returned
4. Blank
Status by mail options are:
1. A All statuses
2. E only Error statuses
3. N No statuses
4. Blank
whereas in EHP7
send status:
Requested status options are:
1. A Always
2. E only if errors
3. N never
4. D If transferred
5. R if read
Status by mail options are:
1. A Always
2. E only if errors
3. N never
4. D If transferred
5. R if read
what is the impact on this.