November 18, 2014 at 1:19 am
Hi All,
While executing one of package in PROD environment we are getting below error.
component "OLE DB Source" could not be created and returned error code 0x800703FA. Make sure that the component is registered correctly]
Any idea, how to resolve that ?
The package is scheduled by Trivoli and calling batch files.Also we have tested the packages in all non-prod environments successfully.
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
November 18, 2014 at 1:26 am
Which OLE DB provider are you using in the source?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 18, 2014 at 1:51 am
Koen Verbeeck (11/18/2014)
Which OLE DB provider are you using in the source?
Native OLE DB\SQL Server Native Client 10.0
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
November 18, 2014 at 1:54 am
Did you try to do a repair of the SSIS installation?
Or maybe remove it and install it again.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 18, 2014 at 2:27 am
Koen Verbeeck (11/18/2014)
Did you try to do a repair of the SSIS installation?Or maybe remove it and install it again.
Not yet Koen.Actually this is PROD server and not maintained by us. However I am wondering how the installation can affect it. Also this packages was executing fine since last two weeks.
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
November 18, 2014 at 2:28 am
rhythmk (11/18/2014)
Koen Verbeeck (11/18/2014)
Did you try to do a repair of the SSIS installation?Or maybe remove it and install it again.
Not yet Koen.Actually this is PROD server and not maintained by us. However I am wondering how the installation can affect it. Also this packages was executing fine since last two weeks.
It's possible the DDL got corrupt or something like that.
Any changes to the server the last two weeks?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 18, 2014 at 3:18 am
Koen Verbeeck (11/18/2014)
rhythmk (11/18/2014)
Koen Verbeeck (11/18/2014)
Did you try to do a repair of the SSIS installation?Or maybe remove it and install it again.
Not yet Koen.Actually this is PROD server and not maintained by us. However I am wondering how the installation can affect it. Also this packages was executing fine since last two weeks.
It's possible the DDL got corrupt or something like that.
Any changes to the server the last two weeks?
DDL got corrupt ?
Yes.Just got to know that one patch was installed last week i.e. Vulnerabilities in Windows OLE Could Allow Remote Code Execution (3011443)
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
November 20, 2014 at 12:42 am
Interestingly the package executed successfully twice after the failure without any fix.But it failed again with same error 🙁
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
November 21, 2014 at 3:25 pm
rhythmk (11/18/2014)
Koen Verbeeck (11/18/2014)
Did you try to do a repair of the SSIS installation?Or maybe remove it and install it again.
Not yet Koen.Actually this is PROD server and not maintained by us. However I am wondering how the installation can affect it. Also this packages was executing fine since last two weeks.
Although not administered by you any fix I think would require a redeploying the solution to the package store if that is where your packages repository is (if you maintain source control especially). I would drop that Ole DB source and re-create it. Then save and re-deploy to the server. At least that is where I would start. Interesting that a native control gave this error.
----------------------------------------------------
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply