Hi!!!
I got a problem, if i try to connect with SQL Native client by IP (exemple: 192.168.1.2MYDATABASE) it doesn't work. But I use: HOMEMYDATABASE it works. But in the 2nd case i cannot connect to SQL Server from another computer.
Thanks fr your help.
fred
When I create a new odbc connection to a SQL server 2005 Db I get a failure telling me dat de SQL server does not allow remote connections.
How can I allow the server to allow this.
Any help appreciated
regards
I am working in a distributed environment, I verified msgs have been successfully send from server1 db1 to server2 db2, but I still get the following error msg from the sender server through SQL profile:
Connection attempt failed with error: '10061(No connection could be made because the target machine actively refused it.)'.
Does anyone experienced the samething?
Thanks!
I have a new server SQL 2005 im setting up a linked server to my 2000 box, however the connection is being refused: Error 10061.
The strange part of it is.
I have other SQL 2000 machines that can connect to this box over the linked server, and I have one linked server from 2005 to a different 2000 box working.
From remote desktop on my new 2005 box I can ping and connect via object explorer to the machine in question. One difference that exists between the 2000 server I can link to and the one that I can not is the port.
The box I can not connect to is on 2433 with the hide server option turned on.
Yes I have tried both the IP and Named pipe with port information when connecting.
Your assistance is appreciated.
Thank you.
You can do anything at www.zombo.com
Hello,
I am not sure if this is the right forum.
This is the first time that I have seen this error,
No connection could be made because the target machine actively refused it
I have a web app that when some one inserts text in a text box and clicks a button it creates a new web page and a new table in the database. Up until this point it has always worked. A datalist returns the data. In the datalist there is a hyperlink that when clicked takes the client to the new webpage. But for some reason it is not working now and that is the error above.
I am lost. Any help appreciated.
Thanks Matt
All,
-> SQL Server 2005 Standard set as a named instance, runs as a local system
-> SQL Server protocol enabled: TCPIP (configured to listen on port 1433 with use of dynamic ports disabled)
-> Remote connections through the SQL Server Surface Area Configuration.
Server starts successfully.
But, I received the following error on trying to process a cube from BI studio is -
OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; TCP Provider: No connection could be made because the target machine actively refused it.
; 08001.
Any hints on how to resolve this problem?
Thanks,
Sanchet
Hi All,
I have created an application using service broker.i have a source database which in a particular server say server A and want to send message to target database which is in another server say server B.
i have configured all the service broker objects and advanced service broker objects in correct way by reffering the site --http://www.sqlservercentral.com/columnists/sindukuri/2797.asp
but when i am trying to send message from my source server to target server , i am getting the following error in sys.transmission_queue.
Connection attempt failed with error: '10061(No connection could be made because the target machine actively refused it.)'.
I have enabled the tcp port in both the server.
Note-My source server is an XP and Target Server is an windows server 2003.
can anybody please tell do i need to set any extra configuration in windows server 2003 or any thing do l need to do which i have left.
please do help!!!!!!!!!!!!!!!!!!
Thanks a lot in advance.....................................
I cannot connect to my SQL2005 server using the old SQL ODBC drivers, I have to use the Native client drivers. The database I am trying to connect to is a SQL 2000 db I just attached. Its owner is a SQL user login, which works fine and can connect remotely.
Thoughts?
Possibly related: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=96732
I found a peculiar thing today while working with SQL Mobile in a multithreaded application (VS2005, application for Pocket PC 2003).
I created a class which has one SqlCeConnection object. Every time I call a function to insert/select/delete something from the local db, I open the connection, execute the query an then close the connection again.
But when I'm calling a function from the db class in thread 1 and in the meantime call a different function (from the same db class of course) in thread 2, things go wrong. Because when function 1 wants to close the connection, function 2 is still using the connection and it will crash my application with a native exception (0xC0000005: access violation).
I can see why the error is happening, but shouldn't there be a nice .NET handled exception instead of a native exception which grinds my app to a hold?
(A workaround I use now is to use multiple connection objects instead of one, but I thought I'd give this feedback anyway)
Hi,
I have two server instances of SQL on my server MYSRVR: default (SQL 2000) and named SQLX (SQL 2005).
I've been using these strings ok for the default (SQL 2000):
"Server=MYSRVR; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
"Server=192.168.1.128; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
and these for the named (SQL 2005)
"Server=MYSRVRSQLX; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
"Server=192.168.1.128SQLX; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
But then adding the SQL port 1433 works for the default:
"Server=MYSRVR,1433; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
"Server=192.168.1.128,1433; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
But this, for named (SQL 2005) actually connects to default. The SQL port is causing the name SQLX to be ignored.
"Server=MYSRVRSQLX,1433; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
"Server=192.168.1.128SQLX,1433; Database=mydb; Network=dbmssocn; Integrated Security=SSPI "
Anyone any ideas?
Hello All,
I need you help badly. Iam a student and iam working on "Creating a Mobile Application with SQL Server Compact Edition" http://msdn2.microsoft.com/en-us/library/ms171908.aspx . This tutorial works fine until
Create the publication snapshot
In SQL Server Management Studio, in Object Explorer, expand the (local) computer node.
Expand the Local Publications folder, select the publication name, right-click SQLMobile, and then click View Snapshot Agent Status.
In the View Snapshot Agent Status dialog box, click Start.
Make sure that the snapshot job has succeeded before you continue.
When I try to create a snapshot iam getting the following error "An unspecified error had occurred in the native SQL Server connection component." . I have no clue what to do next please help me out.
Hi,
I experienced this problems on both Windows Mobile 2003 SE and Windows Mobile 5.0.
Its native development (c++, oledb, atl and mfc).
It's quite simple to reproduce...
1. open a database
2. open a rowset on table A (whatever, valid of course and with both IOpenRowset and ICommandText), read datas and close rowset
3. power off
4. power on
5. try step 2 with another table (failed on openrowset with error 0x80004005) or try table A (sometimes working because of cached memory, sometims failed on Read Datas).
6. being stuck ;-)
Our work-around was, in case we loose our connection (identified by error 0x80004005 on openrowset), we close it and re-open database... ugly for sure, but working.
What I'm looking now is to use some kind of "detection method" like what people in .Net develoment are using "if ConnectionState.Open <> ...) for reopening my database only on demand...
Thanks in advance for any hints,
Fabien.
Dear all,
we have tables with many image columns. We fill these image columns via ODBC and SQLPutData as described in MSDN etc (using SQL_LEN_DATA_AT_EXEC(...), calling SQLParamData and sending the data in chunks of 4096 bytes when receiving SQL_NEED_DATA).
The SQLPutData call fails under the following conditions with sqlstate 08S01
- The database resides on SQL Server 2000
- The driver is SQL Native Client
- The table consists e.g. of one Identity column (key column) and nine image columns
- The data to be inserted are nine blocks of data with the following byte size:
1: 6781262
2: 119454
3: 269
4: 7611
5: 120054
6: 269
7: 8172
8: 120054
9: 269
The content of the data does not matter, (it happens also if only zero bytes are written), nor does the data origin (file or memory).
All data blocks including no 7 are inserted. If the first chunk of data block 8 should be written with SQLPutData the function fails and the connection is broken. There are errors such as "broken pipe" or "I/O error" depending on the used network protocol.
If data no 7 consists of 8173 bytes instead of 8172 all works again.
(Changing the 4096 chunk size length does not help)
Has anybody encountered this or a similar phenomenon?
Thank you
Eartha
Hi
i connect to remote Integration Service. i configure server for remote connection( on component services and DCOM config , ... ) .and now i can connect to Integration Service remotely and correctly.
but when i expand Stored Package and then click to expand MSDB this error will hapen:
login failed for user ... .(microsoft sql native client )
please help me
thanks in advance
How to use Microsoft Data Link(Udl) type file to connect with SQL Server using SQL Native Client,If i use OLDEDB Connection i can make connection using UDL file with Database ,but how can i use a file for a connection using SQL Native Client.Is there any other data link file that can be used to connect with SQL server using SQL Native Client.
View 5 Replies View RelatedOn Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection
Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.
I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
I have tried this on several different operating systems (VISTA and XP ) and several versions of SQL NATIVE CLIENT including 2005.90.3042.0
I have a 64 bit "SQL NATIVE CLIENT" connection that fails. The exact same connection and code succeeds on 32 bit.
My customer and I prepend "oledb:" to the connection string and it starts working.
FAILS on 64 bit:
Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
WORKS
oledb:Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
I debugged my code to the point that I know it is happening when I call CreateAccessor for my SQL statement.
m_hr=m_pIAccessor->CreateAccessor(DBACCESSOR_ROWDATA, GetCols(), (m_pDBBinds+IsBookmarked()), 0, &m_hAccessor, NULL);
Error:
Microsoft SQL Native Client: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Does anyone have any suggestions?
Hi, I have 2 windows 2000 server in cluster with sql server 2000 enterprise edition installed.
I have activated the Server-Requested Encryption by using the sql server network utility (Force Protocol Encryption). After this, I have stoped sql server service. But I can't start it at this moment.
The error is:
19015: The encrypton is required but no available certificat has been found.
Please help me to start sql server.
Thanks.
Michel
I made a point type by C# for deploying in SQL2005.
It builds successfully every time.
When I deploy, it gives the following error:
"Error: Type "SqlServerProject1.TypePoint" is marked for native serialization, but field "x" of type "SqlServerProject1.TypePoint" is not valid for native serialization." although x variable is value type decimal.
using System;
using System.Data;
using System.Data.SqlClient;
using System.Data.SqlTypes;
using Microsoft.SqlServer.Server;
[Serializable]
[SqlUserDefinedType(Format.Native, IsByteOrdered=true)]
public struct TypePoint : INullable
{
private bool m_Null;
private Decimal x;
private Decimal y;
public override string ToString()
{
// Replace the following code with your code
if (IsNull) // added part
{
return "null";
}
else
{
return x + ":" + y;
} // end of this part
// return "";
}
public bool IsNull
{
get
{
// Put your code here
return m_Null;
}
}
public static TypePoint Null
{
get
{
TypePoint h = new TypePoint();
h.m_Null = true;
return h;
}
}
public static TypePoint Parse(SqlString s) // Most Important Part
{
if (s.IsNull)
{
return Null;
}
else // added part
{
TypePoint p = new TypePoint();
string str = s.ToString();
string[] xy = str.Split(':');
p.x = Decimal.Parse(xy[0]);
p.y = Decimal.Parse(xy[1]);
return p;
}
}
public Decimal X
{
get
{
return x;
}
set
{
x = value;
}
}
public Decimal Y
{
get
{
return y;
}
set
{
y = value;
}
} // end of added part
// This is a place-holder method
public string Method1()
{
//Insert method code here
return "Hello";
}
// This is a place-holder static method
public static SqlString Method2()
{
//Insert method code here
return new SqlString("Hello");
}
// This is a place-holder field member
public int var1;
}
Is it possible to do a native BCP from 7.0 to 6.5? I'm having all sorts of data issues when I try.
Would a character bcp work (albeit slowly) instead?
Hello.
Does anybody knowk if it's necessary to upgrade Sql Native Client to conect to a Server when you has upgrade it to Sql 2005 SP2? That is to say, can you conect to a Sql server 2005 SP1 and to a Sql Server 2005 SP2 from a client with the same Sql Native client or you have also to upgrade it?
Thanks.
We have a VB6 app that we're trying to connect to an SQL2005 server.
We're able to connect from dev machines that have SQLExpress, or SQL 2005 tools installed, but we cannot connect from other machines. We've installed sqlncli.msi from the MS site, but this still doesn't work. When we try to login, we get an error that reads "0[Microsoft][SQL Native Client]Fractional truncation" when we try writing to a smalldatetime field. This problem does not happen on the dev machines.
Connection string:
connectiontype = cnnSQLServer
database name = name
pasword = password
userid = uid
servername = servername
driver = {SQL Native Client}
Driver version on the dev machines is: 2005.90.3042.00
Driver version on the roll out machines is: 2005.90.1399.00
What are we doing wrong?
Zeke.
Hi
I need to browse SQL servers on local and network computers in a native C++ program (MFC / ADO).
I developped a .NET module based on SqlDataSourceEnumerator (works fine), but I cannot use it in my program (CLR is not allowed).
-> Is it possible to use SqlDataSourceEnumerator in a native C++ program (=without CLR) ?
Does anyone know where to find the native datatype formats of sqlserver6/7?
View 1 Replies View RelatedWe're upgrading from SQL2K to 05 next week. We want to push the SQL Native Client driver(ODBC) thru the network but IT said it can only be an msi or exe file. Is their anyway we could get this file in this format?
View 4 Replies View RelatedHi all,
Ms SQL Server Native Error 18456 !! Login Failed.
Pls help me out.
Thanx in Advance
Anyone have experience with using SOAP/Native XML Web Services in SQL Server 2005 to expose data to external web clients? Any issues/pitfalls?
-A
I'm wondering if I can take native SQL log backup in addition to DPM backups. We're using DPM for both databases (daily) and logs (every 15min). So, if I take SQL log backup separately, will it break anything in DPM and we won't be able to perform point it time recovery?
View 3 Replies View RelatedI'm new in this forum and I 'm Italian, so my English won't be perfect!
If i want to connect to my SQL Server database in prompt i type:
"osql -U sa" and then i type the password.
So, I get an error that says:
"[Sql Native Client] Provider Via: Impossible to find the specified module.
[Sql Native Client] Access timeout expired
[Sql Native Client] An error occured during the attempt to estabilish a connection to the server. During the connection to SQL Server this error may be caused by pre-defined settings that don't ......"
How i can solve this problem?
Who can help me?
Thank you!!
Maxx
Hello,
Can I use the "SQLOLEDB" provider to connect to a SQL Native Client? Follow-up question: does the "SQLOLEDB" provider use the same TDS transport protocol as the SQL Native Client provider?
Thanks as always!
dotBomb
The Clients Environment:
Windows Server 2003 R2
SQL Server 2005 SP1 Standard Edition Version 9.00.2153.00
SQL Native Client Version 2005.90.2047.0
My Development Environment
Windows XP
SQL Server 2005 SP1 Developer Edition Version 9.00.2047.0
SQL Native Client Version 2005.90.3042.0
The Error: [Microsoft] [ODBC SQL Server Driver] Fractional truncation
We have tons of VB 6 legacy code. (I know.. we are trying to get it to .Net.. just not enough time in the day) We recently installed our application at a cleints site (environment listed above) and all of a sudden we are getting errors every time we execute a rs.update using ADODB. I have pasted an example below. The kicker is that it runs fine in my development environment. I can get around this issue by using a command object to do the insert, but we have thousands of these sprinkled throughout the application and would take weeks to change them over; and of course this client demands to start using our application NOW. I am inclined to think that it is an issue with SQL Client since it does not appear to have been updated when the SP1 was installed. I have read some blogs about issues with SQL Native Client and datetime values.
'Broke Code
Dim RS as New ADODB.Recordet
Dim SQL as String
Dim datGetDate as Date
'THis select statement return an empty recordset. ID is an identity column
SQL = "SELECT * FROM table WHERE id is null
RS.Open SQL, gadoConn,adOpenKeySet, adLockOptimistic
RS.AddNew
RS("col1")=Value1
RS("col2")=Value2
RS("starttime")=datGetDate
RS.Update 'This is where it blows
RS.Close
'New and Improved code. Works perfectly
Dim SQL as String
Dim objCMD as new ADODB.Command
SQL = "INSERT INTO table(col1,col2,starttime) values('" & Value1 & "','" & Value2 & "','" & datGetDate & "')"
With objCMD
.ActiveConnection=gadoConn
.CommandText=SQL
.CommandType=adCmdText
.execute
End with
Thanks!
We are using Visual Studio 2003 to develop a VC++ application to support SQL Server 2000 and 2005 through ODBC driver. I was able to successfully test the application with ODBC driver for 2000. But when it comes to the SQL Server 2005 using native ODBC driver it fails with "ODBCBCP.dll is not compatible with 'SQL Native Client' driver. Please configure 'SQL Server' driver for the DSN or connection string.
Then I tried to use the sqlncli.h inplace of odbcss.h and replaced the odbcbcp.lib with sqlncli.lib pointing to the C:Program FilesMicrosoft SQL Server90SDKLibx86 folder.
Code Snippet
#include <sql.h>
#include <sqlext.h>
#include <sqltypes.h>
#define _SQLNCLI_ODBC_
#include <sqlncli.h>
Now I can not compile the program. The errors I am getting are as follows:
c:Program FilesMicrosoft SQL Server90SDKIncludesqlncli.h(2894): error C2061: syntax error : identifier 'DB_UPARAMS'
c:Program FilesMicrosoft SQL Server90SDKIncludesqlncli.h(2901): error C2061: syntax error : identifier 'DB_UPARAMS'
etc
c:Program FilesMicrosoft SQL Server90SDKIncludesqlncli.h(2938): error C2061: syntax error : identifier 'HCHAPTER'
c:Program FilesMicrosoft SQL Server90SDKIncludesqlncli.h(2944): error C2061: syntax error : identifier 'HCHAPTER'
etc
The same code just works fine in the Visual Studio 2005, but we need the dll in Visual studio 2003.
I think I am missing pretty obvious. Your help is appreciated.