SSIS package not executing on the server but runs fine on my computer...
-
Hi all. I have this SSIS package. It is running on my computer without any problems... not even warnings. When i try to run it on the server... i get this:
Message Executed as user: TEST\TESTadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:45:04 PM Progress: 2008-01-03 15:45:16.77 Source: Create File and insert header Validating: 0% complete End Progress Progress: 2008-01-03 15:45:16.78 Source: Create File and insert header Validating: 50% complete End Progress Progress: 2008-01-03 15:45:16.78 Source: Create File and insert header Validating: 100% complete End Progress Progress: 2008-01-03 15:45:16.80 Source: DataInfo Validating: 0% complete End Progress Progress: 2008-01-03 15:45:16.83 Source: DataInfo Validating: 50% complete End Progress Progress: 2008-01-03 15:45:16.88 Source: DataInfo Validating: 100% complete End Progress Progress: 2008-01-03 15:45:16.88 Source: HeaderInfo Validating: 0% complete End Progress Progress: 2008-01-03 15:45:16.89 Source: HeaderInfo Va... The package execution fa... The step failed.i dont know why... but it is failing and i cant determine why ??? any help would be greatly appreciated :(("Many of life's failures are people who did not realize how close they were to success when they gave up." Thomas A. Edison
-
Hi all. I have this SSIS package. It is running on my computer without any problems... not even warnings. When i try to run it on the server... i get this:
Message Executed as user: TEST\TESTadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:45:04 PM Progress: 2008-01-03 15:45:16.77 Source: Create File and insert header Validating: 0% complete End Progress Progress: 2008-01-03 15:45:16.78 Source: Create File and insert header Validating: 50% complete End Progress Progress: 2008-01-03 15:45:16.78 Source: Create File and insert header Validating: 100% complete End Progress Progress: 2008-01-03 15:45:16.80 Source: DataInfo Validating: 0% complete End Progress Progress: 2008-01-03 15:45:16.83 Source: DataInfo Validating: 50% complete End Progress Progress: 2008-01-03 15:45:16.88 Source: DataInfo Validating: 100% complete End Progress Progress: 2008-01-03 15:45:16.88 Source: HeaderInfo Validating: 0% complete End Progress Progress: 2008-01-03 15:45:16.89 Source: HeaderInfo Va... The package execution fa... The step failed.i dont know why... but it is failing and i cant determine why ??? any help would be greatly appreciated :(("Many of life's failures are people who did not realize how close they were to success when they gave up." Thomas A. Edison
You haven't provided enough information to determine what the problem is. Look at the contents of the output window. The details of the error should be listed there.
Paul Marfleet "No, his mind is not for rent To any God or government" Tom Sawyer - Rush
-
You haven't provided enough information to determine what the problem is. Look at the contents of the output window. The details of the error should be listed there.
Paul Marfleet "No, his mind is not for rent To any God or government" Tom Sawyer - Rush
i dont know where you see output window??? what i have posted to you is what i can see in "Right Click on a job in sql > View History" then you see the log file viewer... But thank you any way... it was a security issue... i managed to get past the problem by changing the path in a file from \\servername\a$\... to a:\..... and now it is working fine... (the servername was the name of the server that the job was executing on.) thank you any way.
"Many of life's failures are people who did not realize how close they were to success when they gave up." Thomas A. Edison
-
i dont know where you see output window??? what i have posted to you is what i can see in "Right Click on a job in sql > View History" then you see the log file viewer... But thank you any way... it was a security issue... i managed to get past the problem by changing the path in a file from \\servername\a$\... to a:\..... and now it is working fine... (the servername was the name of the server that the job was executing on.) thank you any way.
"Many of life's failures are people who did not realize how close they were to success when they gave up." Thomas A. Edison
Support123 wrote:
i dont know where you see output window???
Sorry, I assumed that you were using Visual Studio to run the package. If you were, the output window would have provided details of the error.
Paul Marfleet "No, his mind is not for rent To any God or government" Tom Sawyer - Rush
-
Support123 wrote:
i dont know where you see output window???
Sorry, I assumed that you were using Visual Studio to run the package. If you were, the output window would have provided details of the error.
Paul Marfleet "No, his mind is not for rent To any God or government" Tom Sawyer - Rush
you must debug your SSIS package on Server exactly with Business Intelligence Development Studio This is because there are some problems and error on SSIS packages that you don't aware of them before debugging your package on server, same as pinging an IP from Server that you can't see IP from server but when you try this from your PC this may be correct.
Human knowlege belongs to the world
-
you must debug your SSIS package on Server exactly with Business Intelligence Development Studio This is because there are some problems and error on SSIS packages that you don't aware of them before debugging your package on server, same as pinging an IP from Server that you can't see IP from server but when you try this from your PC this may be correct.
Human knowlege belongs to the world