|
Hi All, I have a simple data flow task that reads data from a table and adds the source to a recordset destination. Unfortunately, the task fails with the error; Error: 0xC020207C at Data Flow Task, Recordset Destination [52]: Unable to create or configure the ADODB.Recordset object. Error: 0xC004701A at Data Flow Task, DTS.Pipeline: component "Recordset Destination" (52) failed the pre-execute phase and returned error code 0x80040154. I know the package works because I have used it on another PC and it works perfectly...So it must be a configuration on my PC somewhere. If anyone has any ideas, I thank you in advance. Dan.
(comments are locked)
|
|
Just a load of questions I'm afraid:
This looks close to your scenario http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/a4fc47b9-d029-4e7c-952d-9e9f666cf2e8/ @Jonathan Allen... This error has been driving me crazy.Help me out! 1. Yes .Logged on as the same user 2. I am logged in as Admin, so permissions would not be an issue. 3. I am executing my package using Command Line. 4. And all my hardware are 64 bit.
Apr 09 '12 at 04:51 AM
mverma
@mverma Seems like there is definitely some configuration issue but you did not mention that the environment are the same. You must make sure that the environments are exactly the same. A difference in Service Pack/ CU can also lead to such problems. For e.g. I hope you are not using ADODB.dll as a reference which has been moved into some other. Please make sure that all the referenced DLLs in the project are available on the specific server and placed in the appropriate folders. Since, we do not know much details, we cannot give you a specific answer.
Apr 09 '12 at 07:12 AM
Usman Butt
(comments are locked)
|
|
I actually am trying to execute my package remotely. When I execute it directly on the local machine(server 1), it works just fine. But when I try to execute it from some other server(server 2), by sending dtexec command from that server 2 to server 1, this error happens. The scenario that I described here,as I understand,executes the package on Server 1 itself .So the two servers need not be of same configuration. PS:To execute my package remotely,I am using psexec. @mverma I do not know much about the internals of psexec. But you need to keep in mind that Recordset destination makes an in memory object and seems like it is tried to be made on the server you are trying to execute the package remotely. I am not too sure, but depending upon your script to fetch data from recordset you may need to install MDAC which is compatible to your targeted SQL Server on the server from which you want to execute the package. And in future, please add every detail you can provide, so the root cause could be identified promptly. This way you would be able to save your precious time.
Apr 09 '12 at 09:47 AM
Usman Butt
Sorry, I forgot the important .NET framework installation. But that all depends upon the environment.
Apr 09 '12 at 10:22 AM
Usman Butt
(comments are locked)
|
|
Thanks for the prompt replies @Usman , I really appreciate your help. And yes, from now on I will provide the whole details. I have sorted out the problem. Your answer had the clue. I was using an In memory Recordset object, which was not accessible from the remote location. All I had to do was to tell the psexec to Load the User's Account profile and not use the System Account and the package executed like a charm!! Glad to know that it helped :) Also, I appreciate sharing your findings.
Apr 09 '12 at 11:16 AM
Usman Butt
(comments are locked)
|
