Backup Exec 11d - Reports won't run!

We are using Backup Exec 11d on a Windows 2003 server with SQL Express 2005 handling the database.

Until just recently we were able to run reports without any problem. In fact, we run a custom report every week on a schedule. Last week it ran; this week it doesn't. Nor do any of the built-in reports run.

When you try to run the report by right clicking the report itself you get this:
"Unable to run report. No further information available"

If you right click the report and choose "Edit' and then click on the "Preview" option you get:
"The report could not be generated. Database Access Denied"

And when trying to run report by right clicking the "Scheduled report" it fails with this error in the Job History:
"e0008385 - The report stored procedure reported an error."

I have verified that the user I am logged in as has access to the database.
I have also added another user, granted database access, and logged in as that user.
I am able to view all other information in the database by viewing the different tabs, so I am assuming that the data is there. I just can't get a report to run.

Any thoughts on what might be the problem?
neil1997Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

St3veMaxCommented:
Hi,

Connect to your Backup Server's SQL Instance at YOURSERVER\BkupExec

Expand the BEDB Database; Open Stored Procs, Look for dbo.ReportDailyJobs and try and run this proc.

This will show you if there's data in there to report on...

HTH
0
neil1997Author Commented:
I am not familiar with SQL....So I am not sure how to do the things that you suggested. Can you give a little more detail on how to do those steps?
0
St3veMaxCommented:
Open SQL Server Management Studio; Expand Databases, Expand BEDB, Expand Programability, Expand S/Procs, locate in the list, right click and select execute.

HTH
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

neil1997Author Commented:
I do not have the SQL Server Management Studio installed. Is there any other way to check this?
0
St3veMaxCommented:
Sadly not; You can download SQL Server Management Studio Express for free. Google it, D/L and Install...
0
neil1997Author Commented:
This is the result of trying to run dbo.ReportDailyJobs;

Msg 18452, Level 14, State 1, Line 1
Login failed for user ' '. The user is not associated with a trusted SQL Server connection

Does that tell you anything? Why is the user name seem to be blank?
0
St3veMaxCommented:
Did that occur when you tried to execute that procedure or when you tried to connect to SQL Server ?
0
neil1997Author Commented:
When running the procedure.
0
St3veMaxCommented:
Who are you logging in as? Yourself or the Backup Exec Service account ?
0
neil1997Author Commented:
We have always used the "Administrator" account to log in to the server. Backup Exec has also always been configured to use the Administrator account instead of the default BESA. That is what doesn't make any sense; everything has been this way for a long time and nothing has been changed. It just didn't work all of the sudden! I found a posting that said that the blank user name in the error indicates an authentication problem. I am currently logging in to the server as the "Administrator". This server is the secondary domain controller, hosts the Backup Exec program, and runs the SQL server. So I am thinking that there shouldn't be any authentication issues between things. I am the Administrator and everything is all running on the same machine.  Any thoughts about the blank username.
0
neil1997Author Commented:
Well after hours of fumbling around in the SQL Management Studio, I tripped over the solution. Or at least it works now.

I got an error that said the database didn't have an owner. I pointed to the BEDB under databases, right clicked and selected properties, in the Database Properties dialog box, I clicked on the Files page, and entered "sa" as the owner.

Now the reports run just fine! I'll take what I can get.
Who knows what caused the problem. I am just relieved that it is working again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.