Hello again,

Did you ever get to the bottom of your issue?

If so, could you post the resolution?

If not, in which of the msdb items views did your test mails...

Hello again,

One possible way to force the Wizard to use Named Pipes to connect to your SQL 2000 Server would be to use SQL Server Configuration Manager to create a...

Hello,

Do you have a valid backup for the DB? (Is it a Production or Dev/Test DB?)

I ask because it is generally recommended to repair errors by restoring from backup rather...

Hello,

I just wanted to check how you are performing the migration e.g. are you using the Migration Wizard and then manually “fixing” the parts that are not converted? Is the...

Hello,

Are the lengths of any of the fields likely to change? If so, you would then have to redefine your Fixed Length file definition. So may be Delimited would be...

Hello again,

I assume it would work if Named Pipes is the first enabled Client Protocol. (You can set the order via the Properties of the Client Protocols node in SQL...

Hello again,

No TCP/IP is not enabled, but my question was when "named pipe" protocol is enabled, it should work when we choose both "both TCP/IP and Named Pipes" protocol. but...

Hello again,

I assume you are connecting from SSMS 2005? Is TCP/IP enabled on this Server?

A couple of things to check:-

1) Is there a firewall between the SQL 2005 and SQL...

Hello,

It might be worthwhile running through the Steps in the following Troubleshooting Guide (if you haven’t already):-

http://www.sqlhacks.com/index.php/Administration/Database-Mail-Troubleshooting

Regards,

John Marsh

Hello,

Can you post the full error message? Especially the Error, Level, State part as that is helpful in tracking down the root cause.

Regards,

John Marsh

Hello Mahesh,

Please see my additional comment above about the OpenRowSet workaround.

Another option would be to gather the data directly from the msdb.dbo.sysjobXXXXX Tables/Views.

Regards,

John Marsh

Hello Mahesh,

You will need to specify a value for the “Job_Aspect” parameter

e.g Exec msdb.dbo.sp_help_job Null, 'job_name', ‘JOB‘

In which case the SP will return only one result set.

Having just tested...

Hello Mahesh,

Are you executing the SP from the msdb DB?

e.g Exec msdb.dbo.sp_help_job Null, 'job_name'

If so, what error do you get?

Regards,

John Marsh

Hello Sam,

Generally speaking it is preferable to filter records at the Server, particularly in order to reduce Network Traffic.

A slight alternative to Lynn Pettis’s suggestion would be to have a...

Hello Jon,

SQL Server Express (2005 & 2008) defaults to Dynamic Ports, whereas the Default Instance of other Editions listen on Static Port 1433 (by default).

Having a Zero in the...