After a breakdown on my virtual webhost, they finally restored the container, but now I randomly get the error when I try to execute queries. I can do a
Select top 20000 from Orders
But
Select * from Orders (about 100k rows total)
Receives the error in my management studio:
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
And this error in my error log:
A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.
I have googled the error and can see that it could be because "Lightweight pooling" is enabled, but this is not the case here.
I run mssql 2008 express on a windows 2003 server.
We get the same random issue on MSSQL where I work and (for us any way) its down to network issues (too much traffic and such).
This blog post by Michael Aspengren explains the error message "A transport-level error has occurred when sending the request to the server."
Related
When working with Snowflake through DataGrip I often get the following timeout error:
JDBC driver encountered communication error. Message: Exception encountered for HTTP request: Operation timed out.
Usually on a second attempt it will be fine, but I always need to wait for this timeout to occur before I can do anything. If I continue to run queries after getting the initial connection it will be fine, but if I was to leave the application for a few minutes, again when I come back it struggles to re-connect for the next query.
My suspicion is that this occurs when the Snowflake warehouse is suspended. It seems like it is waiting on some acknowledgment that the warehouse has been resumed.
Has anyone else encountered this?
I'm getting a strange error in SSIS when connecting to a Sybase ASE server using an ODBC connection. I've got several DFTs connecting to the same server, and when I run the entire package several of them fail mid-way with the error messages below. If I run one DFT at a time, they complete successfully. I've thought about restructuring the package to run them sequentially, but I would lose the benefit of parallel execution, not to mention it would be a lot of work as it's a big package. Hoping someone has seen this before because google hasn't turned up any answers.
[ODBC Source [14]] Error: Open Database Connectivity (ODBC) error occurred.
state: '08S01'. Native Error Code: 30016. [Sybase][ODBC Driver]Bad TDS
response stream received from server.
Unsupported length for TDS_INTN: 111
[ODBC Source [14]] Error: Open Database Connectivity (ODBC) error occurred.
state: '08S01'. Native Error Code: 30016. [Sybase][ODBC Driver]Bad TDS
response stream received from server. Unexpected token type received: 109.
[ODBC Source [69]] Error: Open Database Connectivity (ODBC) error occurred.
state: '01004'. Native Error Code: 32007. [Sybase][ODBC Driver]String data,
right truncated
The main error you are facing is
Right truncation of string data
According to the following Sybase documentation, the probable cause of this error is:
Non-space characters were truncated upon the assignment of string data.
Suggestions
You have to increase the size of the parameter/field/variable used
OR
You can Set string_rtruncation option to Off so no exception is raised when a truncation is occured.
Based on this Sybase Documentation
If the truncated characters consist only of spaces, no exception is raised. The setting of On corresponds to ANSI/ISO SQL/2008 behavior. When this option is set to Off, the exception is not raised and the character string is silently truncated.
String truncation may occur in several places. For example, using INSERT, UPDATE, CAST, or assignment to a variable may truncate a string if the declared destination type is too short.
Similar Problem links
ODBC ERROR "STRING DATA, RIGHT TRUNCATED" WHEN QUERYING DATA IN OPENEDGE DATABASE VIA ORACLE SQL*PLUS
I am losing my patience with this problem. I'm running SQL Server 2008 R2 with all updates.
It is very intermittent. Every now and again this SQL server instance will report the error: Login failed for user 'XX'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection.
Error: 18456, Severity: 14, State: 46.
I know this is a good login, it works all of the other times, and no one changes the credentials.
The above error is immediately followed by this error:
The client was unable to reuse a session with SPID 150, which had been
reset for connection pooling. The failure ID is 46. This error may
have been caused by an earlier operation failing. Check the error logs
for failed operations immediately before this error message.
Error: 18456, Severity: 14, State: 46.
When this occurs a few minutes later this is reported also:
Message
All schedulers on Node 0 appear deadlocked due to a large number of worker threads waiting on ASYNC_NETWORK_IO. Process Utilization 0%.
The above message just keeps repeating until I restart the server.
From researching this issue I've increased the maximum worker threads (currently at 1100). The server has 72G memory and 4 vCPUs, running Windows Server 2008 R2.
i don't encounter this issue at all on my other database servers that run the same environment. Just this one. Any help would be greatly appreciated, I'm running out of options.
I am troubleshooting an error with database mail, and when I went to management->database mail to send a test e mail, I get the following erorr:
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SQLServer.ConnectionInfo)
Additional information:
Lock request time out period exceeded
The statement has been terminated (Microsoft SQL Server, Error: 1222)
When I investigate this further by looking at all blocking transactions on msdb, I find one transaction, that has the name "implicit transaction". Is this the one which is blocking? What can I do?
Ok I found out what happened by looking at all transactions (right click -> reports -> all transactions). From there I found that a server user had a locking transaction open. After making him close it, everything went fine.
I'm trying to run a query which, when successful, executes in 500-600 ms. However, sometimes the query fails and gives a message saying it couldn't connect to the server. The exact message is
Error: ('HY000', '[HY000] [Vertica][VerticaDSII] (10) An error occurred during query preparation: no connection to the server\n (10) (SQLExecDirectW)')
What is the root cause of this error and how do I fix it?