After migration of SQL from 2005 to 2008 all CSV file containing Comma (,) is not getting uploaded thro’ Client machine (Only SSIS client components are installed) though the same file is getting uploaded successfully on database server (Both Server and client components installed). Let me explain the architecture first, Machine A is the database server in which complete SQL 2008 is installed. Machine B is Client machine in which only SSIS Client components are installed. Front end is developed in VB.Net which is on Machine B. SSIS Package is on Machine A. Now the file is not getting uploaded through Machine B but when I copied the same front-end on Machine A the same file is uploaded successfully. There is no issue in uploading a CSV file without comma (,) on both machines. This implies that there is some problem with SSIS Client Components?

Now the file is not getting uploaded through Machine B but when I copied the same front-end on Machine A the same file is uploaded successfully. There is no issue in uploading a CSV file without comma (,) on both machines. This implies that there is some problem with SSIS Client Components? When you say not getting uploaded, what error do you get? I do not think you have an issue with SSIS C.C. (I guess you mean you referenced SSIS DLLs when built your VB app).Arthur My Blog

There are no such things as "SSIS Client Components". That implies there's a set of server components, and that's not the case. There is simply the "SSIS Component". What exactly do you have installed on Machine B? How is your VB.Net application starting execution of the SSIS package? Talk to me now on