Linked server suddenly hung

Hi,
The linked server in production database (SQL server 2008R2) suddenly hung. We were not able to do test connection in SSMS. The queries running were killed but it could not be killed completely. The issue got solved only after restarting SQL server. Openquery
worked fine after SQL reboot. We were not able to find the root cause of it. Can anyone assist in helping us?
Thanks,
Preetha

It's with one SQL server used for connecting progress database. We use progress connection driver to establish connection. Cannot query progress as it is not our db. Could not find a solution for this. Finding very hard to understand the root cause
If you are doing record transfer to PostgresSql linked server will always give pain, dont ask me why this is how linked server is it works best with OLEDB providers but not with other, this is my personal experience. I faced issue where I had to transfer
data from SQL Server to PostgreSql I cannot use OLEDB provider because somehow i found OLEDB provider for postgres has cost associated with It. I used ADO.NET provider( in built in SSIS) and it works perfectly well. I created a wiki article about it I hope
this will help you
How to transfer records from SQL server to PostgresSql
If you want to move data other way around just change source and destination. My article will not be applicable if you work on SQL Server 2005 as ADO.NET was not present in connection manager for 2005 SSIS.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Similar Messages

Linked Server to Access Database in SQL Server 2012 is working perfectly.But, All of sudden it is showing SQL Error Code:7303

Linked Server to Access Database in SQL Server 2012 is working perfectly.But, All of sudden it is showing SQL Error Code:7303
Unable to connect to the database type that is created with earlier versions type. But the same Linked Server in another SQL Server instance is working perfectly. I am unable to rectify what is the problem please help.

All of sudden it is showing SQL Error Code:7303
Error 7303 = "Cannot initialize the data source object of OLE DB provider "%ls" for linked server "%ls"."?
Check the data Provider on the machine, e.g. using ODBC Admin by creating a DSN
Olaf Helper
Hi Olaf Helper,
I don't now how to add a DSN for the Access Database using ODBC Admin. Can you Please help me with that one. as the solution to above problem i Have added a startup parameter -g512 to SQL Server is it effects my existing Assemblies in SQL Server. I am replacing
the startup parameter as -g500 to -g512 here.
Thank you
Regards,
AyubKhan M

Connecting to dynamic link server - FAILED - second time

I bought the creative cloud membership and I use after effects for my projects then send them over to media encoder for rendering.
At first when I would send it over to media encoder it worked just fine, then SUDDENLY, one day, it stopped worked and it would say "connecting to dynamic link server failed".
I deleted the program and re installed it and it did the trick...However, AGAIN, this same problem and unexpectedly risen. I do not want to be deleting and installing every-time this happens.
I have a brand new windows 8.1 computer and I do not know why this is happening. any fixes?

Something is running that is preventing dynamic link from opening. It could be any one of a host of programs. Open up your Task Manager (Activity monitor if you are having the same problem and are on a Mac) and check for all running programs to see which one is hanging. Then either update or uninstall the app that is causing the problem.
If you don't find anything there try purging memory and disk cache first and then allocate more memory to other apps in AE's preferences.

ODSEE 11g - DPS Directory proxy server suddenly increase load average

Hi all
Recently upgraded from directory server 5.2 to ODSEE 11g, one directory proxy configure to one master directory server and one consumer directory server.
all the three instances are in the same sparc t3 machine.
Directory proxy server alerts server load average on the machine is above 6.00 normally it is 0.66. I'm not sure what is causing the sudden burst in the load ? the traffic is normal there is no abnormal requests coming to the server. proxy performance degrades over the span of 24 hours ....and Once i restart the proxy services (dpsadm restart) all load averages comes to normal and directory proxy runs normal for the next two - three weeks. The same cycle continues ...I'm not sure what was causing the sudden load increase.
I increased the JVM heap size from 1GB to 2 GB still continue to have the problem ..did anyone else experience similar problem. How did you fix it....
Any input or advise in the right direction is much appreciated.
Thank you.

server load I'm referring to "prstat command" - server load average suddenly shoot up from 0.66 to 6.00 ie) the CPU usage. Alert is from our server monitoring tool not related to directory proxy.
Clients report connections time out (etime goes from etime=0 ..2..4.....) over 24 hours i can see the etime increases and eventually the proxy server get hung and non responsive. Once I restart all the performance back to normal at-least for another two weeks.
I suspect there might be a memory leak or JVM Garbage collection issue -- any expert input how to figure this out will help.
Here is the JVM args in the proxy server "Xms2g -Xmx2g -Xmn1g -XX:SurvivorRatio=4 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC"
Here is a jstat during the problem
./jstat -gcutil -t 25365 2s 30
Timestamp S0 S1 E O P YGC YGCT FGC FGCT GCT
982106.4 0.00 26.17 4.26 92.25 59.52 523 60.979 689 1002.587 1063.566
982108.4 0.00 26.17 4.40 92.25 59.52 523 60.979 689 1002.587 1063.566
982110.4 0.00 26.17 4.80 92.25 59.52 523 60.979 689 1002.587 1063.566
982112.4 0.00 26.17 5.10 92.25 59.52 523 60.979 690 1002.719 1063.698
982114.4 0.00 26.17 5.15 92.25 59.52 523 60.979 690 1002.719 1063.698
982116.4 0.00 26.17 5.32 92.25 59.52 523 60.979 691 1003.009 1063.988
982118.4 0.00 26.17 5.72 92.25 59.52 523 60.979 691 1003.009 1063.988
982120.4 0.00 26.17 5.80 92.25 59.52 523 60.979 691 1003.009 1063.988
982122.4 0.00 26.17 5.93 92.25 59.52 523 60.979 692 1003.168 1064.146
982124.4 0.00 26.17 6.03 92.25 59.52 523 60.979 692 1003.168 1064.146
982126.4 0.00 26.17 6.15 92.25 59.52 523 60.979 693 1003.481 1064.460
982128.5 0.00 26.17 6.18 92.25 59.52 523 60.979 693 1003.481 1064.460
982130.5 0.00 26.17 6.25 92.25 59.52 523 60.979 693 1003.481 1064.460
982132.5 0.00 26.17 6.29 92.25 59.52 523 60.979 694 1003.656 1064.635
982134.5 0.00 26.17 6.31 92.25 59.52 523 60.979 694 1003.656 1064.635
982136.5 0.00 26.17 6.36 92.25 59.52 523 60.979 695 1003.988 1064.967
982138.5 0.00 26.17 6.89 92.25 59.52 523 60.979 695 1003.988 1064.967
982140.5 0.00 26.17 6.99 92.25 59.52 523 60.979 695 1003.988 1064.967
982142.5 0.00 26.17 7.08 92.25 59.52 523 60.979 696 1004.187 1065.165
982144.5 0.00 26.17 7.31 92.25 59.52 523 60.979 696 1004.187 1065.165
982146.5 0.00 26.17 7.82 92.25 59.52 523 60.979 697 1004.553 1065.531
982148.5 0.00 26.17 7.92 92.25 59.52 523 60.979 697 1004.553 1065.531
982150.5 0.00 26.17 8.01 92.25 59.52 523 60.979 697 1004.553 1065.531
982152.5 0.00 26.17 8.17 92.25 59.52 523 60.979 698 1004.786 1065.764
982154.5 0.00 26.17 8.26 92.25 59.52 523 60.979 698 1004.786 1065.764
982156.5 0.00 26.17 8.38 92.25 59.52 523 60.979 699 1005.174 1066.153
982158.5 0.00 26.17 8.74 92.25 59.52 523 60.979 699 1005.174 1066.153
982160.5 0.00 26.17 8.88 92.25 59.52 523 60.979 699 1005.174 1066.153
982162.5 0.00 26.17 8.96 92.25 59.52 523 60.979 700 1005.433 1066.412
982164.5 0.00 26.17 9.09 92.25 59.52 523 60.979 700 1005.433 1066.412
jstat after the restart
./jstat -gcutil -t 10084 2s 30
Timestamp S0 S1 E O P YGC YGCT FGC FGCT GCT
40312.6 0.00 25.13 88.49 1.98 63.68 21 2.366 0 0.000 2.366
40314.6 0.00 25.13 88.58 1.98 63.68 21 2.366 0 0.000 2.366
40316.6 0.00 25.13 88.71 1.98 63.68 21 2.366 0 0.000 2.366
40318.6 0.00 25.13 88.99 1.98 63.68 21 2.366 0 0.000 2.366
40320.6 0.00 25.13 89.31 1.98 63.68 21 2.366 0 0.000 2.366
40322.6 0.00 25.13 89.36 1.98 63.68 21 2.366 0 0.000 2.366
40324.6 0.00 25.13 89.42 1.98 63.68 21 2.366 0 0.000 2.366
40326.6 0.00 25.13 89.53 1.98 63.68 21 2.366 0 0.000 2.366
40328.6 0.00 25.13 89.60 1.98 63.68 21 2.366 0 0.000 2.366
40330.6 0.00 25.13 89.72 1.98 63.68 21 2.366 0 0.000 2.366
40332.6 0.00 25.13 90.11 1.98 63.68 21 2.366 0 0.000 2.366
40334.6 0.00 25.13 90.56 1.98 63.68 21 2.366 0 0.000 2.366
40336.6 0.00 25.13 90.67 1.98 63.68 21 2.366 0 0.000 2.366
40338.6 0.00 25.13 90.75 1.98 63.68 21 2.366 0 0.000 2.366
40340.6 0.00 25.13 91.09 1.98 63.68 21 2.366 0 0.000 2.366
40342.6 0.00 25.13 91.36 1.98 63.68 21 2.366 0 0.000 2.366
40344.6 0.00 25.13 91.47 1.98 63.68 21 2.366 0 0.000 2.366
40346.6 0.00 25.13 91.53 1.98 63.68 21 2.366 0 0.000 2.366
40348.7 0.00 25.13 91.64 1.98 63.68 21 2.366 0 0.000 2.366
40350.7 0.00 25.13 91.77 1.98 63.68 21 2.366 0 0.000 2.366
40352.7 0.00 25.13 91.87 1.98 63.68 21 2.366 0 0.000 2.366
40354.7 0.00 25.13 91.95 1.98 63.68 21 2.366 0 0.000 2.366
40356.7 0.00 25.13 92.11 1.98 63.68 21 2.366 0 0.000 2.366
40358.7 0.00 25.13 92.19 1.98 63.68 21 2.366 0 0.000 2.366
40360.7 0.00 25.13 92.24 1.98 63.68 21 2.366 0 0.000 2.366
40362.7 0.00 25.13 92.85 1.98 63.68 21 2.366 0 0.000 2.366
40364.7 0.00 25.13 93.19 1.98 63.68 21 2.366 0 0.000 2.366
40366.7 0.00 25.13 93.40 1.98 63.68 21 2.366 0 0.000 2.366
40368.7 0.00 25.13 93.44 1.98 63.68 21 2.366 0 0.000 2.366
40370.7 0.00 25.13 93.47 1.98 63.68 21 2.366 0 0.000 2.366
Any one else had similar behavior. Any input to the right direction is highly appreciated.
Thanks.

Problem with linked server...error 7302

I have a very perplexing problem with a linked server.
We are running SQL Server 2008 on Windows Server 2003. We have two instances, PROD and TEST. Both instances have a linked server to a DB2 environment using the IBMDADB2 driver. Both linked servers are identical. Up until a few days ago, both linked servers worked fine. Suddenly, I started to receive the following error when trying to access the linked server on TEST:
Msg 7302, Level 16, State 1, Procedure sp_testlinkedserver, Line 1
Cannot create an instance of OLE DB provider "IBMDADB2.DB2COPY1" for linked server "cm_nw".
I have tried *everything* save restart the server (which is going to come tonight), reregistering the .dll and querying through openrowset (openquery and testing the connection in SSMS both fail). This includes:
1) Recreating the linked server
2) Going into DCOM and modifying the msdainitialize and checking the permissions.
I am logging into the server using Windows Authentication, but this has worked and nothing has changed on that instance at all. I'm in the Administrators group anyway, as is the SQL Server service account, and that group has permissions on MSDAINITIALIZE. There is nothing in the SQL Server or Windows logs to indicate why the linked server cannot be called.
Note the linked server is set up to use a security context (user name and password) and both linked servers are identical in this aspect. If I recreate the linked server without a password and uncheck "Allow Inprocess" in the provider I get:
The OLE DB provider "IBMDADB2.DB2COPY1" for linked server "CM_NW" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "IBMDADB2.DB2COPY1" for linked server "CM_NW".
OLE DB provider "IBMDADB2.DB2COPY1" for linked server "CM_NW" returned message " SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING"). SQLSTATE=08001
". (Microsoft SQL Server, Error: 7399)
I don't know if that is coming from the SQL Server end or the DB2 end.

I was able to resolve this issue by editing the registry. I imported a registry file called "IBM DB2 ODBC Driver - DB2 X64" from one of my known working servers that has a linked DB2 server installed. So what I'm thinking is happening is that SQL
Server is somehow editing the registry causing it to break.
If you can go through the ODBC administrator and test your connection successfully, than you will know that the problem is not DB2 Connect but it's actually SQL Server.
For anyone that is still having this issue I would look in the registry for any DB2 X64 drivers to see if you have any. If not you can always create the following registry file and call it "IBM DB2 ODBC Driver - DB2 X64.reg" .
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers]
"SQL Server"="Installed"
"Microsoft ODBC for Oracle"="Installed"
"Microsoft Access Driver (*.mdb)"="Installed"
"Microsoft Access-Treiber (*.mdb)"="Installed"
"Driver do Microsoft Access (*.mdb)"="Installed"
"Microsoft dBase Driver (*.dbf)"="Installed"
"Microsoft dBase-Treiber (*.dbf)"="Installed"
"Driver do Microsoft dBase (*.dbf)"="Installed"
"Microsoft Excel Driver (*.xls)"="Installed"
"Microsoft Excel-Treiber (*.xls)"="Installed"
"Driver do Microsoft Excel(*.xls)"="Installed"
"Microsoft Paradox Driver (*.db )"="Installed"
"Microsoft Paradox-Treiber (*.db )"="Installed"
"Driver do Microsoft Paradox (*.db )"="Installed"
"Microsoft Text Driver (*.txt; *.csv)"="Installed"
"Microsoft Text-Treiber (*.txt; *.csv)"="Installed"
"Driver da Microsoft para arquivos texto (*.txt; *.csv)"="Installed"
"Microsoft Visual FoxPro Driver"="Installed"
"Microsoft FoxPro VFP Driver (*.dbf)"="Installed"
"Microsoft dBase VFP Driver (*.dbf)"="Installed"
"Microsoft Visual FoxPro-Treiber"="Installed"
"Driver para o Microsoft Visual FoxPro"="Installed"
"SQL Server Native Client 10.0"="Installed"
"IBM DB2 ODBC DRIVER - DB2x64"="Installed"
"Microsoft Access Driver (*.mdb, *.accdb)"="Installed"
"Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)"="Installed"
"Microsoft Access dBASE Driver (*.dbf, *.ndx, *.mdx)"="Installed"
"Microsoft Access Paradox Driver (*.db)"="Installed"
"Microsoft Access Text Driver (*.txt, *.csv)"="Installed"
"IBM INFORMIX ODBC DRIVER"="Installed"
"ServiceNow ODBC Driver 32-bit"="Installed"
"IBM DB2 ODBC DRIVER - DB2COPY1"="Installed"
"IBM DB2 ODBC DRIVER"="Installed"
Once you've created this file go ahead and create a backup(if desired) of the registry and execute the reg file and restart SQL Server to see if this resolves your issue. If this does resolve your issue I would recommend taking a backup of your registry
in case it breaks again. Keep in mind, other applications may experience issues that have been changed if you revert back to the backup.
Hope this helps!

Connecting to a cube via a linked server

Hi
I want to connect to a SSAS cube via a linked server. When I ran a query against the SSAS cube from directly from the SQL server it runs fine.
If however I run the query in SSMS from my PC I get
OLE DB provider "MSOLAP" for linked server "SSASServer01" returned message "The following system error occurred: .".
Msg 7373, Level 16, State 2, Line 1
Cannot set the initialization properties for OLE DB provider "MSOLAP" for linked server "SSASServer01".
In the properties on the linked server I've defined an account to use for the connection to get round the double hop issue
Any Ideas why I'm still getting the error?
Alex

Hi Mr P,
According to your description, you get the error 7373 with message "Cannot set the initialization properties for OLE DB provider "MSOLAP" for linked server "SSASServer01"." when connecting a SSAS cube via linked server.
Right?
In this scenario, based on the error code 7373, it points to the issue of MSOLAP provider, please firstly check the properties setting for MSOLAP. Make sure the "Allow Inprocess" is selected. You may also have other options selected depends on
your query.
Also check if ports for your server (1434 and 2383) are listening proper locally and externally. Please refer to a similar thread below:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9d5bd9e0-c380-4a0f-bdab-857751c71fba/ole-db-msolap-provider-issues?forum=sqlanalysisservices
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

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.

How to create a view on SQLServer 2008 as an OPENQuery select to a MYSQL linked server

I am trying to create a view on SQLServer through Management Studio based on data on a MYSql server.
I have created the Linked server and I am able to query all data.
Using the syntax select * from OPENQUERY (linkedServer, 'select * from MYSQL-table') - This works fine
What I am trying to do now is issue the following statement
create view ViewnameToBeCreatedOnSQLServer
as select * from OPENQUERY (linkedServer, 'select * from MYSQL-table')
When I run this from SSMS I get the following error
OLE DB provider "MSDASQL" for linked server "TESTTSC2" returned message "[MySQL][ODBC 5.1 Driver][mysqld-5.0.95-log]Table 'FP.M3' doesn't exist".
Msg 7350, Level 16, State 2, Procedure FPMaster3, Line 2
Cannot get the column information from OLE DB provider "MSDASQL" for linked server "TESTTSC2".
The account I am using has create view privs and alter schema privs on the SQlServer side. I am assuming there are not isues on the MYSQL server side since I am able to successfully run the select statement using OPENQUERY. There must be one small
piece I am missing. has anyone experienced the same problem and were you able to find a solution?

All the configurations seem to be in place correctly since I can SELECT any data with no issues. The statement
select * from OPENQUERY (linkedServer, 'select * from MYSQL-table')
works fine and I can change the table I am selecting from which all return data. Therefore, the objects all exists in MYSQL.
The DSN is set up, the linked Server is good, the provider is set up, the DB account has all privs.
It only fails when I try to create the view on SQLServer as a select from a remote table accessed via the linked MYSQL server. I connect to SQLServer with DB account PS which has full privs including CREATE VIEW and ALTER SCHEMA. The MYSQL pass-through account
has read access to all objects in the MYSQL schema. I am trying to figure out if I might be missing some little part of this puzzle when trying to create a new object (CRESTE VIEW) vs. just reading the data (SELECT).
The kicker in all this is that I did create a view on SQLServer in this manner about a year ago and I am able to see the view definition and that view still works! So, this is quite interesting that I am not able to create a new object.
If there any specific information I could provide which might help, I am happy to do that. Just did not want to provide the details on all of the puzzle pieces if it can be avoided but if it comes to that then that's OK also.
Thanks very much! I appreciate your help.

Cannot kill a session that is running a query on a linked server in SQL Server 2008 R2

Hi,
Cannot kill a session that is running a query on a linked server in SQL Server 2008 R2.
When I try to kill, it status shown as "KILLED/ROLLBACK"
I have facing the issue from long back. I searched many and none of them worked for me
Any help is greatly appreciated
Thanks
Jaison
Carver

I guess its stuck, can you see some blocking or any other process blocking the rollback.
can you check rollback status using below command. Or you can use sp_who2 and check status column
select percent_complete,estimated_completion_time from sys.dm_exec_requests
where spid=xxx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

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

Error: An error occurred while preparing the query in openquery on ServiceNow ODBC Link Server

Hi Team,
Greetings of the Day!!!!!
I have a created a link server on SQL Server 2008 R2 databse of Service Now ODBC driver. And written a stored procedure using openquery to get the data from link server.
Now problem is that, when i have scheduled that stored procedure in sql jobs. When this job runs automatically then we are getting below error while when i start the job mannually then it's not giving error.
An error occurred while preparing the query "..........."
Please help me to resolve this issue.
Regards,
Brijendra Pandey

Hi Fanny,
I had reviewed the job history. I am getting below message where as table is exist in the database.
Message
Executed as user: NT AUTHORITY\SYSTEM. OLE DB provider "MSDASQL" for linked server "SNOWDSN" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Base table:incident not found.[10129]". [SQLSTATE 01000] (Message 7412) OLE
DB provider "MSDASQL" for linked server "SNOWDSN" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Base table:sysapproval_approver not found.[10129]". [SQLSTATE 01000] (Message 7412) OLE DB provider "MSDASQL" for linked
server "SNOWDSN" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Base table:problem not found.[10129]". [SQLSTATE 01000] (Message 7412). The step succeeded.
Regards,
Brijendra Pandey

Error while linked server is used to verify the existence of a table

Hi All,
Pls help me solve an issue related to linked Server..
Following is my query:
IF EXISTS (select 1 from [LinkedServerName].Sales.sys.tables where name = 'SalesTable')
BEGIN
DECLARE @LastSales varchar(25)
SET @LastSales = (select CONVERT(VARCHAR(25),max(LastSalesTime)) from [LinkedServerName].SalesDB.dbo.SalesTable)
END
What should happen is, it should check the existence of SalesTable on Linked Server (select 1 from [LinkedServer].Sales.sys.tables where name = 'SalesTable'), and only after the it returns 1, the variable @LastSales should be alloted a value.
But in my case, as soon as I run the code, it gives the error:
The OLE DB provider "SQLNCLI10" for linked server "LinkedServerName" does not contain the table ""Sales"."dbo"."SalesTable"".
The table either does not exist or the current user does not have permissions on that table.
My question is that if the condition fails at the very outset returning null (as the table does not exist), then why it is entering BEGIN and throwing the error.
All your valuable inputs are appreciated !!

Inconsistency is the hailmark of SQL Server.
If you say:
IF EXISTS (select 1 from Sales.sys.tables where name = 'SalesTable')
BEGIN
DECLARE @LastSales varchar(25)
SET @LastSales = (select CONVERT(VARCHAR(25),max(LastSalesTime)) from SalesDB.dbo.SalesTable)
END
This will work as you expect. That is, if the table does not exist, the batch will parse and produce no result. This is because SQL Server has deferred name resolution for tables. If a table is missing at compile time, SQL Server suppresses the error in
hope that the table will be there at run-time.
But there is an exception to this. For table sources on remote data sources, there is no deferred name resolution, but the table has to be there at compile time. This is quite ironic. Personally, I think deferred name resolution (which was introduced in
SQL 7) is a big misfeature, but I could buy if there was deferred name resolution for objects on linked server, since the server may be down, and you have coded for this like you have above. Well, if the server is down, the IF EXISTS will fail to compile to.
You will need to introduce a new scope somewhere to avoid the problem. For instance:
IF EXISTS (select 1 from [LinkedServerName].Sales.sys.tables where name = 'SalesTable')
BEGIN
DECLARE @LastSales varchar(25)
EXEC [Linkedservername].SalesDB.sys.sp_executesql
N'SET @LastSales = (select CONVERT(VARCHAR(25),max(LastSalesTime)) from SalesTable)',
N'@LastSales varchar(25) OUTPUT', @LastSales
END
Erland Sommarskog, SQL Server MVP, [email protected]

A network-related error has occurred where Connecting to Hive ODBC by Linked Server

1) I have created Hive ODBC Driver (Succesfully Tested)
2) I have created Linked Server on SQL Server 2014 (Succesfully Tested)
3) SELECT * FROM OpenQuery([SQLHive],
'SELECT * FROM hivesampletable;')
ERROR:
OLE DB provider "SQLNCLI11" for linked server "SQLHive" returned message "Login timeout expired".
OLE DB provider "SQLNCLI11" for linked server "SQLHive" 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.".
Msg 67, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [67].
INSTRUCTIONS FOLLOWED:
http://ayadshammout.com/2013/05/27/import-hadoop-data-into-sql-bi-semantic-model-tabular/
CONFIGURATIONS OF ON TEST:
-Firewall is OFF
-SQL Server and Windows Authentication mode is ON
- Named Pipes is ON on SQL Server Confi manager
Kenny_I

The subject line and the first point on your list indicates that you want to connect to a Hive data source using ODBC. But the error message tells us that you have set up a linked server with SQL Server Native Client, which is the OLE DB provider you would
use if you want to connect to another SQL Server instance.
For using an ODBC driver, you need to use the MSDASQL provider, and in the @provstr argument you specify which ODBC driver you want to use. That is, something like:
EXEC sp_addlinkedserver 'SQLHive', '', 'MSDASQL',
@provstr = 'Driver={Hive ODBC Driver}....'
As I have not worked with the Hive ODBC Driver, I don't know exactly what goes into the @provstr parameter, but it would be the same as if you connected to Hive from an application.
Erland Sommarskog, SQL Server MVP, [email protected]

The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server ...

Our setup is that we have two databases; a SQL Server 2008 database and an Oracle database (11g). I've got the oracle MTS stuff installed and the Oracle MTS Recovery Service is running. I have DTC configured to allow distributed transactions. All access to the Oracle tables takes place via views in the SQL Server database that go against Oracle tables in the linked server.
(With regard to DTC config: Checked-> Network DTC Access, Allow Remote Clients, Allow Inbound, Allow Outbound, Mutual Authentication (tried all 3 options), Enable XA Transactions and Enable SNA LU 6.2 Transactions. DTC logs in as NT AUTHORITY\NetworkService)
Our app is an ASP.NET MVC 4.0 app that calls into a number of WCF services to perform database work. Currently the web app and the WCF service share the same app pool (not sure if it's relevant, but just in case...)
Some of our services are transactional, others are not.
Each WCF service that is transactional has the following attribute on its interface:
[ServiceContract(SessionMode=SessionMode.Required)]
and the following attribute on the method signatures in the interface:
[TransactionFlow(TransactionFlowOption.Allowed)]
and the following attribute on every method implementations:
[OperationBehavior(TransactionScopeRequired = true, TransactionAutoComplete = true)]
In my data access layer, all the transactional methods are set up as follows:
using (IDbConnection conn = DbTools.GetConnection(_configStr, _connStr))
using (IDbCommand cmd = DbTools.GetCommand(conn, "SET XACT_ABORT ON"))
cmd.ExecuteNonQuery();
using (IDbCommand cmd = DbTools.GetCommand(conn, sql))
... Perform actual database work ...
Services that are transactional call transactional DAL code. The idea was to keep the stuff that needs to be transactional (a few cases) separate from the stuff that doesn't need to be transactional (~95% of the cases).
There ought not be cases where transactional and non-transactional WCF methods are called from within a transaction (though I haven't verified this and this may be the cause of my problems. I'm not sure, which is part of why I'm asking here.)
As I mentioned before, in most cases, this all works fine.
Periodically, and I cannot identify what initiates it, I start getting errors. And once they start, pretty much everything starts failing for a while. Eventually things start working again. Not sure why... This is all in a test environment with a single user.
Sometimes the error is:
Unable to start a nested transaction for OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLSERVERNAME". A nested transaction was required because the XACT_ABORT option was set to OFF.
This message, I'm guessing is happening when I have non-transactional stuff within transactions, as I'm not setting XACT_ABORT in the non-transactional code (that's totally doable, if that will fix my issue).
Most often, however, the error is this:
System.Data.SqlClient.SqlException (0x80131904): The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLSERVERNAME" was unable to begin a distributed transaction.
Now, originally we only had transactions on SQL Server tables and that all worked fine. It wasn't until we added transaction support for some of the Oracle tables that things started failing. I know the Oracle transactions work. And as I said, most of the time, everything is just hunky dorey and then sometimes it starts failing and keeps failing for a while until it decides to stop failing and then it all works again.
I noticed that our transactions didn't seem to have a DistributedIdentifier set, so I added the EnsureDistributed() method from this blog post: http://www.make-awesome.com/2010/04/forcibly-creating-a-distributed-net-transaction/
Instead of a hardcoded Guid (which seemed to cause a lot of problems), I have it generating a new Guid for each transaction and that seems to work, but it has not fixed my problem. I'm wondering if the lack of a DistribuedIdentifier is indicative of some other underlying problem. I've never dealt with an environment quite like this before, so I'm not sure what is "normal".
I've also noticed that the DistributedIdentifier doesn't get passed to WCF. From the client, I have a DistributedIdentifier and a LocalIdentifier in Transaction.Current.TransactionInformation. In the WCF server, however there is only a LocalIdentifier set and it is a different Guid from the client side (which makes sense, but I would have expected the DistributedIdentifier to go across).
So I changed the wait the code above works and instead, on the WCF side, I call a method that calls Transaction.Current.EnlistDurable() with the DummyEnlistmentNotification class from the link above (though with a unique Guid for each transaction instead of the hardcoded guid in the link). I now havea DistributedIdentifier on the server-side, but it still doesn't fix the problem.
It appears that when I'm in the midst of transactions failing, even after I shut down IIS, I'm unable to get the DTC service to shutdown and restart. If I go into Component Services and change the security settings, for example, and hit Apply or OK, after a bit of a wait I get a dialgo that says, "Failed ot restart the MS DTC serivce. Please examine the eventlog for further details."
In the eventlog I get a series of events:
1 (from MSDTC): "The MS DTC service is stopping"
2 (From MSSQL$SQLEXPRESS): "The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions
involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational
message only. No user action is required."
-- Folowed by these 3 identical messages
3 (from MSDTC Client 2): 'MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system GCOVA38.'
4 (from MSDTC Client 2): 'MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system GCOVA38.'
5 (from MSDTC Client 2): 'MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system GCOVA38.'
6 (From MSDTC 2): MSDTC started with the following settings: Security Configuration (OFF = 0 and ON = 1):
Allow Remote Administrator = 0,
Network Clients = 1,
Trasaction Manager Communication:
Allow Inbound Transactions = 1,
Allow Outbound Transactions = 1,
Transaction Internet Protocol (TIP) = 0,
Enable XA Transactions = 1,
Enable SNA LU 6.2 Transactions = 1,
MSDTC Communications Security = Mutual Authentication Required, Account = NT AUTHORITY\NetworkService,
Firewall Exclusion Detected = 0
Transaction Bridge Installed = 0
Filtering Duplicate Events = 1
This makes me wonder if there's something maybe holding a transaction open somewhere?

The statement executed from the sql server. (Installed version sql server 2008 64 bit standard edition SP1 and oracle 11g 64 bit client), DTS enabled
Below is the actual sql statement issued
SET XACT_ABORT ON
BEGIN TRAN
insert into XXX..EUINTGR.UPLOAD_LWP ([ALTID]
          ,[GRANT_FROM],[GRANT_TO],[NO_OF_DAYS],[LEAVENAME],[LEAVEREASON],[FROMHALFTAG]
          ,[TOHALFTAG] ,[UNIT_USER],[UPLOAD_REF_NO],[STATUS],[LOGINID],[AVAILTYPE],[LV_REV_ENTRY])
          values('IS2755','2010-06-01',
'2010-06-01','.5',     'LWOP'     ,'PERSONAL'     ,'F',     'F',     'EUINTGR',
'20101',1,1,0,'ENTRY')
rollback TRAN
OLE DB provider "ORAOLEDB.ORACLE" for linked server "XXX" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "ORAOLEDB.ORACLE" for linked server "XXX" was unable to begin a distributed transaction.
Able to execute the above statement successfully without using transaction.We need to run the statement with transaction.

Very slow Export to Media Encoder and Media Encoder connecting to dynamic link server

My flow is this: Open After Effects CC, import an image sequence, go to File > Export > Add to Adobe Media Encoder Queue...
Every other time i do this it will take 2-3 mins before Media Encoder even shows the splash screen, then it'll take another 1-2 mins to open.
Next, I'll select my custom preset over on the right side of the window, then hit the Play button to begin encoding. Sometimes nothing will happen at all, sometimes I'll see the Orange stripped bar on the lower left and the message Media Encoder connecting to dynamic link server and that'll last 5+ minutes and I end task to get out of AE and ME. Sometimes, ME will begin encoding right away and zip through the small animation sequence quickly without issue.
I have WIndows 7 Pro, I'm on a work network with access to the internet and AE has been updated 24 days ago. I have a subscription and I'm signed on. However, sometimes I do not have the Creative-Cloud icon in my systray.
Thanks,

Thanks. I have 16GB Ram, 64bit Win7, Intel(R) Core(TM) i7-3970X @ 3.50GHz 3.50GHz. AE is set to have maximum disk cache of 46GB. RAM reserved for other applications: 5GB RAM available for AE, PR, Pl, (some triangular icon [edit] which is ME ), Ps: 10GB. nothing else checked on that screen.
Typically just a mail client, 1 or 2 sessions of Firefox, 1 or 2 network folders open when i launch AE.
The last couple of times specifically, i had a 450 frame animation sequence at native 720p. then i added a curves layer on top of it in AE, then added two ~600x300px logos, one in each lower corner, then added a new solid layer which i used as a vignette. Finally over that i added a 720p still image which i held for another 15 seconds beyond the animation.
For the above, i ended-task, rebooted, brought it up again and it lauched ME quickly, then i got the stripped bar and connecting message until i ended task on that, then the 3rd time was the charm - everything opened quickly and it began to encode quickly.
The next three uses late afternoon yesterday were 150 frame animations at 480x270 and they all seemed to work fine. I created the sequence in 3ds max, then closed and went into AE. Then I'd close AE render another sequence, back into AE etc...

Linked server suddenly hung

Similar Messages

Maybe you are looking for