Need to be able to run update queries on DB2 on IBM MF from a Linked Server. Select and Insert queries work but Update and Delete queries don't. DB2 connect is installed and ODBC System dsn's are created for DEV and Production DB2 environments.
The ODBC drivers can be selected when running Imports/Exports but can't be specified through a linked server.
Any Ideas??
Tom...
We have oracle linked server created on one of the sql server 2008 standard , we are fetching data from oracle and updating some records in sql server . Previously its working fine but we are suddenly facing below issue.
Below error occurred during process .
OLE DB provider "OraOLEDB.Oracle" for linked server "<linkedservername>" returned message "".
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 "<linked server name>".
I am attempting to install SQL Server 2005 Developer Edition onto a Windows XP Pro SP2 machine, but unfortunately each time that I attempt to install I receive an error message in the summary log as follows:
Product : Microsoft SQL Server 2005
Product Version: 9.00.1399.06
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup
Last Action : InstallFinalize
Error String : The setup has encountered an unexpected error while Updating Installed Files.
The error is : Fatal error during installation.
Error Number : 29528
There is probably a simple solution for the issue but unfortunately I am unaware of what it is? I can€™t tell if the issue is specific to registry settings, security, file types, etc€¦ The information below surrounds the error w/in the log, any suggestions would be greatly appreciated?
Thanks, Jennifer
MSI (s) (6C:94) [16:02:23:713]: Executing op: SetTargetFolder(Folder=C:WINNTsystem32)
MSI (s) (6C:94) [16:02:23:713]: Executing op: SetSourceFolder(Folder=1System)
MSI (s) (6C:94) [16:02:23:713]: Executing op: FileCopy(SourceName=sqlctr90.dll,SourceCabKey=sqlctr90.dll.7188DA12_A95E_46B7_8623_9D93B5260E2A,DestName=sqlctr90.dll,Attributes=16384,FileSize=66264,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,Version=2005.90.1399.0,Language=1033,InstallMode=58982400,,,,,,,)
MSI (s) (6C:94) [16:02:23:713]: File: C:WINNTsystem32sqlctr90.dll; To be installed; Won't patch; No existing file
MSI (s) (6C:94) [16:02:23:713]: Source for file 'sqlctr90.dll.7188DA12_A95E_46B7_8623_9D93B5260E2A' is compressed
MSI (s) (6C:94) [16:02:23:713]: Note: 1: 2318 2: C:WINNTsystem32sqlctr90.dll
MSI (s) (6C:94) [16:02:23:713]: Note: 1: 2360
MSI (s) (6C:94) [16:02:23:713]: Note: 1: 2360
MSI (s) (6C:94) [16:02:23:723]: Executing op: CacheSizeFlush(,)
MSI (s) (6C:94) [16:02:23:723]: Executing op: InstallProtectedFiles(AllowUI=0)
MSI (s) (6C:94) [16:02:23:723]: Executing op: ActionStart(Name=CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
MSI (s) (6C:94) [16:02:23:733]: Executing op: CustomActionSchedule(Action=CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1025,Source=BinaryData,Target=InstallFTERef,CustomActionData=C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef|C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData)
MSI (s) (6C:2C) [16:02:23:743]: Invoking remote custom action. DLL: C:WINNTInstallerMSI64E.tmp, Entrypoint: InstallFTERef
FTECa.DLL: INFO: FTE: InstallFTERef(), Entering...
FTECa.DLL: INFO: FTE: GetFTERefInstallParams: FTERef : C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTDataoiseCHS.txt Size=1000 IDR=1696
.
.
.
.
.
.
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData sSVE.xml Size=1035 IDR=1142
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTDataoiseTHA.txt Size=1036 IDR=697
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData sTHA.xml Size=1037 IDR=1142
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTDataoiseTRK.txt Size=1038 IDR=2224
MSI (s) (6C:94) [16:02:24:454]: Executing op: ActionStart(Name=Rollback_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing registry updates,)
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData sTRK.xml Size=1039 IDR=1142
MSI (s) (6C:94) [16:02:24:454]: Executing op: CustomActionSchedule(Action=Rollback_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_UpdateETWMOFWithGUID,CustomActionData=100Removing registry updates100000{2373A92B-1C1C-4E71-B494-5CA97F96AA19}MSSQLSERVERC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn)
MSI (s) (6C:94) [16:02:24:454]: Executing op: ActionStart(Name=Do_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Updating Installed Files,)
MSI (s) (6C:94) [16:02:24:454]: Executing op: CustomActionSchedule(Action=Do_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_UpdateETWMOFWithGUID,CustomActionData=010Updating Installed Files100000{2373A92B-1C1C-4E71-B494-5CA97F96AA19}MSSQLSERVERC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn)
MSI (s) (6C:10) [16:02:24:464]: Invoking remote custom action. DLL: C:WINNTInstallerMSI64F.tmp, Entrypoint: Do_UpdateETWMOFWithGUID
<Func Name='LaunchFunction'>
Function=Do_UpdateETWMOFWithGUID
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_UpdateETWMOFWithGUID
PerfTime Start: Do_UpdateETWMOFWithGUID : Tue Feb 13 16:02:24 2007
<Func Name='Do_UpdateETWMOFWithGUID'>
Calling installSqlEvent Trance
The arguments that are passed to InstallSqlEventTrace are InstanceName: MSSQLSERVER , ProductCodeL: {2373A92B-1C1C-4E71-B494-5CA97F96AA19} , BinPath: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
INFO: Checking installed version
INFO: Writing MOF file
ERROR: Unable to open registry key: HRESULT = 0x80070005, Key = SYSTEMCurrentControlSetControlWMISecurity
The value returned is -2147024891
<EndFunc Name='Do_UpdateETWMOFWithGUID' Return='1603' GetLastError='0'>
PerfTime Stop: Do_UpdateETWMOFWithGUID : Tue Feb 13 16:02:24 2007
Gathering darwin properties for failure handling.
Error Code: 1603
MSI (s) (6C!D0) [16:02:37:273]: Product: Microsoft SQL Server 2005 -- Error 29528. The setup has encountered an unexpected error while Updating Installed Files. The error is: Fatal error during installation.
Error 29528. The setup has encountered an unexpected error while Updating Installed Files. The error is: Fatal error during installation.
<EndFunc Name='LaunchFunction' Return='1603' GetLastError='203'>
MSI (s) (6C:94) [16:02:37:283]: User policy value 'DisableRollback' is 0
MSI (s) (6C:94) [16:02:37:283]: Machine policy value 'DisableRollback' is 0
Action ended 16:02:37: InstallFinalize. Return value 3.
Here's a problem that I can't find anyone else has run into. I'm usingAccess and SQL Server, but the theory would be the same for any db.I have a large number of tables that contain linked records(intersection tables mostly). In the interest of space, I'llillustrate an example:tblStudents (ID, Name)tblTeachers (ID, Name)tblClasses (ID, Name)tblEnroll (StudentID,ClassID,TeacherID)I have about 10 people who each use a separatecopy of this database (in access). I want them (at the end of eachday) to be ableto update all the records that they entered that day into a databasethat I have setup on a server (SQL Server 2005). Both databases havethe exact same structure.Caveat 1: All of the classes, students, and teachers are not the sameon each database, but the server database should contain all of them.Caveat 2: There is no way for the clients to automatically insert intothe server, they are offsite and out of range.Herein lies the problem: when a record is inserted into the server froma client, all of the links are lost since the ID will be different onthe server that it was on the client.I don't think a simple update / insert query will work, and most db'sand languages don't play nice with recordset appends.What are your thoughts??
View 1 Replies View RelatedPerhaps i'm missing something but when i update the master report and then go and run the linked report, it's not updating? Is this a known issue?
If i update the master and re-link the linked report, then all is well? Shouldn't the linked report reflect the master report in real-time and i shouldn't have to re-link the report?
Am i the only one having this problem? Thanks!
Hello
I have an SQL 2005 Express table with the fields DocID (Unique), DocTitle, DocPath and DocSubmitter.
I am using a Web Form to insert records, I can do the Title (textbox) and Path (FileUpload) no problem.
The submitter is linked via a submitterID relationship to another table, submitters. So it will be expecting a number (1-30) not a name as listed in a dropdown list on the web form.
How do I update this field???
Thanks, Mark
I currently have a database that I can update in Microsoft Access by going into datasheet view of the table and just changing the value of a given field.
Here is the problem. I have made a copy of this database by backing it up and restoring to a new database. Now when I go into Access datasheet view to update, I get the following error: "ODBC--update on a linked table '<tablename>' failed". I have tried restoring to a database on the same server as well as others and have checked for differences set for each database as well as differneces in indexes. Any suggestions would be appreciated.
Thanks in advance
Keith
Hi,
I updated a report adding parameter expressions. A linked report based on the report I updated didn't get the parameter expressions when I deployed the base report. Anybody else having that issue? It's not much of a problem. I just have to recreate the linked report which is a nusance.
Thanks,
DD
Hi Guys:
Our company wanted to try out SQL Server 2005 Enterprise Edition (64 Bit). So, we were on free trial of the Enterprise Edition for past 5 months. After which we decided to go for SQL SERVER 2005 Standard Edition (64 Bit). And, Last week, we installed the SQL Server Standard Edition (64 Bit) on our server. After installation, everything was restored as before.
The version we are on right now is:
Microsoft SQL Server 2005 - 9.00.3054.00 (X64) Mar 23 2007 18:41:50 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
Strangely, a job which ran fine till then is failing with the following error: And, to be more specific, when this job is run manually in the form of a stored procedure using the query optimizer it runs fine. But, when its executed as a scheduled job on SQL Agent, it fails. The History logs record the following error.
Error :
The OLE DB provider "SQLNCLI" for linked server "LV-SQL2" reported an error. Authentication failed. [SQLSTATE 42000] (Error 7399) Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "LV-SQL2". [SQLSTATE 42000] (Error 7303) OLE DB provider "SQLNCLI" for linked server "LV-SQL2" returned message "Invalid authorization specification". [SQLSTATE 01000] (Error 7412).
I tried everything possible, even recreated the job, but, no avail.
I also considered the possibility if SQL Agent login account did not have enough permissions. So, I changed the SQL Agent login to windows authentication, but the job still fails. So, its the problem has nothing to do with login accounts either.
For the record, I have cross checked all these too.
1. Enabled the remote connections in Surface Area Config
2. Added local server login to remote server login mappings.
3. Checked 'Rpc' and 'Rpc Out' under server options. Also, the Connection Timeout and Query Timeout have been set to zero (0).
Any suggestions pointing towards problem solution appreciated.
Thank you.
1. Replication Transactional between two servers
-- SQL Server 2005 as Distributors and Subscribers
---SQL Server 2000 as Publishers
2. Linked Servers errors:
" Server (Publication Server) is not configured for DATA ACCESS. (Microsoft SQL Server, Error: 7411)"
Did anyone familiar with this problem?
Thankssss
TJ_1
Hello, I have a datagrid which is populated with data from an MS SQL server database. When I run an update query it always throws an exception - what is the most likely cause for this given that I am using the code below: 1 public void DataGrid_Update(Object sender, DataGridCommandEventArgs e)
2 {
3 String update = "UPDATE Fruit SET Product = @ID, Quantity = @Q, Price = @P, Total = @T where Product = @Id";
4
5 SqlCommand command = new SqlCommand(update, conn);
6
7 command.Parameters.Add(new SqlParameter("@ID", SqlDbType.NVarChar, 50));
8 command.Parameters.Add(new SqlParameter("@Q", SqlDbType.NVarChar, 50));
9 command.Parameters.Add(new SqlParameter("@P", SqlDbType.NVarChar, 50));
10 command.Parameters.Add(new SqlParameter("@T", SqlDbType.NVarChar, 50));
11 command.Parameters["@ID"].Value = DataGrid.DataKeys[(int)e.Item.ItemIndex];
12 command.Connection.Open();
13
14 try
15 {
16 command.ExecuteNonQuery();
17 Message.InnerHtml = "Update complete!" + update;
18 DataGrid.EditItemIndex = -1;
19 }
20 catch (SqlException exc)
21 {
22 Message.InnerHtml = "Update error.";
23 }
24
25 command.Connection.Close();
26
27 BindGrid();
28 }
All of the row types in MS SQL server are set to nvarchar(50) - as I thought this would eliminate any inconsistencies in types. Thanks anyone
I am getting an error (number -2147217887, error message "ODBC--call failed.") when I try to execute an rst.Update. I have an MS Access 2013 application using an ODBC connection to SQL Server 2008 r2. I am using a query to update a table. It is a simple Select query with no joins. I have checked to make sure the table can be updated.
I was not sure if there were any special permissions that I need to set to allow a linked table to be updated in MS Access this way?
could someone please explain the following error msg! the code seg that is gen the error is as follows, followed by the err msg. I"m trying to update a table on a linked server (paeddb1.gold). both servers are running MS SQL7
update paeddb1.gold.dbo.controls_peg
set amt = t.amt
from #temp_peg_control t, paeddb1.gold.dbo.controls_peg p
where t.peg = p.peg
and t.cntl_type = p.cntl_type
and t.fy = p.fy
Could not open table '"gold"."dbo"."controls_peg"' from OLE DB provider 'SQLOLEDB'. The provider could not support a row lookup position. The provider indicates that conflicts occurred with other properties or requirements.
[OLE/DB provider returned message: Errors occurred]
I have a "linked server" configured in my SQL Server 2000 (SP4) server, which used to work correctly. However, I had to reinstall SQL Server (I backed up and restored the master/model/etc databases, so all my settings stayed the same). Since then, I've been getting this error when I try to use the linked server:
Invalid schema or catalog specified for provider 'MSDASQL'.
OLE DB error trace [Non-interface error: Invalid schema or catalog specified for the provider.].
The linked server is a FoxPro database, which does not use catalog or schema names. So, my select syntax looks like this:
SELECT * FROM Server...Table
SQL Server is aparently expecting something like this:
SELECT * FROM Server.Catalog.Schema.Table
Does anyone know how I can fix it so that it allows the "empty dot" method to work like it used to?'
Thanks!
Josh
Hi Pals,
We have an SSIS package within which we are calling a stored procedure which eventually call a sql server dbo.fn() which contains code to lookup data inside oracle using Linked Server for Oracle.
We are calling the Package dynamically from the stored procedure by creating a SQL Server Agent Job, I am getting the below error very often. Can we fix the error in any way?
“EXEC sp_UpdateTname 369,'939390',2008 " failed with the following error: "Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "ORATEST".". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
When I hard code global variables and ran the package I am able to see the successful execution of the package.
Can anybody point out where could the error lies?
I got the following error when using linked server:
OLE DB provider "SQLNCLI" for linked server "SACPANRPT" returned message "Cannot start more transactions on this session.".
Msg 7395, Level 16, State 2, Line 1
Unable to start a nested transaction for OLE DB provider "SQLNCLI" for linked server "SACPANRPT". A nested transaction was required because the XACT_ABORT option was set to OFF.
Hiwhen i try to run a query using linked servers, i get the followingerror.Server: Msg 125, Level 15, State 1, Line 1Case expressions may only be nested to level 10.I do have more than 10 case statements, it works fine when it is lessthan 10. can anyone tell me if there is a way to have more than 10case statements. thanks alot.Jaymy querySelect category, val, Sum(QTY) As QTY , yrFrom(Select val, QTY2 As QTY,KEEP = CaseWhen code = '004' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '005' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '003' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '017' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '007' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '008' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '009' And ((YR > 2003) Or (YR = 2003 And MON > 11))Then 'N'When CODE = '010' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '038' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '032' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '030' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'When CODE = '018' And ((YR > 2003) Or (YR = 2003 And MON > 12))Then 'N'Else 'Y' EndFromamf a Join linkedserver.source.dbo.table2 b On a.COM = b.COMWhere CATEGORY In ('1') And CODE In ('001','003','004','005')And b.YR Between 2003 And 2004 And b.MON <= 1) xWhere KEEP = 'Y'Group By CATEGORY, YR
View 2 Replies View RelatedHI
I have win 2003 64 sp2 SQL 2005 sp2. I downloaded an informix 64bit driver 3.00FC then set system dsn which works fine when i apply and test the connection.
I tried to create a new linked server using Microsoft OLE simple provider against the odbc when I get this error
Does anyone have any suggestions??
Many thanks
Robert
TITLE: Microsoft SQL Server Management Studio
------------------------------
"The test connection to the linked server failed."
------------------------------
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 "MSDAOSP" for linked server "CERP". (Microsoft SQL Server, Error: 7303)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3186&EvtSrc=MSSQLServer&EvtID=7303&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Hello,
SQL Server version is Enterprise Edition 8.00.2039 SP4
and one oracle database linked via Microsoft OLe DB provider for Oracle. Oracle db name: SCP.
One of the job inserts data to sql database from querying oracle database; randomly fails with the error message below.
**************************
INSERT INTO mom_services ('SQL TABLE')
SELECT *
FROM OPENQUERY(SCP,'SELECT SERIAL_NO_ FROM SCADMIN.DEVICEM1 WHERE CONTAINER=''MOM''')
***************************
Server: Msg 7399, Level 16, State 1, Line 3
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: Oracle error occurred, but error message could not be retrieved from Oracle.]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
What I have done;
Oracle client uninstalled server restarted and oracle client installed .
Linked server deleted and recreated but nothing changed.
Any ideas ?
Osman
Hello, I'm installing MOSS 2007 as stand alone which includes SQL Server 2005 Express edition. My install is failing during the DB install. The server is Windows Server 2003, Enterprise Edition SP 2.
The error I'm receiving states "Setup has encountered an unexpected error while updating security settings on HTTP Services".
Here are snippets including the "return value 3" found in the log "SQLSetup0001_COHNTFS15_SQL.log".
Snippet 1:
<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Thu May 01 08:36:14 2008
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='0' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Thu May 01 08:36:14 2008
MSI (s) (D8:EC) [08:36:14:535]: Executing op: ActionStart(Name=Do_PropSetLoginModeNT.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Setting SQL Server Authentication Mode,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (D8:EC) [08:36:14:535]: Executing op: CustomActionSchedule(Action=Do_PropSetLoginModeNT.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_PropSetLoginModeNT,CustomActionData=010Setting SQL Server Authentication Mode50000MSSQL.1)
MSI (s) (D8:40) [08:36:14:535]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI538.tmp, Entrypoint: Do_PropSetLoginModeNT
<Func Name='LaunchFunction'>
Function=Do_PropSetLoginModeNT
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_PropSetLoginModeNT
PerfTime Start: Do_PropSetLoginModeNT : Thu May 01 08:36:14 2008
<Func Name='Do_PropSetLoginModeNT'>
Switching server to NT integrated security
<EndFunc Name='Do_PropSetLoginModeNT' Return='0' GetLastError='0'>
PerfTime Stop: Do_PropSetLoginModeNT : Thu May 01 08:36:14 2008
MSI (s) (D8:EC) [08:36:14:566]: Executing op: ActionStart(Name=Do_HttpServiceSecurity.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Updating security settings on HTTP services,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (D8:EC) [08:36:14:566]: Executing op: CustomActionSchedule(Action=Do_HttpServiceSecurity.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_HttpServiceSecurity,CustomActionData=100Updating security settings on HTTP services100000)
MSI (s) (D84) [08:36:14:566]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI539.tmp, Entrypoint: Do_HttpServiceSecurity
<Func Name='LaunchFunction'>
Function=Do_HttpServiceSecurity
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_HttpServiceSecurity
PerfTime Start: Do_HttpServiceSecurity : Thu May 01 08:36:14 2008
<Func Name='Do_HttpServiceSecurity'>
Error updating HTTPFilter service security (5)
<EndFunc Name='Do_HttpServiceSecurity' Return='1603' GetLastError='0'>
PerfTime Stop: Do_HttpServiceSecurity : Thu May 01 08:36:14 2008
Gathering darwin properties for failure handling.
Error Code: 1603
MSI (s) (D8!20) [08:36:14:785]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29528. The setup has encountered an unexpected error while Updating security settings on HTTP services. The error is: Fatal error during installation.
Error 29528. The setup has encountered an unexpected error while Updating security settings on HTTP services. The error is: Fatal error during installation.
<Failure Type='Fatal' Error='1603'>
<EndFunc Name='LaunchFunction' Return='1603' GetLastError='0'>
MSI (s) (D8:EC) [08:36:14:800]: User policy value 'DisableRollback' is 0
MSI (s) (D8:EC) [08:36:14:800]: Machine policy value 'DisableRollback' is 0
Action ended 8:36:14: InstallFinalize. Return value 3.
Snippet 2:
<Func Name='LaunchFunction'>
Function=Set_CommitFlag
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='F' GetLastError='0'>
Doing Action: Set_CommitFlag
PerfTime Start: Set_CommitFlag : Thu May 01 08:36:22 2008
<Func Name='Set_CommitFlag'>
Set_CommitFlag called successfully.Rollbacked
<EndFunc Name='Set_CommitFlag' Return='0' GetLastError='0'>
PerfTime Stop: Set_CommitFlag : Thu May 01 08:36:22 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (D8:EC) [08:36:22:988]: Executing op: ActionStart(Name=RollbackSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing temporary files,)
MSI (s) (D8:EC) [08:36:22:988]: Executing op: CustomActionRollback(Action=RollbackSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1281,Source=BinaryData,Target=RollbackSupportFiles,)
MSI (s) (D8:7C) [08:36:22:988]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI54B.tmp, Entrypoint: RollbackSupportFiles
MSI (s) (D8:EC) [08:36:23:004]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (D8:EC) [08:36:23:004]: Error in rollback skipped. Return: 5
MSI (s) (D8:EC) [08:36:23:004]: Entering MsiProvideAssembly. AssemblyName: Microsoft.AnalysisServices.AdomdClient,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:004]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:019]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:019]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.Instapi,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:019]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:019]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:019]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.SqlTDiagM,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:019]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:035]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:035]: Entering MsiProvideAssembly. AssemblyName: MSClusterLib,Version="1.0.0.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="1.0.0.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:035]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:050]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:050]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.MgdSqlDumper,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.1399.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:050]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:050]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:050]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.Rmo,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:050]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:066]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:066]: Entering MsiProvideAssembly. AssemblyName: Microsoft.AnalysisServices.DeploymentEngine,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:066]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:082]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:082]: Entering MsiProvideAssembly. AssemblyName: Microsoft.AnalysisServices,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:082]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:082]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:082]: Entering MsiProvideAssembly. AssemblyName: Microsoft.DataWarehouse.Interfaces,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:082]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:097]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:097]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.RegSvrEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:097]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:113]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:113]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.BatchParser,Version="9.0.242.0",Culture="neutral",processorArchitecture="x86",PublicKeyToken="89845dcd8080cc91",FileVersion="2005.90.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:113]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:113]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:113]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.ServiceBrokerEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:113]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:129]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:129]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.WmiEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:129]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:144]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:144]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.ConnectionInfo,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:144]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:160]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:160]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.SqlEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:160]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:207]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:207]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.SmoEnum,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:207]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:207]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:207]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.SString,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:207]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:222]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:222]: Entering MsiProvideAssembly. AssemblyName: Microsoft.SqlServer.Smo,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0", AppContext: , InstallMode: -4
MSI (s) (D8:EC) [08:36:23:222]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (D8:EC) [08:36:23:238]: MsiProvideAssembly is returning: 1607
MSI (s) (D8:EC) [08:36:23:238]: No System Restore sequence number for this installation.
MSI (s) (D8:EC) [08:36:23:238]: Unlocking Server
MSI (s) (D8:EC) [08:36:23:238]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 8:36:23: INSTALL. Return value 3.
last few lines of log:
Property(S): RSVirtualDirectoryManager = Reports$OFFICESERVERS
Property(S): SOURCEDIR = d:a1847ef4f3beaf9c2353Setup
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERACCOUNT = NT AUTHORITYNETWORK SERVICE
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {B266876E-56D9-493C-9322-0C01155F1C52}
Property(S): ProductToBeRegistered = 1
MSI (s) (D8:EC) [08:36:23:441]: Note: 1: 1708
MSI (s) (D8:EC) [08:36:23:441]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.
MSI (s) (D8:EC) [08:36:23:457]: Cleaning up uninstalled install packages, if any exist
MSI (s) (D8:EC) [08:36:23:457]: MainEngineThread is returning 1603
MSI (s) (D84) [08:36:23:566]: Destroying RemoteAPI object.
MSI (s) (D8:E0) [08:36:23:566]: Custom Action Manager thread ending.
=== Logging stopped: 5/1/2008 8:36:23 ===
MSI (c) (104) [08:36:23:597]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (104) [08:36:23:597]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/1/2008 8:36:23 ===
I'm suspecting it's a permission error, but I can't verify this. Any thoughts? Thanks in advance.
I'm trying to execute commands on a SQL Server on the same domain. Following the instructions, I called sp_addlinkedserver N'LinkSQLSrvr', ' ', N'SQLOLEDB', N'NetSQLSrvr' then sp_addlinkedsrvlogin N'LinkSQLSrvr', false, N'Joe', N'Visitor', N'VisitorPwd'. No complaints. When I execute a select statement, however (eg. select top 10 colname from LinkSQLSrvr.dbname.dbo.tblname) I get:
Server: Msg 7353, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' supplied inconsistent metadata. An extra column was supplied during execution that was not found at compile time.
Tried it on different combinations of local and remote servers and I get exactly the same error each time. Help!
SQL 2000
I have a process that calls several stored procs which access a database on a linked server.
code that fails:
SELECT DISTINCT em.er_id, em.er_name, bp.bpo_id, bp.bpo_name
FROM [dbrptc13dayoldprod].ues.dbo.Employer em
Inner Join [dbrptc13dayoldprod].ues.dbo.BPO bp ON
em.er_bpoid = bp.bpo_id
Error message:
Server: Msg 913, Level 16, State 8, Line 1 Could not find database ID 6. Database may not be activated yet or may be in transition.
The database is accessible from query analyzer with a simple select from the linked server. Also if I change any letter in the ues.dbo.Employer em or ues.dbo.BPO bp part to a different case it works fine.
For example: -changed the BPO to BPo- this works!
SELECT DISTINCT em.er_id, em.er_name, bp.bpo_id, bp.bpo_name
FROM [dbrptc13dayoldprod].ues.dbo.Employer em
Inner Join [dbrptc13dayoldprod].ues.dbo.BPo bp ON
em.er_bpoid = bp.bpo_id
Please help I can't figure this one out.
Thanks.
Server: Msg 7356, Level 16, State 1, Line 1 OLE DB provider 'SQLOLEDB' supplied inconsistent metadata for a column. Metadata information was changed at execution time.
OLE DB error trace [Non-interface error: Column 'customerID' (compile-time ordinal 1) of object '"ABCDB"."dbo"."vwCustomer_xxxxk"' was reported to have a DBCOLUMNFLAGS_ISNULLABLE of 0 at compile time and 32 at run time].
above error messages occurs when I try to run a proc which inside a query statement of select to a linked SQL6.5 database. The thing puzzled me is that
linked query to run outside the proc is just fine, but errors within the proc. the running server is MSDE 2k with sp3. Look at knowledgebase about "
DBCOLUMNFLAGS_ISNULLABLE" is only related to DB2 or SQL7 or SQL2000 before sp3.... man...
thanks
I'm running SQL Server 2000 and I have a linked server setup to another SQL Server 2000 box. I've got a stored procedure that creates a temporary table and is pulling information from local tables and from tables located on the linked server. When I run this stored procedure it bombs on me when it hits the linked server part returning an error message of:
Server: Msg 7391, Level 16, State 1, Procedure app_GetOfficeOrders, Line 29
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator.
Now I can run a query against a table located on the linked server that returns just a table count and everything works fine. I'm just having problems with that one stored procedure. Any suggestions would be appreciated.
P.S. I have verified that it isn't a time-out error and it isn't a permissions issues.
Thanks
I am trying to call an RPC from SQL2KSP3 to Sybase ASE 12.5. SQL2K is on an IBM Intel Server running Win2KSP4, ASE is on an IBM RS6000 w/ AIX 5.2.
I have the ASE server set up as a linked server in SQL 2000, and doing queries is working fine, i.e. I can
SELECT * FROM asesrvr.testdb.dbo.tablename
and get back all the data in tablename from the testdb database on the ASE server asesrvr.
However, when I try to run an RPC using the same syntax, I get a generic 7212 error (Could not execute procedure 'procname' on remote server 'asesrvr'. I am calling the rpc with
DECLARE @output char(1)
EXEC asesrvr.testdb.dbo.procname @output output
I'm using Sybase's ASE OLEDB provider; on the Linked Server Properties, I have
General Tab
Product name: asesrvr
Data source: devprod
Provider string: <empty>
Location: greyed out
Catalog: <empty>
Security Tab
One local login, sa, which has impersonate checked as the sa passwords on the two servers are the same (I want to eliminate security as an issue while I try to get this working).
Server Options Tab
Collation Compatible: checked
Data Access: checked
RPC: checked
RPC Out: checked
Use Remote Collation: unchecked
Collation Name: <empty>
Connection Timeout: 0
Query Timeout: 0
SQL2K's @@version is
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Any ideas on how I can troubleshoot this further? It does not appear to be limited to this one procedure (this one only has one output parameter and one line of code, so it's about as simple as it can get for testing purposes). Again, queries work fine, so the linked server itself is connected and working, at least for queries.
Thanks very much for your help,
Vince
Does Anyone know what this means?
I run the query in the attached file on multiple servers with success but some of them refuse to cooperate. I've tried recreating the linked server on the problem servers but this doesn't help. All I want to do is check db file size and free space and get it to work. Why does it have to be so damn complicated?
Any ideas welcome - including an entirely different way of doing this.
The script and table definitions in question are attached
Could not open table '"Helpdesk_New"."dbo"."LogStats"' from OLE DB provider 'SQLOLEDB'. The provider could not support a row lookup position. The provider indicates that conflicts occurred with other properties or requirements.
[OLE/DB provider returned message: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IOpenRowset::OpenRowset returned 0x80040e21: [PROPID=DBPROP_BOOKMARKS VALUE=True STATUS=DBPROPSTATUS_CONFLICTING], [PROPID=DBPROP_COMMANDTIMEOUT VALUE=600 STATUS=DBPROPSTATUS_OK], [PROPID=Unknown PropertyID VALUE=True STATUS=DBPROPSTATUS_OK], [PROPID=DBPROP_IRowsetLocate VALUE=True STATUS=DBPROPSTATUS_CONFLICTING], [PROPID=DBPROP_IRowsetChange VA...
I have setup a linked server to a Sybase database using the ODBC driver (which in turn uses the Sybase OLE DB provider). Logged onto the box as the SQL Service account everything is good. Using Enterprise Manager from any machine to the SQL Server box using an account that is a local administrator on the SQL Server box everything is good. However, if I attempt to make a connection via Enterprise Manager with an account that does not have local administrator rights on the server I get an error. I get the same error if I attempt an OPENQUERY against a table in the Linked server database. The error I receive is as follows:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [SYBASE][ODBC Sybase driver]Allocation of a Sybase Open Client Context failed. Sybase normally generates a SYBINIT.ERR file contianing more specific reasons for failing.]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005: ].
The drives are secured so that only local administrators have rights to them.
I found in the Microsoft KB the follownig article:
http://support.microsoft.com/?kbid=814398
In this article it is suggesting that I need to open up the server from this lockdown. So, just to test this out without having to restart SQL Server I first allowed for full access to the C drive to "Everyone" and everything was good.
My question then is, has anybody else ran into this sort of thing? It doesn't seem right that I have to open up some folder on the database server to everyone in order to get a linked server going.
Thanks
We are currently having the following problem. When trying to connect using "Be made using the login's current security context" I am getting the following error message "Login Failed for NTAuthorityAnonLogin". Yesterday this worked. The setup is as follows
SQL2008R2, nine instances on a cluster. The instance can use "current security context" when both instances are on the same node ie instance 1 node a to instance 2 node a , but when one is on node a and the other is on node b, i.e., instance 1 node 1 to instance 2 node b, we get the error above.
I am trying to use a linked server and it works as long as I do not specify the sp_addlinkedserver @provstr parameter. If I specify that parameter I always get a 7416 "Access to the remote server is denied because no login-mapping exists" error. I have tried adding the logins various ways but it's very specific to the @provstr parameter, and it doesn't even matter what I put in that parameter. As soon as I put something in there whether it is valid or invalid, I get the error.
Anyone else seen this? There is an amazing lack of any discussion about the error when I search for it.
I'm trying to link my local SQL 2005 with a remote oracle database. I have downloaded the oracle 10g client. It seems the client installed a data source driver for me to use (Oracle in OraDb10g_home2). I created a new data source named 'Company' which I have successfully connecting using that driver.
The following is the script I'm using to create my linked server:
USE master
GO
sp_addlinkedserver
@server = 'Company',
@provider = 'OraOLEDB.Oracle',
@srvproduct = 'oracle',
@datasrc = 'Company'
GO
sp_addlinkedsrvlogin
@rmtsrvname = 'Company',
@useself = 'false',
@rmtuser = 'Company1',
@rmtpassword = 'MyPassword'
These both execute successfully.
Then when I go to make a select call:
SELECT * FROM OPENQUERY(Company, 'SELECT * FROM CAMPUS')
I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "OraOLEDB.Oracle" for linked server "Company" reported an error. The provider did not give any information about the error.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "Company".
I think my proplem may be that this provider does not match with my data source.... Any ideas?
I've been assigned with finding the issue behind this error on one of our production systems:
TCP Provider: The semaphore timeout period has expired. [SQLSTATE 07008] (Error 121) OLE DB provider "SQLNCLI" for linked server "SERVER1" returned message "Communication link failure". [SQLSTATE 01000] (Error 7412). The step failed.
I've Googled the error to death, searched the forums here and at other SQL sites as well and have found nothing that points me at the cause. I've found the individual parts of the error but not the whole. Maybe I've just been looking at it too long and am missing something simple. Anyone have any ideas?
These are two linked SQL2005 64bit enterprise Win2k3 servers. The error comes when an automated daily job is run. Sometimes it happens at once, sometimes after 5 minutes, sometimes after an hour. I can see nothing wrong with the server itself or the network.
Thanks in advance.
Hi,
I
was making a linked server connection between SQL Server 2000 and
Oracle 8.1.5 (both running on Windows 2000 Server), and I was creating
an insert trigger in one of the SQL Server table to insert the same
value to the Oracle table. But when I try to make an insert to the
table, the following error occurred :
Server: Msg 7391, Level 16, State 1, Procedure <triggername>, Line xx
The operation could not be performed because the OLE DB provider 'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA' ITransactionJoin::JoinTransaction returned 0x8000d048].
I
tried to change the trigger into a SELECT statement only and the error
still occurred. But when I tried to insert a row directly to the linked
server via Query Analyzer, it succeeded.
I have read KB 280106, KB
306212, and KB 329332, and I've tried SET XACT_ABORT ON statement, but
none of them can solve the problem.
If there's anyone who has idea on what's wrong or has a suggestion what I should try please help.
Thank you in advance.
Hello,
I am trying to create the linked server to IBM DB2 server, and getting the following error message. Can some one take a look at this and let me know. Thanks!
TCP Provider: No connection could be made because the target machine actively refused it.
OLE DB provider "SQLNCLI" for linked server "Linked server name" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "linked server name" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". (Microsoft SQL Server, Error: 10061)
even if I create the linked server using the management studio I am getting the following error when I try to test the connection for the linked server.
TITLE: Microsoft SQL Server Management Studio
------------------------------
"The test connection to the linked server failed."
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The OLE DB provider "DB2OLEDB" has not been registered. (Microsoft SQL Server, Error: 7403)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=7403&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------