Source server MSSQL7.0
Destination server MSSQL2K
I'm setting up replication for reporting purposes to another SQL-server.
When I start the distribution agent I get the following error:
Column name '<here's the name of a column I didn't publish and don't need to replicate>' does not exist in the target table.
Error number: 1911
I assume this is because of some dependencies between the columns.
Is there any way I can replicate without those columns?
RegardsDependency doesn't get replicated unless you specified. If you think the error was caused by the column dependency, check the unique index and the foreign key constraint to see whether the 'for replication' is checked or not.|||Thanks, you gave me the hint I needed.
I was scripting the creation of the publication because I need to setup replication for over 20 db's.
In the script you have to change the sp_addarticle @.schema_option value.
Regards
Showing posts with label exist. Show all posts
Showing posts with label exist. Show all posts
Thursday, March 29, 2012
Monday, March 26, 2012
Error 16916: A cursor with the name "tentative_cursor" does not exist
Hi,
I am creating a stored procedure which contains the declaration of a cursor, fetch the cursor, close the cursor, deallocate cursor. I tried executing this code in SQL analyzer and found working. But when I use the same code inside a create stored procedure, it throws the following error message.
Error 16916: A cursor with the name "tentative_cursor" does not exist
As a result, I am not able to proceed in creation of stored procedure with the above SQL statements.
Can any one help me where the problem is..
My SQL statements..
---
DECLARE tentative_cursor CURSOR
FOR select * from TbTentativeBookingTable where ExpTime < GETDATE()
GO
OPEN tentative_cursor
GO
DECLARE @.transactionno BIGINT
...
...
FETCH ...
CLOSE tentative_cursor
---
Thanks
-SudhakarThe GO keyword serves to terminate a SQL batch, so it implicitly ends a stored procedure declaration. There may be other problems too, but at the very least you need to remove the GO keyword(s).
-PatP
I am creating a stored procedure which contains the declaration of a cursor, fetch the cursor, close the cursor, deallocate cursor. I tried executing this code in SQL analyzer and found working. But when I use the same code inside a create stored procedure, it throws the following error message.
Error 16916: A cursor with the name "tentative_cursor" does not exist
As a result, I am not able to proceed in creation of stored procedure with the above SQL statements.
Can any one help me where the problem is..
My SQL statements..
---
DECLARE tentative_cursor CURSOR
FOR select * from TbTentativeBookingTable where ExpTime < GETDATE()
GO
OPEN tentative_cursor
GO
DECLARE @.transactionno BIGINT
...
...
FETCH ...
CLOSE tentative_cursor
---
Thanks
-SudhakarThe GO keyword serves to terminate a SQL batch, so it implicitly ends a stored procedure declaration. There may be other problems too, but at the very least you need to remove the GO keyword(s).
-PatP
Thursday, March 22, 2012
Error 15123
When trying to use the generate SQL Wizard, I get an error
Error 15123: The configuration option 'user options' does not exist, or it may be an advanced option. Valid configuration options are:
This just started happening this week. Does anyone have any ideas?
That error normally pops up when you're trying to use the xp_cmdshell function, but it doesn't seem like you're doing that. Can you think of anything that may have changed just before it quit working?|||To my knowledge there have been no changes to that server for awhile. It is a development server and has more hands in it than Carter has pills. I was hoping for a "oh, you shot yourself in the foot this way". We did have an event where we were keeping too many backups and filled the data disk and caused some hiccops in another area. Is there a possibility that something got corrupted? I know the values are in the tables, I traced that back and compared with this server's test counterpart.|||To my knowledge there have been no changes to that server for awhile. It is a development server and has more hands in it than Carter has pills. I was hoping for a "oh, you shot yourself in the foot this way". We did have an event where we were keeping too many backups and filled the data disk and caused some hiccops in another area. Is there a possibility that something got corrupted? I know the values are in the tables, I traced that back and compared with this server's test counterpart.|||It's possible. Sometimes I try to move the error around or force it, so one strategy might be to back up the DB and restore it on the same or another server. Alternately, you could use the database copy wizard to copy to a new DB and see if the problem forces itself out somewhere.|||The error happens on all databases, so I did detach one of the dbs and copy it to another server. The problem did not follow the db. I figure, we get through this one project and then rebuild the box.|||
Wow - very odd. I wonder if it's a file-locking issue at the OS. In any caes, I'm glad that worked for you. Let me know if I can help in any way.
error 15007: The login'anything' does not exist.
This error makes no sense to me whatsoever.
I'm using Enterprise Manager to create a new user for a new dbase and
regardless of anything I put in there, it gives me that 15007 message.Make sure the user that you are adding to the database has corresponding
login created.
Ex:
--To create login
use master
go
sp_addlogin 'user1', 'password'
go
--To add the user to the current database(here im picking up northwind).
use northwind
go
sp_grantdbaccess 'user1'
go
--
-Vishal
"Robert Blackwell" <robbie@.NOspamwowcentral.com> wrote in message
news:enYIIRVVDHA.2328@.TK2MSFTNGP12.phx.gbl...
> This error makes no sense to me whatsoever.
> I'm using Enterprise Manager to create a new user for a new dbase and
> regardless of anything I put in there, it gives me that 15007 message.
>|||Okay thanks, I was able to copy your instructions exactly. However, isn't
there a way to do all of that in Enterprise Manager?|||Hmm, maybe I should try clicking the new login button on the tool bar? ;o)
Thanks again.
I'm using Enterprise Manager to create a new user for a new dbase and
regardless of anything I put in there, it gives me that 15007 message.Make sure the user that you are adding to the database has corresponding
login created.
Ex:
--To create login
use master
go
sp_addlogin 'user1', 'password'
go
--To add the user to the current database(here im picking up northwind).
use northwind
go
sp_grantdbaccess 'user1'
go
--
-Vishal
"Robert Blackwell" <robbie@.NOspamwowcentral.com> wrote in message
news:enYIIRVVDHA.2328@.TK2MSFTNGP12.phx.gbl...
> This error makes no sense to me whatsoever.
> I'm using Enterprise Manager to create a new user for a new dbase and
> regardless of anything I put in there, it gives me that 15007 message.
>|||Okay thanks, I was able to copy your instructions exactly. However, isn't
there a way to do all of that in Enterprise Manager?|||Hmm, maybe I should try clicking the new login button on the tool bar? ;o)
Thanks again.
Error 15007 - login 'user1' does not exist
I restored a test database from a backup of production
and my users using a user account called user could not
login again. I try to create a new user and get the above
message. Any help please.This is a multi-part message in MIME format.
--=_NextPart_000_026A_01C34FA0.C1C01AE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Check out sp_change_users_login in the BOL.
-- Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Aboki" <waco361@.hotmail.com> wrote in message =news:099201c34fc1$7b3948a0$a001280a@.phx.gbl...
I restored a test database from a backup of production and my users using a user account called user could not login again. I try to create a new user and get the above message. Any help please.
--=_NextPart_000_026A_01C34FA0.C1C01AE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Check out sp_change_users_login in the =BOL.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Aboki" wrote in =message news:099201c34fc1$7b=3948a0$a001280a@.phx.gbl...I restored a test database from a backup of production and my users =using a user account called user could not login again. I try to create a =new user and get the above message. Any help please.
--=_NextPart_000_026A_01C34FA0.C1C01AE0--
and my users using a user account called user could not
login again. I try to create a new user and get the above
message. Any help please.This is a multi-part message in MIME format.
--=_NextPart_000_026A_01C34FA0.C1C01AE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Check out sp_change_users_login in the BOL.
-- Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Aboki" <waco361@.hotmail.com> wrote in message =news:099201c34fc1$7b3948a0$a001280a@.phx.gbl...
I restored a test database from a backup of production and my users using a user account called user could not login again. I try to create a new user and get the above message. Any help please.
--=_NextPart_000_026A_01C34FA0.C1C01AE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Check out sp_change_users_login in the =BOL.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Aboki"
--=_NextPart_000_026A_01C34FA0.C1C01AE0--
error 15007
I am having some issues with authenticatio in that
sql account exist although the account do not seem to have permission to log on to the server
error 15007
The sets of servers are in 3 domains with a complete trust model
and teg message staes the login does not exist
When i attempt to create the login a separate error states that the user name already existsA few more details would be nice in order to provide a complete answer. You say you have three domains and that trusts have been established among the domains. For the sake of argument, let's call the domains A, B and C. Let's also say that SQL Server is running on a server in domain A. Finally, let's say that you have two users you want to add:
B\UserName
C\UserName
With Windows accounts, you don't create the account. The account already exists in the OS. Instead, you GRANT the windows account access to the appropriate database. See SQL BOL sp_grantlogin.
EXEC sp_grantlogin 'B\UserName'
EXEC sp_grantlogin 'C\UserName'
Note that you would then need to grant access to the appropriate database using sp_grantdbaccess. Example:
Use MyDatabase
EXEC sp_grantdbaccess 'B\UserName'
EXEC sp_grantdbaccess 'C\UserName'
Note that B\UserName and C\UserName are not the same entities; they may share a common UserName, but the are distinct and separate. Pass-through authentication does not apply here since these are domain accounts.
If this does not help you to solve your issue, may I suggest that you post the actual details of your situation so we can understand the issue better?
Regards,
Hugh Scott
sql account exist although the account do not seem to have permission to log on to the server
error 15007
The sets of servers are in 3 domains with a complete trust model
and teg message staes the login does not exist
When i attempt to create the login a separate error states that the user name already existsA few more details would be nice in order to provide a complete answer. You say you have three domains and that trusts have been established among the domains. For the sake of argument, let's call the domains A, B and C. Let's also say that SQL Server is running on a server in domain A. Finally, let's say that you have two users you want to add:
B\UserName
C\UserName
With Windows accounts, you don't create the account. The account already exists in the OS. Instead, you GRANT the windows account access to the appropriate database. See SQL BOL sp_grantlogin.
EXEC sp_grantlogin 'B\UserName'
EXEC sp_grantlogin 'C\UserName'
Note that you would then need to grant access to the appropriate database using sp_grantdbaccess. Example:
Use MyDatabase
EXEC sp_grantdbaccess 'B\UserName'
EXEC sp_grantdbaccess 'C\UserName'
Note that B\UserName and C\UserName are not the same entities; they may share a common UserName, but the are distinct and separate. Pass-through authentication does not apply here since these are domain accounts.
If this does not help you to solve your issue, may I suggest that you post the actual details of your situation so we can understand the issue better?
Regards,
Hugh Scott
Wednesday, March 21, 2012
Error 14262: specified @job_id... does not exist
Got a client who is getting this error when trying "Start synchronizing" on
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> 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
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> 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
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>
Wednesday, March 7, 2012
Error : SQL server does not exist or access denied.
Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
Michael
Hi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael
|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
Michael
Hi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael
|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag
Error : SQL server does not exist or access denied.
Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
MichaelHi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
MichaelHi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag
Subscribe to:
Posts (Atom)