February 15, 2008 at 8:40 am
I have a weird case going on with one of my virtual servers that is running SQL 2005. I have created Maintenance Plans for my databases. All of my databases are SIMPLE recovery (as it is a test server). I run a FULL backup once per night and then run differential backups every 3 hours throughout the day.
The problem is that my differential backups will sometimes run and sometimes fail. When they fail I get the message:
Could not load package "Maintenance Plans\DBName" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Unable to complete lgin process due to delay in opening server connection). The SQL statment that was issued has failed. The package could not be loaded. The step failed.
The reason that this is weird is that the job will run sometime and then fail other times, but I always get the same message. I have about 30 databases that are trying to run together and only some fail, but it is usually not the same ones. I'm not sure if it could be a matter of not enough memory on the virtual server to handle the load or some other issue.
We were running a process similar to this using SQL 2000. In fact the virtual server running SQL 2000 ran the exact process and same databases as above. If anyone has any thoughts they would be appreciated.
February 15, 2008 at 12:54 pm
I would like to guess some other processes were running on your server when differential backups started. These processes may locks the database from backup. Could you monitor other jobs running on your server when differential backup starts?
February 15, 2008 at 2:13 pm
I watched the other jobs and applications that we had running on this server at the last backup timeframe...just now. There were no other jobs that we have defined that were running at the time and only about two people accessing. (This is a newer test server that we haven't informed everyone exists just yet).
However, when the differential backups started running I noticed our memory usage jump so high that we had no more available. Also noticed CPU usage jump to 100%.
But it looks like we just need to get some more memory for the server to let it run. As I was looking I noticed it only has about 1.5GB of memory. Though that was enough for our SQL 2000 server, 2005 looks like it may be more memory hungry. We have started to have the same issue with development machines that are having the developer edition installed on them. The same machines had SQL 2000 installed, we upgraded to SQL 2005 and now their memory is maxed out there as well (this is an issue that I was informed of after the original post).
Thanks.
March 7, 2008 at 8:04 am
I'm getting the exact same error only with a maintenance plan doing log backups. It also only occurs very intermittently. Also using SQL 2005 SP2.
March 7, 2008 at 8:16 am
Been having a similiar issue with SSIS, see this thread:
http://qa.sqlservercentral.com/Forums/Topic455318-148-1.aspx
March 7, 2008 at 9:16 am
Hi,
This sounds like an issue with the Connection Manager resolution at runtime, maybe due to memory pressure or a timeout issue with OLEDB provider, as the connections are not created until runtime. Common denomenator is SSIS, so I would suggest you enable package logging and use the Diagnostic event at package level to confirm.
Thanks,
Phillip Cox
MCITP - DBAdmin
March 7, 2008 at 10:03 am
Phillip Cox (3/7/2008)
Hi,This sounds like an issue with the Connection Manager resolution at runtime, maybe due to memory pressure or a timeout issue with OLEDB provider, as the connections are not created until runtime. Common denomenator is SSIS, so I would suggest you enable package logging and use the Diagnostic event at package level to confirm.
Thanks,
Phillip Cox
MCITP - DBAdmin
Tried all sorts of traces and logging, couldn't find anything pointing to anything in particular. I found a similiar issue in another thread on SSC, and tried that fix (see the thread referenced earlier), and it has seemed to help with part of the issues. I still have intermittent issues with some packages just hanging (should run for 9 seconds, still running 30 minutes later..., cancel the job and restart at the same point and everything runs fine).
😎
November 9, 2011 at 1:16 pm
SQLHAWK (3/7/2008)
I'm getting the exact same error only with a maintenance plan doing log backups. It also only occurs very intermittently. Also using SQL 2005 SP2.
Its been over 3 years but wanted to ask if you remember what was the problem ? We have same error on one of the systems with transaction log backup maintenance plan on a SQL 2005 SP2.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply