Hey buddy, you're going to get booted if you keep answering peoples questions with an advertisement.

I had the exact same problem, it is caused by an update to ActiveX killbits pushed out thorugh windows update. To undertand the issue and fix it follow the instructions...

I'm also having this problem or something similar. Any reports that contain charts will not export or print.

I recently had an issue where the print control stopped working after...

I am running Sql 2000 sp3. I found the problem, unfortunately I have no idea how it happened. When I had some time to mess around on the production system...

Unless anyone else chimes in this weekend with anything else to try I'll probably end up opening a ticket with MS on Monday. Hopefully they will be able to figure...

GilaMonster (7/3/2008)

---

Very strange...

Do you have space on the source server to restore one of the full backups that produces an error on the standby server? If so, please restore the...

GilaMonster (7/3/2008)

---

Have you done a checkDB on the source database?

While it's not unheard of for a backup to have an error, to have multiple backups producing the same error is...

Mani Singh (7/3/2008)

---

select name,dbid from sys.sysdatabases

get the DBID from above result then

select object_name(id,yourdatabase id),id from sys.sysobjects

here id=1371151930

check the name of the Object and figure out if this is a index...

That statement doesn't seem to run, here's what comes back:

------------------------------------------------------------------------------

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).

Server: Msg 11, Level 16, State 1, Line 0

General network error. Check your network documentation.

Connection Broken

------------------------------------------------------------------------------

I've tried...

Here's what I get:

-----------------------------------------------------------------------

Server: Msg 8928, Level 16, State 1, Line 1

Object ID 1371151930, index ID 0: Page (1:2948) could not be processed. See other errors for details.

Server: Msg 8944,...

Thanks for the links Mani. I checked out the articles you listed but none apply specifically to my problem. I don't get the error when I back up the DB...

We discovered that running a full backup at night causes the issue. Does anyone know why running a backup would cause a query to run slow?

Thank you Rudy, what I meant when I said it behaves the same is that after I changed the default database settings in EM to:

Default Data Directory: M:\MSSQL\Data  (removed extra slash...

They originally were defined with the slashes at the end but I changed it and it still behaves the same.

Yes, the filepath column has the double slash.

I'm not up for the reinstall project, rather live with the minor problem and fix as needed. BTW - the easy fix is...