Looks like you have not used the Configuration Manager to change the service account. Refer this

Change the service account using Configuration Manager. This should fix this issue.

Locking a login feature is not available in SQL Server 2000. Alternatively you can DENY LOGIN permissions for that login.

This link [/url]has almost all the scripts that a DBA ever needs.

This will not create the backup file at default location. It depends on what is the value of...

Use sqlcmd.exe to execute the query and name the ouput file as .csv. Refer this

Add an output file to the job step to get more details on the failure.

You may use the parameters mentioned here inside the VBScript.

There is no direct way of doing this. However, the following modification in the Registry works for you.

Caution: Modifying the registry can have serious impacts. Ensure to have proper...

The SQLAGENT.out file should have more details as to why it failed. This file is usually located at

[Installation Drive]\Microsoft SQL Server\MSSQL.1\MSSQL\LOG

Yes the datatypes. Also found this information. You may try the workaround.

Here is the note from MSDN

C2 audit mode saves a large amount of event information to the log file, which can grow quickly. If the data directory in which logs...

Try entering the actual instance name in "ServerHost" under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\SQLServerAgent

in registry.

Use ALTER LOGIN in conjunction with the above query to turn on CHECK POLICY

This provides you many options.

It depends on with what error the copy job is failing.