‎2009 Sep 01 2:11 PM
Hi,
all printing has previously worked, but now suddenly the following error occurs when printing using the LOCL printer (Device Type: SAPWIN, Access Method: G)
Status test: "Frontend unavailable"
SP01 Log:
-
SAP spool error log
=====================
Print request processing log
The host spool is reporting errors
Unable to connect to output processor
Request postponed 1 times
Most important attributes of spool request
Request number 9707
Request name LIST1S LOCL SAPMSPAD_K91
Client 100
Owner username
Request attributes
Time created 2009090112464700
Remaining life +00007235959
Dispo 1 (Go/Hold) G
Dispo 2 (Keep/Delete) K
Dispo 3 (Indirect/Direct) D
Default output device LOCL
Default no. copies 1
Format X_65_200
Main print request characteristics
Spool request number 9707
Print request number 1
Print request attributes
Time created 2009090112464800
Output device LOCL
Format X_65_200
Character converter active when first problem occurred
No information available
-
dev_PrintTrace log includes the following info:
-
2009-09-01 11:15:18 CONTROL_CREATE failed with L_SUBRC 2
username calld = batch =
2009-09-01 11:15:18 CONTROL_CREATE failed with sy-subrc 1
username calld = batch =
-
When printing with a printer with device type PDF1, and access method F through SAP GUI for Windows the SPAD status "Incorrect" occurs, but no info in the log.
The above PDF1-printer works perfectly through SAP GUI for HTML.
Scheduled printing through GUI for Windows with Device Type Post2 and Access Method U aslo works fine.
Any ideas for how to solve is very appreciated!
Thanks
‎2009 Sep 01 2:32 PM
> Status test: "Frontend unavailable"
>
> username calld = batch =
>
> 2009-09-01 11:15:18 CONTROL_CREATE failed with sy-subrc 1
>
> username calld = batch =
Its look like you are scheduling background job using frontend printer ?
a®
‎2009 Sep 01 2:42 PM
Hm, no there is no scheduling going on. I get this by simply using Tx SPAD, Display Output Devices, Print this list, and selecting the LOCL printer.
Update: Regular frontend printing - i.e. not through scheduling - also works fine with Device Type Post2 and Access Method U.
Edited by: Oscar Ivarsson on Sep 2, 2009 11:04 AM
‎2009 Sep 03 9:30 AM
Have you recently changed your GUI version? There may have been some updates as to how the front-end printing is made there. If so, can you check with an older version just to be sure?