Get Data Moving 1
Results 1 to 5 of 5

Thread: SQL Server linked server "Provider caused a server fault in an external process"

  1. #1
    bugmeister is offline Junior Member
    Join Date
    Apr 2008
    Posts
    4
    Rep Power
    0

    SQL Server linked server "Provider caused a server fault in an external process"

    Hi,

    We are currently running the following configuration:

    Attunity Server

    Server OS: AIX 4.3
    Server Attunity: 5.0.1.0
    Server DB: DISAM

    SQL Server

    Server OS: Windows Server 2008 R2
    SQL Server version: 2008 R2

    We have various SQL Server linked servers using the Attunity OLE DB provider. They work fine for SELECT queries and some UPDATEs, but for instance INSERTing from SQL Server using the linked server throws this error:

    Msg 7399, Level 16, State 1, Line 1
    The OLE DB provider "AttunityConnect" for linked server "BRZDATA" reported an error. Provider caused a server fault in an external process.
    Msg 7306, Level 16, State 2, Line 1
    Cannot open the table "XMESS" from OLE DB provider "AttunityConnect" for linked server "BRZDATA". Unknown provider error.

    You can run a SELECT from XMESS table using the linked server without problem. An example insert query (this one I have cast to the server's data types, but it work doesn't work either way):

    insert into BRZDATA...XMESS (XM_GROUP, XM_CODE, XM_MESSAGE)
    values (cast('A1' as CHAR(2)), cast('AAA' as CHAR(3)), cast('AAAA' as CHAR(75)))

    The XMESS table is simple with XM_GROUP = STRING(3), XM_CODE = STRING(3) and XM_MESSAGE = STRING(75). And the insert isn't conflicting with any unique keys etc.

    The INSERT error happens for it seems all tables.

    We did not have an issue on Windows Server 2003 R2 with SQL Server 2005.

    Any ideas?

    Thanks in advance,
    Peter

  2. #2
    bugmeister is offline Junior Member
    Join Date
    Apr 2008
    Posts
    4
    Rep Power
    0
    Here are some events from the Windows event log corresponding to the INSERT error:

    Faulting application name: DllHost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bca54
    Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
    Exception code: 0xc0000005
    Fault offset: 0x00000000000526c6
    Faulting process id: 0x898
    Faulting application start time: 0x01cbd257811ee7b2
    Faulting application path: C:\Windows\system32\DllHost.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: bf70dc56-3e4a-11e0-a91c-005056954562

    --- and ---

    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: DllHost.exe
    P2: 6.1.7600.16385
    P3: 4a5bca54
    P4: ntdll.dll
    P5: 6.1.7600.16559
    P6: 4ba9b802
    P7: c0000005
    P8: 00000000000526c6
    P9:
    P10:

    Attached files:

    These files may be available here:
    C:\Users\admin\AppData\Local\Microsoft\Windows\WER \ReportQueue\AppCrash_DllHost.exe_3240b6dbcae8731b 17b85f43a2c1215765738_1f67098e

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: bf70dc56-3e4a-11e0-a91c-005056954562
    Report Status: 4

  3. #3
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    11
    Hi Peter,

    By default, linked servers are created in "Allow In Process" mode, which means that the provider shares the SQL Server resources. We have seen some problems running in this mode so, one thing to try is to run the provider in "Out of Process" mode. To do that:
    • Create a new Linked Server.
    • Click on the "Provider Options".
    • Uncheck the "Allow In Process" checkbox.

    If that didn't help, check the Attunity client and server log files under the Attunity installation TMP folder.


    Regards,

    Gadi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  4. #4
    bugmeister is offline Junior Member
    Join Date
    Apr 2008
    Posts
    4
    Rep Power
    0
    Thanks for the reply Gadi.

    We are actually already operating with "Allow On Process" unticked as previously we had stability issues with SQL Server when it was ticked.

    I checked the nav.log file and it has these errors (seemingly linked to the insert error) - hadn't seen them before as they seem to only stay in the log for a short time:

    [8026] IDBSchemaRowset: Schema is not supported or invalid - 'DBSCHEMA_CHECK_CONSTRAINTS_BY_TABLE'.
    [8026] IDBSchemaRowset: Schema is not supported or invalid - 'DBSCHEMA_TABLE_STATISTICS'.

    Any ideas?

  5. #5
    Costi Zaboura is offline World Wide Support Manager
    Join Date
    Aug 2006
    Posts
    300
    Rep Power
    14
    Hi

    I think at this stage we are need to enable several debug flags to better understand the problem..
    I stronlgly recommend that you conatct your local Attunity support team to help you further with that.


    best regards
    Costi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •