Does executing the below query generate any errors?

xp_cmdshell 'dir c:\xxx\yy\zzz\filename.xls'

There are two options.

1) To add a new data file to tempdb on a drive which has enough space.

2) Kill the SPID which is currently active on it.

Since this...

Does the folder "c:\xxx\yy\zzz" exist on the server where SQL Server is running?

This behavior is by design. To overcome this issue, you can select "All Databases" or "User databases" while creating the maintenance plan.

Assuming that you are referring to the connection strings in .Net or some other application, yes you can build the connecting string yourself. Define text parameters, assign value to them...

Check if any open transactions are there on tempdb. Once those transactions are complete the size will return to normalcy.

These screenshots should help you to read the SQL Server Error Log.

http://goo.gl/kRQ0z

http://goo.gl/9DGCk

This article has the syntax for sp_purge_jobhistory. You may create a job which executes a query similar to the one below. This query deletes records older than 10 days.

DECLARE @oldestdate...

As the error message states that particular index is disabled. Rebuild it manually to enable it or drop it if that index is not required.

You may find this article useful.

and this[/url] as well.

You may find the script posted under "Maintenance Plans" section in this link useful.

Is the replication working correctly? If yes, are you backing up the transaction log at the Publisher?

This is the SPID that indicates there a few transactions to be replicated on that database

You may include some error handling in the query that you are using. TRY...CATCH would be better approach. More details here

Agree with Lynn. Check if the ANSI_NULLS and QUOTED_IDENTIFIER options had been set to ON when the View was created.