there are some procedure u can use thier output:

1- sp_helplogin

2- sp_change_users_login

if u killed a process its statment will be rolled back, so u dont have to wory that much.

but if the code have "begin transaction and commit transaction" if u...

go there u will find a good one.

http://www.sqlfarms.com

can u copy the step code and execute it manauly, so u can make sure about the problem in the step code or in the agent.

use sql server 2005 help to search for DDL trigger its all u need.

and u can search this site for audit tracing.

u cant get DTS this way u have to get them some how.

if u want to track every statments runs by a user u could use traces,

if u want to track drop or creating database object like table u can use database...

this trigger will not fire until u insert a value in it, so the trigger on this one (master..log_tbl )

want help getting what u want.

if thats was the problem then the procedure will generate an error even before the built index.

i have one question how the SQL Server Agent Service account were locked out.

u can open the package from the Visual studio that installed with SQL 2005, and open project, then select the backage.

u can do what ever u want there..

have u tryed BackupOperator role, and u can check if there is a deny any were in those roles.

dont prevent the user from doing so, and i dont think that u can prevent a DB Admin from droping a sp.

but u can make the DDL trigger to recreate...

try to fix IIS, and change ur IP, reinstall network driver..

if u hadnt find the reason stop wasting time and reinstall windows.

have u checked the service account u might need to retype the password or change the service account user.