Today when I got it, there was no "Possible UCE::" on the title. I wonder what the difference between yesterday's and today's is that this didn't appear...

Okay, now I'm curious.

I'm running a test on a table that has 69 columns and between 6-7 million rows of data. No WHERE clause and I'll include the "DropClearBuffers"...

egejo15,

I know you're eager to get your problem resolved, but speaking as a paranoid DBA, you should NEVER upload your database files up where someone can hack them. There...

Wow. I didn't even think of that option. Thanks, Matt. I'll give that a try.

I have created SSIS packages which run on a SQL 2k5 server but connect to my SQL 2000 server and do work on it without any problem.

So if...

Ian,

There are other possible show stoppers. Linked servers and queries that use OPENDATASOURCE / OPENROWSET. Make sure you account for all possible objects that have references to these...

HA!

ROTFLOL!

Then the only thing left is the firewall issue Ian mentioned.

Tell me about it!

At least I'm not going to waste a day's worth of "making it purty" now that I know it wasn't my fault. @=)

Try deleting the Linked Server and recreating it. Sometimes that's the only thing that can help in situations like this.

Fiona,

Make sure your font sizes are also all the same. This is another issue that can cause line up problems between subreports and main reports.

Not that it helped me...

Are you sure you haven't typo'd the Server name itself?

Fiona,

I'm having the same problem. Everything's lined up in preview, but not in the Report Server website. I think it's a rendering issue, but I can't figure out...

That tells me the account you were using had something wrong with it. Maybe a typo or maybe a permissions issue. Once you figure out what the problem...

Make sure the user account that you've got set up with this linked server has the appropriate permissions on the database for the T-SQL query you're trying to run. ...