Have you gone thru the following suggestion from Tibor-

It is an errorlog file for the SQL server Agent service. The fact that it is so big in size is worrying....

Do you see this user entry in sp_helpuser output(Users Column)?

sp_helpuser

I did the same on my instance and it is working fine as user is listed out there.

Or Try this:

...

Is this database migrated or came from Microsoft Access?

MJ

I suspect it has do to something with database collation. Also, check sys.objects view results to verify the tablenames there.

Are they having [] in their name in sys.objects too?

MJ

What is the table name here? Is it a sql reserved keyword?

MJ

Steve, Thanks for your prompt reply. Yep I was asking for some major bullet points that need to be considered prior to migration.

I got that from ur reply(windows authenticated logins...

Declare @BytesUsed Varchar(1000),

@BytesFree Varchar(1000),

@TotalBytes BIGINT,

@IDENTITY INT,

@drive Char(1),

@sql Varchar(1000)

SET NOCOUNT ON

Create table ##DiskSpace ( Drive Char(1), TotalSpace Bigint, FreeSpace Bigint,

PercentageFree as (FreeSpace*100 / TotalSpace...

Go thru this link once which says "You cannot restore system database backups to a different build of SQL Server":-

http://support.microsoft.com/kb/264474

HTH

MJ

Are you opening TCP port on your local machine or on remote server? Is the 2005 instance you are trying to access is name instance or default one?

Manu

You can use the following code:

declare @Command as varchar(5000)

set @Command = 'C:\Progra~1\winzip\wzzip.exe "H:\SQLBKUP\test.zip" "H:\SQLBKUP\test.txt"'

exec master.dbo.xp_cmdshell @Command

Make sure that 'C:\Progra~1\winzip\wzzip.exe "H:\SQLBKUP\test.zip" "H:\SQLBKUP\test.txt"' is a single long statement in one line(no line...

Go thru this link once:

http://www.databasejournal.com/features/mssql/article.php/3556461

HTH

MJ

You can make use of xp_cmdshell under execute sql task under dts package:

cd "directory path where file that need to be zipped is placed"

"C:\Program Files\WinZip\wzzip.exe" -sPassword -ee -yc zipfilename.zip filethatneedstobezippedname

MJ

Okie. Try this leave login name in uppercase(as configured under AD) and change username(currently it would be all uppercase) to have letters in lowercase.

Hope this helps..

MJ

SQL installation in your case is case sensitive one. Change job owner from N'EBE\HBUCKNER' to N'EBE\hbuckner' and then try executing the job again.

MJ

Try using sp_droppublication(if publication still exists), sp_dropsubscriber and sp_removedbreplication stored procedures on publisher.

MJ