It is an internal procedure call. Most likely associated with sys.sp_rename. Refer this

What is the build of SQL Server? If it is below SQL Server 2005 SP2, then the Maintenance Plans are dependent of SSIS. In that case you may want to...

Does the...

Does the C drive has enough space? Also cleaning up the temp directory of the SQL Server service account should help.

It is usually located at

C:\Documents and Settings\[ServiceAccount]\Local Settings\Temp

There is some other process active on the database. You need to clear that connection before bringing the database into MULTI_USER mode.

I had discussed a similar issue here[/url]

I could not repro the issue on SSMS 9.00.4035. Which version of SSMS are you using?

Operating System Error 80 = The file already exists

How are you using xp_cmdshell? Can you please post the code snippet?

Open the Maintenance Plan

Click on "Manage Connections"

By default there will be a connection named "Local server connection"

Check if there are any other conflicting connections in the same window.

You can find out which process is using that file. An example explained here[/url]

The first line states that the tempdb is starting.

The second line states that the Recovery is Complete....

Schedule a transaction log backup. It ensures that the Transaction Log size is under check and most importantly provides point in time recovery option.

Read this article[/url] for more information.

This discussion would answer your question.

I have a SQL Server 2005, whose tempdb grows to 19.6G (which is very large in my case). I tried to shrink it, but failed. Although no one...

I second Derrick. Think there is a job which is trying to make the connection to SQL Server

Add an output file to the Job Step (under Advanced)

In the job script after each statemet (like -- Table to hold Price Changes etc.) add a PRINT statement like

PRINT 'Starting...