Showing posts with label occurred. Show all posts
Showing posts with label occurred. Show all posts

Sunday, 25 March 2012

CONNECT TO SERVER PROBLEM

I am getting this message when trying to connect to SQL SERVER 2005;
An error has occurred while establishing connection to the server.When connecting to SQL Server 2005, this failure may be caused by the fact that under default settings SQL Server does not allow remote connections(provider:shared memory provider , error 40-could not open a connection to SQL Server)(MicrosoftSQL SERVER, Error: 2)
Can anyone help to fix this problem please

Are you using SQL Express? If so, you need to enable remote connections. They are disabled by default.

Thanks,
Sam Lester (MSFT)

|||SQL SERVER 2005, STANDART
|||

On the server execute these statements:

sp_configure 'remote admin connections', 1

go

reconfigure

go

Then you should be able to connect from a client workstation.

Tuesday, 20 March 2012

Connect to Database in SQL 2005 Express

I am trying to connect to the sample databases in SQL Express. I am getting this error.

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

I have downloaded and installed AdventureWorks, Northwind, and Pubs. If I have to allow remote connections how do I do that? I am a studen and I am brand new at this.

first ensure the sample database you wish to use is registered (some of the samples must first be attached from the D/L .mdf files).

second startup the SURFACE AREA CONFIG TOOL via the start menu. after the splash screen display click on the configure services and connections link.

select the Remote Connection node in the tree and select the second radio button to enable remote connections.

if you still have problems you should look at the protocols your sql server has enabled and which protocol format you are using to connect.

|||

1. Open SQL Server Configuration Manager under "Microsoft SQL Sever 2005" "Configuration Tools"

2. Navigate to "Sql Server 2005 Network Configuration" --"Protocols for SQL2005"

3. Enable "Shared Memory" , "Named Pipes" & "TCP/IP"

This should solve the problem

|||I figured it out. I feel stupid now. I just had to right click on database and click attach. Then click add. This brought me out to the windows hierarchy where I was able to find the Northwind database and click on it to add it.|||

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Connect to Database in SQL 2005 Express

I am trying to connect to the sample databases in SQL Express. I am getting this error.

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

I have downloaded and installed AdventureWorks, Northwind, and Pubs. If I have to allow remote connections how do I do that? I am a studen and I am brand new at this.

first ensure the sample database you wish to use is registered (some of the samples must first be attached from the D/L .mdf files).

second startup the SURFACE AREA CONFIG TOOL via the start menu. after the splash screen display click on the configure services and connections link.

select the Remote Connection node in the tree and select the second radio button to enable remote connections.

if you still have problems you should look at the protocols your sql server has enabled and which protocol format you are using to connect.

|||

1. Open SQL Server Configuration Manager under "Microsoft SQL Sever 2005" "Configuration Tools"

2. Navigate to "Sql Server 2005 Network Configuration" --"Protocols for SQL2005"

3. Enable "Shared Memory" , "Named Pipes" & "TCP/IP"

This should solve the problem

|||I figured it out. I feel stupid now. I just had to right click on database and click attach. Then click add. This brought me out to the windows hierarchy where I was able to find the Northwind database and click on it to add it.|||

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Friday, 24 February 2012

Conflict Viewer error:

Un unexpected error occurred while trying to launch the Conflict Viewer.
Nothing more and of course, no conflict viewer...
Any idea how to fix this?
Michael
I am having the same issue. Anybody aware of this.
thanks
"AlohaMike" wrote:

> Un unexpected error occurred while trying to launch the Conflict Viewer.
> Nothing more and of course, no conflict viewer...
> Any idea how to fix this?
> Michael

Conflict Error

Hi All;

I am getting ;

INSERT statement conflicted with TABLE FOREIGN KEY constraint 'FK_ChecklistCases_ChecklistFGroups'. The conflict occurred in database 'Test', table 'ChecklistFGroups'. The statement has been terminated.

but it seems to be no error can you help me please I can send you the related part of database

thank youit says you are violating the forien key constriant..its always a good idea to check if the data exists before you insert..

hth

Sunday, 12 February 2012

Configuring Distributor

I keep getting the error message:
An error occurred during decryption.
There is no remote user 'distributor_admin' mapped to local user '(null)'
from the remote server 'repl_distributor'.
Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
I have tried a local server account (as BOL describes), I have tried using
my own SQL account (that has sa priviliges of course), I have even tried the
domain account that runs SQL Agent service (despite the note right there on
the screen that recommends not to!). I get this error at the end of all the
steps whether I try to create a new publication or if I try to configure the
publisher.
ANY help would be appreciated!!
Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
remote server called repl_distributor which uses the distributor admin
account. In SQL Server 2005 this has been replaced by a linked server. In
some cases I have seen the upgrade of a replication topology with a remote
distributor does not work successfully.
In my cases I had to add the linked server and password manually, IIRC.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>I keep getting the error message:
> An error occurred during decryption.
> There is no remote user 'distributor_admin' mapped to local user '(null)'
> from the remote server 'repl_distributor'.
> Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
> I have tried a local server account (as BOL describes), I have tried using
> my own SQL account (that has sa priviliges of course), I have even tried
> the
> domain account that runs SQL Agent service (despite the note right there
> on
> the screen that recommends not to!). I get this error at the end of all
> the
> steps whether I try to create a new publication or if I try to configure
> the
> publisher.
> ANY help would be appreciated!!
|||It is a fresh install. Add a linked serer to what? could you send me the
details of adding the linked sever I am completely lost.
"Hilary Cotter" wrote:

> Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
> remote server called repl_distributor which uses the distributor admin
> account. In SQL Server 2005 this has been replaced by a linked server. In
> some cases I have seen the upgrade of a replication topology with a remote
> distributor does not work successfully.
> In my cases I had to add the linked server and password manually, IIRC.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>
>
|||Check to ensure there is a linked server called repl_distributor and it uses
the security context of distributor_admin
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...[vbcol=seagreen]
> It is a fresh install. Add a linked serer to what? could you send me the
> details of adding the linked sever I am completely lost.
> "Hilary Cotter" wrote:
|||I tried adding the linked server and it STILL failed! But I'm making progess
because now I know exactly where the error is occuring, when adding the
linked server:
Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91
An error occurred during decryption.
Funny, I tried looking up this error number when all this first happened
(notice below, the text is a little different from my original error) and I
got nothing in my serarch results from Microsoft. I was able to get this to
work on another server, so at least I know it is some internal setting
specific to this server...Any ideas?
REALLY appreciate your help so far!!
"Hilary Cotter" wrote:

> Check to ensure there is a linked server called repl_distributor and it uses
> the security context of distributor_admin
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
>
>
|||Hilary,
Should this linked server be created on the distributor, or the subscriber,
or both? I am seeing a similar error when trying to setup replication in my
production environment, although it worked fine in test (currently being
rebuilt, so I have no comparison to use atm). I am thinking this might be a
part of my problem.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uoTqv58THHA.3592@.TK2MSFTNGP03.phx.gbl...
> Check to ensure there is a linked server called repl_distributor and it
uses[vbcol=seagreen]
> the security context of distributor_admin
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
the[vbcol=seagreen]
In
>