We got this Error in one of our SQL-Jobs tonight:
Error: Executing the query "exec P_ALL" failed with the following error: "Could not locate bookmark due to data movement.". Possible
failure reasons: Problems with the query, "ResultSet" property not set
correctly, parameters not set correctly, or connection not established
correctly.
I can't find any explanation on the web. The MS SQL Server 11.0.7462.6 is running on VMware. It is noticeable that the error came exactly at 03:00:13 am.
I know it is not easy to say, but do you think it is possible, that the VM moved the data and because of that, the Job failed? Do you know other reasons for this error?
The event error log has no further Information.
Thank you for your time!
Related
We have a situation in our SQL Server 2008R2 installation where too many error messages are being generated. We keep getting about 100 new messages every minute.
This is how it looks like:
And this is another portion:
The problem is that I cannot understand what is really going on as the error messages aren't too helpful. Could anyone provide any pointers about what these messages are about and how I can go about troubleshooting this issue?
I am having some issues with database backups.
My database is in simple recovery mode and database backup occurs every night. We some times getting backup job failed and throwing the error as below.
ERROR:
The operating system returned the error '112(failed to retrieve text for this error. Reason: 15105) while attempting 'SetEndOfFile' on \backups\sqlbackups\finename
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Problems with the query / Property not set correctly / Parameters not set correctly: this is running from past 2 years.
I am still unsure why this happens some times.
If anyone having the same issue and figured out the possible reason, please discuss
Server info: SQL Server 2008 R2, Standard
Database info: simple recovery mode and is acting as a publisher with size 1.4TB
Thanks in advance
It seems you haven't enough space on your destination place. Make sure that there is enough free space on your drive and try again. If you use a third-party tool to backup your databases set "Auto-delete" option to delete your old backups.
I have this error during my package execution.This error doesnt stop my data flow though but i want to get rid of this error as this might effect in near future.All my packages use the ssis logging to log the errors.Even though i have my connection (in this case i am using project level connections) exist on project.It still throws a error.
I have found a solution that when we change the project level connections manager to package level connection i dont get any issues(which is not recommended in our environment).So i request all you sql users to help me out.
Thank you,
I'm working in a VBA module for Access that queries linked tables, generates reports based off the data, and then uses a PDF printer to save the reports to disk. There's a timer in the primary form that will, every N seconds, run an Access query against a "JOBQUEUE" table to see if there are new jobs.
If the database server becomes unavailable, this operation will of course time out. The run-time error of 3051 is being logged, and the loop will try to continue. The loop can't finish, however, because the following error comes right after the VB Run-Time error;
Title is "Microsoft SQL Server Login", so it's not within VB as far as I can tell.
Connection Failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB][ConnectionOpen(Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or access is denied.
In every forum & discussion I've found that mentions this error, the asker is concerned with the cause of the error. In this case, I can assume that the error is temporary, and that it needs to continue trying to connect because the installation is unattended. Access goes into a "Not Responding..." state when it's timing out against the DB, and that's OK too, if connection is restored before it goes into the MsgBox described above, it will pick up where it left off and soldier on.
Does anyone know of a way that I can either mute that msgbox, preferably programatically, but I'd take anything at this point that can be done remotely that isn't an RDP session.
Edit: Link to image
The error I was getting was indeed not a run-time error that could be caught from code. Rather, it was SQL timing out after I already swallowed & dismissed time-outs in run-time in my VBA module.
The error does not seem to ever appear now that I have introduced a new timer that resets the loop that runs a query against my linked tables. It can't be logged & swallowed, but it can be prevented by being smarter about how I handle timeouts in run-time.
I am having a strange problem that happens randomly on a server. Some mornings, our client will call in and say their website is not working with the following error message:
The underlying provider failed on Open.
The temporary fix I found for this was to manually go in and restart the SQL Server service. Once this is done it works just fine until the next random time it happens. So my question is, does anyone know what exactly is happening? If so, how can I prevent this in the future?
I have tried searching everywhere for this with the only explanation saying that updates were being applied to the service and it wasn't restarted properly. But I couldn't find any fixes. Thanks in advance
This error:
'FCB::Open failed: could not open file (LDF file) for the file number 2. OS error: 32( The process cannot access the file because it's being used by another process)
is quite troubling and should not be occurring, unless you just restarted your SQL Service. It would easily cause the problems that you are seeing. I would take this to GoDaddy.
If you are getting this error through your Nagios check.
Make sure you deselect "autoclose" as an option on the database.
You can select the option in: Database properties -> Options
Here select at Auto Close: false