Hi~~.
In client side, the sqlncli is needed.
Below is the script of installing sqlncli.msi package.
msiexec /i sqlncli.msi /quiet /norestart /le C:sqlncli.log
Question is, how can I check the installation?
If it is already installed skip the installing process.
If not install the package.
I tried to install a sql 2005 desktop engine. This fails with the error: An installaton package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package €˜sqlncli.msi€™ I used a fresh, new download SQLEXPR.EXE. What shall I do?
I have spend days trying to install SQLEXPR_ADV.EXE. I need it to run the Pinnacle Studio 10 installation fully. I have managed to switch on all the services that the set up demanded, but I keep getting stuck because the installation cannot find sqlncli.msi. I have a copy of it from the SQL site, but where do I stick it so that the installer can find it. I have tried to place it in the SQL directory in Program Files, I have placed it in the folder which is generated by the installer, I have sat it next to the Installer itself but to no avail. I have installed the msi independently nd the process says that it was successfully installed but the SQL2005 Express Installed still cannot find it.
Help!
Hello, I've a problem with a software developed in C# with the framework 2.0. This is the error I receive : The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" was unable to begin a distributed transaction. OLE DB provider "SQLNCLI" for linked server "XXX_LINKED_SERVER" returned message "No transaction is active.". If I try directly to restart the process, it works fine. Is there someone who can help me ? This is the process 1. In C# --> Call of a Query : select from the linked server (db in sql 2005) and insert into a table SQL 2005 2. In the C# --> using (TransactionScope scope = new TransactionScope()) and insert in a table in SQL 2005 which is link server Thank in advance.
View 1 Replies View RelatedDeployed Report having SSIS package as source do not work when Indirect Package configuration is used in ETL package. It seems ETL package when called/executed from Report manager does not recognize environment variable to pick up the dtsconfig file.
The Report works when Direct package configuration is used to same dtsconfig file.
What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod very difficult.
SQL Server 2005 Setup Fails. I've followed all the instructions but keep
View 12 Replies View RelatedHi,
I'm looing for advice on how to organize my SSIS packages. I'll quickly describe my requiremenst, and then outline how I see the solution.
1. Should work for development in BI Studio. Design time experience should be good, so static schema information should be available in all steps. Packages should run in debug mode inside BI Studio.
2. Should be able to run automated tests (which I gather is difficult. See proposed solution below). Tests should run both on a test machine, in batch mode, and from BI Studio.
3. Should work for deployment.
The packages should be fine-grained. Automated tests will be implemented as SSIS packages that call the packages to be tested via an Execute Package Task. There will be one test package per testcase. A test will look like: [Create Schema] -> [Load test data]->[Execute Package to be tested]->[Verify expected results]->[Teardown].
There will be one master test package that executes all the tests.
For this I need a) some way to vary the connections for the packages depending on whether they are run from a testcase or from the normal control flow. I'm considering making the connection strings configurations based on a parent package variable. Other configuration types strike me as not suitable since developers will want to run packages both as part of normal flow and as testcases on their machines. Is this a viable strategy? Any drawbacks?
b) need to organize testcases some way. I tried putting tests in a subfolder of the project to minimize the clutter, but BI studio shows them at the root node. I tried putting a new project (for containing the tests) in the same folder, and adding the packages (via add existing item), but BI Studio insists of adding copies (!) of the package files, rather than reusing the existing files. Any suggestions?
I welcome any feedback, suggestions of alternate strategies, etc.
/Anders
I keep getting a failure when trying to run my agent which is trunning an SSIS 2005 package. I have checked the logins and appear to have given the right logins owner to the msdb database and my other databases but still getting this error:
03/09/2006 10:13:31,Run EBN Process,Error,0,BG-22SQL,Run EBN Process,(Job outcome),,The job failed. The Job was invoked by User domainmyuserid. The last step to run was step 1 (Run EBN SSIS Package).,00:00:02,0,0,,,,0
03/09/2006 10:13:31,Run EBN Process,Error,1,BG-22SQL,Run EBN Process,Run EBN SSIS Package,,Executed as user: domainaccount_we_setup_to_run_all_sql_services_on_this_server. The package execution failed. The step failed.,00:00:02,0,0,,,,0
Is it the package that is failing or permission issue?
Hi,
I would like to now how can I check if a specific package is running now, at the moment.
the reason I need it is because I enable in a web page to run ssis package using web servise. I would like to be sure that no more than 1 person is starting the package until it completes.
Does any one has any idea?
Iram
I have scheduled an SQL Job to run every 15 mins. This runs an SSIS package. But sometimes my package might execute for more than 15 mins. In this case, a second instance of the package would start. I don't want this to happen. So is there any way I can check whether the package is already running before I continue the execution of the same. Right now I am using a mutex to handle this problem. Are there any problems using the mutex and is there a better way to handle this?
Thanks in advance.
Sumesh
How to Deploy SQL server Database to another PC, How to create apackage that craetes Database as well as ODBC driver for accessing dataat enduser PC, using .Net VB
View 2 Replies View Relatedhi,
i'm total newbee on SSIS packages and therefore need guidance.
I want to make a ssis package that (in order):
- check in table (tbl_orders) if there is any new order made
- if new order is made, update column (time_last_change)
- if this order has geography ID (ID_geography) inserted, insert name of geography.
Thank you in advance,
Hi,
My name is Vinh, I am a new bee in SQL Server 2005. I am using template script (see below) from SQL Server to create account but when I am right click in database mail for testing email and I got the message, could not connect to mail server.
Below I am trying to use smtp to connect but I know in my company we are using Exchange Mail Server. will that make a lot different?
Please help me,
Thank you very much,
sp_configure 'database mail xps', 1
GO
reconfigure
GO
-------------------------------------------------------------
-- Database Mail Simple Configuration Template.
--
-- This template creates a Database Mail profile, an SMTP account and
-- associates the account to the profile.
-- The template does not grant access to the new profile for
-- any database principals. Use msdb.dbo.sysmail_add_principalprofile
-- to grant access to the new profile for users who are not
-- members of sysadmin.
-------------------------------------------------------------
DECLARE @profile_name sysname,
@account_name sysname,
@SMTP_servername sysname,
@email_address NVARCHAR(128),
@display_name NVARCHAR(128);
-- Profile name. Replace with the name for your profile
SET @profile_name = 'TestProfile';
-- Account information. Replace with the information for your account.
SET @account_name = 'vdang';
SET @SMTP_servername = 'smtp.cgdnow.com';
SET @email_address = 'vdang@cdgnow.com';
SET @display_name = 'Vinh, Dang';
-- Verify the specified account and profile do not already exist.
IF EXISTS (SELECT * FROM msdb.dbo.sysmail_profile WHERE name = @profile_name)
BEGIN
RAISERROR('The specified Database Mail profile (<profile_name,sysname,SampleProfile>) already exists.', 16, 1);
GOTO done;
END;
IF EXISTS (SELECT * FROM msdb.dbo.sysmail_account WHERE name = @account_name )
BEGIN
RAISERROR('The specified Database Mail account (<account_name,sysname,SampleAccount>) already exists.', 16, 1) ;
GOTO done;
END;
-- Start a transaction before adding the account and the profile
BEGIN TRANSACTION ;
DECLARE @rv INT;
-- Add the account
EXECUTE @rv=msdb.dbo.sysmail_add_account_sp
@account_name = @account_name,
@email_address = @email_address,
@display_name = @display_name,
@mailserver_name = @SMTP_servername;
IF @rv<>0
BEGIN
RAISERROR('Failed to create the specified Database Mail account (<account_name,sysname,SampleAccount>).', 16, 1) ;
GOTO done;
END
-- Add the profile
EXECUTE @rv=msdb.dbo.sysmail_add_profile_sp
@profile_name = @profile_name ;
IF @rv<>0
BEGIN
RAISERROR('Failed to create the specified Database Mail profile (<profile_name,sysname,SampleProfile>).', 16, 1);
ROLLBACK TRANSACTION;
GOTO done;
END;
-- Associate the account with the profile.
EXECUTE @rv=msdb.dbo.sysmail_add_profileaccount_sp
@profile_name = @profile_name,
@account_name = @account_name,
@sequence_number = 1 ;
IF @rv<>0
BEGIN
RAISERROR('Failed to associate the speficied profile with the specified account (<account_name,sysname,SampleAccount>).', 16, 1) ;
ROLLBACK TRANSACTION;
GOTO done;
END;
COMMIT TRANSACTION;
done:
GO
I have created a package that use SSIS check pointing for failure-retry mechanism. I knew that when this package fails, on restarting the package it starts from the task where it got failed.
Is it possible for me to override this on a custom condition and start the package at an earlier task where it executed successfully?
Ex:
Check pointing is enabled.
FTP task è Write to Staging Table è Write to Target table.
Assuming I am downloading XML file through FTP and writing to a table.
FTP Download is successful.
Read from XML file and write to Staging table task failed because of downloaded file is not a well formed XML.
Here, FTP task is completed successfully; it failed only in the second task. When I re-run the package; it starts from the second [Read from XML file and write to staging table] task because of check pointing.
Is it possible for me to restart from the FTP task on a custom condition where it executed successfully?
hi guys,
I'm using MS SQL Server 2005 with MDAC 2.8. When I test my project into TCP/IP, the project does not pick the records completely.
My connection string is using Provider=SQLNCLI.1
Do I need to install SQL Native Client to work-stations ?
Do I need to remove the MDAC ?
Than you.
I have a strange problem.
On almost all clients I can connect to mys database server using sqlcmd -S <server> and the connection is authenticated using kerberos.
One one of my clients the command fails. When I have Named Pipes enabled the connection works fine but is made with NTLM authentication.
All servers and clinets are members of the same domain and thay are ll on the same LAN segment. No firewalls are active anywhere.
Where do I look for a solution?
Hello Folks,
We are using the Redistributable installer for the SQL Native client, SQLNCLI.MSI, with our solution. On MSDN here: http://msdn.microsoft.com/en-us/library/ms131334.aspx it recommends using the APPGUID keyword to specify your application product code. This is to ensure that the installer will know the dependancy between the Native Client and your application.
Unfortunately there doesn't seem to be much info around APPGUID itself. Does anyone know how that ID is generated? What the rules around it are? Or just some better definition of where it comes from?
Thanks, Mark
I was trying to update a named instance of SQL Express SP1. I double clicked it and during extraction I get this error message:
The file C:Document and SettingsByersNLocal SettingsTempBSISQLEXP05TRACTsetupsqlcli.msi could not be opened.
SQL Express came bundled with another porgram so I'm thining it could be a bad cd. I also thought about reinstalling Windows Installer 3.1. Anybody experience this error?
I recently my hosting company to provide SQLNCLI provider for MS SQL2005 DB. Right now, they are only providing SQLOLEDB provider for connection.
Connection is slow and unreliable at this point using sqloledb while it was running fine with SQL 2000 db.
When I asked them for SQLNCLI, they replied...
------------------
Unfortunately we cannot install the SQLNCLI driver for MSSQL 2005 as it runs under the system context which would be a security risk to the server. I apologize for the inconvenience.
If you have any questions or require additional assistance, please do not hesitate to contact our support team anytime at
----------------------
How true is this? Will it be really risk? It doesnt make sense to me if this would be risk why microsoft even will produce it.
Can anyone throw some light on this issue?
Thanks
I'm looking for some code snippet that will allow me to use ADO.NET and the SQL Native client for database failover scenarios.
Currently what I have does not work and am running out of options.
I would greatly appreciate any help.
Thanks,
Luis B
Hi all,
I need to be able to create a DSN through code that connects to SQL Server using SQL Native Client. I have found the following article: http://support.microsoft.com/kb/q184608/. This demonstrates most of what I need, but it does not show how to set the username and password, which is something that I need to do.
Any ideas how I can do this?
Regards,
Stephen.
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.
I am running a SQL2K on a Server2K box. I have linked servers to SQL2005 Express on WinXP. I am trying to get data off of the SQL2005 DB to the central DB on SQL2K. This has been running for about a year. I am now getting an error message as follows:
Server: Msg 7356, Level 16, State 1, Line 1
OLE DB provider 'SQLNCLI' supplied inconsistent metadata for a column. Metadata information was changed at execution time.
OLE DB error trace [Non-interface error: Column 'TestVarChar' (compile-time ordinal 2) of object '"WKS"."DBo"."testtable"' was reported to have changed. The exact nature of the change is unknown].
When I run the following Queries on the SQL2K box:
SELECT * from WKSA400.WKS.DBo.testtable
or
SELECT * from OPENQUERY(WKSA400, 'SELECT * from WKS.DBO.testtable')
I did notice that if my testtable has only numeric fields, it works fine. It only has a problem with alphanumeric fields.
If I run 'exec sp_tables_ex WKSA400' on the SQL2K, it works fine. I get a listing of all the tables on the remote server. This tells me that my security is fine. It seems to be a conversion from the 2005 to 2000 SQL. If it had not been working for over a year, the dent in the wall the size of my head would be much smaller.
Howdy Folks!
So I tried the typical IDBDataSourceAdmin:estroyDataSource() command to destroy an existing sql server 2005 express database and guess what it returned:
E_NOTIMPL (not implemented)
This leaves me in the dark on how I'm supposed to drop an existing database in SQL Native Client OLEDB. Any ideas?
My specific code is:
//Set initialization properties.
hr = m_pIDBInitialize->QueryInterface(IID_IDBProperties, (void **)&m_pIDBProperties);
CHKHR(hr, L"Failed to obtain IDBProperties interface", _ExitCreate);
// Sets properties in the Data Source and initialization property groups
hr = m_pIDBProperties->SetProperties(uiNumPropsets, dbpropset);
CHKHR(hr, L"Failed to set data source properties", _ExitCreate);
//Attempt to initialize connection
hr = m_pIDBInitialize->Initialize();
hr = m_pIDBDataSourceAdmin->DestroyDataSource();
hr = m_pIDBInitialize->Uninitialize();
Thanks!!
Hi,
I just migrated a SQL7 instance into SQL2005. Use the backup and restore method. The following was the steps done :
1) Database Backup from sql7 and restore on sql2005
2) Create user on sql2005
3) Configure SQL Native client for instance
- When apps tried to access the server, they encounter the following error
Could not find server ServernameSQL7 in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. - /elogs/lib/db.asp, line 70
4) As requested, i ran sp_addlinkedserver Servername. After which the apps got back with this error
OLE DB provider "SQLNCLI" for linked server "Servername" returned message "Login timeout error" - /elogs/lib/db.asp, line 70
I am unsure of how to proceed from here. Please assist.
Thanks and Regards,
Siva
I am running an SSIS package to extract data from a source SQL Server database to our own database. The source is on a linked server. The package worked until a column size was increased on a table on the source.
If I run a query against the linked server table I get the following error:
'OLE DB provider 'SQLNCLI' for linked server 'GSC-RPT.SVR.BANKONE.NET' returned data that does not match expected data length for column '[GSC-RPT.SVR.BANKONE.NET].[Peregrine].[dbo].[scProblem].short_description'. The (maximum) expected data length is 100, while the returned data length is 160.'
I've tried deleting the links and recreating them. Nothing works. I don't understand why my database query is expecting a data length of 100. Why does it not pick up the definition of the field length from the linked server? How has it retained this expectation when I have deleted the linkage and recreated it?
Hi,
I am trying to setup up a linked server in our test environment that allows Server A to run a stored procedure that writes to server B. However, I am receiving the following errors when attempting to make the connection and execute the stored procedure.
OLE DB provider "SQLNCLI" for linked server "TEST2" returned message "Invalid authorization specification".
Msg 7399, Level 16, State 1, Procedure Test_SP, Line 230
The OLE DB provider "SQLNCLI" for linked server "TEST2" reported an error. Authentication failed.
Msg 7303, Level 16, State 1, Procedure Test_SP, Line 230
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "TEST2".
I've created a user (linkuser) that has db_reader/db_writer access to the destination box. I'm using SQL Server under the Server type on the General Tab. I've added the user(linkuser) as the local login to impersonate on the destination box. However, the stored procedure is still erroring. Any Suggestions?
Thanks,
J
I have a client/server app with a connection string:
Provier=SQLNCLI;Server=ServerIP;Database=DBName;UID=Name;PWD=Password
This connection string works for Vista 64bit but not for Vista Business 32bit...
What have I done so far to the Vista Business 32bit...
1. Downloaded/Installed SQLNCLI from Microsoft Site
2. Tested the connection string several ways with no luck...
3. Was able to get Vista Business 32bit to connect via a File DSN with the same credentials... DSN route is not an option for this app...
Any ideas?
I am linking to another SQL Server database to extract data into my own system. Following an increase in size on one of the columns in a table I am extracting, I am getting the following error:
'OLE DB provider 'SQLNCLI' for linked server 'gsc-rpt.svr.bankone.net' returned data that does not match expected data length for column '[gsc-rpt.svr.bankone.net].[Peregrine].[dbo].[scProblem].short_description'. The (maximum) expected data length is 100, while the returned data length is 148'
The column short_description has been increased from 100 to 1024. Writing a simple query, SELECT (max(len(short_description)) FROM dbo.Peregrine_Problem will generate the error, but if I embed the same SQL into an Excel VBA macro and connect to the server, it happily returns the result 1024. Our Access databases also link to the table on the remote server and handle the increased column size properly.
I have done everything I can think of, including deleting the linked server within SQL Server MS, and recreating it, but I can't override the setting of 100.
Any ideas?
Does anyone know how to configure a mirrored pair as a linked server on a 3rd instance?
Say I have a mirrored database on two servers: PRIMARY and SECONDARY.
I want to create a linked server on a 3rd machine that allows me to access the database on the mirrored pair.
This is what I'm using:
EXEC master.dbo.sp_addlinkedserver
@server = N'MIRROR',
@srvproduct=N'',
@provider=N'SQLNCLI',
@provstr=N'Server=PRIMARY;FailoverPartner=SECONDARY;'
select count (*) from mirror.pubs.dbo.authors
and it works fine if the database on PRIMARY is alive. however when the mirror has failed over to SECONDARY and PRIMARY is no longer available, I get the following when I try to query the database via the linked server:
OLE DB provider "SQLNCLI" for linked server "MIRROR" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "MIRROR" 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.".
Msg 10061, Level 16, State 1, Line 0
TCP Provider: No connection could be made because the target machine actively refused it.
As far as I can tell, it doesn't try to contact SECONDARY at all. It seems like SQL Server is ignoring the FailoverPartner attribute.
If I switch PRIMARY and SECONDARY in the connection string (ie @provstr=N'Server=SECONDARY;FailoverPartner=PRIMARY;') then it works when SECONDARY is online, but not when the mirror has failed back to PRIMARY.
Any ideas?
Piers.
I have .NET Framework 2.0 and Visual studio 2005 installed on my machine. I also have SQL Server 2000 Developer Edition installed with Service Pack 4.
When I try to install SQL Server 2005 express, I get an error when the setup tries to install SQL Native Client. I have read many forums, but couldnt find a resolution. I can not see SQL Native Client in my Add Remove Programs either.
I tried to unzip the SQLEXPR.exe into a temp folder and when I right click sqlncli.msi and say Repair or Uninstall. It says "This action is valid for products that are currently installed."
When i try to run the sqlncli.msi file ..i get an error message saying "Installation of Microsoft SQL Server Native Client failed because a higher version already exisits on the machine. To proceed uninstall the higher version and then run Microsoft SQL Server Native Client Setup"
Please help as I am unable to install SQL Server 2005 Express....
SQL Server Native Client -- Set up failed
SQL VSS Writer -- Set up failed
Database Services -- Set up failed
Thank you in advance
Log mesg -==
Verbose logging started: 12/17/2007 23:18:36 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (74:B4) [23:18:36:828]: Resetting cached policy values
MSI (c) (74:B4) [23:18:36:828]: Machine policy value 'Debug' is 0
MSI (c) (74:B4) [23:18:36:828]: ******* RunEngine:
******* Product: {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
******* Action:
******* CommandLine: **********
MSI (c) (74:B4) [23:18:36:828]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (74:B4) [23:18:36:828]: Grabbed execution mutex.
MSI (c) (74:B4) [23:18:36:828]: Cloaking enabled.
MSI (c) (74:B4) [23:18:36:828]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (74:B4) [23:18:36:828]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (100) [23:18:36:828]: Grabbed execution mutex.
MSI (s) (10:E0) [23:18:36:843]: Resetting cached policy values
MSI (s) (10:E0) [23:18:36:843]: Machine policy value 'Debug' is 0
MSI (s) (10:E0) [23:18:36:843]: ******* RunEngine:
******* Product: {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
******* Action:
******* CommandLine: **********
MSI (s) (10:E0) [23:18:36:843]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (10:E0) [23:18:36:843]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (10:E0) [23:18:36:843]: User policy value 'DisableMedia' is 0
MSI (s) (10:E0) [23:18:36:843]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Looking for sourcelist for product {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Adding {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Now checking product {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Media is enabled for product.
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Processing net source list.
MSI (s) (10:E0) [23:18:36:843]: Note: 1: 1706 2: -2147483647 3: sqlncli.msi
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Processing media source list.
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Trying media source G:.
MSI (s) (10:E0) [23:18:36:843]: Note: 1: 2203 2: G:sqlncli.msi 3: -2147287038
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (10:E0) [23:18:36:843]: Note: 1: 1706 2: -2147483647 3: sqlncli.msi
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Processing URL source list.
MSI (s) (10:E0) [23:18:36:843]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (s) (10:E0) [23:18:36:843]: Note: 1: 1706 2: -2147483647 3: sqlncli.msi
MSI (s) (10:E0) [23:18:36:843]: Note: 1: 1706 2: 3: sqlncli.msi
MSI (s) (10:E0) [23:18:36:843]: SOURCEMGMT: Failed to resolve source
MSI (s) (10:E0) [23:18:36:843]: MainEngineThread is returning 1612
MSI (c) (74:B4) [23:18:36:859]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (74:B4) [23:18:36:859]: MainEngineThread is returning 1612
=== Verbose logging stopped: 12/17/2007 23:18:36 ===
Does anyone know how to configure a mirrored pair as a linked server on a 3rd instance?
Say I have a mirrored database on two servers: PRIMARY and SECONDARY.
I want to create a linked server on a 3rd machine that allows me to access the database on the mirrored pair.
This is what I'm using:
EXEC master.dbo.sp_addlinkedserver
@server = N'MIRROR',
@srvproduct=N'',
@provider=N'SQLNCLI',
@provstr=N'Server=PRIMARY;FailoverPartner=SECONDARY;'
select count (*) from mirror.pubs.dbo.authors
and it works fine if the database on PRIMARY is alive. however when the mirror has failed over to SECONDARY and PRIMARY is no longer available, I get the following when I try to query the database via the linked server:
OLE DB provider "SQLNCLI" for linked server "MIRROR" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "MIRROR" 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.".
Msg 10061, Level 16, State 1, Line 0
TCP Provider: No connection could be made because the target machine actively refused it.
As far as I can tell, it doesn't try to contact SECONDARY at all. If I switch PRIMARY and SECONDARY in the connection string (ie @provstr=N'Server=SECONDARY;FailoverPartner=PRIMARY;') then it works when SECONDARY is online, but not when the mirror has failed back to PRIMARY.
Any ideas?
Piers.
I'm trying to retrieve native character data (SQL_WCHAR) through ODBC into an SQL_C_CHAR buffer using SQLBindCol and SQLFetch.
The database is SQL Server 2005 Developer Edition.
If I use DRIVER={SQL Server}, i.e., use SQLSRV32, everything gets converted properly.
If I use DRIVER={SQL Native Client}, i.e., use SQLCNLI, I apparently get garbage. This is true for ntext, nchar and nvarchar. I also have problems with xml, but I haven't gotten far enough to isolate what's going on with it.