I am using SQLServer 2000, Visual Studio 2003, C#.
I am writing a web part which requires me to connect to a local sql
database.
I wrote a class which handles the connection and reading of the table.
When I try to call .Open on the connection, it fails, the exception is
something to do with permission.
I used the same class to connect with a console application and a
windows application, and it works fine. I am able to connect and read
the table.
Can anyone shed some light on what is the difference between
connecting/accessing to a database via Web Application as opposed to a
Non-Web App.
TIAI think your problem has something to do with permission as the error
indicates. If you are writing an ASP.Net web page then your web application
is running as the ASPUSER Windows user and chances are this use does not
have permissions to connect to the database. When you run as a Windows
application you run as you and you probably have admin permissions on the
box which gives you SA permissions in the database so you can do whatever
you want. Confirm that you are running as ASPUSER and then create a login
and user for it in SQL Server.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168476873.734347.313800@.k58g2000hse.googlegroups.com...
>I am using SQLServer 2000, Visual Studio 2003, C#.
> I am writing a web part which requires me to connect to a local sql
> database.
> I wrote a class which handles the connection and reading of the table.
> When I try to call .Open on the connection, it fails, the exception is
> something to do with permission.
> I used the same class to connect with a console application and a
> windows application, and it works fine. I am able to connect and read
> the table.
> Can anyone shed some light on what is the difference between
> connecting/accessing to a database via Web Application as opposed to a
> Non-Web App.
> TIA
>|||Roger,
Thanks for the reply.
I ran SQL Server Enterprise Manager and for that database, I checked
the Users.
there are two, dbo and guest, both having full permissions.
How would I confirm tthat I am running as ASPUSER and create a login
for it?
Thanks,
IV
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> I think your problem has something to do with permission as the error
> indicates. If you are writing an ASP.Net web page then your web applicati
on
> is running as the ASPUSER Windows user and chances are this use does not
> have permissions to connect to the database. When you run as a Windows
> application you run as you and you probably have admin permissions on the
> box which gives you SA permissions in the database so you can do whatever
> you want. Confirm that you are running as ASPUSER and then create a login
> and user for it in SQL Server.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168476873.734347.313800@.k58g2000hse.googlegroups.com...|||Log in as an admin. USE the database where your tables are and execute
these commands (substituting the name of you machine for servername)
CREATE LOGIN [servername\ASPNET] FROM WINDOWS
CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
http://msdn2.microsoft.com/en-us/library/ms189751.aspx
http://msdn2.microsoft.com/en-us/library/ms173463.aspx
You will then have to grant this user access to the objects it needs to
access for your application
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168487427.667116.147270@.p59g2000hsd.googlegroups.com...
> Roger,
> Thanks for the reply.
> I ran SQL Server Enterprise Manager and for that database, I checked
> the Users.
> there are two, dbo and guest, both having full permissions.
> How would I confirm tthat I am running as ASPUSER and create a login
> for it?
> Thanks,
> IV
> Roger Wolter[MSFT] wrote:
>|||Roger,
I appreciate you taking the time to help me out.
I tried what you said and am still failing with the same exception.
Imtiaz
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> Log in as an admin. USE the database where your tables are and execute
> these commands (substituting the name of you machine for servername)
> CREATE LOGIN [servername\ASPNET] FROM WINDOWS
> CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
> http://msdn2.microsoft.com/en-us/library/ms189751.aspx
> http://msdn2.microsoft.com/en-us/library/ms173463.aspx
> You will then have to grant this user access to the objects it needs to
> access for your application
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168487427.667116.147270@.p59g2000hsd.googlegroups.com...
Saturday, February 25, 2012
Cannot connect via Web Application...
I am using SQLServer 2000, Visual Studio 2003, C#.
I am writing a web part which requires me to connect to a local sql
database.
I wrote a class which handles the connection and reading of the table.
When I try to call .Open on the connection, it fails, the exception is
something to do with permission.
I used the same class to connect with a console application and a
windows application, and it works fine. I am able to connect and read
the table.
Can anyone shed some light on what is the difference between
connecting/accessing to a database via Web Application as opposed to a
Non-Web App.
TIA
I think your problem has something to do with permission as the error
indicates. If you are writing an ASP.Net web page then your web application
is running as the ASPUSER Windows user and chances are this use does not
have permissions to connect to the database. When you run as a Windows
application you run as you and you probably have admin permissions on the
box which gives you SA permissions in the database so you can do whatever
you want. Confirm that you are running as ASPUSER and then create a login
and user for it in SQL Server.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168476873.734347.313800@.k58g2000hse.googlegr oups.com...
>I am using SQLServer 2000, Visual Studio 2003, C#.
> I am writing a web part which requires me to connect to a local sql
> database.
> I wrote a class which handles the connection and reading of the table.
> When I try to call .Open on the connection, it fails, the exception is
> something to do with permission.
> I used the same class to connect with a console application and a
> windows application, and it works fine. I am able to connect and read
> the table.
> Can anyone shed some light on what is the difference between
> connecting/accessing to a database via Web Application as opposed to a
> Non-Web App.
> TIA
>
|||Roger,
Thanks for the reply.
I ran SQL Server Enterprise Manager and for that database, I checked
the Users.
there are two, dbo and guest, both having full permissions.
How would I confirm tthat I am running as ASPUSER and create a login
for it?
Thanks,
IV
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> I think your problem has something to do with permission as the error
> indicates. If you are writing an ASP.Net web page then your web application
> is running as the ASPUSER Windows user and chances are this use does not
> have permissions to connect to the database. When you run as a Windows
> application you run as you and you probably have admin permissions on the
> box which gives you SA permissions in the database so you can do whatever
> you want. Confirm that you are running as ASPUSER and then create a login
> and user for it in SQL Server.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168476873.734347.313800@.k58g2000hse.googlegr oups.com...
|||Log in as an admin. USE the database where your tables are and execute
these commands (substituting the name of you machine for servername)
CREATE LOGIN [servername\ASPNET] FROM WINDOWS
CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
http://msdn2.microsoft.com/en-us/library/ms189751.aspx
http://msdn2.microsoft.com/en-us/library/ms173463.aspx
You will then have to grant this user access to the objects it needs to
access for your application
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168487427.667116.147270@.p59g2000hsd.googlegr oups.com...
> Roger,
> Thanks for the reply.
> I ran SQL Server Enterprise Manager and for that database, I checked
> the Users.
> there are two, dbo and guest, both having full permissions.
> How would I confirm tthat I am running as ASPUSER and create a login
> for it?
> Thanks,
> IV
> Roger Wolter[MSFT] wrote:
>
|||Roger,
I appreciate you taking the time to help me out.
I tried what you said and am still failing with the same exception.
Imtiaz
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> Log in as an admin. USE the database where your tables are and execute
> these commands (substituting the name of you machine for servername)
> CREATE LOGIN [servername\ASPNET] FROM WINDOWS
> CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
> http://msdn2.microsoft.com/en-us/library/ms189751.aspx
> http://msdn2.microsoft.com/en-us/library/ms173463.aspx
> You will then have to grant this user access to the objects it needs to
> access for your application
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168487427.667116.147270@.p59g2000hsd.googlegr oups.com...
I am writing a web part which requires me to connect to a local sql
database.
I wrote a class which handles the connection and reading of the table.
When I try to call .Open on the connection, it fails, the exception is
something to do with permission.
I used the same class to connect with a console application and a
windows application, and it works fine. I am able to connect and read
the table.
Can anyone shed some light on what is the difference between
connecting/accessing to a database via Web Application as opposed to a
Non-Web App.
TIA
I think your problem has something to do with permission as the error
indicates. If you are writing an ASP.Net web page then your web application
is running as the ASPUSER Windows user and chances are this use does not
have permissions to connect to the database. When you run as a Windows
application you run as you and you probably have admin permissions on the
box which gives you SA permissions in the database so you can do whatever
you want. Confirm that you are running as ASPUSER and then create a login
and user for it in SQL Server.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168476873.734347.313800@.k58g2000hse.googlegr oups.com...
>I am using SQLServer 2000, Visual Studio 2003, C#.
> I am writing a web part which requires me to connect to a local sql
> database.
> I wrote a class which handles the connection and reading of the table.
> When I try to call .Open on the connection, it fails, the exception is
> something to do with permission.
> I used the same class to connect with a console application and a
> windows application, and it works fine. I am able to connect and read
> the table.
> Can anyone shed some light on what is the difference between
> connecting/accessing to a database via Web Application as opposed to a
> Non-Web App.
> TIA
>
|||Roger,
Thanks for the reply.
I ran SQL Server Enterprise Manager and for that database, I checked
the Users.
there are two, dbo and guest, both having full permissions.
How would I confirm tthat I am running as ASPUSER and create a login
for it?
Thanks,
IV
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> I think your problem has something to do with permission as the error
> indicates. If you are writing an ASP.Net web page then your web application
> is running as the ASPUSER Windows user and chances are this use does not
> have permissions to connect to the database. When you run as a Windows
> application you run as you and you probably have admin permissions on the
> box which gives you SA permissions in the database so you can do whatever
> you want. Confirm that you are running as ASPUSER and then create a login
> and user for it in SQL Server.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168476873.734347.313800@.k58g2000hse.googlegr oups.com...
|||Log in as an admin. USE the database where your tables are and execute
these commands (substituting the name of you machine for servername)
CREATE LOGIN [servername\ASPNET] FROM WINDOWS
CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
http://msdn2.microsoft.com/en-us/library/ms189751.aspx
http://msdn2.microsoft.com/en-us/library/ms173463.aspx
You will then have to grant this user access to the objects it needs to
access for your application
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168487427.667116.147270@.p59g2000hsd.googlegr oups.com...
> Roger,
> Thanks for the reply.
> I ran SQL Server Enterprise Manager and for that database, I checked
> the Users.
> there are two, dbo and guest, both having full permissions.
> How would I confirm tthat I am running as ASPUSER and create a login
> for it?
> Thanks,
> IV
> Roger Wolter[MSFT] wrote:
>
|||Roger,
I appreciate you taking the time to help me out.
I tried what you said and am still failing with the same exception.
Imtiaz
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> Log in as an admin. USE the database where your tables are and execute
> these commands (substituting the name of you machine for servername)
> CREATE LOGIN [servername\ASPNET] FROM WINDOWS
> CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
> http://msdn2.microsoft.com/en-us/library/ms189751.aspx
> http://msdn2.microsoft.com/en-us/library/ms173463.aspx
> You will then have to grant this user access to the objects it needs to
> access for your application
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168487427.667116.147270@.p59g2000hsd.googlegr oups.com...
Cannot connect via Linked Server
We have two servers, each with named instances of SQL Server 2000 SP3a installed. Server1\Instance1 has a linked server to Server2\Instance2. The linked server is using the SQLOLEODB provider. This linked server is setup with remote login and a correct
password. We get an error #17: SQL Server does not exist or access denied. We also get the same behaviour while trying an OPENROWSET query from the Server1\Instance1 Query Analyzer. All other SQL Server instances we have installed (on other machines)
can connect to Server2\Instance2 with a SQLOLEDB linked server, no problems.
As far as I can tell, this error is only happening when using the SQL Server. I can connect to the remote (Server2\Instance2) server using osql from Server1, and I can even connect to Server2\Instance2 by using a SQLOLEDB connection from a desktop app (f
or example, I can test the connection successfully in a UDL using SQLOLEDB to the remote server from Server1).
We are only using named pipes. I have verified that all client and all server network utilities are set exclusively to named pipes. This is true. I have also performed a network trace on the Server1 server. It does not even attempt to contact the Serv
er2 machine. I have also network traced a different SQL Server instance on another machine that can connect to Server2\Instance2 and it's network trace shows a very clear, immediate connection to the Server2.
What other steps can I take to troubleshoot this problem? I think that I have hit all the common trouble points in setting up a linked server.
Thanks,
Frank
Update: We noticed that there was an additional NIC card on the Server1 server that had an APIPA IP address. We have disabled this NIC and now the network trace is showing some communication between Server1 and Server2.
Basically, the trace shows Server1 attempts to connect using SMB to set the session up on Server2. Server2 responds with an NT error 22, STATUS_MORE_PROCESSING_REQUIRED, then a few frames later, it tries to open the IPC$ pipe on Server2. Server2 respond
s with an NT error 34, STATUS_ACCESS_DENIED. So why is SMB not allowing connections to the IPC$ pipe? I can log in to the Server1 machine under the same account as SQL Server is running as and issue a successful "net use \\Server2\IPC$" without a proble
m. The network trace requests from Server1 for the net use look similar to those generated by SQL Server linked server. Why does one get an access denied and the other does not?
Thanks,
Frank
|||Hi Frank,
I learned you are failed to create linked Server between Server1\Instance1
and Server2\Instance2. The error "SQL Server does not exist or access
denied." occurred.
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
2. Please check to see if UDP port 1434 is enabled.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Yuan, I have completed the following steps for troubleshooting from your post. My comments are indented below each of your suggestions:
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
I have checked the Server & Client network utilities: named pipes is default and the only protocol. That was stated in my original post.
2. Please check to see if UDP port 1434 is enabled.
Yes, port 1434 UDP is listening on the Server2 machine.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
Adding the linked server is not the problem. I can do it either through Enterprise Manager or the stored procedure. It is when I try to connect to the linked server (for example, when EM queries for table names from the linked server) that I get
Error #17 SQL Server does not exist or access denied, as stated in my original post.
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
I have been monitoring the event log (all application, security and system) for any errors on either system and there is nothing.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
I have tried to create an alias with the same results. No connectivity; access denied.
I have hit most of these normal troubleshooting steps. I don't usually jump to a network trace before trying things like this. The SMB network trace for opening the named pipe shows an access denied error from the Server2. What other issues might cause
this?
Thanks,
Frank
|||Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>X<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/default...b;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Yuan, we have tried creating a SQL Server without using the OLEDB provider and this failed in the same manner as the prior failures. Both the openquery and the four part fully qualified name queries failed with Error #17, SQL Server does not exist or acc
ess denied.
The MDAC is 2.7SP1 on Server1, 2.8 on Server2...
Any help at this point would be greatly appreciated...
Thanks,
Frank
-- "Yuan Shao" wrote: --
Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>?X<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/default...b;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Frank,
Thanks for your feedback. After reviewing our discussion in detail, I
noticed you test the connection successfully in a UDL using SQLOLEDB to the
remote server (server2/instance2) from Server1. However, you still got the
error "SQL Server does not exist or access denied." using linked server
I would like you to check if this is a permission problem. Please try to
create a linked server with sa login and check to see if the same error
persists. I have attached a linkedserver.zip file with my notification to
help describe the configuration of linked server using sa login.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Yuan, we have tried connecting to the linked server using the sa password and it still results in the original failure: Error 17, SQL Server does not exist or access denied. It seems like it is the named pipes connectivity shutting the door down rather t
han SQL Server, although I cannot verify this as neither SQL Server nor the operating system are logging this (despite having all failure logging turned on both the OS local security policy and in SQL Server). Any other ideas?
Thanks,
Frank
|||Have you tried a connection method other than named pipes. Try making TcpIP and secondary connection method and setting up an alias using IP.
Are both servers on the same segment?
Sometimes netbios names are not passed across segments.
Have you tried rebooting the server1 since disabling the NIC. Sometimes it needs to rebroadcast its existance on the NIC.
Thanks
Jeff
|||Hello Frank,
Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/default...=sz;en-us;top.
If this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*Subject Line
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Thanks for using MSDN Newsgroups.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
| Thread-Topic: Cannot connect via Linked Server
| thread-index: AcQh0Df+wj3plzMnQ3+eAqcmfTrgkg==
| X-WN-Post: microsoft.public.sqlserver.connect
| From: "=?Utf-8?B?RnJhbmsgSm9uZXM=?=" <frank@.bogusfiosincfake.com>
| References: <99E987D2-0636-4917-8627-8E1A87789198@.microsoft.com>
<4B4AE818-15A4-4C50-97DC-7370D8DC8D49@.microsoft.com>
<3tFzedKHEHA.612@.cpmsftngxa06.phx.gbl>
| Subject: RE: Cannot connect via Linked Server
| Date: Tue, 13 Apr 2004 20:26:04 -0700
| Lines: 4
| Message-ID: <50E78236-79B1-4D3F-9BFE-CB02692DB966@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:40978
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Yuan, we have tried connecting to the linked server using the sa password
and it still results in the original failure: Error 17, SQL Server does not
exist or access denied. It seems like it is the named pipes connectivity
shutting the door down rather than SQL Server, although I cannot verify
this as neither SQL Server nor the operating system are logging this
(despite having all failure logging turned on both the OS local security
policy and in SQL Server). Any other ideas?
Thanks,
Frank
|
password. We get an error #17: SQL Server does not exist or access denied. We also get the same behaviour while trying an OPENROWSET query from the Server1\Instance1 Query Analyzer. All other SQL Server instances we have installed (on other machines)
can connect to Server2\Instance2 with a SQLOLEDB linked server, no problems.
As far as I can tell, this error is only happening when using the SQL Server. I can connect to the remote (Server2\Instance2) server using osql from Server1, and I can even connect to Server2\Instance2 by using a SQLOLEDB connection from a desktop app (f
or example, I can test the connection successfully in a UDL using SQLOLEDB to the remote server from Server1).
We are only using named pipes. I have verified that all client and all server network utilities are set exclusively to named pipes. This is true. I have also performed a network trace on the Server1 server. It does not even attempt to contact the Serv
er2 machine. I have also network traced a different SQL Server instance on another machine that can connect to Server2\Instance2 and it's network trace shows a very clear, immediate connection to the Server2.
What other steps can I take to troubleshoot this problem? I think that I have hit all the common trouble points in setting up a linked server.
Thanks,
Frank
Update: We noticed that there was an additional NIC card on the Server1 server that had an APIPA IP address. We have disabled this NIC and now the network trace is showing some communication between Server1 and Server2.
Basically, the trace shows Server1 attempts to connect using SMB to set the session up on Server2. Server2 responds with an NT error 22, STATUS_MORE_PROCESSING_REQUIRED, then a few frames later, it tries to open the IPC$ pipe on Server2. Server2 respond
s with an NT error 34, STATUS_ACCESS_DENIED. So why is SMB not allowing connections to the IPC$ pipe? I can log in to the Server1 machine under the same account as SQL Server is running as and issue a successful "net use \\Server2\IPC$" without a proble
m. The network trace requests from Server1 for the net use look similar to those generated by SQL Server linked server. Why does one get an access denied and the other does not?
Thanks,
Frank
|||Hi Frank,
I learned you are failed to create linked Server between Server1\Instance1
and Server2\Instance2. The error "SQL Server does not exist or access
denied." occurred.
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
2. Please check to see if UDP port 1434 is enabled.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Yuan, I have completed the following steps for troubleshooting from your post. My comments are indented below each of your suggestions:
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
I have checked the Server & Client network utilities: named pipes is default and the only protocol. That was stated in my original post.
2. Please check to see if UDP port 1434 is enabled.
Yes, port 1434 UDP is listening on the Server2 machine.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
Adding the linked server is not the problem. I can do it either through Enterprise Manager or the stored procedure. It is when I try to connect to the linked server (for example, when EM queries for table names from the linked server) that I get
Error #17 SQL Server does not exist or access denied, as stated in my original post.
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
I have been monitoring the event log (all application, security and system) for any errors on either system and there is nothing.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
I have tried to create an alias with the same results. No connectivity; access denied.
I have hit most of these normal troubleshooting steps. I don't usually jump to a network trace before trying things like this. The SMB network trace for opening the named pipe shows an access denied error from the Server2. What other issues might cause
this?
Thanks,
Frank
|||Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>X<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/default...b;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Yuan, we have tried creating a SQL Server without using the OLEDB provider and this failed in the same manner as the prior failures. Both the openquery and the four part fully qualified name queries failed with Error #17, SQL Server does not exist or acc
ess denied.
The MDAC is 2.7SP1 on Server1, 2.8 on Server2...
Any help at this point would be greatly appreciated...
Thanks,
Frank
-- "Yuan Shao" wrote: --
Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>?X<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/default...b;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Frank,
Thanks for your feedback. After reviewing our discussion in detail, I
noticed you test the connection successfully in a UDL using SQLOLEDB to the
remote server (server2/instance2) from Server1. However, you still got the
error "SQL Server does not exist or access denied." using linked server
I would like you to check if this is a permission problem. Please try to
create a linked server with sa login and check to see if the same error
persists. I have attached a linkedserver.zip file with my notification to
help describe the configuration of linked server using sa login.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Yuan, we have tried connecting to the linked server using the sa password and it still results in the original failure: Error 17, SQL Server does not exist or access denied. It seems like it is the named pipes connectivity shutting the door down rather t
han SQL Server, although I cannot verify this as neither SQL Server nor the operating system are logging this (despite having all failure logging turned on both the OS local security policy and in SQL Server). Any other ideas?
Thanks,
Frank
|||Have you tried a connection method other than named pipes. Try making TcpIP and secondary connection method and setting up an alias using IP.
Are both servers on the same segment?
Sometimes netbios names are not passed across segments.
Have you tried rebooting the server1 since disabling the NIC. Sometimes it needs to rebroadcast its existance on the NIC.
Thanks
Jeff
|||Hello Frank,
Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/default...=sz;en-us;top.
If this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*Subject Line
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Thanks for using MSDN Newsgroups.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
| Thread-Topic: Cannot connect via Linked Server
| thread-index: AcQh0Df+wj3plzMnQ3+eAqcmfTrgkg==
| X-WN-Post: microsoft.public.sqlserver.connect
| From: "=?Utf-8?B?RnJhbmsgSm9uZXM=?=" <frank@.bogusfiosincfake.com>
| References: <99E987D2-0636-4917-8627-8E1A87789198@.microsoft.com>
<4B4AE818-15A4-4C50-97DC-7370D8DC8D49@.microsoft.com>
<3tFzedKHEHA.612@.cpmsftngxa06.phx.gbl>
| Subject: RE: Cannot connect via Linked Server
| Date: Tue, 13 Apr 2004 20:26:04 -0700
| Lines: 4
| Message-ID: <50E78236-79B1-4D3F-9BFE-CB02692DB966@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:40978
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Yuan, we have tried connecting to the linked server using the sa password
and it still results in the original failure: Error 17, SQL Server does not
exist or access denied. It seems like it is the named pipes connectivity
shutting the door down rather than SQL Server, although I cannot verify
this as neither SQL Server nor the operating system are logging this
(despite having all failure logging turned on both the OS local security
policy and in SQL Server). Any other ideas?
Thanks,
Frank
|
Cannot connect via Linked Server
We have two servers, each with named instances of SQL Server 2000 SP3a insta
lled. Server1\Instance1 has a linked server to Server2\Instance2. The link
ed server is using the SQLOLEODB provider. This linked server is setup with
remote login and a correct
password. We get an error #17: SQL Server does not exist or access denied.
We also get the same behaviour while trying an OPENROWSET query from the Se
rver1\Instance1 Query Analyzer. All other SQL Server instances we have inst
alled (on other machines)
can connect to Server2\Instance2 with a SQLOLEDB linked server, no problems.
As far as I can tell, this error is only happening when using the SQL Server
. I can connect to the remote (Server2\Instance2) server using osql from Se
rver1, and I can even connect to Server2\Instance2 by using a SQLOLEDB conne
ction from a desktop app (f
or example, I can test the connection successfully in a UDL using SQLOLEDB t
o the remote server from Server1).
We are only using named pipes. I have verified that all client and all serv
er network utilities are set exclusively to named pipes. This is true. I h
ave also performed a network trace on the Server1 server. It does not even
attempt to contact the Serv
er2 machine. I have also network traced a different SQL Server instance on
another machine that can connect to Server2\Instance2 and it's network trace
shows a very clear, immediate connection to the Server2.
What other steps can I take to troubleshoot this problem? I think that I ha
ve hit all the common trouble points in setting up a linked server.
Thanks,
FrankUpdate: We noticed that there was an additional NIC card on the Server1 serv
er that had an APIPA IP address. We have disabled this NIC and now the netw
ork trace is showing some communication between Server1 and Server2.
Basically, the trace shows Server1 attempts to connect using SMB to set the
session up on Server2. Server2 responds with an NT error 22, STATUS_MORE_PR
OCESSING_REQUIRED, then a few frames later, it tries to open the IPC$ pipe o
n Server2. Server2 respond
s with an NT error 34, STATUS_ACCESS_DENIED. So why is SMB not allowing con
nections to the IPC$ pipe? I can log in to the Server1 machine under the sa
me account as SQL Server is running as and issue a successful "net use \\Ser
ver2\IPC$" without a proble
m. The network trace requests from Server1 for the net use look similar to
those generated by SQL Server linked server. Why does one get an access den
ied and the other does not?
Thanks,
Frank|||Hi Frank,
I learned you are failed to create linked Server between Server1\Instance1
and Server2\Instance2. The error "SQL Server does not exist or access
denied." occurred.
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
2. Please check to see if UDP port 1434 is enabled.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Yuan, I have completed the following steps for troubleshooting from your
post. My comments are indented below each of your suggestions:
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
I have checked the Server & Client network utilities: named pipes is default
and the only protocol. That was stated in my original post.
2. Please check to see if UDP port 1434 is enabled.
Yes, port 1434 UDP is listening on the Server2 machine.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
Adding the linked server is not the problem. I can do it either through Ent
erprise Manager or the stored procedure. It is when I try to connect to the
linked server (for example, when EM queries for table names from the linked
server) that I get
Error #17 SQL Server does not exist or access denied, as stated in my origin
al post.
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
I have been monitoring the event log (all application, security and system)
for any errors on either system and there is nothing.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
I have tried to create an alias with the same results. No connectivity; acc
ess denied.
I have hit most of these normal troubleshooting steps. I don't usually jump
to a network trace before trying things like this. The SMB network trace f
or opening the named pipe shows an access denied error from the Server2. Wh
at other issues might cause
this?
Thanks,
Frank|||Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>_<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/defaul...kb;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Yuan, we have tried creating a SQL Server without using the OLEDB provider a
nd this failed in the same manner as the prior failures. Both the openquery
and the four part fully qualified name queries failed with Error #17, SQL S
erver does not exist or acc
ess denied.
The MDAC is 2.7SP1 on Server1, 2.8 on Server2...
Any help at this point would be greatly appreciated...
Thanks,
Frank
-- "Yuan Shao" wrote: --
Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>?_<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/defaul...kb;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Frank,
Thanks for your feedback. After reviewing our discussion in detail, I
noticed you test the connection successfully in a UDL using SQLOLEDB to the
remote server (server2/instance2) from Server1. However, you still got the
error "SQL Server does not exist or access denied." using linked server
I would like you to check if this is a permission problem. Please try to
create a linked server with sa login and check to see if the same error
persists. I have attached a linkedserver.zip file with my notification to
help describe the configuration of linked server using sa login.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Yuan, we have tried connecting to the linked server using the sa password an
d it still results in the original failure: Error 17, SQL Server does not ex
ist or access denied. It seems like it is the named pipes connectivity shut
ting the door down rather t
han SQL Server, although I cannot verify this as neither SQL Server nor the
operating system are logging this (despite having all failure logging turned
on both the OS local security policy and in SQL Server). Any other ideas?
Thanks,
Frank|||Have you tried a connection method other than named pipes. Try making TcpIP
and secondary connection method and setting up an alias using IP.
Are both servers on the same segment?
Sometimes netbios names are not passed across segments.
Have you tried rebooting the server1 since disabling the NIC. Sometimes it
needs to rebroadcast its existance on the NIC.
Thanks
Jeff|||Hello Frank,
Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/defaul...d=sz;en-us;top.
If this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*Subject Line
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Thanks for using MSDN Newsgroups.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
| Thread-Topic: Cannot connect via Linked Server
| thread-index: AcQh0Df+wj3plzMnQ3+eAqcmfTrgkg==
| X-WN-Post: microsoft.public.sqlserver.connect
| From: "examnotes" <frank@.bogusfiosincfake.com>
| References: <99E987D2-0636-4917-8627-8E1A87789198@.microsoft.com>
<4B4AE818-15A4-4C50-97DC-7370D8DC8D49@.microsoft.com>
<3tFzedKHEHA.612@.cpmsftngxa06.phx.gbl>
| Subject: RE: Cannot connect via Linked Server
| Date: Tue, 13 Apr 2004 20:26:04 -0700
| Lines: 4
| Message-ID: <50E78236-79B1-4D3F-9BFE-CB02692DB966@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:40978
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Yuan, we have tried connecting to the linked server using the sa password
and it still results in the original failure: Error 17, SQL Server does not
exist or access denied. It seems like it is the named pipes connectivity
shutting the door down rather than SQL Server, although I cannot verify
this as neither SQL Server nor the operating system are logging this
(despite having all failure logging turned on both the OS local security
policy and in SQL Server). Any other ideas?
Thanks,
Frank
|
lled. Server1\Instance1 has a linked server to Server2\Instance2. The link
ed server is using the SQLOLEODB provider. This linked server is setup with
remote login and a correct
password. We get an error #17: SQL Server does not exist or access denied.
We also get the same behaviour while trying an OPENROWSET query from the Se
rver1\Instance1 Query Analyzer. All other SQL Server instances we have inst
alled (on other machines)
can connect to Server2\Instance2 with a SQLOLEDB linked server, no problems.
As far as I can tell, this error is only happening when using the SQL Server
. I can connect to the remote (Server2\Instance2) server using osql from Se
rver1, and I can even connect to Server2\Instance2 by using a SQLOLEDB conne
ction from a desktop app (f
or example, I can test the connection successfully in a UDL using SQLOLEDB t
o the remote server from Server1).
We are only using named pipes. I have verified that all client and all serv
er network utilities are set exclusively to named pipes. This is true. I h
ave also performed a network trace on the Server1 server. It does not even
attempt to contact the Serv
er2 machine. I have also network traced a different SQL Server instance on
another machine that can connect to Server2\Instance2 and it's network trace
shows a very clear, immediate connection to the Server2.
What other steps can I take to troubleshoot this problem? I think that I ha
ve hit all the common trouble points in setting up a linked server.
Thanks,
FrankUpdate: We noticed that there was an additional NIC card on the Server1 serv
er that had an APIPA IP address. We have disabled this NIC and now the netw
ork trace is showing some communication between Server1 and Server2.
Basically, the trace shows Server1 attempts to connect using SMB to set the
session up on Server2. Server2 responds with an NT error 22, STATUS_MORE_PR
OCESSING_REQUIRED, then a few frames later, it tries to open the IPC$ pipe o
n Server2. Server2 respond
s with an NT error 34, STATUS_ACCESS_DENIED. So why is SMB not allowing con
nections to the IPC$ pipe? I can log in to the Server1 machine under the sa
me account as SQL Server is running as and issue a successful "net use \\Ser
ver2\IPC$" without a proble
m. The network trace requests from Server1 for the net use look similar to
those generated by SQL Server linked server. Why does one get an access den
ied and the other does not?
Thanks,
Frank|||Hi Frank,
I learned you are failed to create linked Server between Server1\Instance1
and Server2\Instance2. The error "SQL Server does not exist or access
denied." occurred.
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
2. Please check to see if UDP port 1434 is enabled.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Yuan, I have completed the following steps for troubleshooting from your
post. My comments are indented below each of your suggestions:
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
I have checked the Server & Client network utilities: named pipes is default
and the only protocol. That was stated in my original post.
2. Please check to see if UDP port 1434 is enabled.
Yes, port 1434 UDP is listening on the Server2 machine.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
Adding the linked server is not the problem. I can do it either through Ent
erprise Manager or the stored procedure. It is when I try to connect to the
linked server (for example, when EM queries for table names from the linked
server) that I get
Error #17 SQL Server does not exist or access denied, as stated in my origin
al post.
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
I have been monitoring the event log (all application, security and system)
for any errors on either system and there is nothing.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
I have tried to create an alias with the same results. No connectivity; acc
ess denied.
I have hit most of these normal troubleshooting steps. I don't usually jump
to a network trace before trying things like this. The SMB network trace f
or opening the named pipe shows an access denied error from the Server2. Wh
at other issues might cause
this?
Thanks,
Frank|||Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>_<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/defaul...kb;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Yuan, we have tried creating a SQL Server without using the OLEDB provider a
nd this failed in the same manner as the prior failures. Both the openquery
and the four part fully qualified name queries failed with Error #17, SQL S
erver does not exist or acc
ess denied.
The MDAC is 2.7SP1 on Server1, 2.8 on Server2...
Any help at this point would be greatly appreciated...
Thanks,
Frank
-- "Yuan Shao" wrote: --
Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>?_<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/defaul...kb;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Frank,
Thanks for your feedback. After reviewing our discussion in detail, I
noticed you test the connection successfully in a UDL using SQLOLEDB to the
remote server (server2/instance2) from Server1. However, you still got the
error "SQL Server does not exist or access denied." using linked server
I would like you to check if this is a permission problem. Please try to
create a linked server with sa login and check to see if the same error
persists. I have attached a linkedserver.zip file with my notification to
help describe the configuration of linked server using sa login.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Yuan, we have tried connecting to the linked server using the sa password an
d it still results in the original failure: Error 17, SQL Server does not ex
ist or access denied. It seems like it is the named pipes connectivity shut
ting the door down rather t
han SQL Server, although I cannot verify this as neither SQL Server nor the
operating system are logging this (despite having all failure logging turned
on both the OS local security policy and in SQL Server). Any other ideas?
Thanks,
Frank|||Have you tried a connection method other than named pipes. Try making TcpIP
and secondary connection method and setting up an alias using IP.
Are both servers on the same segment?
Sometimes netbios names are not passed across segments.
Have you tried rebooting the server1 since disabling the NIC. Sometimes it
needs to rebroadcast its existance on the NIC.
Thanks
Jeff|||Hello Frank,
Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/defaul...d=sz;en-us;top.
If this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*Subject Line
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Thanks for using MSDN Newsgroups.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
| Thread-Topic: Cannot connect via Linked Server
| thread-index: AcQh0Df+wj3plzMnQ3+eAqcmfTrgkg==
| X-WN-Post: microsoft.public.sqlserver.connect
| From: "examnotes" <frank@.bogusfiosincfake.com>
| References: <99E987D2-0636-4917-8627-8E1A87789198@.microsoft.com>
<4B4AE818-15A4-4C50-97DC-7370D8DC8D49@.microsoft.com>
<3tFzedKHEHA.612@.cpmsftngxa06.phx.gbl>
| Subject: RE: Cannot connect via Linked Server
| Date: Tue, 13 Apr 2004 20:26:04 -0700
| Lines: 4
| Message-ID: <50E78236-79B1-4D3F-9BFE-CB02692DB966@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:40978
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Yuan, we have tried connecting to the linked server using the sa password
and it still results in the original failure: Error 17, SQL Server does not
exist or access denied. It seems like it is the named pipes connectivity
shutting the door down rather than SQL Server, although I cannot verify
this as neither SQL Server nor the operating system are logging this
(despite having all failure logging turned on both the OS local security
policy and in SQL Server). Any other ideas?
Thanks,
Frank
|
Cannot connect using TCP/IP protocol
Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?
What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?
What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?
Cannot connect using TCP/IP protocol
Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem.
>any advice?
Cannot connect using TCP/IP protocol
Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem
.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without proble
m.
>any advice?
TCP/IP protocol. NamePipe is OK. Other XP client can connect without problem
.
any advice?What is the error number and error message?
There are some TCP/IP issues with older MDAC versions - did
you check/try updating the MDAC version on the 98 client?
-Sue
On Mon, 24 Oct 2005 01:50:02 -0700, "alex"
<alex@.discussions.microsoft.com> wrote:
>Win98 client cannot connect to SQL 2K (sp3) on WIN SERVER 2003 (sp1) using
>TCP/IP protocol. NamePipe is OK. Other XP client can connect without proble
m.
>any advice?
cannot connect using tcp/ip
Hi,
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I tes
t
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I tes
t
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
cannot connect using tcp/ip
Hi,
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-
Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut
|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
it using telnet in port 1433, nothing happends.
I need to connect to this server via Internet.
How can I do?
Leo-
Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
> Hi,
> I'm using SQL Server 2000 and I'm trying to connect via TCP/IP. When I test
> it using telnet in port 1433, nothing happends.
> I need to connect to this server via Internet.
> How can I do?
> Leo-
Have you enabled TCP on the Server? There should be a program "SQL Server
Client Configuration" on the server. If not, search for SVRNETCN.EXE on the
server. With this program you can check if TCP is enabled.
Second problem could be a firewall.
bye,
helmut
|||I have enabled TCP port (1433). I can access to that port from any computer
in my intranet. But I cannot do this using my internet IP.
There's no router issue. I think it's due to Windows XP SP2 Firewall, but I
have open those ports to.
Leo-
"helmut woess" <hw@.iis.at> escribi en el mensaje
news:1nee56bcb93ir$.rpvg777x77c0.dlg@.40tude.net...
> Am Tue, 15 Nov 2005 13:17:12 -0300 schrieb Leo Deserio:
>
> Have you enabled TCP on the Server? There should be a program "SQL Server
> Client Configuration" on the server. If not, search for SVRNETCN.EXE on
> the
> server. With this program you can check if TCP is enabled.
> Second problem could be a firewall.
> bye,
> helmut
Cannot connect using sql authentication in query analyzer
I just moved a database from one sql server to another. Both use Windows
2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
I connect to the database in the old server without a problem. I connect to
the new server fine with NT authentication, or if I log in as sa with SQL
authentication, but if I log in as a different user with SQL authentication
on the new server, I get this message:
Unable to connect to server Enterprise3:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
Server is terminating this process.
Ooops - Just remembered one other piece that may be impartant: We were
swapping the two servers, so had to rename both. With SQL Server 7, that
means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
to reapply the service packs and the hotfixes, but it will not allow it.
(Current installation is more recent.) This is not a problem with the SP3
server, but only with the sp4+ server.
"UWKC Admin" wrote:
> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Hi
What do you call "mini-reinstall"? If you have problems, always do a full
install, anything else is not supported by Microsoft.
Regards
Mike
"UWKC Admin" wrote:
[vbcol=seagreen]
> Ooops - Just remembered one other piece that may be impartant: We were
> swapping the two servers, so had to rename both. With SQL Server 7, that
> means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
> to reapply the service packs and the hotfixes, but it will not allow it.
> (Current installation is more recent.) This is not a problem with the SP3
> server, but only with the sp4+ server.
> "UWKC Admin" wrote:
|||Mike - Thanks for the question. When I say mini-reinstall, I mean the
reinstall that SQL Server demands we do after renaming a SQL Server 7.0
installation. It tells us something to the effect that that the
installstallation is bad and may have been tampered with, then tells us to
reinstall SQL Server. We do that, using the original SQL Server CD. I call
it a mini-install because it only takes a couple of minutes to complete.
"UWKC Admin" wrote:
> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Did you run sp_dropserver and sp_addserver after you
changed the server name and updated the registry with the
SQL Server CD (the process you refer to as a mini-reinstall
just updates the server name entries in the registry)?
e.g.
sp_dropserver 'YourOldServerName'
go
sp_addserver 'YourNewServerName', local
This part of the process just updates the server name in the
sysservers table. You should run in on both servers that you
renamed.
I'm not sure this will make any difference as I don't
remember anyone getting access violations if they miss any
of the steps in renaming a server...but worth a try.
-Sue
On Thu, 9 Dec 2004 11:33:06 -0800, "UWKC Admin"
<UWKCAdmin@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mike - Thanks for the question. When I say mini-reinstall, I mean the
>reinstall that SQL Server demands we do after renaming a SQL Server 7.0
>installation. It tells us something to the effect that that the
>installstallation is bad and may have been tampered with, then tells us to
>reinstall SQL Server. We do that, using the original SQL Server CD. I call
>it a mini-install because it only takes a couple of minutes to complete.
>"UWKC Admin" wrote:
2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
I connect to the database in the old server without a problem. I connect to
the new server fine with NT authentication, or if I log in as sa with SQL
authentication, but if I log in as a different user with SQL authentication
on the new server, I get this message:
Unable to connect to server Enterprise3:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
Server is terminating this process.
Ooops - Just remembered one other piece that may be impartant: We were
swapping the two servers, so had to rename both. With SQL Server 7, that
means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
to reapply the service packs and the hotfixes, but it will not allow it.
(Current installation is more recent.) This is not a problem with the SP3
server, but only with the sp4+ server.
"UWKC Admin" wrote:
> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Hi
What do you call "mini-reinstall"? If you have problems, always do a full
install, anything else is not supported by Microsoft.
Regards
Mike
"UWKC Admin" wrote:
[vbcol=seagreen]
> Ooops - Just remembered one other piece that may be impartant: We were
> swapping the two servers, so had to rename both. With SQL Server 7, that
> means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
> to reapply the service packs and the hotfixes, but it will not allow it.
> (Current installation is more recent.) This is not a problem with the SP3
> server, but only with the sp4+ server.
> "UWKC Admin" wrote:
|||Mike - Thanks for the question. When I say mini-reinstall, I mean the
reinstall that SQL Server demands we do after renaming a SQL Server 7.0
installation. It tells us something to the effect that that the
installstallation is bad and may have been tampered with, then tells us to
reinstall SQL Server. We do that, using the original SQL Server CD. I call
it a mini-install because it only takes a couple of minutes to complete.
"UWKC Admin" wrote:
> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Did you run sp_dropserver and sp_addserver after you
changed the server name and updated the registry with the
SQL Server CD (the process you refer to as a mini-reinstall
just updates the server name entries in the registry)?
e.g.
sp_dropserver 'YourOldServerName'
go
sp_addserver 'YourNewServerName', local
This part of the process just updates the server name in the
sysservers table. You should run in on both servers that you
renamed.
I'm not sure this will make any difference as I don't
remember anyone getting access violations if they miss any
of the steps in renaming a server...but worth a try.
-Sue
On Thu, 9 Dec 2004 11:33:06 -0800, "UWKC Admin"
<UWKCAdmin@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mike - Thanks for the question. When I say mini-reinstall, I mean the
>reinstall that SQL Server demands we do after renaming a SQL Server 7.0
>installation. It tells us something to the effect that that the
>installstallation is bad and may have been tampered with, then tells us to
>reinstall SQL Server. We do that, using the original SQL Server CD. I call
>it a mini-install because it only takes a couple of minutes to complete.
>"UWKC Admin" wrote:
Cannot Connect using IP to Clustered Named Instance
I am having trouble connecting when using the IP address to a named
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
Cannot connect using ADO with Excel Microsoft Jet Provider 4.0
Hi:
I have a vb 6 app that exports data from sql to excel. The user has the ability to select either local or server. When they select server, the connection string is modified to include the server name instead of the local msde instance to look like this:
"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"
I'm using Microsoft Jet Provider 4.0 and OpenDataSource.
SELECT * INTO TempXL FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',
'Data Source=C:\test\xltest.xls;Extended Properties=Excel 8.0')...[Sheet1$]
This code works fine when user is accessing msde on local, but when using above DSN, I receive the following message:
"2147217900 - OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEdB.4.0' IDBInitialize:: Initialize returned 0x800040005: The provider did not give any information about the error.]
When I trace the connection, these error messages occur:
Failed to set proper user name ('NT AUTHORITY\SYSTEM') for the connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot alter table 'TblXMyTable' because this table does not exist in database 'master'. (State 42S02) (Code 4902)
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'TblxMytable'. (State 42S02) (Code 208)
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. The provider did not give any information about the error. (State 42000) (Code 7399)
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: The provider did not give any information about the error.]. (State 01000) (Code 7300)
I am especially puzzled by the second message because I am specifying the database name in my connection string as:
"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"
I can read from the server copy and copy to Excel, but I cannot write back to SQL. Can someone please tell me what I'm doing wrong?
Thanks in advance for any help.,
I had a problem similar to this when working with VB6, DAO, ADO and SQL Server 2005.
One user could do a query, another user could not.
In fact, the error message was similar to yours. The error message claimed that the table we were trying to query did NOT EXIST.
So, I believe your problem lies with Security.
Try making the user a database owner of the database in question. If this solves your problem, then you can look for a way to set the permission/security correctly for the specifc tables they need access to.
Cannot connect using ADO with Excel Microsoft Jet Provider 4.0
Hi:
I have a vb 6 app that exports data from sql to excel. The user has the ability to select either local or server. When they select server, the connection string is modified to include the server name instead of the local msde instance to look like this:
"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"
I'm using Microsoft Jet Provider 4.0 and OpenDataSource.
SELECT * INTO TempXL FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',
'Data Source=C:\test\xltest.xls;Extended Properties=Excel 8.0')...[Sheet1$]
This code works fine when user is accessing msde on local, but when using above DSN, I receive the following message:
"2147217900 - OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEdB.4.0' IDBInitialize:: Initialize returned 0x800040005: The provider did not give any information about the error.]
When I trace the connection, these error messages occur:
Failed to set proper user name ('NT AUTHORITY\SYSTEM') for the connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot alter table 'TblXMyTable' because this table does not exist in database 'master'. (State 42S02) (Code 4902)
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'TblxMytable'. (State 42S02) (Code 208)
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. The provider did not give any information about the error. (State 42000) (Code 7399)
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: The provider did not give any information about the error.]. (State 01000) (Code 7300)
I am especially puzzled by the second message because I am specifying the database name in my connection string as:
"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"
I can read from the server copy and copy to Excel, but I cannot write back to SQL. Can someone please tell me what I'm doing wrong?
Thanks in advance for any help.,
I had a problem similar to this when working with VB6, DAO, ADO and SQL Server 2005.
One user could do a query, another user could not.
In fact, the error message was similar to yours. The error message claimed that the table we were trying to query did NOT EXIST.
So, I believe your problem lies with Security.
Try making the user a database owner of the database in question. If this solves your problem, then you can look for a way to set the permission/security correctly for the specifc tables they need access to.
Cannot connect toMyserver\SQLEXPRESS
Hi,
i installed Sql server 2005 express edition on an Windows XP professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
--
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
CasperIs SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
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)
----
---
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an Windows XP professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> 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)
> ----
---
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>|||Let's see your ConnectionString.
____________________________________
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)
----
---
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> 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)
> ----
---
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>
i installed Sql server 2005 express edition on an Windows XP professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
--
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
CasperIs SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
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)
----
---
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an Windows XP professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> 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)
> ----
---
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>|||Let's see your ConnectionString.
____________________________________
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)
----
---
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> 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)
> ----
---
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>
Cannot connect toMyserver\SQLEXPRESS
Hi,
i installed Sql server 2005 express edition on an windows xp professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
Casper
Is SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
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)
------
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an windows xp professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>
|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> 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)
> ------
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>
|||Let's see your ConnectionString.
____________________________________
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)
------
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>
|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> 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)
> ------
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>
i installed Sql server 2005 express edition on an windows xp professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
Casper
Is SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
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)
------
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an windows xp professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>
|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> 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)
> ------
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>
|||Let's see your ConnectionString.
____________________________________
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)
------
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>
|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> 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)
> ------
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>
Cannot connect to to the other server when setting up replication in SQL 2005
Im trying to setup replication between two 2005 standard editions. They are on the same LAN and installed equally + SP1. They are installed as named instances (with the same instance name MSSQL01). Remote access is allowed and TCP/IP and shared memory and I can connect between them.
SQL1\MSSQL01 is configured as the publisher & distributor and the snapshot is done. When Im using the subscriber wizard from SQL1 to create the subscriptions and add SQL2\MSSQL01 as a subscriber the connection fails to the remote server.
The error message is:
TITLE: Connect to Server
Cannot connect to SQL2\MSSQL01.
ADDITIONAL INFORMATION:
Failed to connect to server SQL2\MSSQL01. (Microsoft.SqlServer.ConnectionInfo)
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
When I do a manual connection to SQL2 using the server managemnet studio on SQL1 I cannot connect using the instance name e.g. SQL2\MSSQL01, it works only when only using the server name e.g. SQL2. Then I have full access both when using a windows or SQL user.
When trying with using the server name only when setting up the subscription, I got a error saying that I need to use the full name.
TITLE: Connect to Server
Cannot connect to TFMHQARNDE07.
ADDITIONAL INFORMATION:
SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, ' SQL2\MSSQL01'. (Replication.Utilities)
I can also mention that theese servers are cloned from another server and I needed to drop the old servername and add the new servername (sp_addserver) on both servers to get the publisher to work.
When I try to setup the subscription from SQL2 and add SQL1 as a publisher I get the same error.
Any one have any idea what it can be?
I found the problem. I didnt have the SQL Browser service runnning which looks to be needed when using instances. After starting it, it works to connect.
Cannot connect to the SQL 2005 Express
I created test project and want to use SQL 2005 database inside.
1. I created Test database with DEFAULT rights
2. I go into server explorer, press Add Connection. Shows message box for connecting to the server: <PCNAME> using windows authntification.
But NO database allowed to view :(.
Which setting should be set for SQL server database to i could connect and work with it?
P.S I use LOCAL connection. The Application and Server should be on the same PC.|||sqlexpress is a named instance with instance name as "sqlexpress". For local connection, your connection string can be ".\sqlexpress", "(local)\sqlexpress", "<machinename>\sqlexpress", and e.t.c..
some other useful info: http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
|||I do not use connection string - I use Visual Studio User Interface for connecting. I could try to connect as blind but I want to get list of the databases and connect on click.
Could you please give me advice how I could to do that?
|||In Visual Studio, click Connect to Database in Server Explorer. Under Choose Data Source, select Microsoft SQL Server. Under Data Provider drop-down list, select .NET Framework Data Provider for SQL Server and click Continue. On the Add Connection window, in the Server Name drop-down list, either you type .\SQLEXPRESS or select it in your list. Select the database in the drop-down list and click Test Connection. Once you're done, you now have this connection in your SQL Server 2005 Express database from Visual Studio 2005|||bass_player wrote:
On the Add Connection window, in the Server Name drop-down list, either you type .\SQLEXPRESS or select it in your list. Select the database in the drop-down list and click Test Connection.
I CANNOT SEE ANY databases, so I CANNOT SELECT invisible (for me) database and because I ask - WHICH RIGHTS I should to set in MS SQL Express to Databases could be visible.
Server list - exist (one server: <PCNAME>)
Databases list is EMPTY!!!!!!
|||The list is for server, a server can host multiple databases. In order to see your local server in the drop down list, you need to have your SQL Browser running. Did you try to type ".\sqlexpress"?
|||
Aaaaaaa!!!....
I've understood. You all were right. .\sqlexpress is required - and all works.
Thanx bass_player and Xinwei Hong - MSFT
cannot connect to the server
hello,
i want to install sql server 2000 in my machine which has win xp. now the
problem is that it does not get connected to the server. error message comes
that there is a connection failure.
pls help me
thank u
bituDid you configuire the firewall to let the appropiate ports SQL Server
is configured for let through ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
i want to install sql server 2000 in my machine which has win xp. now the
problem is that it does not get connected to the server. error message comes
that there is a connection failure.
pls help me
thank u
bituDid you configuire the firewall to let the appropiate ports SQL Server
is configured for let through ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
cannot connect to the server
hello,
i want to install sql server 2000 in my machine which has win xp. now the
problem is that it does not get connected to the server. error message comes
that there is a connection failure.
pls help me
thank u
bitu
Did you configuire the firewall to let the appropiate ports SQL Server
is configured for let through ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
i want to install sql server 2000 in my machine which has win xp. now the
problem is that it does not get connected to the server. error message comes
that there is a connection failure.
pls help me
thank u
bitu
Did you configuire the firewall to let the appropiate ports SQL Server
is configured for let through ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Cannot connect to the Reporting Services 2005 - SQL Server Managem
I installl SQL Server 2005 Reporting and did correctly set it up (Report
Server and Report Management).
Now I cannot connect the Reporting Services Server through SQL Server
Management.
When trying to connect I get :
TITLE: Connect to Server
--
Cannot connect to ASED\RS2005WC.
--
ADDITIONAL INFORMATION:
The underlying connection was closed: An unexpected error occurred on a
receive. (Microsoft.SqlServer.Management.UI.RSClient)
--
Unable to read data from the transport connection: An existing connection
was forcibly closed by the remote host. (System)
--
An existing connection was forcibly closed by the remote host (System)
--
BUTTONS:
OK
--
Please helpOn Dec 18, 4:26 pm, Pascal <Pas...@.discussions.microsoft.com> wrote:
> I installl SQL Server 2005 Reporting and did correctly set it up (Report
> Server and Report Management).
> Now I cannot connect the Reporting Services Server through SQL Server
> Management.
> When trying to connect I get :
> TITLE: Connect to Server
> --
> Cannot connect to ASED\RS2005WC.
> --
> ADDITIONAL INFORMATION:
> The underlying connection was closed: An unexpected error occurred on a
> receive. (Microsoft.SqlServer.Management.UI.RSClient)
> --
> Unable to read data from the transport connection: An existing connection
> was forcibly closed by the remote host. (System)
> --
> An existing connection was forcibly closed by the remote host (System)
> --
> BUTTONS:
> OK
> --
> Please help
This link might help.
http://www.cisco-cert.com/Connect/95598-SQL-Server-management-studio--A-connection-to-the-report-server-failed--remote-server-
Regards,
Enrique Martinez
Sr. Software Consultant
Server and Report Management).
Now I cannot connect the Reporting Services Server through SQL Server
Management.
When trying to connect I get :
TITLE: Connect to Server
--
Cannot connect to ASED\RS2005WC.
--
ADDITIONAL INFORMATION:
The underlying connection was closed: An unexpected error occurred on a
receive. (Microsoft.SqlServer.Management.UI.RSClient)
--
Unable to read data from the transport connection: An existing connection
was forcibly closed by the remote host. (System)
--
An existing connection was forcibly closed by the remote host (System)
--
BUTTONS:
OK
--
Please helpOn Dec 18, 4:26 pm, Pascal <Pas...@.discussions.microsoft.com> wrote:
> I installl SQL Server 2005 Reporting and did correctly set it up (Report
> Server and Report Management).
> Now I cannot connect the Reporting Services Server through SQL Server
> Management.
> When trying to connect I get :
> TITLE: Connect to Server
> --
> Cannot connect to ASED\RS2005WC.
> --
> ADDITIONAL INFORMATION:
> The underlying connection was closed: An unexpected error occurred on a
> receive. (Microsoft.SqlServer.Management.UI.RSClient)
> --
> Unable to read data from the transport connection: An existing connection
> was forcibly closed by the remote host. (System)
> --
> An existing connection was forcibly closed by the remote host (System)
> --
> BUTTONS:
> OK
> --
> Please help
This link might help.
http://www.cisco-cert.com/Connect/95598-SQL-Server-management-studio--A-connection-to-the-report-server-failed--remote-server-
Regards,
Enrique Martinez
Sr. Software Consultant
Cannot connect to the report server db.
After I reboot the server, the following error message show on:
"Schedule and delivery process cannot connect to the report server
database"
Before I reboot the server, I try to set a new subscription.
I think this is boot sequence problem.
Anyone have any ideas.Do you also get this error when browsing to //localhost/reportserver? If so
then running rsconfig.exe should solve your problem.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Veronica" <Veronica@.discussions.microsoft.com> wrote in message
news:7DC58382-396E-480F-9293-431B206A0DFE@.microsoft.com...
> After I reboot the server, the following error message show on:
> "Schedule and delivery process cannot connect to the report server
> database"
> Before I reboot the server, I try to set a new subscription.
> I think this is boot sequence problem.
> Anyone have any ideas.|||No error when browsing to //localhost/reportserver.
What argument should be pass when running rsconfig.exe?
Thank you!
"Daniel Reib [MSFT]" wrote:
> Do you also get this error when browsing to //localhost/reportserver? If so
> then running rsconfig.exe should solve your problem.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Veronica" <Veronica@.discussions.microsoft.com> wrote in message
> news:7DC58382-396E-480F-9293-431B206A0DFE@.microsoft.com...
> > After I reboot the server, the following error message show on:
> > "Schedule and delivery process cannot connect to the report server
> > database"
> >
> > Before I reboot the server, I try to set a new subscription.
> > I think this is boot sequence problem.
> >
> > Anyone have any ideas.
>
>|||It sounds like you are using integrated security to connect to the RS
catalog. Most likely the ReportServer user does not have permission to
connect to the catalog. You can use the -c command with rsconfig to set the
connection method that rs will use to talk to the DB.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Veronica" <Veronica@.discussions.microsoft.com> wrote in message
news:0E5299FF-C132-4C90-9D20-4C255354093B@.microsoft.com...
> No error when browsing to //localhost/reportserver.
> What argument should be pass when running rsconfig.exe?
> Thank you!
> "Daniel Reib [MSFT]" wrote:
> > Do you also get this error when browsing to //localhost/reportserver?
If so
> > then running rsconfig.exe should solve your problem.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Veronica" <Veronica@.discussions.microsoft.com> wrote in message
> > news:7DC58382-396E-480F-9293-431B206A0DFE@.microsoft.com...
> > > After I reboot the server, the following error message show on:
> > > "Schedule and delivery process cannot connect to the report server
> > > database"
> > >
> > > Before I reboot the server, I try to set a new subscription.
> > > I think this is boot sequence problem.
> > >
> > > Anyone have any ideas.
> >
> >
> >
"Schedule and delivery process cannot connect to the report server
database"
Before I reboot the server, I try to set a new subscription.
I think this is boot sequence problem.
Anyone have any ideas.Do you also get this error when browsing to //localhost/reportserver? If so
then running rsconfig.exe should solve your problem.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Veronica" <Veronica@.discussions.microsoft.com> wrote in message
news:7DC58382-396E-480F-9293-431B206A0DFE@.microsoft.com...
> After I reboot the server, the following error message show on:
> "Schedule and delivery process cannot connect to the report server
> database"
> Before I reboot the server, I try to set a new subscription.
> I think this is boot sequence problem.
> Anyone have any ideas.|||No error when browsing to //localhost/reportserver.
What argument should be pass when running rsconfig.exe?
Thank you!
"Daniel Reib [MSFT]" wrote:
> Do you also get this error when browsing to //localhost/reportserver? If so
> then running rsconfig.exe should solve your problem.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Veronica" <Veronica@.discussions.microsoft.com> wrote in message
> news:7DC58382-396E-480F-9293-431B206A0DFE@.microsoft.com...
> > After I reboot the server, the following error message show on:
> > "Schedule and delivery process cannot connect to the report server
> > database"
> >
> > Before I reboot the server, I try to set a new subscription.
> > I think this is boot sequence problem.
> >
> > Anyone have any ideas.
>
>|||It sounds like you are using integrated security to connect to the RS
catalog. Most likely the ReportServer user does not have permission to
connect to the catalog. You can use the -c command with rsconfig to set the
connection method that rs will use to talk to the DB.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Veronica" <Veronica@.discussions.microsoft.com> wrote in message
news:0E5299FF-C132-4C90-9D20-4C255354093B@.microsoft.com...
> No error when browsing to //localhost/reportserver.
> What argument should be pass when running rsconfig.exe?
> Thank you!
> "Daniel Reib [MSFT]" wrote:
> > Do you also get this error when browsing to //localhost/reportserver?
If so
> > then running rsconfig.exe should solve your problem.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Veronica" <Veronica@.discussions.microsoft.com> wrote in message
> > news:7DC58382-396E-480F-9293-431B206A0DFE@.microsoft.com...
> > > After I reboot the server, the following error message show on:
> > > "Schedule and delivery process cannot connect to the report server
> > > database"
> > >
> > > Before I reboot the server, I try to set a new subscription.
> > > I think this is boot sequence problem.
> > >
> > > Anyone have any ideas.
> >
> >
> >
Cannot connect to the Report Mgr.
Hi All,
I'm experiencing the error referenced in the following link to MS
Support
http://support.microsoft.com/Default.aspx?kbid=922656
I implemented the workaround but I'm still getting the error. Actually
when I started I was receiving "error message 1" and then when I
updated my RSWebApplication.config file to use the fully qualified URL
using the IP Address that is assigned to the Default Web Site's "IP
Address" property.
My config file now looks like this...
<ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
The server is a Windows 2003 server and the Reporting Services was
installed with SQL2005 but not configured. I was able to configure the
Reports server (from what I can tell) using the "Reporting Services
Configuration" tool).
Any idea as to what may still be causing the problem?
Thanks in advance for any help you can offer.
Mike Gorgone
Senior Software Engineer
PictureU PromotionsOn Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
> Hi All,
> I'm experiencing the error referenced in the following link to MS
> Support
> http://support.microsoft.com/Default.aspx?kbid=922656
> I implemented the workaround but I'm still getting the error. Actually
> when I started I was receiving "error message 1" and then when I
> updated my RSWebApplication.config file to use the fully qualified URL
> using the IP Address that is assigned to the Default Web Site's "IP
> Address" property.
> My config file now looks like this...
> <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> The server is a Windows 2003 server and the Reporting Services was
> installed with SQL2005 but not configured. I was able to configure the
> Reports server (from what I can tell) using the "Reporting Services
> Configuration" tool).
> Any idea as to what may still be causing the problem?
> Thanks in advance for any help you can offer.
> Mike Gorgone
> Senior Software Engineer
> PictureU Promotions
The last response in this link might be helpful.
http://www.sqlreportingservices.net/Ask/1730.aspx
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 21, 9:55 pm, EMartinez <emartinez...@.gmail.com> wrote:
> On Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
>
> > Hi All,
> > I'm experiencing the error referenced in the following link to MS
> > Support
> >http://support.microsoft.com/Default.aspx?kbid=922656
> > I implemented the workaround but I'm still getting the error. Actually
> > when I started I was receiving "error message 1" and then when I
> > updated my RSWebApplication.config file to use the fully qualified URL
> > using the IP Address that is assigned to the Default Web Site's "IP
> > Address" property.
> > My config file now looks like this...
> > <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > The server is a Windows 2003 server and the Reporting Services was
> > installed with SQL2005 but not configured. I was able to configure the
> > Reports server (from what I can tell) using the "Reporting Services
> > Configuration" tool).
> > Any idea as to what may still be causing the problem?
> > Thanks in advance for any help you can offer.
> > Mike Gorgone
> > Senior Software Engineer
> > PictureU Promotions
> The last response in this link might be helpful.http://www.sqlreportingservices.net/Ask/1730.aspx
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Hi Enrique,
Thanks for the link. I've seen some information along those same lines
but I can't set the IP Address property to "All Addresses" the IP
needs to be set to the specific address we have in there.
Is there any war around that?
Mike
I'm experiencing the error referenced in the following link to MS
Support
http://support.microsoft.com/Default.aspx?kbid=922656
I implemented the workaround but I'm still getting the error. Actually
when I started I was receiving "error message 1" and then when I
updated my RSWebApplication.config file to use the fully qualified URL
using the IP Address that is assigned to the Default Web Site's "IP
Address" property.
My config file now looks like this...
<ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
The server is a Windows 2003 server and the Reporting Services was
installed with SQL2005 but not configured. I was able to configure the
Reports server (from what I can tell) using the "Reporting Services
Configuration" tool).
Any idea as to what may still be causing the problem?
Thanks in advance for any help you can offer.
Mike Gorgone
Senior Software Engineer
PictureU PromotionsOn Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
> Hi All,
> I'm experiencing the error referenced in the following link to MS
> Support
> http://support.microsoft.com/Default.aspx?kbid=922656
> I implemented the workaround but I'm still getting the error. Actually
> when I started I was receiving "error message 1" and then when I
> updated my RSWebApplication.config file to use the fully qualified URL
> using the IP Address that is assigned to the Default Web Site's "IP
> Address" property.
> My config file now looks like this...
> <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> The server is a Windows 2003 server and the Reporting Services was
> installed with SQL2005 but not configured. I was able to configure the
> Reports server (from what I can tell) using the "Reporting Services
> Configuration" tool).
> Any idea as to what may still be causing the problem?
> Thanks in advance for any help you can offer.
> Mike Gorgone
> Senior Software Engineer
> PictureU Promotions
The last response in this link might be helpful.
http://www.sqlreportingservices.net/Ask/1730.aspx
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 21, 9:55 pm, EMartinez <emartinez...@.gmail.com> wrote:
> On Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
>
> > Hi All,
> > I'm experiencing the error referenced in the following link to MS
> > Support
> >http://support.microsoft.com/Default.aspx?kbid=922656
> > I implemented the workaround but I'm still getting the error. Actually
> > when I started I was receiving "error message 1" and then when I
> > updated my RSWebApplication.config file to use the fully qualified URL
> > using the IP Address that is assigned to the Default Web Site's "IP
> > Address" property.
> > My config file now looks like this...
> > <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > The server is a Windows 2003 server and the Reporting Services was
> > installed with SQL2005 but not configured. I was able to configure the
> > Reports server (from what I can tell) using the "Reporting Services
> > Configuration" tool).
> > Any idea as to what may still be causing the problem?
> > Thanks in advance for any help you can offer.
> > Mike Gorgone
> > Senior Software Engineer
> > PictureU Promotions
> The last response in this link might be helpful.http://www.sqlreportingservices.net/Ask/1730.aspx
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Hi Enrique,
Thanks for the link. I've seen some information along those same lines
but I can't set the IP Address property to "All Addresses" the IP
needs to be set to the specific address we have in there.
Is there any war around that?
Mike
cannot connect to the local instance
I have SQL server 2000 installed on my machine,
Under the "SQL Server Group" , if I click on the local insatnce (computerNam
e\NETSDK(window NT)) , I get the following error:
"The SQL server \\computerName\NETSDK is not known to be running, are you s
ure you wish to connect"
if I click yes, I get this second error message:
"A connection could not be established to computername/NETSDK.
Reason: SQL server does not exist or access denied.
ConnectionOpen(Connect())...
Please verify SQL Server is running and check your SQL Server registration p
roperties..."
when I check the registration, nothing look unusual for me.
thanks for helpYou didn't indicate whether you verified that the MSSQLServer service was
running. If so, are you using windows authentication or SQL authentication?
If you are using Windows authentication, try the sa account (assuming you
know/remember the password and that the server is in mixed mode). If you
get in using sa, check to be sure that you haven't removed the
builtin\administrators login without also adding your own. People tend to
forget this and get themselves locked out...
"tony" <myemail@.mail.com> wrote in message
news:2C272FD6-7C9E-441D-9AB7-DE70AC17946F@.microsoft.com...
> I have SQL server 2000 installed on my machine,
> Under the "SQL Server Group" , if I click on the local insatnce
(computerName\NETSDK(window NT)) , I get the following error:
> "The SQL server \\computerName\NETSDK is not known to be running, are you
sure you wish to connect"
> if I click yes, I get this second error message:
> "A connection could not be established to computername/NETSDK.
> Reason: SQL server does not exist or access denied.
> ConnectionOpen(Connect())...
> Please verify SQL Server is running and check your SQL Server registration
properties..."
> when I check the registration, nothing look unusual for me.
> thanks for help
>|||Hi Tony,
Thank you for using the newsgroup and thanks for Don's reply.
Don have pointed out some place you should check first and here I just want
to add some more information for your reference. You could look at this
following article:
INF: Potential Causes of the "SQL Server Does Not Exist or Access Denied"
Error Message
http://support.microsoft.com/?id=328306
Hope this help. If you still have questions, please feel free to post
message here and we are glad to help.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||the problem occured while backing up a database, the backup failed and I los
t connection to my local instance.
SQL server(as interface) is running fine on my machine and I can connect to
other remote server but not to the local one.
when I try to register the local one (under 'SQL Server Group') , I get an e
rror message saying that 'SQL Server does not exist or .....)
when I check the service, SQLServer service does not have even an entry an
d I couldn't locate it as a service.
I uninstalled SQL server (client tool) and I can still run the client on my
machine as if I didn't uninstall it, but with no connection to the local one
.
I installed it again and still getting the same error message.
The service does not exist, and SQL server is installed, how can that happen
s ?
thank you again.|||how can I add MSSQLServer as a service.
SQL server is running but does not have entry under the Service node.|||Hi Tony,
Thank you for your update.
It is a little strange now. Do you mean that after un-install the SQL
Server, and then in the Services Snap-in in the MMC, you cannot see the
SQL Server Service but your application could still connect to it? When a
SQL Server is running well on you computer, it should have the service
configured on your computer, no matter it is started or stopped.
I would like to narrow down the problem step-by-step
1) Please go to the command prompt ( 'Start'->'Run', then type in 'cmd' and
press Enter), then type 'net start', could you get any service of SQL
Server? It could be
MSSQLSERVER or MSSQL$<instance_name>.
2) If no, type in 'net start MSSQLSERVER, what's the message you get?
Note: For other SQL Server instance, type in 'net start
MSSQL$<The_Instance_Name>'
3) If it said
The MSSQLSERVER service is starting......
The MSSQLSERVER service was started successfully.
OR
The requested service has already been started.
Then you could be sure that the SQL Server is installed on your computer.
Then, please use the Enterprise Manager to register it.
Hope this helps.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Baisong,
Thank you for yall your help.
I reinstalled SQL server (client) again in order to see if it is going to ap
pear in the " Services Snap-in in the MMC",
and it INSTALLED SUCCEFULLY (as the install said) , and I run it, through
"Entreprise Manager", and I could connect to other remote sql servers, but w
hen I tried to register the local instance, I get a message :"SQL server doe
s not exist or..."
then I checked the Services Snap-in in the MMC, but still cannot see it or s
ee any SQL service at all.
Then I followed your instruction excatly:
1) when typing : "net start" , I can see all services except anything for SQ
L or MSSQL or .......
2) when typing : "net start MSSQLSERVER" , that's what I got: "The service
name is invalid"
After done all that, I create a shortcut for "Entreprise Manager" on the des
ktop, then I uninstalled SQL server again.
1) Now I cannot see "Microsoft SQL Sever" entry under start -> Programs ->
Microsoft Sql server anymore,
but the shortcut to it still exist on my desktop, and when I double click it
, it run normally as I didn't uninstall it, and I still
can run queries and connect to other remote servers except the local one, th
en I followed you instruction again, and got
the same message as I got before the uninstall; (nothing for MSSQL.... and
"The service name is inavlid").
Is there anyway to add MSSQLServer as a service in the Services Snap-in in t
he MMC manually ?
Thank you again|||Hi Tony,
Thank you for your update.
From your informtion, it seems you do not installed the SQL Server service
on you machine, just the SQL Server management tools such as the Enterprise
Manager or Query Analyzer.
So, I recommend you to un-installed the tools again. Then check your
Operating System and choose the right edition of SQL Server. Please refer
to the following article:
Operating Systems Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_ts_7eur.asp
Then, please re-intall the proper SQL Server 2000 by choosing 'Server and
Client Tools' selection during the intallation. After all the installation,
you will notice the SQL Server Service is in the Server snap-shot in the
MMC.
Hope this helps and if you still have question, please feel free to post
message here and I am glad to help.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Under the "SQL Server Group" , if I click on the local insatnce (computerNam
e\NETSDK(window NT)) , I get the following error:
"The SQL server \\computerName\NETSDK is not known to be running, are you s
ure you wish to connect"
if I click yes, I get this second error message:
"A connection could not be established to computername/NETSDK.
Reason: SQL server does not exist or access denied.
ConnectionOpen(Connect())...
Please verify SQL Server is running and check your SQL Server registration p
roperties..."
when I check the registration, nothing look unusual for me.
thanks for helpYou didn't indicate whether you verified that the MSSQLServer service was
running. If so, are you using windows authentication or SQL authentication?
If you are using Windows authentication, try the sa account (assuming you
know/remember the password and that the server is in mixed mode). If you
get in using sa, check to be sure that you haven't removed the
builtin\administrators login without also adding your own. People tend to
forget this and get themselves locked out...
"tony" <myemail@.mail.com> wrote in message
news:2C272FD6-7C9E-441D-9AB7-DE70AC17946F@.microsoft.com...
> I have SQL server 2000 installed on my machine,
> Under the "SQL Server Group" , if I click on the local insatnce
(computerName\NETSDK(window NT)) , I get the following error:
> "The SQL server \\computerName\NETSDK is not known to be running, are you
sure you wish to connect"
> if I click yes, I get this second error message:
> "A connection could not be established to computername/NETSDK.
> Reason: SQL server does not exist or access denied.
> ConnectionOpen(Connect())...
> Please verify SQL Server is running and check your SQL Server registration
properties..."
> when I check the registration, nothing look unusual for me.
> thanks for help
>|||Hi Tony,
Thank you for using the newsgroup and thanks for Don's reply.
Don have pointed out some place you should check first and here I just want
to add some more information for your reference. You could look at this
following article:
INF: Potential Causes of the "SQL Server Does Not Exist or Access Denied"
Error Message
http://support.microsoft.com/?id=328306
Hope this help. If you still have questions, please feel free to post
message here and we are glad to help.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||the problem occured while backing up a database, the backup failed and I los
t connection to my local instance.
SQL server(as interface) is running fine on my machine and I can connect to
other remote server but not to the local one.
when I try to register the local one (under 'SQL Server Group') , I get an e
rror message saying that 'SQL Server does not exist or .....)
when I check the service, SQLServer service does not have even an entry an
d I couldn't locate it as a service.
I uninstalled SQL server (client tool) and I can still run the client on my
machine as if I didn't uninstall it, but with no connection to the local one
.
I installed it again and still getting the same error message.
The service does not exist, and SQL server is installed, how can that happen
s ?
thank you again.|||how can I add MSSQLServer as a service.
SQL server is running but does not have entry under the Service node.|||Hi Tony,
Thank you for your update.
It is a little strange now. Do you mean that after un-install the SQL
Server, and then in the Services Snap-in in the MMC, you cannot see the
SQL Server Service but your application could still connect to it? When a
SQL Server is running well on you computer, it should have the service
configured on your computer, no matter it is started or stopped.
I would like to narrow down the problem step-by-step
1) Please go to the command prompt ( 'Start'->'Run', then type in 'cmd' and
press Enter), then type 'net start', could you get any service of SQL
Server? It could be
MSSQLSERVER or MSSQL$<instance_name>.
2) If no, type in 'net start MSSQLSERVER, what's the message you get?
Note: For other SQL Server instance, type in 'net start
MSSQL$<The_Instance_Name>'
3) If it said
The MSSQLSERVER service is starting......
The MSSQLSERVER service was started successfully.
OR
The requested service has already been started.
Then you could be sure that the SQL Server is installed on your computer.
Then, please use the Enterprise Manager to register it.
Hope this helps.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Baisong,
Thank you for yall your help.
I reinstalled SQL server (client) again in order to see if it is going to ap
pear in the " Services Snap-in in the MMC",
and it INSTALLED SUCCEFULLY (as the install said) , and I run it, through
"Entreprise Manager", and I could connect to other remote sql servers, but w
hen I tried to register the local instance, I get a message :"SQL server doe
s not exist or..."
then I checked the Services Snap-in in the MMC, but still cannot see it or s
ee any SQL service at all.
Then I followed your instruction excatly:
1) when typing : "net start" , I can see all services except anything for SQ
L or MSSQL or .......
2) when typing : "net start MSSQLSERVER" , that's what I got: "The service
name is invalid"
After done all that, I create a shortcut for "Entreprise Manager" on the des
ktop, then I uninstalled SQL server again.
1) Now I cannot see "Microsoft SQL Sever" entry under start -> Programs ->
Microsoft Sql server anymore,
but the shortcut to it still exist on my desktop, and when I double click it
, it run normally as I didn't uninstall it, and I still
can run queries and connect to other remote servers except the local one, th
en I followed you instruction again, and got
the same message as I got before the uninstall; (nothing for MSSQL.... and
"The service name is inavlid").
Is there anyway to add MSSQLServer as a service in the Services Snap-in in t
he MMC manually ?
Thank you again|||Hi Tony,
Thank you for your update.
From your informtion, it seems you do not installed the SQL Server service
on you machine, just the SQL Server management tools such as the Enterprise
Manager or Query Analyzer.
So, I recommend you to un-installed the tools again. Then check your
Operating System and choose the right edition of SQL Server. Please refer
to the following article:
Operating Systems Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_ts_7eur.asp
Then, please re-intall the proper SQL Server 2000 by choosing 'Server and
Client Tools' selection during the intallation. After all the installation,
you will notice the SQL Server Service is in the Server snap-shot in the
MMC.
Hope this helps and if you still have question, please feel free to post
message here and I am glad to help.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Subscribe to:
Posts (Atom)