Cross posted. All replies here

Please go through the Summary.txt file located on C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\LOG. It will the detail about which component failed.

In the Cleanup task did you enter .bak instead of bak as file extension?

You may use sp_CompareDB posted in this discussion.

If DAC is also not an option, as Henrico suggested try connecting to the instance using startup account credentials.

These examples should get you started.

http://blog.netnerds.net/2008/02/create-a-basic-sql-server-2005-trigger-to-send-e-mail-alerts/%5B/url%5D

http://www.datasprings.com/Resources/ArticlesInformation/CreatingEmailTriggersinSQLServer2005.aspx

Does the "test" user have permissions on AuditDatabase database?

In that case you need to Open the maintenance plan and click on Save to update the MP to use the existing databases.

Other option is to use a custom script...

Glad to know that the issue is resolved.

This means there is an open transaction on Tempdb.

I have not come across any performance issues because of creating SQL Logins back to back

Like mentioned earlier this article has a script for fixing Maintenance Plans.

Does these queries give you any output? If not, try shrinking tempdb now.

SELECT * FROM sys.dm_exec_requests WHERE database_id = 2

go

select * from sys.dm_tran_locks where resource_database_id=2

go

Since you are able to execute that file under the credentials of service account, permissions issue is ruled out.

Does the folder or file has spaces in between or the length...

Did you try launching the exe under the credentials of the service account (by logging on to the server using service account / using "Run as" for the exe)