Outgoing payment print error -199 openPrinter - sapb1

When I updated my SAP database from MSSQL 2008 to MSSQL 2008 R2, Outgoing payment printing is making error (-199) openPrinter and exit the program.
The sample error
If anyone knows this error, please help.

Related

Azure Logic Apps SQL Connector Error: Bad Request

I'm using the SQL Connector in Azure Logic Apps to connect to our Azure SQL Database to perform queries, update tables, and execute stored procedures. After several months of developing logic apps, I'm seeing the below error message when using the SQL Connector "Execute Stored Procedure (V2)". I'm only encountering this error with this specific connector. All the other connectors work just fine. Has anyone encountered this error before and had success troubleshooting?
Error:
Could not retrieve values. Error code: 'BadRequest', Message: 'The value's length for key 'application name' exceeds it's limit of '128'.
clientRequestId: 'XXXXX'. More diagnostic information: x-ms-client-request-id is 'XXXXX'.
Just had a call with Microsoft Support and got confirmation: this is the global issue in the SQL connector of LogicApp. They are working on this to fix, no ETA for now.
Update: should be fixed from around 29.03.2022 03:00 CET

SQL Server 2016 Severity 015 Not Alerting

Trying to setup an alert in SQL Server 2016 for Severity 015 (syntax errors in SQL statements) however it will not fire off. I can generate the error with a bad SQL statement in query.
I have confirmed DB Mail is working and test messages come in as expected. EMail setup and valid operator in place. I was also able to generate a 017 Alert (insufficient resources) error and get alerted with no problem using the following:
RaisError (N'An error occurred Severity 17: insufficient resources ! ', 17, 1)
With Log
Go
FYI, the reason I need this alerting is we are converting from SQL Server 2008 to SQL Server 2016 and older commands like *= are all over the place. Need to know when they are coming in because of being missed somewhere.
Thanks in advance for any guidance and help.

How to resolve the following error in R using ODBC when connecting to SQL Server?

Error in result_fetch(res#ptr, n):
nanodbc/nanodbc.cpp:2966: 07009: [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index
I have cloned the code for an R dashboard from my company's datahub. When I run it, it has this error when it attempts to pull the data from our database. My partner has the exact same code on his machine and it runs just fine. I have read about similar errors and I only can find that it has to do with a bug in the SQL code. I don't think this can be the case because the code works as is on other machines.
maybe this similar question will help you
R DBI ODBC error: nanodbc/nanodbc.cpp:3110: 07009: [Microsoft][ODBC Driver 13 for SQL Server]Invalid Descriptor Index
If the code works on your coworkers computer, have you compared the EXACT R and Package versions as well as the SQL versions?

Copying to table error, 0xc0202009, 0xc020901c, 0xc0209029 and 0xc0047022

SQL Server Management Studio 2012 is showing up this error when I try to import excel data to an existing table. I'm not sure what is the error here and I do not know how to fix it...
Can you tell me what is the error here?

SQL Server 2008 R2 Linked Server to another SQL Server 200r R2 select query error Invalid data for type "Numeric"

we are having the following error message on a SQL Server 2008 R2 with SP1 linked server to another SQL Server 2008 R2 with SP2. The error message is: Invalid data for type "numeric" and is happening intermittently. It worked for couple months and re-appearing again. Called Microsoft Support last July 2012, they haven't able to solve it either and we closed the case after it mysteriously disappeared. All we did is just applied some Windows OS patches before the problem disappeared. Now the problem is re-appearing. The error message was from a simple query
select *
from Sales_LinkedServer].sales.dbo.temp_sales_detail
However, this table contains over 2 millions records. Tried and still failed using the
OPENQUERY:
Select *
From OPENQUERY ([Sales_LinkedServer],
'Select *
From Sales.dbo.temp_sales_detamil');
Also, this is happening on our production server but the similar Dev server has no problem at all.