web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

BYOD export error - SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.

(0) ShareShare
ReportReport
Posted on by

Hi All,

On one of sandbox, we have setup BYOD export. suddenly it has started failing with this error.

The export job is scheduled to run for every hour and it normally runs for 2-3 minutes. but since yesterday it has started taking 4 hours and then fails with below error.  It is incremental push on data entity.

During this 4 hours, we checked the SQL and there are no Locking and also query shows 'Running'. but after few hours it fails somehow. There is nothing from our side we changed. 

Can someone please help understand what could have gone wrong? We are thinking to raise MS Support case but thought to ask experts here if we can fix it in case it is easier solution.

This data entity is credit card transactions which is biggest table in our database and we are not in position to republish entity as it will take days to migrate all the data again in entity store. 

<?xml version="1.0"?><Errors><Error><ErrorCode>-1071636471</ErrorCode><SubComponent>Oledb Source [179]</SubComponent><Description>SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 11.0"  Hresult: 0x80004005  Description: "Unspecified error".</Description></Error><Error><ErrorCode>-1073450982</ErrorCode><SubComponent>SSIS.Pipeline</SubComponent><Description>Oledb Source failed the pre-execute phase and returned error code 0x80004005.</Description></Error></Errors>

Regards,

Vikky

I have the same question (0)
  • Suggested answer
    Mea_ Profile Picture
    60,284 on at

    It could be Violation of PRIMARY KEY constraint, so check key on that entity and make sure there are no duplicates in the data.

  • WillWU Profile Picture
    22,361 on at

    Hi IamVikky,

    Please check the indexes of your staging table.  If indexes are set to not allow duplicates, maybe there are duplicate data in the table.

  • Tom De Walsche Profile Picture
    5 on at

    Hi Vikky,

    We are encountering this issue also on our production environment since we went to PU42. Did you already found the root cause of this issue ?

    It seems like the problem is now solved by removing the data entities from old data projects and adding them to new onces. But I would be very happy to understand the underlying reason.

    BR

    Tom

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 522 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans