?
Solved

Veritas Backup Exec - Database Query Failure

Posted on 2005-03-15
8
Medium Priority
?
1,459 Views
Last Modified: 2013-12-01
At my wits end!

Have ben trying to get Backup Exec to "See", "Connect" to my database store on an SQL server,
but I keep on getting the same error:

     An error was encountered while attempting to browse the contents of SQL server.
     Database Query Failure. See the job log for details.

First off, there is no job log be cause the job cannot be created.
Second, I have been through a number of Microsoft and Veritas tech articles telling me to perform all sorts of voodoo on my SQL & Media server, but to no avail. I still get the error message!

Am using integrated security on the SQL server so have assigned the Backup Users account to the job, which as you all know gives the user account local diety status on the server.

Also tried creating an account to logon to the SQL instance, but have not been able to figure out how to attach it to the SQL instance because I cannot see the instance in the Selections!

Has anyone out there experienced this problem?

Your help is appreciated!

Thank you,

Mike

0
Comment
Question by:keatscon
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 23

Expert Comment

by:Rahul Misra
ID: 13546115
please ensure that the service for yr SQL server are running.
stop services for any other backup software that u might have installed on yr server.
also stop the removable storage media service.
0
 

Author Comment

by:keatscon
ID: 13546330
1. Services are running
2. There is no other backup software running
3. This service is set to manual and, when I checked it, was stoped.


No Success!  =(
0
 

Author Comment

by:keatscon
ID: 13546978
Okay, Veritas Support is useless, in all forms.

I found a tech article on the Veritas web site that may have the answer I need, unfortunately it looks like it was written by someone with a third grade understanding of English.

The article number is 76237 and goes like this:

> The problenm was a mistmach between 2 files from MDAC,  I used the component
> checker and I detected that  almost all the files are the same version on
> both servers except the OLEDB32.DLL file, the SQL server uses the 2.71.904.2.0
> and the other 2.80.1022.0., this is the root of the problem.
>
> In order to replace this file do the following steps:
>
> 1. Go to the C:\windows\system32\ddlcache folder and replace the
> OLEDB32.DLL file with the new one in this folder first.
> Note This is a hidden and system folder.

> 2. Then replace the all the other OLEDB32.DLL file that you had found on
> the computer.

> 3.- Restart system to let the changes take effect.

As you can see the article does not state from which directory the file is copied from and to which directory you copy the file to. Never mind the version of the file.

Can anyone out there clear this up for me? Which version of the OLEDB32.dll should SQL be using on a W2K3 Server, Std.?
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 

Author Comment

by:keatscon
ID: 13547107
Out of frustration and desperation I tried something on my own.

Replaced the older version of OLEDB32.dll on the SQL server (C:\Program Files\Common Files\System\Ole DB\oledb32.dll) with a newer version that I copied from the media server. Rebooted the SQL server and can now backup my SQL DB's!!!!

Life is Grand.

Thank you all for your assistance!


Regards,

Mike
0
 

Accepted Solution

by:
modulo earned 0 total points
ID: 14011971
PAQed with points refunded (250)

modulo
Community Support Moderator
0
 

Expert Comment

by:stu74
ID: 26495827
Even though this is a very old post, I have found that you still need to do the same fix as keatscon carried out to enable the SQL Server Agent on Backup Exec 2010 to be able to backup a SQL Server 2008 database. To have to apply a fix that is nearly 5 years old to a brand new piece of software like Backup Exec 2010 is a nonsense.

So...I copied the c:\program files\common files\system\ole db\ole32db.dll file from my BEWS 2010 (Windows 2008 R2 x64) server over to my SQL Server 2008 Server (Windows 2008 SP1) into the same directory, overwriting the existing file and retried the SQL database backup job and it worked.

Stu
0

Featured Post

New benefit for Premium Members - Upgrade now!

Ready to get started with anonymous questions today? It's easy! Learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Finding original email is quite difficult due to their duplicates. From this article, you will come to know why multiple duplicates of same emails appear and how to delete duplicate emails from Outlook securely and instantly while vital emails remai…
In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
Suggested Courses

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question