Hope it shud hold them, but can do a simple try checking the .trn backup file size after inserting only images and backing it in a sample db.

How about trying to execute the job with t-sql using if/else or case statements.Just a guess.

Just a blind guess

Has the rebuild index job ran with a change in the fill factor from 5-10% or something like that.

Is this the first time you are logging?

if IIS is fine:

looks like you need to review ssrs configuration:

Reporting Services Configuration Tool

http://msdn.microsoft.com/en-us/library/ms156305(SQL.90).aspx

also

Troubleshooting Reporting Services

http://msdn.microsoft.com/en-us/library/ms159135(SQL.90).aspx

may be try this:

Change the Reports / ReportServer...

Is the 90GB growth on mdf or ldf or is it combined?

Check for the space usage of all the tables, check for reserved space here.

I havent seen it documented anywhere, but I had it in my experience many times.

Autogrowth value going to 6-7digit as percentage!!!

there is also a bug in SQL 2005 with autogrowth when you restore a db or restart the services etc.

In the view sys.database_files is_growth_percent changes from 0-1, which means that...

There can be many reasons like

network glitch at that time, someone amended the pwd's, services restart etc.

Is this the first time you are logging to SSRS?

Check if you have already configured reporting services at

All programs-->SQL 2005-->Conf. tools-->reporting services conf.

You should see all ticks there.

try connecting to them using SQL authentication mode instead of windows authentication with a valid credentials.

Looks like a connection failure, check if the users credentials who run the job are still the same or changed?.

Try manually executing the job with some valid connections and let...

what is the status of IIS?

Check if it is a .trn backup with recovery mode as simple.

View the job history, which will give you some idea.

Do you have the required priviliges to do that?

As what user you are logging on?

Check if all the Services are running in sql server configuration manager

check the protocols if they are enabled.

You sometimes get the same error, when you have entered a wrong userid/pwd.