fail component error notification

I have created a package which forms data from flat file to sql database.I have a data flow where all my data is processed to destination.if the package fails by any chance i want an email notification with the cause of the error.how can i do this.please let me know..I'd start with Send Mail task and the OnError event handler for the package.|||Will i be able to send mail with the list of errors occured if the do the above|||Can you specify your goal in more detail? Do you want one email with all errors listed? Do you want all errors, or just the primary error that caused the package to fail?|||I want all the errors in one email.|||

This post might help:

http://agilebi.com/cs/blogs/jwelch/archive/2007/05/05/handling-multiple-errors-in-ssis.aspx

I created an example that uses a Script task in the OnError event to collect all the errors, and then uses a second Script task in the OnPostExecute event to process them. You could simply add a Send Mail task to the OnPostExecute to send the email.

Extranet Thick Client Connection

Hi,
I have a Windows Forms application that uses ADO.NET 1.1 to communicate with SQL Server 2K. I would like to start retailing my Windows app, allowing clients who are not in my domain or work-group to communicate with a database on MY SQL Server using Wind
ows Integrated Authentication. Can I get some guidance on exactly how this would be done please?
JT
Windows Authentication without a domain means you're using Workgroup
Security. This essentially requires you to duplicate nt user accounts and
passwords on both machines. This will work with Named Pipe connections.
It will not work with Sockets.
I'd recommend securing the traffic with SQL's protocol encryption. You'll
need a server certificate installed on the SQL Server.
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thanks Kevin - I appreciate it. How do you communicate with Named Pipes over the internet? My clients would be at sites far remote from my SQL Server(s). Would I have to have a VPN? Would exposing SQL Server as a Web Service be an option?
JT
"Kevin McDonnell [MSFT]" wrote:

> Windows Authentication without a domain means you're using Workgroup
> Security. This essentially requires you to duplicate nt user accounts and
> passwords on both machines. This will work with Named Pipe connections.
> It will not work with Sockets.
> I'd recommend securing the traffic with SQL's protocol encryption. You'll
> need a server certificate installed on the SQL Server.
> 276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
> Server
> http://support.microsoft.com/?id=276553
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||You would not use Named Pipes over the internet. The ports required for it
to work would make your
firewall insecure.
If you're remote clients are VPNing in, then I would think that they'd also
would be authenticating
against a DC. So, after they've done this they should be able to use
Windows Auth to SQL.
If you're clients are coming from an Extranet, do you have a 1 way Trust
between machines there and your other domain?
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Extranet Thick Client Connection

Hi,
I have a Windows Forms application that uses ADO.NET 1.1 to communicate with
SQL Server 2K. I would like to start retailing my Windows app, allowing cl
ients who are not in my domain or work-group to communicate with a database
on MY SQL Server using Wind
ows Integrated Authentication. Can I get some guidance on exactly how this
would be done please?
JTWindows Authentication without a domain means you're using Workgroup
Security. This essentially requires you to duplicate nt user accounts and
passwords on both machines. This will work with Named Pipe connections.
It will not work with Sockets.
I'd recommend securing the traffic with SQL's protocol encryption. You'll
need a server certificate installed on the SQL Server.
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin - I appreciate it. How do you communicate with Named Pipes ove
r the internet? My clients would be at sites far remote from my SQL Server(
s). Would I have to have a VPN? Would exposing SQL Server as a Web Service
be an option?
JT
"Kevin McDonnell [MSFT]" wrote:

> Windows Authentication without a domain means you're using Workgroup
> Security. This essentially requires you to duplicate nt user accounts and
> passwords on both machines. This will work with Named Pipe connections.
> It will not work with Sockets.
> I'd recommend securing the traffic with SQL's protocol encryption. You'll
> need a server certificate installed on the SQL Server.
> 276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
> Server
> http://support.microsoft.com/?id=276553
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||You would not use Named Pipes over the internet. The ports required for it
to work would make your
firewall insecure.
If you're remote clients are VPNing in, then I would think that they'd also
would be authenticating
against a DC. So, after they've done this they should be able to use
Windows Auth to SQL.
If you're clients are coming from an Extranet, do you have a 1 way Trust
between machines there and your other domain?
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.