Linked server error 7303

Good morning,
I created a linked server to
access sql server 2008.
At first everything worked properly,
now returns the error 7303.
I have already shared the folder with all
of the database permits users full control
of sql server users , users of
the system, etc..
Does anyone know how can you fix?
I found a solution on the Internet,
says to create an Admin user
on the machine, and as a path
to a temporary folder on your
hard disk different from the profile, by entering
the required permissions to SQL Server, but not
seems to work after a while let us start, however,
to return the error 7303.
i found if i drop linked server , restart pc and reacreate it , it work , but when i restard pc all return error 7303.
SQL Version : 10.0.2573
Thanking you in advance,
GR

Hi Normand!,
Access db its a 97 version converted into 2000.
If i run a select statement(select * from TEST...TAB_EAN from SSMS error is(italian version):
Il provider OLE DB "Microsoft.Jet.OLEDB.4.0" per il server collegato "TEST" ha restituito il messaggio "Errore non specificato.".
Messaggio 7303, livello 16, stato 1, riga 1
Impossibile inizializzare l'oggetto origine dei dati del provider OLE DB "Microsoft.Jet.OLEDB.4.0" per il server collegato "TEST".
I've read the link you provide but without success.
The linked server use the provider: Microsoft.Jet.OLEDB.4.0
GR
update:
I tryed to use sql server with user Local System , i can create the linked server  and use it, but if i restart the pc and restart the sql server service, i have the the same error (7303)

Similar Messages

  • SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

    Hi all,
    I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
    System specification:
    Windows server 2012 64 bit
    SQL SERVER 2012 64 bit
    REMOTE SERVER SQL 2000 32 bit
    I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
    Create a linked server with the query below in SQL 2012:
    EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
    EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
    GO
    but when i browse the linked server i receved error 7303.

    You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
    However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
    SQLNCLI11 - does not support connections to SQL 2000.
    SQLNCLI10 - failed with some obscure message that I don't recall.
    SQLNCLI - Don't recall that the problem was here.
    SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
    I don't think I got through all version of the ODBC drivers, though.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Hadoop ODBC linked server error: Specified driver could not be loaded due to system error 182

    Hi,
    I am trying to connect to a Hadoop server through a linked server in SQL Server. I downloaded and installed the Microsoft Hive ODBC driver - HiveODBC64.msi. But while I am trying to create the Linked server using this ODBC driver I am getting below error.
    " Specified driver could not be loaded due to system error 182 (Microsoft Hive ODBC driver, D:\....\HiveODBC64.dll). (Microsoft SQL Server, Error: 7303)"
    When I tested it locally and in another server, it is working properly. I am getting this error only in this server. looks like a dll error. But cannot identify where/what is the error. Could someone help me fix this issue.
    Server info:
    OS Name: Microsoft Windows Server 2008 R2 Enterprise Version 6.1.7601 Service Pack 1 Build 7601
    SQL SERVER: Microsoft SQL Server 2008 R2(SP1)

    Hi LinkedServer,
    According to your description, you want to create linked server to connect to a Hadoop server in SQL Server, and you have created it successfully in the test server, the problem is that you get the issue in the production environment, right?
    Based on the error message, as you said it seems that the issue is related to the HiveOBDC64.dll assembly. Since you have done it on the test server, you can copy and replace HiveODBC64.dll to production server in the C:\Program Files\Microsoft Hive ODBC
    Driver\lib directory. Or you can reinstall the Microsoft Hive ODBC driver. Here is a blog which describe how to create a SQL Server Linked Server to HDInsight HIVE using Microsoft Hive ODBC Driver step by step, please refer to the link below to double check
    if your steps are correct.
    http://blogs.msdn.com/b/igorpag/archive/2013/11/12/how-to-create-a-sql-server-linked-server-to-hdinsight-hive-using-microsoft-hive-odbc-driver.aspx
    Regards,
    Charlie Liao
    TechNet Community Support

  • Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

    Hi All,
    Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error  when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
    instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account. 
    'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' 
    Appreciate your quick response. 
    Vikas.M.S

    Hello,
    Please read the following resources:
    http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Linked server error from sql server to oracle

    Hi
    Please help i am getting below error
    Problem Description: OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE10G" returned message "ORA-01403: no data found".
    Msg 7346, Level 16, State 2, Line 1
    Cannot get the data of the row from the OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE10G".
    Platform details
    SQl server end
    =====================
    SQl server version :2005
    Oracle client version :10.2.0.1.0
    sql server Platform:widow server 2003 standard edition 32 bit
    ===========================
    oracle server end
    * DB Server = 10.2.0.4
    * Platform = IBM AIX
    AIX version=5.3
    Regards

    Hi,
    This forum is for connecting to non-Oracle databases from Oracle.
    There is a specific forum for Oracle Provider for OLE DB so it would be better to ask the question in that forum -
    Oracle Provider for OLE DB
    Regards,
    Mike

  • Like Server error Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'

     Getting error when trying to test the link server from remote ... Please help

    Hello,
    You've supplied us with little information other than what little is in the title. I'll refer you to a post I wrote about this. Please read
    through it and post back if it does not fix your issue. There are a few other resource links in the post to check out, but it's most likely related to a Kerberos/SPN issue.
    -Sean
    The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

  • Linked Server Error from SQL2008R2 to SQL2000

    I am trying to Execute Query/SP from my local machine which SQL 2008R2 To SQL 2000 32 bit. 
    Created Linked Server from Local machine to SQL2000 Machine..
    Query /SP run fine from SSMS but when I am trying to run through this below script keep giving me error .
    I converted Select query into SP 
     EXEC msdb.dbo.sp_send_dbmail
        @profile_name = 'SQL-MailAlerts',
        @recipients = '**********',
        @query = 'EXEC dbo.QueryResult',
        @query_attachment_filename = 'result.csv',
        @attach_query_result_as_file = 1,
        @body_format = 'text' ;
    Error :
    Msg 22050, Level 16, State 1, Line 0
    Error formatting query, probably invalid parameters
    Msg 14661, Level 16, State 1, Procedure sp_send_dbmail, Line 504
    Linked servers cannot be used under impersonation without a mapping for the impersonated login.
    Basically trying to get Query result from SQL 2000 Database into mail if anyone has better idea let me know.
    Thanks
    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

    Maybe you should read the posts before you reply? Logicinisde runs DB mail on SQL 2008R2, but is trying to retrieve data from SQL 2000 instances.
    SQL 2000 may be out of support, but that will not prevent users from keeping their instances around as long as needed. In some cases they may have no choice, because they are running a third-party system which does not support later versions of SQL Server.
    I have gathered that this is particularly common in the healthcare industry in the US.
    Hi Erland Sommarskog,
    Thanks for your suggestion, the scenario which you post is really to take into consideration. I suggest our customer upgrading the SQL Server version for helping resolve his issues which may be encountered on the SQL Server 2000. Thanks for your understanding.
    Thanks for your post again.
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Linked Server error - Msg 7311, Level 16, State 2

    We have three SQL Servers:
    SQL 2008 Instance w/ SP1 cumulative update #5; running on Windows Server 2008 r2
    SQL 2008 Instance w/ SP1 cumulative update #5; running on Windows Server 2003 r2
    SQL 2000 Instance w/ SP4; running on Windows Server 2003 r2 W/ SP2
    We have a linked server connection from #2 to #3, which works perfectly.  However, our linked server connection from #1 to #3 does not work.  here is the error message we get:
    OLE DB provider "SQLNCLI10" for linked server "CCSSQLTEST01A" returned message "Unspecified error".
    OLE DB provider "SQLNCLI10" for linked server "CCSSQLTEST01A" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".
    Msg 7311, Level 16, State 2, Line 1
    Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI10" for linked server "CCSSQLTEST01A". The provider supports the interface, but returns a failure code when it is used.
    I've read articles saying we may need to run a specific script on the server we are linking to, due to missing SPs, but how can that be possible if the other linked server connection works?  We are linking from two identical
    SQL Server instances (other than the OS)...
    The only other difference I know of, is that #1 was an upgrade from SQL 2005, but #2 was a clean install of SQL 2008.
    Suggestions? 
    Clint

    I really don't think this is the case otherwise in my .Net applications I'd have to determine the version of the target SQL server, then instantiate the appropriate connection object.  Things just don't work that way.   I'm pretty sure
    you will find that a SQL Native Client 10 provider can connect to anything from SQL 2008 and below, but not anything above (once it is released :).
    The real issue is given in the message. Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO"
    If
    you source server is 64 bit and your target is 32 bit then you will need to do the following.  (I have to pass credit to Kun Sik Lee of Costar Group for this one)
    create
    procedure sp_tables_info_rowset_64
         @table_name
    sysname,
         @table_schema    
    sysname =
    null,  
         @table_type
    nvarchar(255)
    = null
    as
    declare @Result
    int set @Result
    = 0
    exec @Result
    = sp_tables_info_rowset
    @table_name, @table_schema, @table_type
    GO
    use [master]
    GO
    GRANT
    EXECUTE ON [dbo].[sp_tables_info_rowset_64]
    TO [LinkServerUser]
    GO

  • Linked server error

    When I run below query its giving error:
       SELECT *
    FROM [P3FI.WORLD]..[ADHOC].[V_POSITION_FW]
    Msg 7356, Level 16, State 1, Line 1
    The OLE DB provider "OraOLEDB.Oracle" for linked server "P3FI.WORLD" supplied inconsistent metadata for a column. The column "CONFID_AGREEMENT_SIGNED" (compile-time ordinal 3) of object ""ADHOC"."V_CONTRACTOR_FW""
    was reported to have a "DBCOLUMNFLAGS_ISNULLABLE" of 0 at compile time and 32 at run time.
    When I run this query  
    select * from openquery([P3FI.WORLD],'select * from adhoc.V_CONTRACTOR_FW')  
    it runs fine
    Please suggest
    Best regards,
    Vishal

    What happens is that when SQL Server compiles the query, it interrogates the OLE DB provider about the metadata for the table, and the OLE DB provider appears to say that the column does not accept null. But later when the query is exectued, SQL Server is
    told that the column is nullable. SQL Server does not like being lied to, and drops out.
    This is not very simple to troubleshoot, at least not for an SQL Server person, because the prime suspect is the OLE DB provider, which comes from Oracle.
    However, there is one possibility where SQL Server is involved: Assume that this query already was in the cache, because someone ran it yesterday. Since then the column on the Oracle side was altered to permit NULL. When you do this inside SQL Server, all
    queries related to the table are flushed from the cache, but obviously this does not happen when you change a table on a different server.
    One way to test this is to run the query with a different query text (so that you don't get a cache hit), for instance:
    SELECT * FROM [P3FI.WORLD]..[ADHOC].[V_POSITION_FW] AS MyAliasNewOfToday
    (The cache lookup is from a hash of the query text.)
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Linked Server Error message

     Hi,
    I have 3 SQL servers, A, B, and C.
    i am able to establish a linked server from A to C and C to A
    i am able to establish a linked server from B to C and C to B.
    but when i try to establish a linked server from A to B, i have been getting this error, i am goin nuts because if there is any problem with A, then even C shud not ne able to connect but its connecting, if theres any problem with B , C shud not connect but its connecting.
    C is connecting to both A and B without errors.
    Also A is connecting to C and B is connecting to C.
    But the problem is between A and B Servers.
    when i test the connection from B to A i get this message,
    A is SQl 2000, B is 2008, c is 2008.
    Pls suggest wat do i do.
    Y is there a problem of connection between only A to B and B to A.
    While making a linked Server from B to A without using Security, i get the error
    The OLE DB provider "SQLNCLI10" for linked server "A" reported an error. Authentication failed.
    Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "A".
    OLE DB provider "SQLNCLI10" for linked server "A" returned message "Invalid authorization specification". (.Net SqlClient Data Provider)
    when i connect using the sa account i get the folowing error,
    VIA Provider: The specified module could not be found.
    OLE DB provider "SQLNCLI10" for linked server "A" returned message "Login timeout expired".
    OLE DB provider "SQLNCLI10" for linked server "A" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". (.Net SqlClient Data Provider)
    Thanks a Ton for any kind a help

    Muchas gracias por la ayuda con el problema:
    The OLE DB provider "SQLNCLI10" for linked server "A" reported an error. Authentication failed.
    Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "A".
    OLE DB provider "SQLNCLI10" for linked server "A" returned message "Invalid authorization specification".
    Esto me ayudo a resolverlo:
    https://sites.google.com/site/greateindiaclub/software-zones/database-community/sql-server/cannotinitializethedatasourceobjectofoledbprovidersqlncli10forlinkedserver
    Pero despues me apareció el siguiente problema:
    The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "B" was unable to begin a distributed transaction.
    OLE DB provider "SQLNCLI10" for linked server "B" returned message "El administrador de transacción ha deshabilitado su soporte para transacciones de red o remotas.".
    Y lo resolví con esto:
    EXEC sp_serveroption @server = 'ServerB',@optname = 'remote
    proc transaction promotion', @optvalue = 'false' ;
    Fuente:  http://www.sqlservercentral.com/Forums/Topic1102122-146-1.aspx#bm1102224
    Saludos...
    Desarrollador en .NET

  • Error when creating a linked server to IBM iSeries AS/400

    I am migrating databases from SQL Standard 2005 (32 bit) to SQL Standard
    2012 (64 bit) and getting errors when I create the needed Linked Servers to our IBM as/400. I scripted the as400 linked server from the 2005 server and created it on the 2012 server:
    EXEC master.dbo.sp_addlinkedserver @server = N'AS400', @srvproduct=N'DB2 UDB for iSeries', @provider=N'MSDASQL', @datasrc=N'AS400'
    EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'AS400',@useself=N'False',@locallogin=NULL,@rmtuser=N'USER_NAME',@rmtpassword='PSSWD'
    (plus various sp_serveroptions)
    I then verified that the MSDASQL Provider "Allow Inprocess" was checked and the Linked Server is listed as using the provider but when I try to view the objects under the "AS400" Linked Server I get an error saying: Cannot initialize the
    data source object of OLE DB provider "MSDASQL" for linked server "AS400". (Microsoft SQL Server, Error: 7303)
    I was told to download and install OLEDB provider for DB2.  I downloaded DB2OLEDBV4 but when I try to install it I try to install it I get a OK Box saying: "Microsoft OLE DB Provider for DB2 requires the Microsoft SQL Server 2008 or later
    version.  Ensure that this version is fullfilled before installing Microsoft OLE DB Provider for DB2." when I click OK, I get "Setup was interrupted before Microsoft OLE DB Provider for DB2 could be completely installed" and the install
    exists.  I am installing on SQL 2012!
    Can anyone please advise...

    Hi,
    Based on your description, we know that you got an error when you installed the OLEDB provider for DB2. Microsoft OLE DB Provider for DB2 V4.0 is needed If you use SQL Server 2008 R2 or SQL Server 2012 to connect to IBM DB2 databases.When you install the
    OLEDB provider for DB2 V4.0, we need to make sure that the system meets the following requirements:
    • Windows Server 2008 R2 SP1 or Windows 7 SP1 or Windows Server 2008 SP2.
    • Microsoft SQL Server 2012 (Enterprise, Developer or Evaluation Edition) or Microsoft SQL Server 2008 R2 (Datacenter, Enterprise, Developer or Evaluation Edition) is installed.
    • Microsoft .NET Framework 4.0.             
    As your post,it seems that you have installed SQL Server 2012 Standard Edition,this edition is not supported by Microsoft OLEDB Provider for DB2 V4.0. I recommend you to upgrade the standard edition to enterprise edition and reinstall the OLEDB Provider.You
    can try this method and if you have any questions,please feel free to revert.
    For more detailed information, you can review the following link.http://msdn.microsoft.com/en-us/library/hh873008(v=sql.110).aspx  
    Thanks
    Lydia Zhang

  • UCCX 10.1 - Linked Server - Copying HR data to external SQL Server for reporting

    I have a customer that is migrating from UCCX 7 to UCCX 10.  They currently have a 2008 SQL Server R2 that they use for custom reports.  They have a package that runs nightly to copy relevant data from UCCX 7 to the their server and then run reports daily against that database.   Pretty easy when everything is in MS SQL.  My plan was to set up a linked server in SQL 2008 to the UCCX server.  This would allow me to easily run a query against Informix and move the data over as before.  However, I am having problems adding the linked server.
    I have installed the Informix drivers (both 32 and 64 bit) during the troubleshooting.
    The DSN is created and connects to UCCX just fine.
    When I attempt to add the linked server using 64 bit driver DSN I get the following:
    Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "UCCX101".
    OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
    OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
    OLE DB provider "MSDASQL" for linked server "UCCX101" returned message "[Informix][Informix ODBC Driver][-11302] Insufficient Connection information was supplied". (.Net SqlClient Data Provider)
    When I attempt to add the linked server using the 32 bit driver DSN I get the following:
    Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "32UCCX101".
    OLE DB provider "MSDASQL" for linked server "32UCCX101" returned message "[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". (Microsoft SQL Server, Error: 7303)
    It appears to me there is a 32/64 bit conflict no matter route I go.
    Can anyone tell me what I am missing?
    Is there a better approach to take to achieve the ultimate goal?
    Any suggestions are greatly appreciated.
    TIA
    John

    I have created linked servers on an SQL2K box that points back to CCX. First off, you have to set the password for the UCCX HR user to some known value.
    exec sp_dropserver 'fonccx9_01', 'droplogins'
    EXEC sp_addlinkedserver
    @server='fonccx9_01', -- Name of the Linked Server, when it is created.
    @srvproduct='Microsoft OLE DB Provider for ODBC', -- OLE DB Provider.
    @provider='MSDASQL', -- Provider_name.
    @datasrc ='fonccx9-01', -- DSN Name of the ODBC Data Source.
    @provstr= -- ODBC Connection String.
    'Driver={IBM Informix ODBC};Server=fonccx9_01_uccx;Database=db_cra; Uid=uccxhruser; Pwd=Some-Password;'
    EXEC sp_addlinkedsrvlogin
        @rmtsrvname = 'fonccx9_01',
        @useself = 'FALSE',
        @rmtuser = 'uccxhruser',
        @rmtpassword = 'Some-Password'
    Note that the server name is "fonccx9-01", but the dash is an illegal character in the server name, so you have to change that to an underscore. You still have to manually build the ODBC data source on the box where you are trying to create the linked server.

  • Instant Client with SQLServer2005 Linked Server

    I have successfully installed Instant Client 11.2.0.1.0 on my Windows Server2008. I am able to create an ODBC data source selecting the driver "Oracle in instantclient_11_2". I have also been able to link tables from Access to Oracle. I can logon to Oracle through SQLPlus and execute a query against the Oracle database. I am unsure how to set a Linked Server object in SqlServer 2005. When I use "Microsoft OLE DB Provider for ODBC Drivers" and supply the Product - DBName and Data Source - ODBC data source previously created here is the error I receive:
    TITLE: Microsoft SQL Server Management Studio
    "The linked server has been created but failed a connection test. Do you want to keep the linked server?"
    ADDITIONAL INFORMATION:
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "DB1".
    OLE DB provider "MSDASQL" for linked server "DB1" returned message "Specified driver could not be loaded due to system error 1114 (Oracle in instantclient_11_2).". (Microsoft SQL Server, Error: 7303)
    Thanks!

    Although the 10.1.0.3 instant client for windows doesn't appear to be "officially out", if I try to download
    http://download.oracle.com/otn/nt/instantclient/instantclient-basic-win32-10.1.0.3.zip and similar files, the files do exist.
    Unfortunately this version still can't connect to my corporate Oracle database:
    Oracle8i Enterprise Edition Release 8.1.6.0.0, 64 bit - Production
    With the Partitioning option
    JServer Release 8.1.6.0.0 - Production
    Oh well, back to a full client install of Oracle 9i.
    Perhaps the official release when its documented on the Instant Client download page will work.
    Jamie

  • Connect Non-SAP Oracle db (32bit) in sql 2005 (64 bit) using linked server

    Hi,
    I am connecting Oracle 10g database from SQL 2005 using linked server, in which i get the error
    "Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
    OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
    were not found. " (Microsoft SQL Server, Error: 7303)
    SAP Server with sql 2005 db is in 64 bit server / Windows 2003
    Non-SAP Oracle 10g is in 32 bit windows 2003 server.
    i have installed Oracle 64 bit client in the SAP Server and also copied the 64 bit version of dboraslib.dll to the DIR_LIBRARY path. I am able to view the oracle tables in the oracle client.
    But, when i create the linked server, it gives the above error.
    If i install 32 bit version of Oracle client in the SAP Server, i am able to create the linked server in the db level, but, it says "Work Process restarted, session terminated" message in the Z program in SAP.
    The same works in the test environment where both are 32 bit servers. problem is when SAP server is in 64 bit and non sap is in 32 bit.
    Please suggest.
    Thanks and Regards,
    Nagu

    "Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
    OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
    were not found. " (Microsoft SQL Server, Error: 7303)
    check the workprocess traces for errors (and/or SM21). It seems that the system is "not aware" that an Oracle client is installed.
    64bit programs can´t load 32bit libraries/DLLs that´s why the workprocess dumps when you use the 32bit client.
    Markus

  • How to data insert Source server and Linked server (Target Server) at same transaction

    I have try several times for Data insert Source server and Linked server (Target Server) at same transaction.  I am using Begin transaction.  but Source server is completed and Linked server error (or Linked server Completed and source server
    ERROR). at this moment I want ROLL back. how?

    Hi
    Run below query by changing to yourr linked server name and see if DTC is enable or not.. if not
    Begin distributed transaction
    select * from [ServerName].master.dbo.sysprocesses
    Commit Transaction
    To enable MSDTC on each Web server on Windows Server 2008
    Click Start, click Run, type dcomcnfg and then click OK to open Component Services.
    In the console tree, expand Component Services, expand Computers, expand My Computer, and then expand Distributed Transaction Coordinator.
    Right click Local DTC, and click Properties to display the Local DTC Properties dialog box.
    Click the Security tab.
    In the Security Settings section, click Network DTC Access.
    In the Client and Administration section, select Allow Remote Clients and Allow Remote Administration.
    In the Transaction Manager Communication section, select Allow Inbound and Allow Outbound.
    In the Transaction Manager Communication section, select Mutual Authentication Required (if all remote machines are running Windows Server 2003 SP1), select Incoming Caller Authentication Required (if running MSDTC in a cluster), or select No Authentication
    Required if some of the remote machines are pre-Windows Server 2003 SP1. No Authentication Required is the recommended selection.
    Select Enable XA Transactions, and then click OK.
    Repeat steps 1 through 9 on the other Web servers.
    Thanks
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Maybe you are looking for

  • No active nametab exists for SY

    Hi, I have created a BAPI and it has IMPORT and EXPORT values. I have checked the REMOTE-ENABLED MUDULE redio buttoms. This bapi works perfectly well for Java Web Dynpro. I now create a ABAP web dynpro and create a SERVICE CALL. Everything looks ok,

  • How to set luma key in FCX 10.1.2?  Luma key adjustments do not open when selecting the  Effects button on the toolbar.

    Using FCPX 10.1.2 and trying to adjust a luma key, when selecting the Effects button on the Toolbar, the adjustments do not appear.  Any suggestions?

  • RFC to JDBC

    Hi All, My scenario is RFCXIJDBC. Source side: SAP has data in Z tables which can be Picked and sent by RFC to Xi. In Target side Database the data sholud be transferred to two tables based on the certain condition & the two tables are having certain

  • Dmp 4400 can't play local files

    I am using a DMP-4400 with firmware v.5.2.2. The unit connects to the network fine and is able to display webpages from the internet without problem; the ftp server is working fine also. However, when I attempt to play any type of local file ( locate

  • Problems installing Adobe Elements 4.0

    Wow, do I love my Macbook Pro. No waiting to order it. Got it 3 weeks ago at the Apple Store. No noise, no problem installing my old files .etc. However, tonight I tried to install Adobe Elements 4 two times. Both times at the last seconds of install