Tuesday, March 27, 2012

Connection Problem

Hello there
I have two servers on diffrent computer
Both of them are registered together
One of them declared as a publisher and the otherone as subscripter
When i add the subscript it gave me an error of connecting between them and
the synchronize is not active
where the problem can be?
Normally when you get the subscription is not active it means that your
publication is not activated.
in your publication database do this
sp_changepublication 'publicationname','status','active'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Oded Kovach" <roygoldh@.hotmail.com> wrote in message
news:O8FBVRMlEHA.712@.TK2MSFTNGP09.phx.gbl...
> Hello there
> I have two servers on diffrent computer
> Both of them are registered together
> One of them declared as a publisher and the otherone as subscripter
> When i add the subscript it gave me an error of connecting between them
and
> the synchronize is not active
> where the problem can be?
>

Connection Problem

Hi All,
I can not connect to sql serve 2005 using SQL Serve Management Studio,
I got these error in ERROR.LOG file. Any help is really appreciated.
Thanks.
2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack
2)
2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
2006-09-21 12:48:21.54 Server All rights reserved.
2006-09-21 12:48:21.54 Server Server process ID is 4948.
2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-09-21 12:48:21.54 Server This instance of SQL Server last
reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
user action is required.
2006-09-21 12:48:21.54 Server Registry startup parameters:
2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft
SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-09-21 12:48:21.64 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
informational message; no user action is required.
2006-09-21 12:48:22.64 Server Using dynamic lock allocation.
Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per
node. This is an informational message only. No user action is
required.
2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2006-09-21 12:48:24.23 Server The Microsoft Distributed
Transaction Coordinator (MS DTC) service could not be contacted. If
you would like distributed transaction functionality, please start this
service.
2006-09-21 12:48:24.48 Server Database mirroring has been enabled
on this instance of SQL Server.
2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
"sa".
2006-09-21 12:48:25.46 spid5s Starting up database
'mssqlsystemresource'.
2006-09-21 12:48:25.54 spid5s The resource database build version
is 9.00.2047. This is an informational message only. No user action is
required.
2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
an informational message only. No user action is required.
2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
2006-09-21 12:48:30.54 spid12s The Service Broker protocol
transport is disabled or not configured.
2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
transport is disabled or not configured.
2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
2006-09-21 12:48:31.39 Server A self-generated certificate was
successfully loaded for encryption.
2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
1.
2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
VIA support library [QLVipl.dll]. This normally indicates the VIA
support library does not exist or is corrupted. Please repair or
disable the VIA network protocol. Error: 0x7e.
2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
3.
2006-09-21 12:48:31.43 Server Could not start the network library
because of an internal error in the network library. To determine the
cause, review the errors immediately preceding this one in the error
log.
2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
1.
2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
thread. Check the SQL Server error log and the Windows event logs for
information about possible related problems.Are you using VIA? If not, try disabling the protocol using
the SQL Server Configuration Manager.
-Sue
On 21 Sep 2006 21:58:12 -0700, "sara" <sarasara82@.gmail.com>
wrote:

>Hi All,
>I can not connect to sql serve 2005 using SQL Serve Management Studio,
>I got these error in ERROR.LOG file. Any help is really appreciated.
>Thanks.
>2006-09-21 12:48:21.53 Server Microsoft SQL Server 2005 -
>9.00.2047.00 (Intel X86)
> Apr 14 2006 01:12:25
> Copyright (c) 1988-2005 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack
>2)
>2006-09-21 12:48:21.54 Server (c) 2005 Microsoft Corporation.
>2006-09-21 12:48:21.54 Server All rights reserved.
>2006-09-21 12:48:21.54 Server Server process ID is 4948.
>2006-09-21 12:48:21.54 Server Logging SQL Server messages in file
>'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
>2006-09-21 12:48:21.54 Server This instance of SQL Server last
>reported using a process ID of 4396 at 9/21/2006 1:05:02 AM (local)
>9/21/2006 8:05:02 AM (UTC). This is an informational message only; no
>user action is required.
>2006-09-21 12:48:21.54 Server Registry startup parameters:
>2006-09-21 12:48:21.59 Server -d C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\DATA\master.mdf
>2006-09-21 12:48:21.59 Server -e C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\LOG\ERRORLOG
>2006-09-21 12:48:21.59 Server -l C:\Program Files\Microsoft
>SQL
>Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
>2006-09-21 12:48:21.64 Server SQL Server is starting at normal
>priority base (=7). This is an informational message only. No user
>action is required.
>2006-09-21 12:48:21.64 Server Detected 2 CPUs. This is an
>informational message; no user action is required.
>2006-09-21 12:48:22.64 Server Using dynamic lock allocation.
>Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per
>node. This is an informational message only. No user action is
>required.
>2006-09-21 12:48:23.65 Server Attempting to initialize Microsoft
>Distributed Transaction Coordinator (MS DTC). This is an informational
>message only. No user action is required.
>2006-09-21 12:48:24.23 Server The Microsoft Distributed
>Transaction Coordinator (MS DTC) service could not be contacted. If
>you would like distributed transaction functionality, please start this
>service.
>2006-09-21 12:48:24.48 Server Database mirroring has been enabled
>on this instance of SQL Server.
>2006-09-21 12:48:24.84 spid5s Starting up database 'master'.
>2006-09-21 12:48:25.42 spid5s SQL Trace ID 1 was started by login
>"sa".
>2006-09-21 12:48:25.46 spid5s Starting up database
>'mssqlsystemresource'.
>2006-09-21 12:48:25.54 spid5s The resource database build version
>is 9.00.2047. This is an informational message only. No user action is
>required.
>2006-09-21 12:48:25.98 spid5s Server name is 'BLAHBLAH'. This is
>an informational message only. No user action is required.
>2006-09-21 12:48:25.98 spid9s Starting up database 'model'.
>2006-09-21 12:48:26.46 spid9s Clearing tempdb database.
>2006-09-21 12:48:30.10 spid9s Starting up database 'tempdb'.
>2006-09-21 12:48:30.54 spid12s The Service Broker protocol
>transport is disabled or not configured.
>2006-09-21 12:48:30.54 spid12s The Database Mirroring protocol
>transport is disabled or not configured.
>2006-09-21 12:48:31.12 spid12s Service Broker manager has started.
>2006-09-21 12:48:31.39 Server A self-generated certificate was
>successfully loaded for encryption.
>2006-09-21 12:48:31.40 Server Error: 26055, Severity: 16, State:
>1.
>2006-09-21 12:48:31.40 Server The SQL Server failed to initialize
>VIA support library [QLVipl.dll]. This normally indicates the VIA
>support library does not exist or is corrupted. Please repair or
>disable the VIA network protocol. Error: 0x7e.
>2006-09-21 12:48:31.42 Server Error: 17182, Severity: 16, State:
>1.
>2006-09-21 12:48:31.42 Server TDSSNIClient initialization failed
>with error 0x7e, status code 0x60.
>2006-09-21 12:48:31.43 Server Error: 17182, Severity: 16, State:
>1.
>2006-09-21 12:48:31.43 Server TDSSNIClient initialization failed
>with error 0x7e, status code 0x1.
>2006-09-21 12:48:31.43 Server Error: 17826, Severity: 18, State:
>3.
>2006-09-21 12:48:31.43 Server Could not start the network library
>because of an internal error in the network library. To determine the
>cause, review the errors immediately preceding this one in the error
>log.
>2006-09-21 12:48:31.43 Server Error: 17120, Severity: 16, State:
>1.
>2006-09-21 12:48:31.43 Server SQL Server could not spawn FRunCM
>thread. Check the SQL Server error log and the Windows event logs for
>information about possible related problems.|||Yes. It was VIA protocol problem. Thanks.
Sue Hoegemeier wrote:[vbcol=seagreen]
> Are you using VIA? If not, try disabling the protocol using
> the SQL Server Configuration Manager.
> -Sue
> On 21 Sep 2006 21:58:12 -0700, "sara" <sarasara82@.gmail.com>
> wrote:
>sqlsql

connection problem

I get the following 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. (provider: Named Pipes Provider, error: 40 - Could not open
a connection to SQL Server)
From the following code:
<%@. Page Language="VB" Debug="true" %>
<script runat="server">
Dim ConnectionString As String = "server=
(local);database=ASPExamples"
Dim SelectCommand As String = "SELECT CustomerID, name, phone from
customers"
Dim isEditing As Boolean = False
Dim myConnection As New SqlConnection(ConnectionString)
Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
Dim ds As New DataSet()
myCommand.Fill(ds)
DataGrid1.DataSource = ds
DataGrid1.DataBind()
End SubSee:
http://betav.com/blog/billva/2006/0...onnected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Roger Halls" <roghalls@.gmail.com> wrote in message
news:Xns992A7925D4244roghallsgmailcom@.19
8.186.190.150...
>I get the following 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. (provider: Named Pipes Provider, error: 40 - Could not open
> a connection to SQL Server)
> From the following code:
> <%@. Page Language="VB" Debug="true" %>
> <script runat="server">
> Dim ConnectionString As String = "server=
> (local);database=ASPExamples"
> Dim SelectCommand As String = "SELECT CustomerID, name, phone from
> customers"
> Dim isEditing As Boolean = False
> Dim myConnection As New SqlConnection(ConnectionString)
> Dim myCommand As New SqlDataAdapter(SelectCommand, myConnection)
> Dim ds As New DataSet()
> myCommand.Fill(ds)
> DataGrid1.DataSource = ds
> DataGrid1.DataBind()
>
> End Sub

connection problem

Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
HawkHi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend

>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thank you very much and have a good one
Hawk

connection problem

Hi.
I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
connect to database from remote machines with Windows 98Se, but i can't
connect from machines with Windows XP.
ChrisI think that it is a problem with not having the 'correct' client network
utilities installed.
On the Start menu, select [All Programs], [Microsoft SQL Server], th
en
[Client Network Utility].
In the [Enabled Protocols] window, you should have both TCP/IP and Named
Pipes.
If one is missing, select the missing protocol from the list on the left
side, and click the [Enable] button.
Hopefully, if my memory is correct, that will take care of the problem.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>|||Have you tried temporarily disabling the firewall on the XP machines?
John Opincar
john.opincar@.sundesksoftware.com
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>

Connection Problem

Hi All,
I use the following code lines for connecting to SQL Server 2005 using
JDBC in Java:
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
String connectionUrl =
"jdbc:sqlserver:// SERVER;user=USER;databaseName=db;Authent
icationMethod=auto
";
but I got the error: Login failed for user 'USER'
I want to use windows authentication and I am pretty sure I use the
correct username. Can you please help me?
Thanks a lot.AuthenticationMethod=auto is correct but you would not
supply a user in the connection string to have the
connection use Windows authentication. If you supply the
user, it will use SQL authentication, not windows.
-Sue
On 9 Oct 2006 00:56:14 -0700, "sara" <sarasara82@.gmail.com>
wrote:

>Hi All,
>I use the following code lines for connecting to SQL Server 2005 using
>JDBC in Java:
>Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
> String connectionUrl =
>"jdbc:sqlserver:// SERVER;user=USER;databaseName=db;Authent
icationMethod=aut
o";
>but I got the error: Login failed for user 'USER'
>I want to use windows authentication and I am pretty sure I use the
>correct username. Can you please help me?
>Thanks a lot.

Connection problem

I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql