SAP升级MSSQL 2008至R2后，outgoing payment打印报-199 openPrinter错误求助

Hey there, let's work through this (-199) openPrinter error you're facing when printing outgoing payments post-MSSQL upgrade. This error typically points to issues with printer access, compatibility, or SAP configuration that got disrupted during the database update. Here's a step-by-step breakdown to fix it:

• Check Printer Permissions & Driver Compatibility

  • First, verify that the SAP application server's service account (usually SAPService<SID>) has proper local permissions for the target printer. Database upgrades sometimes reset service account privileges—head to the printer's Properties > Security tab, add the SAP service account, and grant it Print and Manage Printer permissions.
  • Update your printer driver to a version compatible with both MSSQL 2008 R2 and your server's OS. Outdated drivers often break after environment changes; grab the latest stable driver directly from the printer manufacturer's website.

• Validate SAP Print Configuration

  • Use transaction code SPAD to check your output device setup. Confirm the device type (e.g., WIN for Windows printers) and access method (e.g., C for direct Windows printing) are correctly configured. Sometimes the database upgrade breaks parameter associations—use the "Test" button in SPAD to recheck the printer connection.
  • Double-check that the printer name specified in your SAP print request matches exactly with the Windows printer name (note: Windows printer names are case-sensitive). Typos or mismatched names will trigger this error every time.

• Restart Critical Services & Check Logs

  • Restart both the SAP print service (SAP<SID>_<InstanceNumber>) and the Windows Print Spooler service. Temporary cache glitches from the upgrade can block printer access, and a restart often clears this up.
  • Dig into Windows Event Viewer's Application and System logs for printer or SAP-related errors. These logs will give you more granular details—like driver load failures or explicit permission denials—that the generic -199 error doesn't reveal.

• Test Local & SAP Print Workflows

  • Log into the SAP application server using the SAP service account, then try printing a simple test document directly to the target printer. If this fails, the issue is system-level (not SAP-specific) and you can focus on fixing the printer setup itself.
  • Use transaction code SP01 to view the full details of your failed print request. The log here might include additional context about why the printer couldn't be opened, which can narrow down your troubleshooting.

If none of these steps resolve the issue, sharing details like your SAP version, server OS, and printer model would help refine the troubleshooting further.

内容的提问来源于stack exchange，提问作者Junzeit M Rodriguez