Running a trace is a good option. But ensure that you are running a server side trace. Here[/url] is an example.

It worked for me on all versions of SQL server and both 32 bit and 64 bit. The TID that you were trying to use in select * from sys.processes...

Now try to register the DTS.dll using regsvr32.exe.

The path is C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll

You may find this useful.

On a dedicated SQL server box, I usually set the max memory to 80% of the Total Physical RAM available.

Check if running sysdbupg script helps. Refer this

Check for any SQL related installation...

Check for excessive locks on MSDB database

Is this an option?

Detach those databases

Connect to SSMS as SA

Attach the databases using CREATE DATABASE...FOR ATTACH

The SQL Server Configuration Manager and the Services console would list all the SQL related services already installed on the server.

To find table names through t-sql one needs permissions on some of the sys*.* tables. Here[/url] is an example.

If you are using WITH NOINIT only one...

dbadotraghu (9/27/2010)

---

Hi Pradeep

As soon as I stop the trace, the file size grows to 128KB and the content of the trace file will be.. "The trace has been stopped"....

Ali,

Please look into the SQLSetupNumber_ServerName_Core(local).log file. Most likely this error has something to do with the folder layout. Please refer this article.

Agree with Jeffrey. If you are using Maintenance Plan to backup the database, it will create a file for each run. Here is a step by step guide to create...