Skip to Content
avatar image
Former Member

Print issue in PRD server

Dear All,

In our PRD server all the print is going in the waiting state ,,,how to resolve the issue ...as we are using 3 spool work process but the one spool work process is stopped and remaining 2 are free but not doing any thing ,,,plz give any suggestion to resolve the issue.

RABLEEN

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Feb 27, 2014 at 06:49 PM

    Dear Rableen ,

    did you tried manually printing from that waiting list using Tx sp01  ?? if yes what was the result

    also perform the following configuration

    run Tx Su3

    go to Defaults tab

    in Spool Control area select the following 

    1-     Output Device

    2-     Output immediately

    3-     Delete after Output 

    Best Regards

    AhMeD

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 27, 2014 at 07:48 AM

    Hi Rableen,

         Without providing any information it is little bit difficult to give answer for your query. Provide us SP01 Error screen shot for that request.

    1. Ensure the printer port should open b/w the user's desktop and the local printer. You can ask the user to pint for any of the word document to check whether he is able to print or not

    2. Check in SU01 for that user is having printer access or not

    3. Login with User's credentials from your desktop and try to give print whether you are able to print or not

    4. Check any network issue b/w SAP Server and Local Printers

    As i told you it is not easy thing to give direct resolution. Ask if you have any queries

    Regards

    Santosh K

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      As @Santosh pointed out, addtional information will be more helpful for the community.

      Something I would first look at is the error of the waiting state, in SP01 after executing a query double click on the waiting status and it will provide more information with why the system put it into a waiting status.

  • avatar image
    Former Member
    Feb 27, 2014 at 02:42 PM

    Normally if one  SPO work process is busy or in error the other 2 should take the incomming work.

    Can you stop the "waiting" spool requests and start one for test to see if it is going through?

    Also you can restart the SPO PID from os level and set the start flag on it in dpmon

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 27, 2014 at 04:51 PM

    Rableen,

    If all you spools are going in waiting status, sometime i have noticed is that if any particular job is running which create temp files under the path

    /usr/sap/<SID>/DVEBMGS00/data

    can create temp large spool files which could also fill up the file system if you 2-4 GB filsystem, taking all the space and not able to create new spool temp files..etc eventually letting the other to pile up

    Thank you

    Add comment
    10|10000 characters needed characters exceeded