Cannot restore database: 2012

Thursday, March 29, 2012

Can't connect from a vista client to SQL 2005 box,other machines work fine

Hey. I've a windows vista machine which can't connect to SQL 2005 box. Other machines which are lower than vista work fine. Also, vista box can connect to other SQL 2005 instances but can't connect to only one instance. But, I can connect to the instance fine from my XP box. Also, it's not a permissions issue. This user is an SA and can connect form some other machine. SQL 2005 box is at 2047 version right now. And, the user is able to connect to some other boxes which are also at 2047. Please help. Thank you

Add the account sepcifically to the SQL Server. When you connect from Vista (because of the UAC) it strips out your group SID from local admins, so SQL Server doesn't know who you are, and that's probably what is causing your issue. Add the user's account by name to the box.

If this post answers your question, make sure you mark it "answered" so others can find it quickly.

Thanks -

Buck Woody
http://www.buckwoody.com

Can't connect as SA through ODBC manager...why?

Hi All,
I can connect to my MSDE server by logging in as SA from the command line
but not through the ODBC manager utility in windows. I need to setup system
DSNs for a few applications but can't because they require I use SQL
authentication. When I reach that step in the ODBC manager I type in SA and
the password and hit next I get a 18456 "login failed for sa" error. My
server is in mixed mode (I checked the registry), the domain admins group has
login privilages to MSDE, I have no firewall active on any NICs, and none of
my passwords contain a semicolon. I have no clue what I'm missing here. Can
some one point me in the right direction or link me to a good article on how
to setup system dsns through the command line?
Thanks,
Prikly Pete Peterson
MSDE can only be used as the source of the data. It's not licensed to host
Reporting Services (as we discuss in our Reporting Services
book --www.sqlreportingservices.net). Chapter 2 (freely downloadable from
the site) explains why.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"ComfortablySAD" <ComfortablySAD@.discussions.microsoft.com> wrote in message
news:32E686BF-63A6-4DFF-9A7D-A00E8B6CAE09@.microsoft.com...
> Hi All,
> I can connect to my MSDE server by logging in as SA from the command line
> but not through the ODBC manager utility in windows. I need to setup
> system
> DSNs for a few applications but can't because they require I use SQL
> authentication. When I reach that step in the ODBC manager I type in SA
> and
> the password and hit next I get a 18456 "login failed for sa" error. My
> server is in mixed mode (I checked the registry), the domain admins group
> has
> login privilages to MSDE, I have no firewall active on any NICs, and none
> of
> my passwords contain a semicolon. I have no clue what I'm missing here.
> Can
> some one point me in the right direction or link me to a good article on
> how
> to setup system dsns through the command line?
> Thanks,
> Prikly Pete Peterson
sql

Cant Connect anymore

Need help. I changed my TCP connect port for SQL2005 to port 9601.
(ON THE SERVER..went into SQL Config manager >
SQL 2005 Net Config / TCPIP Properties
Changed TCP Port to 9601
Changed TCP PORT for IP2 section to 9601 where ip is 127.0.0.1
Changed TCP for IPAll section to 9601
Dynamic TCP Port was unchanged and remained blank..
Under SQL Config Manager > SQL Native Client Network
Changed TCP PORT to 9601
--
On my laptop went to
SQL Server Config manager
Changed TCP Port to 9601
under SQL Native Client /
Client Protocols / TCPIP..
REBOOTED EVERYONE..
I have a vb.net app, tried to access SQL DB and it failed, so I added the
new port (9601) in the connect
string, and then it worked, so I know the server port was changed to 9601.
However, can no longer connect VIA SQL 2005 Management STUDIO, says
An error has occ while establich connect... TCP Provider error: No
connection could be
made.. target machine actively refused it. Error #10061).
The vb.net app works with new port, why doesn't SQL Management studio?
Changed back to 1433 and everything works again. I've got to change the
port,
How can I and get SQL Management studio to work with a non default port?
Tried the Management studio on another machine.. same error, although vb.net
app connects fine under new port. This is crazy..
The server has an internet Ip address and I am accesing it via .com name (
in the vb.net app too)
( I tried the straight IP address, didn't work either)
Thanks BUCI stumbled across the answer, if I change the default port, I HAVE to create
an alias name and use it in the login box instead of the servername itself..
BUC
<Buc> wrote in message news:%23rm9$GUSGHA.4600@.TK2MSFTNGP11.phx.gbl...
> Need help. I changed my TCP connect port for SQL2005 to port 9601.
> (ON THE SERVER..went into SQL Config manager >
> SQL 2005 Net Config / TCPIP Properties
> Changed TCP Port to 9601
> Changed TCP PORT for IP2 section to 9601 where ip is 127.0.0.1
> Changed TCP for IPAll section to 9601
> Dynamic TCP Port was unchanged and remained blank..
> Under SQL Config Manager > SQL Native Client Network
> Changed TCP PORT to 9601
> --
> On my laptop went to
> SQL Server Config manager
> Changed TCP Port to 9601
> under SQL Native Client /
> Client Protocols / TCPIP..
> REBOOTED EVERYONE..
> I have a vb.net app, tried to access SQL DB and it failed, so I added the
> new port (9601) in the connect
> string, and then it worked, so I know the server port was changed to 9601.
> However, can no longer connect VIA SQL 2005 Management STUDIO, says
> An error has occ while establich connect... TCP Provider error: No
> connection could be
> made.. target machine actively refused it. Error #10061).
> The vb.net app works with new port, why doesn't SQL Management studio?
> Changed back to 1433 and everything works again. I've got to change the
> port,
> How can I and get SQL Management studio to work with a non default port?
> Tried the Management studio on another machine.. same error, although
> vb.net app connects fine under new port. This is crazy..
> The server has an internet Ip address and I am accesing it via .com name
> ( in the vb.net app too)
> ( I tried the straight IP address, didn't work either)
> Thanks BUC
>|||Sounds like you don't have the sqlbrowser service running. The browser
service maps incoming requests to the port where the database is listening
so without the sqlbrowser service running, you have to specify the port in
the connect string.
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
<Buc> wrote in message news:OzOFXlUSGHA.524@.TK2MSFTNGP10.phx.gbl...
>I stumbled across the answer, if I change the default port, I HAVE to
>create an alias name and use it in the login box instead of the servername
>itself..
> BUC
> <Buc> wrote in message news:%23rm9$GUSGHA.4600@.TK2MSFTNGP11.phx.gbl...
>

Can't connect after Windows XP SP2

Has i reviewed here after Windows XP SP2, MSDE has some problems conecctiong
over a network.
I installed SP3a for MSDE 2000 but the problem persists.
I put a permission to sqlserver.exe but my access to it over a network (and
internet) is blocked.
How can i solve this problem?
thanks,
Goncalo Boleo
hi,
"john raub" <john_raub@.ascendrms.com> ha scritto nel messaggio
news:20c601c4bdd8$f28b0840$a601280a@.phx.gbl
> problem with a customer that installed a 3rd party
> firewall software. He has since uninstalled, but we still
> can't connect to the machine containing the MSDE server.
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012
to see if they can help
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Can't connect after changing IP address

After changing from DHCP network address to a static IP address I can
not connect to my local database using ".\MyDBS" notation, howver
"127.0.0.1\MyDBS" works. Also, both work after restarting the SQL
service.
I am using the query analyzer to test success or failure.
My event logs show nothing and my SQL logs show no errors.
Any ideas on how to debug this further or solve it altogether?
Thank youHi Arron,
Thank you for using the newsgroup and it is my pleasure to help you with
you issue.
From your information, after change the IP, in the Query Analyzer, you
could not connect to my local database using ".\MyDBS" while
"127.0.0.1\MyDBS" works. After you restart the SQL Server service, this
problem do not happen, right?
I want to go forward with some more information since I could not
re-produce this problem on my computer. Do you encouter any error message
when using ".\MYDBS" that indicating you cannot connect to the server? How
about using the '(local)'? If you do not restart the SQL Server service,
it will not connect to the server even after some time? If you connect from
another machine by Query Analyer, do you meet the same problem?
When a SQL Server is started, it will listen to the IP and the port of when
it is started. So, when you change the IP address, you should restart the
SQL Server service and then it will listen to the new IP address. For the
localhost and the 127.0.0.1 will be the local machine.
You could refer to the following article for the name resolution:
http://www.microsoft.com/technet/pr.../ewsa/ewsach08.
mspx#XSLTsection124121120120
Hope this helps. If you still have questions, please feel free to post
message here and I am glad to help.
Thanks.
Sincerely Yours
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 Aaron,
I am reviewing you post and since we have not heard from you for some time
in the newsgroup, I wonder if you got answer from my answer. For any
question, please post your 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.

Can't connect after change the security setting

Hi, Experts! I very new to SQL server. I made a stupid movement by mistakenl
y
change the security of property of local(windows NT) from log in using this
account to system account. After the machine restarted, i can't no longer
start up SQL server. When I click local (window NT) in enterprise manager it
says "a connection could not be established to local. Reason, SQL serer
doesn't exist or access denied". I think it is the change of security that
the access was denied. How should I resolve this problem' Thanks so much.Thats weird, did the SQLServer service start up ? Look in the Service
manager. The service account can be switched in here. if you changed
the authentication method you can set it back via the registry entry as
mentioned in here:
---
http://support.microsoft.com/defaul...b;EN-US;q285097
---
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
---
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSq
lServer\LoginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
-URL---
HTH, Jens Suessmeyer.|||Jens,
Thank you so very much for your reply. I changed the registry loginmode from
2 to 1 and it did not work; I tried to change from 1 to 0, it did not work
either. In the service, I was not able to start up MSSQLSERVER. I got this
message "MSSQL SERVER service on local computer started and then stopped.
Some services stop automatically if they have no work to do ...".
Thanks.
"Jens" wrote:

> Thats weird, did the SQLServer service start up ? Look in the Service
> manager. The service account can be switched in here. if you changed
> the authentication method you can set it back via the registry entry as
> mentioned in here:
> ---
> http://support.microsoft.com/defaul...b;EN-US;q285097
> ---
> INF: How to Change the Default Login Authentication Mode to SQL While
> Installing SQL Server 2000 Desktop Engine by Using Windows Installer
> ---
> <snip>
> Another way to change the security mode after installation is to stop
> SQL Server and set the appropriate registry key for your installation:
>
> Default instance:
> HKLM\Software\Microsoft\MSSqlserver\MSSq
lServer\LoginMode
>
> Named instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
> Name\MSSQLServer\LoginMode
>
> to 2 for mixed-mode or 1 for integrated. (Integrated is the default
> setup for the SQL Server 2000 Data Engine.)
> </snip>
>
> -URL---
>
> HTH, Jens Suessmeyer.
>|||Lokk in the event log to see why it failed, did you try to change the
service accoutn back to the original one in the service manager ?
Some error occured and you have to know which one, this information is
presented in the event log.
Jens Suessmeyer.|||Thank you Jens. You saved me. I was panic about it. It is the evaluation
period expired. We have license now. How can I update the license without
losing the data? If not doable it is ok too. Thanks. whew...
"Jens" wrote:

> Lokk in the event log to see why it failed, did you try to change the
> service accoutn back to the original one in the service manager ?
> Some error occured and you have to know which one, this information is
> presented in the event log.
> Jens Suessmeyer.
>|||http://support.microsoft.com/defaul...kb;en-us;281574
HTH, Jens Suessmeyer.|||Thank you so very much Jens. You are very helpful!!
"jsuessmeyer@.web.de" wrote:

> http://support.microsoft.com/defaul...kb;en-us;281574
> HTH, Jens Suessmeyer.
>

Can't connect after change the security setting

Hi, Experts! I very new to SQL server. I made a stupid movement by mistakenly
change the security of property of local(windows NT) from log in using this
account to system account. After the machine restarted, i can't no longer
start up SQL server. When I click local (window NT) in enterprise manager it
says "a connection could not be established to local. Reason, SQL serer
doesn't exist or access denied". I think it is the change of security that
the access was denied. How should I resolve this problem? Thanks so much.
Thats weird, did the SQLServer service start up ? Look in the Service
manager. The service account can be switched in here. if you changed
the authentication method you can set it back via the registry entry as
mentioned in here:
http://support.microsoft.com/default...;EN-US;q285097
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
-URL---
HTH, Jens Suessmeyer.
|||Jens,
Thank you so very much for your reply. I changed the registry loginmode from
2 to 1 and it did not work; I tried to change from 1 to 0, it did not work
either. In the service, I was not able to start up MSSQLSERVER. I got this
message "MSSQL SERVER service on local computer started and then stopped.
Some services stop automatically if they have no work to do ...".
Thanks.
"Jens" wrote:

> Thats weird, did the SQLServer service start up ? Look in the Service
> manager. The service account can be switched in here. if you changed
> the authentication method you can set it back via the registry entry as
> mentioned in here:
> http://support.microsoft.com/default...;EN-US;q285097
> INF: How to Change the Default Login Authentication Mode to SQL While
> Installing SQL Server 2000 Desktop Engine by Using Windows Installer
> <snip>
> Another way to change the security mode after installation is to stop
> SQL Server and set the appropriate registry key for your installation:
>
> Default instance:
> HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\Lo ginMode
>
> Named instance:
> HKLM\Software\Microsoft\Microsoft SQL Server\Instance
> Name\MSSQLServer\LoginMode
>
> to 2 for mixed-mode or 1 for integrated. (Integrated is the default
> setup for the SQL Server 2000 Data Engine.)
> </snip>
>
> -URL---
>
> HTH, Jens Suessmeyer.
>
|||Lokk in the event log to see why it failed, did you try to change the
service accoutn back to the original one in the service manager ?
Some error occured and you have to know which one, this information is
presented in the event log.
Jens Suessmeyer.
|||Thank you Jens. You saved me. I was panic about it. It is the evaluation
period expired. We have license now. How can I update the license without
losing the data? If not doable it is ok too. Thanks. whew...
"Jens" wrote:

> Lokk in the event log to see why it failed, did you try to change the
> service accoutn back to the original one in the service manager ?
> Some error occured and you have to know which one, this information is
> presented in the event log.
> Jens Suessmeyer.
>
|||http://support.microsoft.com/default...b;en-us;281574
HTH, Jens Suessmeyer.
|||Thank you so very much Jens. You are very helpful!!
"jsuessmeyer@.web.de" wrote:

> http://support.microsoft.com/default...b;en-us;281574
> HTH, Jens Suessmeyer.
>
sql

can't connect 2005 reporting server...need help

Can't connect 2005 reporting server

We installed sql 2005 server and reporting services (standard edition) on
window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
admin and got error when i try to connect report server:
Cannot execute a program. The command being executed was
"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
@."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
execute a program. The command being executed was
"C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
@."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
anyone knows about this and thanks alot for a help
Karen,On Apr 27, 2:24 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
wrote:
> We installed sql 2005 server and reporting services (standard edition) on
> window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> admin and got error when i try to connect report server:
> Cannot execute a program. The command being executed was
> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information about
> the error and where it originated in the code.
> Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> execute a program. The command being executed was
> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> anyone knows about this and thanks alot for a help
> Karen,
Please refer to my previous post at:
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9efeaacdc0875e6d/7ce06f2ec8a78f36#7ce06f2ec8a78f36
Regards,
Enrique Martinez
Sr. Software Consultant|||Hi Enrique,
Thanks your replay and i do have .NET 2.0 installed. I feel like its
security issue.
What is security context of .NETservice account (NT
Authority\NetworkService)? and how do you confiure this account for web
service identity?
"EMartinez" wrote:
> On Apr 27, 2:24 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
> wrote:
> > We installed sql 2005 server and reporting services (standard edition) on
> > window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> > admin and got error when i try to connect report server:
> > Cannot execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> > execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> >
> > Source Error:
> > An unhandled exception was generated during the execution of the current web
> > request. Information regarding the origin and location of the exception can
> > be identified using the exception stack trace below.
> >
> > anyone knows about this and thanks alot for a help
> >
> > Karen,
>
> Please refer to my previous post at:
> http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9efeaacdc0875e6d/7ce06f2ec8a78f36#7ce06f2ec8a78f36
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Hi Enrique,
Thanks your replay and we do have .Net 2.0 installed. I feel like that this
problem related to security issue.
How do you configure your web service account (NT Authoriry/NetworkServices)
?
Karen,
"EMartinez" wrote:
> On Apr 27, 2:24 pm, Karen Chen <KarenC...@.discussions.microsoft.com>
> wrote:
> > We installed sql 2005 server and reporting services (standard edition) on
> > window2003 with sp1 and IIS 6.0 is running on it as well. I am in local
> > admin and got error when i try to connect report server:
> > Cannot execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Runtime.InteropServices.ExternalException: Cannot
> > execute a program. The command being executed was
> > "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
> > @."C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> > Files\reports$sql2005\47980326\bf0ad169\lzwjfwcj.cmdline".
> >
> > Source Error:
> > An unhandled exception was generated during the execution of the current web
> > request. Information regarding the origin and location of the exception can
> > be identified using the exception stack trace below.
> >
> > anyone knows about this and thanks alot for a help
> >
> > Karen,
>
> Please refer to my previous post at:
> http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/9efeaacdc0875e6d/7ce06f2ec8a78f36#7ce06f2ec8a78f36
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>

Cant Connect - SQL Server does not exist

Hi
We recently had a SQL Server 2K, Win2K box crash on us, and we had to
reinstall Windows.
Sql Server was also damaged (I think the registry got corrupted), and
so I reinstalled that too (couldnt start the Services). The server is
now up and running, but from any other computers (such as my desktop)
I can't connect to the server. If I open QA, for example, I can locate
the server name using the ... button (so it's there), but when I put
in a UID & PWD I get the "SQL Server does not exist or access denied"
error.
If I start QA on the server itself, though, and connect using the same
UID & PWD, there's no problem.
any ideas?
Thanks
SeanEnsure that both the server and client share a network protocol in common.
Try to ping the server name and IP from the client to ensure connectivity.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sean" <plugwalsh@.yahoo.com> wrote in message
news:3698af3c.0408100316.2596d560@.posting.google.com...
> Hi
> We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> reinstall Windows.
> Sql Server was also damaged (I think the registry got corrupted), and
> so I reinstalled that too (couldnt start the Services). The server is
> now up and running, but from any other computers (such as my desktop)
> I can't connect to the server. If I open QA, for example, I can locate
> the server name using the ... button (so it's there), but when I put
> in a UID & PWD I get the "SQL Server does not exist or access denied"
> error.
> If I start QA on the server itself, though, and connect using the same
> UID & PWD, there's no problem.
> any ideas?
> Thanks
> Sean|||Sorry - had the wrong IP in the hosts file... doh!
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<uIsqD7sfEHA.396@.
TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Ensure that both the server and client share a network protocol in common.
> Try to ping the server name and IP from the client to ensure connectivity.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Sean" <plugwalsh@.yahoo.com> wrote in message
> news:3698af3c.0408100316.2596d560@.posting.google.com...

Cant Connect - SQL Server does not exist

Hi
We recently had a SQL Server 2K, Win2K box crash on us, and we had to
reinstall Windows.
Sql Server was also damaged (I think the registry got corrupted), and
so I reinstalled that too (couldnt start the Services). The server is
now up and running, but from any other computers (such as my desktop)
I can't connect to the server. If I open QA, for example, I can locate
the server name using the ... button (so it's there), but when I put
in a UID & PWD I get the "SQL Server does not exist or access denied"
error.
If I start QA on the server itself, though, and connect using the same
UID & PWD, there's no problem.
any ideas?
Thanks
Sean
Ensure that both the server and client share a network protocol in common.
Try to ping the server name and IP from the client to ensure connectivity.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sean" <plugwalsh@.yahoo.com> wrote in message
news:3698af3c.0408100316.2596d560@.posting.google.c om...
> Hi
> We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> reinstall Windows.
> Sql Server was also damaged (I think the registry got corrupted), and
> so I reinstalled that too (couldnt start the Services). The server is
> now up and running, but from any other computers (such as my desktop)
> I can't connect to the server. If I open QA, for example, I can locate
> the server name using the ... button (so it's there), but when I put
> in a UID & PWD I get the "SQL Server does not exist or access denied"
> error.
> If I start QA on the server itself, though, and connect using the same
> UID & PWD, there's no problem.
> any ideas?
> Thanks
> Sean
|||Sorry - had the wrong IP in the hosts file... doh!
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<uIsqD7sfEHA.396@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Ensure that both the server and client share a network protocol in common.
> Try to ping the server name and IP from the client to ensure connectivity.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Sean" <plugwalsh@.yahoo.com> wrote in message
> news:3698af3c.0408100316.2596d560@.posting.google.c om...

Cant Connect - SQL Server does not exist

Hi
We recently had a SQL Server 2K, Win2K box crash on us, and we had to
reinstall Windows.
Sql Server was also damaged (I think the registry got corrupted), and
so I reinstalled that too (couldnt start the Services). The server is
now up and running, but from any other computers (such as my desktop)
I can't connect to the server. If I open QA, for example, I can locate
the server name using the ... button (so it's there), but when I put
in a UID & PWD I get the "SQL Server does not exist or access denied"
error.
If I start QA on the server itself, though, and connect using the same
UID & PWD, there's no problem.
any ideas?
Thanks
SeanEnsure that both the server and client share a network protocol in common.
Try to ping the server name and IP from the client to ensure connectivity.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sean" <plugwalsh@.yahoo.com> wrote in message
news:3698af3c.0408100316.2596d560@.posting.google.com...
> Hi
> We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> reinstall Windows.
> Sql Server was also damaged (I think the registry got corrupted), and
> so I reinstalled that too (couldnt start the Services). The server is
> now up and running, but from any other computers (such as my desktop)
> I can't connect to the server. If I open QA, for example, I can locate
> the server name using the ... button (so it's there), but when I put
> in a UID & PWD I get the "SQL Server does not exist or access denied"
> error.
> If I start QA on the server itself, though, and connect using the same
> UID & PWD, there's no problem.
> any ideas?
> Thanks
> Sean|||Sorry - had the wrong IP in the hosts file... doh!
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message news:<uIsqD7sfEHA.396@.TK2MSFTNGP12.phx.gbl>...
> Ensure that both the server and client share a network protocol in common.
> Try to ping the server name and IP from the client to ensure connectivity.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Sean" <plugwalsh@.yahoo.com> wrote in message
> news:3698af3c.0408100316.2596d560@.posting.google.com...
> > Hi
> >
> > We recently had a SQL Server 2K, Win2K box crash on us, and we had to
> > reinstall Windows.
> >
> > Sql Server was also damaged (I think the registry got corrupted), and
> > so I reinstalled that too (couldnt start the Services). The server is
> > now up and running, but from any other computers (such as my desktop)
> > I can't connect to the server. If I open QA, for example, I can locate
> > the server name using the ... button (so it's there), but when I put
> > in a UID & PWD I get the "SQL Server does not exist or access denied"
> > error.
> >
> > If I start QA on the server itself, though, and connect using the same
> > UID & PWD, there's no problem.
> >
> > any ideas?
> > Thanks
> > Sean

can't connect

hey all,
i'm trying, unsuccessfully, to connect to my msde(sp4) which is on another
pc (has xp sp2) wirelessly thru a virtual pc which has Enterprise Manager on
it.
My results have been a moving target. One day i can connect via my virtual
pc with enterprise manager and the next day i can connect via my host pc with
a plain UDL link but never both.
i don't understand the inconsistency in connecting to the pc that has msde
on it. i've successfully mapped a drive to it. the msde machine's windows
firewall is on accepting file and print sharing (port 445 enabled). i have a
4-port wireless router and as i mentioned before i'm trying to connect
wirelessly.
am i missing something here?
thanks,
rodchar
how do i verify my network is working properly?
"Andrea Montanari" wrote:

> hi Rodchar,
> rodchar wrote:
> you do not need to have file system shares to connect to.. you only have to
> worry about "general" network connectivity across the involved machines and
> that the target server accepts remote connections (as it already should, as
> you get some sort of connectivity)...
> verify your network is poroperly working..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>

Can't Connect

I have just installed Sql server 2005 on my Win XP Pro machine.
When I go into the sql server management studio, there is only
one entry under the "database engine" entry in the registered servers'
panel on the left. It is MyServerName\SQLEXPRESS.
When I click on it and then select connect, either new query
or object explorer, I get one of the following errors.
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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 )
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (Provider : Named Pipes Provider, error 40 - Could not open
a connection
to sql server.
I have looked all over the internet, but couldn't find anything that
would help.
I went into the sql server configuration manger, and enabled the name
pipes and rebooted.
I didn't work. In the sql service configuration manager I have five
services that are status of
running and startup mode of automatic. However they are not for the
SQLExpress server.
They are for another sql server name, that I put in for the server name
when I installed
sql server 2005. I thought that would be the server name.
There are two entries under sql server 2005 network configuration
Protocals for SQLEXPRESS and
Protocals for Myotherservername
How can I connect.
Why do I have two instances are those instances of servers,
I thought that there was only server.
What do I do?
Thanks in Advance,
Laurence
I suggest starting with my blog entry on connecting. Just search
www.betav.com/blog/billva. There are several relevant articles there.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
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)
------
"Larry" <NoSpam@.Something.com> wrote in message
news:e5O9nLU3HHA.5316@.TK2MSFTNGP04.phx.gbl...
>I have just installed Sql server 2005 on my Win XP Pro machine.
> When I go into the sql server management studio, there is only
> one entry under the "database engine" entry in the registered servers'
> panel on the left. It is MyServerName\SQLEXPRESS.
> When I click on it and then select connect, either new query
> or object explorer, I get one of the following errors.
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the 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 )
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (Provider : Named Pipes Provider, error 40 - Could not open a
> connection
> to sql server.
> I have looked all over the internet, but couldn't find anything that would
> help.
> I went into the sql server configuration manger, and enabled the name
> pipes and rebooted.
> I didn't work. In the sql service configuration manager I have five
> services that are status of
> running and startup mode of automatic. However they are not for the
> SQLExpress server.
> They are for another sql server name, that I put in for the server name
> when I installed
> sql server 2005. I thought that would be the server name.
> There are two entries under sql server 2005 network configuration
> Protocals for SQLEXPRESS and
> Protocals for Myotherservername
>
> How can I connect.
> Why do I have two instances are those instances of servers,
> I thought that there was only server.
> What do I do?
> Thanks in Advance,
> Laurence
>
>
>
>
|||Thank You.
William Vaughn wrote:
> I suggest starting with my blog entry on connecting. Just search
> www.betav.com/blog/billva. There are several relevant articles there.
>
sql

Can't Connect

Win 2000, sqlServer 2000 Personal edition
Trying ot connect using .asp Vb Script
1. Sql server set to use Windows Authentication
2. Log onto Windows 2000 as Jim Bunton {no password)
3 Server 'Study' running ok
4. sql query analyser
i. "SELECT User_Name > dbo
ii. [using database NorthWind]
"SELECT * FROM Customers" > gives expected result
5. VB script
** BEGIN CODE connect.asp ***
<%
@. LANGUAGE="VBSCRIPT"
%>
<%
Option explicit
response.expires = 0
%>

<html>
<head>
<title></title>
</head>
<body>
<%
dim Cn, CnStr
Set Cn = Server.CreateObject("ADODB.Connection")
Cn.ConnectionTimeOut = 1
Cn.provider="sqloledb"
response.write "Conn Provider is " & Cn.provider
CnStr="Data Source=Study;Initial Catalog=Norhwind;User
Id=sa;Password=;"
' Tried all sorts of user id's and paswords
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
Bunton';Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
=dbo;Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
JimBunton;Password=;"
'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
='Study\Jim Bunton';Password=;"
%>
--
<%
response.write "Cnstr = " & CnStr
'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
Cn.open CnStr
%>
--
<%
response.write "The End - ran ok"
%>
</body>
</html>
**** END CODE *****
? what to do?
? am I missing something 'obvious' out ?
Jim Bunton
If you are using windows authentication (also known as a
trusted connection) to connect, you don't supply a user
name, password in the connection string. Instead, you
indicate this by using Integrated Security=SSPI
in your connection string.
You also want to make sure the database is correct. In your
examples, you want to make sure you use Northwind (you have
Norwind listed).
You can find sample connection strings using the SQL Server
OLE DB provider at:
http://www.carlprothman.net/Default...erForSQLServer
-Sue
On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:

>Win 2000, sqlServer 2000 Personal edition
>Trying ot connect using .asp Vb Script
>1. Sql server set to use Windows Authentication
>2. Log onto Windows 2000 as Jim Bunton {no password)
>3 Server 'Study' running ok
>4. sql query analyser
> i. "SELECT User_Name > dbo
> ii. [using database NorthWind]
> "SELECT * FROM Customers" > gives expected result
>5. VB script
>** BEGIN CODE connect.asp ***
><%
> @. LANGUAGE="VBSCRIPT"
>%>
><%
> Option explicit
> response.expires = 0
>%>
>
><html>
><head>
><title></title>
></head>
><body>
><%
> dim Cn, CnStr
> Set Cn = Server.CreateObject("ADODB.Connection")
> Cn.ConnectionTimeOut = 1
> Cn.provider="sqloledb"
> response.write "Conn Provider is " & Cn.provider
> CnStr="Data Source=Study;Initial Catalog=Norhwind;User
>Id=sa;Password=;"
> ' Tried all sorts of user id's and paswords
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
>Bunton';Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
>=dbo;Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
>JimBunton;Password=;"
> 'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
>='Study\Jim Bunton';Password=;"
>%>
>--
><%
> response.write "Cnstr = " & CnStr
> 'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
> Cn.open CnStr
>%>
>--
><%
> response.write "The End - ran ok"
>%>
></body>
></html>
>**** END CODE *****
>? what to do?
>? am I missing something 'obvious' out ?
|||Thanks for your clear response Sue.
Unfortunately I still have a problem:
The following works:-
<%
dim Cn, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
Cn.Provider = "sqloledb"
Cn.Properties("Data Source") = "Study\StudySQLServer"
Cn.Properties("Initial Catalog") = "NorthWind"
Cn.Properties("Connect Timeout") = "3"
Cn.Properties("User ID") = "sa"
Cn.Properties("Password") = "mypassword"
Cn.open
. . . code which displays Customer info
The folowing does NOT:-
<%
dim Cn, CnStr, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
CnStr="Provider=sqloledb;" & _
"Data Source=Study\StudySqlServer;" & _
"Initial Catalog=NorthWind;" & _
"Integrated Security=SSPI"
response.write "cnStr = " & cnStr
' response.end
Cn.open CnStr
It fails at Cn.open CnStr
Error Type:
(0x80040E4D)
/MyWebs/Connect_wAuth.asp, line 15
response.write "cnStr = " & cnStr gives:-
cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=NorthWind;Integrated Security=SSPI
In Query Analyser (login using Windows Authentification)
select user_Name() >> dbo
select * from Customers >> a list of customers
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5fl6r704knccn7jfun1kf4@.4ax.com...
> If you are using windows authentication (also known as a
> trusted connection) to connect, you don't supply a user
> name, password in the connection string. Instead, you
> indicate this by using Integrated Security=SSPI
> in your connection string.
> You also want to make sure the database is correct. In your
> examples, you want to make sure you use Northwind (you have
> Norwind listed).
> You can find sample connection strings using the SQL Server
> OLE DB provider at:
> http://www.carlprothman.net/Default...erForSQLServer
> -Sue
> On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
> <jBunton@.BlueYonder.co.uk> wrote:
>
|||Then it's likely the authentication settings on the IIS side
of it. Try adding the IUSR account as a login in SQL Server
with the appropriate permissions as needed for your code.
Also, turned on failed login audits in SQL Server and
restart the instance. That will help you track down what
login is failing.
-Sue
On Tue, 20 Sep 2005 10:17:50 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:
[vbcol=seagreen]
>Thanks for your clear response Sue.
>Unfortunately I still have a problem:
>The following works:-
><%
>dim Cn, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> Cn.Provider = "sqloledb"
> Cn.Properties("Data Source") = "Study\StudySQLServer"
> Cn.Properties("Initial Catalog") = "NorthWind"
> Cn.Properties("Connect Timeout") = "3"
> Cn.Properties("User ID") = "sa"
> Cn.Properties("Password") = "mypassword"
> Cn.open
> . . . code which displays Customer info
>The folowing does NOT:-
><%
>dim Cn, CnStr, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> CnStr="Provider=sqloledb;" & _
> "Data Source=Study\StudySqlServer;" & _
> "Initial Catalog=NorthWind;" & _
> "Integrated Security=SSPI"
> response.write "cnStr = " & cnStr
> ' response.end
> Cn.open CnStr
>It fails at Cn.open CnStr
>Error Type:
>(0x80040E4D)
>/MyWebs/Connect_wAuth.asp, line 15
>response.write "cnStr = " & cnStr gives:-
>cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=NorthWind;Integrated Security=SSPI
>In Query Analyser (login using Windows Authentification)
>select user_Name() >> dbo
>select * from Customers >> a list of customers
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5fl6r704knccn7jfun1kf4@.4ax.com...

Can't connect

I've installed Visual Studio 2005 (including SQL Express) on a XP Home
machine. I've currently problems to connect to the SQL-Server getting the
following error message
C:\Dokumente und Einstellungen\Robert>sqlcmd
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
I've allready
- enabled the Protocolls via the SQL Server Configuration Manager
- stopped the firewall
- tried it via Access, VS 2005 Server Explorer, ...
I get access to the database when I use SSEUTIL ! Using this tool it was
e.g. possible to attach/dettach a database.
Any idea whats wrong?
Are you in fact trying to connect remotely? If you are, you will need to
enable and start SQLBrowser also. If not, are you using .\sqlexpress as
your server name in the connection string?
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
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
> I've installed Visual Studio 2005 (including SQL Express) on a XP Home
> machine. I've currently problems to connect to the SQL-Server getting the
> following error message
> C:\Dokumente und Einstellungen\Robert>sqlcmd
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> I've allready
> - enabled the Protocolls via the SQL Server Configuration Manager
> - stopped the firewall
> - tried it via Access, VS 2005 Server Explorer, ...
> I get access to the database when I use SSEUTIL ! Using this tool it was
> e.g. possible to attach/dettach a database.
> Any idea whats wrong?
|||Hi Roger,
thank you very much. I missed the ".\sqlexpress". Adding this to the
connection string everything worked.
"Roger Wolter[MSFT]" wrote:

> Are you in fact trying to connect remotely? If you are, you will need to
> enable and start SQLBrowser also. If not, are you using .\sqlexpress as
> your server name in the connection string?
> --
> 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
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
>
>

Can't Connect

I can't connect to this new box via sql server 2000, every time I try to
register sql server to this new server, I get this message:" SQL Server does
not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
running on the new box when I connect via remote access to the box. How can
I connect? They also created a DNS, but still can't connect via sql server.
Thanks.
--
New SQL Server DBAWhat account or login are you using when you try to register sql? I'm
guessing you are trying to register the new SQL server to your Enterprise
Manager?
JD
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:910795E9-3EB7-4DD2-89D3-E2FBA95100E4@.microsoft.com...
>I can't connect to this new box via sql server 2000, every time I try to
> register sql server to this new server, I get this message:" SQL Server
> does
> not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
> running on the new box when I connect via remote access to the box. How
> can
> I connect? They also created a DNS, but still can't connect via sql
> server.
> Thanks.
> --
> New SQL Server DBA|||I am using the sa account. Yes i am using EM. Thanks.
--
New SQL Server DBA
"Joe D" wrote:

> What account or login are you using when you try to register sql? I'm
> guessing you are trying to register the new SQL server to your Enterprise
> Manager?
> JD
>
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:910795E9-3EB7-4DD2-89D3-E2FBA95100E4@.microsoft.com...
>
>

Can't Connect

I can't connect to this new box via sql server 2000, every time I try to
register sql server to this new server, I get this message:" SQL Server does
not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
running on the new box when I connect via remote access to the box. How can
I connect? They also created a DNS, but still can't connect via sql server.
Thanks.
New SQL Server DBA
What account or login are you using when you try to register sql? I'm
guessing you are trying to register the new SQL server to your Enterprise
Manager?
JD
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:910795E9-3EB7-4DD2-89D3-E2FBA95100E4@.microsoft.com...
>I can't connect to this new box via sql server 2000, every time I try to
> register sql server to this new server, I get this message:" SQL Server
> does
> not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
> running on the new box when I connect via remote access to the box. How
> can
> I connect? They also created a DNS, but still can't connect via sql
> server.
> Thanks.
> --
> New SQL Server DBA
|||I am using the sa account. Yes i am using EM. Thanks.
New SQL Server DBA
"Joe D" wrote:

> What account or login are you using when you try to register sql? I'm
> guessing you are trying to register the new SQL server to your Enterprise
> Manager?
> JD
>
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:910795E9-3EB7-4DD2-89D3-E2FBA95100E4@.microsoft.com...
>
>

Can't Connect

Win 2000, sqlServer 2000 Personal edition
Trying ot connect using .asp Vb Script
1. Sql server set to use Windows Authentication
2. Log onto Windows 2000 as Jim Bunton {no password)
3 Server 'Study' running ok
4. sql query analyser
i. "SELECT User_Name > dbo
ii. [using database NorthWind]
"SELECT * FROM Customers" > gives expected result
5. VB script
** BEGIN CODE connect.asp ***
<%
@. LANGUAGE="VBSCRIPT"
%>
<%
Option explicit
response.expires = 0
%>

<html>
<head>
<title></title>
</head>
<body>
<%
dim Cn, CnStr
Set Cn = Server.CreateObject("ADODB.Connection")
Cn.ConnectionTimeOut = 1
Cn.provider="sqloledb"
response.write "Conn Provider is " & Cn.provider
CnStr="Data Source=Study;Initial Catalog=Norhwind;User
Id=sa;Password=;"
' Tried all sorts of user id's and paswords
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
Bunton';Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
=dbo;Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
JimBunton;Password=;"
'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
='Study\Jim Bunton';Password=;"
%>
--
<%
response.write "Cnstr = " & CnStr
'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
Cn.open CnStr
%>
--
<%
response.write "The End - ran ok"
%>
</body>
</html>
**** END CODE *****
? what to do'
' am I missing something 'obvious' out ?
Jim BuntonIf you are using windows authentication (also known as a
trusted connection) to connect, you don't supply a user
name, password in the connection string. Instead, you
indicate this by using Integrated Security=SSPI
in your connection string.
You also want to make sure the database is correct. In your
examples, you want to make sure you use Northwind (you have
Norwind listed).
You can find sample connection strings using the SQL Server
OLE DB provider at:
http://www.carlprothman.net/Default...derForSQLServer
-Sue
On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:

>Win 2000, sqlServer 2000 Personal edition
>Trying ot connect using .asp Vb Script
>1. Sql server set to use Windows Authentication
>2. Log onto Windows 2000 as Jim Bunton {no password)
>3 Server 'Study' running ok
>4. sql query analyser
> i. "SELECT User_Name > dbo
> ii. [using database NorthWind]
> "SELECT * FROM Customers" > gives expected result
>5. VB script
>** BEGIN CODE connect.asp ***
><%
> @. LANGUAGE="VBSCRIPT"
>%>
><%
> Option explicit
> response.expires = 0
>%>
>
><html>
><head>
><title></title>
></head>
><body>
><%
> dim Cn, CnStr
> Set Cn = Server.CreateObject("ADODB.Connection")
> Cn.ConnectionTimeOut = 1
> Cn.provider="sqloledb"
> response.write "Conn Provider is " & Cn.provider
> CnStr="Data Source=Study;Initial Catalog=Norhwind;User
>Id=sa;Password=;"
> ' Tried all sorts of user id's and paswords
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id = 'Jim
>Bunton';Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
>=dbo;Password=;"
> 'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
>JimBunton;Password=;"
> 'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
>='Study\Jim Bunton';Password=;"
>%>
>--
><%
> response.write "Cnstr = " & CnStr
> 'ERROR ALWAYS OCCURS ON NEXT LINEon the next line
> Cn.open CnStr
>%>
>--
><%
> response.write "The End - ran ok"
>%>
></body>
></html>
>**** END CODE *****
>? what to do'
>' am I missing something 'obvious' out ?|||Thanks for your clear response Sue.
Unfortunately I still have a problem:
The following works:-
<%
dim Cn, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
Cn.Provider = "sqloledb"
Cn.Properties("Data Source") = "Study\StudySQLServer"
Cn.Properties("Initial Catalog") = "NorthWind"
Cn.Properties("Connect Timeout") = "3"
Cn.Properties("User ID") = "sa"
Cn.Properties("Password") = "mypassword"
Cn.open
. . . code which displays Customer info
The folowing does NOT:-
<%
dim Cn, CnStr, SqlStr,rsCustomers
Set Cn=Server.CreateObject("ADODB.Connection")
CnStr="Provider=sqloledb;" & _
"Data Source=Study\StudySqlServer;" & _
"Initial Catalog=NorthWind;" & _
"Integrated Security=SSPI"
response.write "cnStr = " & cnStr
' response.end
Cn.open CnStr
It fails at Cn.open CnStr
Error Type:
(0x80040E4D)
/MyWebs/Connect_wAuth.asp, line 15
response.write "cnStr = " & cnStr gives:-
cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=N
orthWind;Integrated Security=SSPI
In Query Analyser (login using Windows Authentification)
select user_Name() >> dbo
select * from Customers >> a list of customers
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5fl6r704knccn7jfun1
kf4@.4ax.com...
> If you are using windows authentication (also known as a
> trusted connection) to connect, you don't supply a user
> name, password in the connection string. Instead, you
> indicate this by using Integrated Security=SSPI
> in your connection string.
> You also want to make sure the database is correct. In your
> examples, you want to make sure you use Northwind (you have
> Norwind listed).
> You can find sample connection strings using the SQL Server
> OLE DB provider at:
> [url]http://www.carlprothman.net/Default.aspx?tabid=87#OLEDBProviderForSQLServer[/url
]
>
> -Sue
>
> On Mon, 19 Sep 2005 11:44:58 GMT, "Jim Bunton"
> <jBunton@.BlueYonder.co.uk> wrote:
>
>|||Then it's likely the authentication settings on the IIS side
of it. Try adding the IUSR account as a login in SQL Server
with the appropriate permissions as needed for your code.
Also, turned on failed login audits in SQL Server and
restart the instance. That will help you track down what
login is failing.
-Sue
On Tue, 20 Sep 2005 10:17:50 GMT, "Jim Bunton"
<jBunton@.BlueYonder.co.uk> wrote:
[vbcol=seagreen]
>Thanks for your clear response Sue.
>Unfortunately I still have a problem:
>The following works:-
><%
>dim Cn, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> Cn.Provider = "sqloledb"
> Cn.Properties("Data Source") = "Study\StudySQLServer"
> Cn.Properties("Initial Catalog") = "NorthWind"
> Cn.Properties("Connect Timeout") = "3"
> Cn.Properties("User ID") = "sa"
> Cn.Properties("Password") = "mypassword"
> Cn.open
> . . . code which displays Customer info
>The folowing does NOT:-
><%
>dim Cn, CnStr, SqlStr,rsCustomers
> Set Cn=Server.CreateObject("ADODB.Connection")
> CnStr="Provider=sqloledb;" & _
> "Data Source=Study\StudySqlServer;" & _
> "Initial Catalog=NorthWind;" & _
> "Integrated Security=SSPI"
> response.write "cnStr = " & cnStr
> ' response.end
> Cn.open CnStr
>It fails at Cn.open CnStr
>Error Type:
>(0x80040E4D)
>/MyWebs/Connect_wAuth.asp, line 15
>response.write "cnStr = " & cnStr gives:-
>cnStr = Provider=sqloledb;Data Source=Study\StudySqlServer;Initial Catalog=
NorthWind;Integrated Security=SSPI
>In Query Analyser (login using Windows Authentification)
>select user_Name() >> dbo
>select * from Customers >> a list of customers
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message news:5tuui1l8ku9a5f
l6r704knccn7jfun1kf4@.4ax.com...sql

Can't Connect

I have just installed Sql server 2005 on my Win XP Pro machine.
When I go into the sql server management studio, there is only
one entry under the "database engine" entry in the registered servers'
panel on the left. It is MyServerName\SQLEXPRESS.
When I click on it and then select connect, either new query
or object explorer, I get one of the following errors.
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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 )
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (Provider : Named Pipes Provider, error 40 - Could not open
a connection
to sql server.
I have looked all over the internet, but couldn't find anything that
would help.
I went into the sql server configuration manger, and enabled the name
pipes and rebooted.
I didn't work. In the sql service configuration manager I have five
services that are status of
running and startup mode of automatic. However they are not for the
SQLExpress server.
They are for another sql server name, that I put in for the server name
when I installed
sql server 2005. I thought that would be the server name.
There are two entries under sql server 2005 network configuration
Protocals for SQLEXPRESS and
Protocals for Myotherservername
How can I connect.
Why do I have two instances are those instances of servers,
I thought that there was only server.
What do I do?
Thanks in Advance,
LaurenceI suggest starting with my blog entry on connecting. Just search
www.betav.com/blog/billva. There are several relevant articles there.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
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)
----
---
"Larry" <NoSpam@.Something.com> wrote in message
news:e5O9nLU3HHA.5316@.TK2MSFTNGP04.phx.gbl...
>I have just installed Sql server 2005 on my Win XP Pro machine.
> When I go into the sql server management studio, there is only
> one entry under the "database engine" entry in the registered servers'
> panel on the left. It is MyServerName\SQLEXPRESS.
> When I click on it and then select connect, either new query
> or object explorer, I get one of the following errors.
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the 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 )
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (Provider : Named Pipes Provider, error 40 - Could not open a
> connection
> to sql server.
> I have looked all over the internet, but couldn't find anything that would
> help.
> I went into the sql server configuration manger, and enabled the name
> pipes and rebooted.
> I didn't work. In the sql service configuration manager I have five
> services that are status of
> running and startup mode of automatic. However they are not for the
> SQLExpress server.
> They are for another sql server name, that I put in for the server name
> when I installed
> sql server 2005. I thought that would be the server name.
> There are two entries under sql server 2005 network configuration
> Protocals for SQLEXPRESS and
> Protocals for Myotherservername
>
> How can I connect.
> Why do I have two instances are those instances of servers,
> I thought that there was only server.
> What do I do?
> Thanks in Advance,
> Laurence
>
>
>
>|||Thank You.
William Vaughn wrote:
> I suggest starting with my blog entry on connecting. Just search
> www.betav.com/blog/billva. There are several relevant articles there.
>

Can't connect

I've installed Visual Studio 2005 (including SQL Express) on a XP Home
machine. I've currently problems to connect to the SQL-Server getting the
following error message
C:\Dokumente und Einstellungen\Robert>sqlcmd
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
I've allready
- enabled the Protocolls via the SQL Server Configuration Manager
- stopped the firewall
- tried it via Access, VS 2005 Server Explorer, ...
I get access to the database when I use SSEUTIL ! Using this tool it was
e.g. possible to attach/dettach a database.
Any idea whats wrong?Are you in fact trying to connect remotely? If you are, you will need to
enable and start SQLBrowser also. If not, are you using .\sqlexpress as
your server name in the connection string?
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
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
> I've installed Visual Studio 2005 (including SQL Express) on a XP Home
> machine. I've currently problems to connect to the SQL-Server getting the
> following error message
> C:\Dokumente und Einstellungen\Robert>sqlcmd
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> I've allready
> - enabled the Protocolls via the SQL Server Configuration Manager
> - stopped the firewall
> - tried it via Access, VS 2005 Server Explorer, ...
> I get access to the database when I use SSEUTIL ! Using this tool it was
> e.g. possible to attach/dettach a database.
> Any idea whats wrong?|||Hi Roger,
thank you very much. I missed the ".\sqlexpress". Adding this to the
connection string everything worked.
"Roger Wolter[MSFT]" wrote:

> Are you in fact trying to connect remotely? If you are, you will need to
> enable and start SQLBrowser also. If not, are you using .\sqlexpress as
> your server name in the connection string?
> --
> 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
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
>
>

Can't Connect

I can't connect to this new box via sql server 2000, every time I try to
register sql server to this new server, I get this message:" SQL Server does
not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
running on the new box when I connect via remote access to the box. How can
I connect? They also created a DNS, but still can't connect via sql server.
Thanks.
--
New SQL Server DBAWhat account or login are you using when you try to register sql? I'm
guessing you are trying to register the new SQL server to your Enterprise
Manager?
JD
"Newbie" <Newbie@.discussions.microsoft.com> wrote in message
news:910795E9-3EB7-4DD2-89D3-E2FBA95100E4@.microsoft.com...
>I can't connect to this new box via sql server 2000, every time I try to
> register sql server to this new server, I get this message:" SQL Server
> does
> not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
> running on the new box when I connect via remote access to the box. How
> can
> I connect? They also created a DNS, but still can't connect via sql
> server.
> Thanks.
> --
> New SQL Server DBA|||I am using the sa account. Yes i am using EM. Thanks.
--
New SQL Server DBA
"Joe D" wrote:
> What account or login are you using when you try to register sql? I'm
> guessing you are trying to register the new SQL server to your Enterprise
> Manager?
> JD
>
> "Newbie" <Newbie@.discussions.microsoft.com> wrote in message
> news:910795E9-3EB7-4DD2-89D3-E2FBA95100E4@.microsoft.com...
> >I can't connect to this new box via sql server 2000, every time I try to
> > register sql server to this new server, I get this message:" SQL Server
> > does
> > not exist or access denied. ConnectionOpen. Connect. " SQL Server 2000 is
> > running on the new box when I connect via remote access to the box. How
> > can
> > I connect? They also created a DNS, but still can't connect via sql
> > server.
> > Thanks.
> > --
> > New SQL Server DBA
>
>

Cant connect

Win 2000, sqlServer 2000 Personal edition

Trying ot connect using .asp Vb Script

1. Sql server set to use Windows Authentication
2. Log onto Windows 2000 as Jim Bunton {no password)
3 Server 'Study' running ok
4. sql query analyser
i. "SELECT User_Name > dbo
ii. [using database NorthWind]
"SELECT * FROM Customers" > gives expected result

5. VB script
** BEGIN CODE connect.asp ***
<%
@. LANGUAGE="VBSCRIPT"
%
<%
Option explicit
response.expires = 0
%
<!-- #include file="adovbs.inc" --
<html>
<head>
<title></title>
</head>
<body>
<%
dim Cn, CnStr
Set Cn = Server.CreateObject("ADODB.Connection")
Cn.ConnectionTimeOut = 1
Cn.provider="sqloledb"
response.write "Conn Provider is " & Cn.provider
CnStr="Data Source=Study;Initial Catalog=Norhwind;User
Id=sa;Password=;"
' Tried all sorts of user id's and paswords
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
'Jim Bunton';Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id
=dbo;Password=;"
'CnStr="Data Source=Study;Initial Catalog=Norhwind;User Id =
JimBunton;Password=;"
'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
='Study\Jim Bunton';Password=;"
%>
----
<%
response.write "Cnstr = " & CnStr
'ERROR ALWAYS OCCURS ON NEXT LINE
Cn.open CnStr
'Error Type:
'(0x80004005)
'Unspecified error
'/myweb/mywebs/connect.asp, line 35
%>
----
<%
response.write "The End - ran ok"
%
</body
</html
**** END CODE *****

? what to do??
?? am I missing something 'obvious' out ?

Jim BuntonJim Bunton (jBunton@.BlueYonder.co.uk) writes:
> Win 2000, sqlServer 2000 Personal edition
> Trying ot connect using .asp Vb Script
> 1. Sql server set to use Windows Authentication
> 2. Log onto Windows 2000 as Jim Bunton {no password)

You're a brave man!

> 'CnStr="Data Source='Study';Initial Catalogue='Norhwind';User Id
>='Study\Jim Bunton';Password=;"

That is not likely to be correct. User Id and Password is for SQL
authentication, and SQL logins usually don't have \ in them. To login
with Windows authentication, specify "Integrated Security=SSPI", or
Trusted_connect=Yes.

And spell Northwind correctly. :-)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Cant Connect

I have installed SQL 2005 and just done a normal install. I have opened
Server Management Studio and try and connect but I get the error;
...this failure may be caused buy the face that under the default settings
SQL server does not allow remote connections (provider: TCP Provider, error:
0 - No connection could be made because the target machine actively refused
it) (Microsoft SQL Server, error 10061)
Now this error only happens when connecting to the DB engine, it works fine
connecting to analysis services. I have chosen Windows Auth and also
specifying my sql account with the password with is a member of the SQL
groups in the users container but still doesn't work. I am logged in as
Administrator but I get this error.
I have installed SQL before and it worked fine, then it messed up so I
installed SQLExpress now I installed 2005 beta again to play some more and
its done this.
I am using server 2003 SP1
Thanks for your help
ChrisFIXED :D
I just needed to manually create the MSSQL ODBC connector and its fine
learn something new everyday
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co.uk...
>I have installed SQL 2005 and just done a normal install. I have opened
>Server Management Studio and try and connect but I get the error;
> ...this failure may be caused buy the face that under the default settings
> SQL server does not allow remote connections (provider: TCP Provider,
> error: 0 - No connection could be made because the target machine actively
> refused it) (Microsoft SQL Server, error 10061)
> Now this error only happens when connecting to the DB engine, it works
> fine connecting to analysis services. I have chosen Windows Auth and also
> specifying my sql account with the password with is a member of the SQL
> groups in the users container but still doesn't work. I am logged in as
> Administrator but I get this error.
> I have installed SQL before and it worked fine, then it messed up so I
> installed SQLExpress now I installed 2005 beta again to play some more and
> its done this.
> I am using server 2003 SP1
> Thanks for your help
> Chris
>|||Going on from this however, if i wanted a desktop machine to connect, say,
Microsoft Access to my SQL database, do i need to create a MSSQL client
connection in the desktop ODBC?
Thanks
Chris
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:zsjQf.138255$DM.65219@.fe3.news.blueyonder.co.uk...
> FIXED :D
> I just needed to manually create the MSSQL ODBC connector and its fine
> learn something new everyday
> "kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
> news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co.uk...
>|||> Going on from this however, if i wanted a desktop machine to connect,
> say, Microsoft Access to my SQL database, do i need to create a MSSQL
> client connection in the desktop ODBC?
This is one of two possible choices.
The other one is to create an ADP and use OLE DB provider.
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution|||sorry to sound dumb, but could you dumb that down a bit please lol
thanks
chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bbff8c8132b72f2d7d6@.news.virgilio.it...
> This is one of two possible choices.
> The other one is to create an ADP and use OLE DB provider.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>|||> sorry to sound dumb, but could you dumb that down a bit please lol
Sorry for my poor english, but I was not able to welle translate your senten
ce.
May you explain better, please?
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution|||Can you explain what you mean by
"The other one is to create an ADP and use OLE DB provider."
I dont know what it is, also, would it be better to do it your way or my
way?
Thanks
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc088c813301ae47a36@.news.virgilio.it...
> Sorry for my poor english, but I was not able to welle translate your
> sentence. May you explain better, please?
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>|||> 2) ODBC driver
> 2) this method lets you use Access as simply as with any other MDB.
> Indeed, you have to define a system DSN in Windows Data Source, then
> you create an MDB and link tables from the ODBC source you defined.
> Yet, you are not able to exploit stored procedures, views, functions,
> and so on.
I forgot to say that using ODBC driver you cannot see relationships too.
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution|||Ah yes I do remember now, I think I have tried to use these befor.
Thanks for your assistance
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:hr2612lvbhhr1teiojvhb7aba44nb3huoe@.
4ax.com...
> ADP is an Access Data Project - an Access front end that
> uses SQL Server as the backend and doesn't involve Jet or
> mdb files. You can find more information on this in the
> Access help files - look for Access Project topics.
> -Sue
> On Sat, 11 Mar 2006 15:16:14 GMT, "kicken18"
> <chrisflyer@.blueyonder.co.uk> wrote:
>
>|||Thank you for the good help there, I can now go and test this.
Thank you for your time
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc418c813581ba41986@.news.virgilio.it...
> From Access you have two possibilities to use a MS SQL database.
> 1) OLE DB provider
> 2) ODBC driver
> 1) this is the best choice, in conjuntion to an Access Data Project.
> Microsoft created ADPs in order to interface SQL Server databases by
> Access via OLE DB provider and Jet Data Provider. ADPs connect to a SQL
> instance and let you see tables, stored procedures, views, functions, and
> so on.
> 2) this method lets you use Access as simply as with any other MDB.
> Indeed, you have to define a system DSN in Windows Data Source, then you
> create an MDB and link tables from the ODBC source you defined. Yet, you
> are not able to exploit stored procedures, views, functions, and so on.
> I suggest you to use the first method.
> Bye.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>sql

cant connect

i am devleoping an ASP.Net website now. i got a problem on connecting. when i try to connect (i manually made thew connection), it wont connect. the error is this:

System.Data.SqlClient.SqlException: Cannot open user default database. Login failed.
Login failed for user 'MANEC\Batman'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

I have other other webpage that uses sqlconenction. they connect fine but they are not manually created. i created their connection through the sqldatasource wizard. i am testing these pages using the built-in server of VWD-Express but when you test it on IIS it gets an error (this is my 2nd problem). i am totally confused.

i am thinking there is something missing in the connection that i manually created. I put the settings in the "web.config" file but it did no good.

can you give me instruction on how to properly connect from Web? PLS? i have no problem connecting when i am creating desktop applications (using C# & SQLExpress).

PLS HELP. pls.

Seems that the user has an orphaned database assigned to, try to set the deault database of the user to a valid one.

sp_defaultdb

Changes the default database for a Microsoft SQL Server login.

More information in the BOL.

HTH; jens Suessmeyer.

|||

thanks for the reply. i have solved this issue by setting sql authentication to mixed mode and assigned a username/password on the connection string. it connects now.

i can see that the connection is ok but when i am attemting to create a new table to the ASPNETDB.mdf, i get this error message:

System.Data.SqlClient.SqlException: Unable to open the physical file "D:\myDocs\Visual Studio 2005\WebSites\techPad\App_Data\ASPNETDB.MDF". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
Unable to open the physical file "D:\myDocs\Visual Studio 2005\WebSites\techPad\App_Data\ASPNETDB_log.ldf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
Cannot open user default database. Login failed.
Login failed for user 'xxx'.
File activation failure. The physical file name "D:\myDocs\Visual Studio 2005\WebSites\techPad\App_Data\ASPNETDB_log.ldf" may be incorrect.at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

PLS HELP.

|||OK, strange thing. Seems that you connected with the attachdbfile option a database, but connect with another connection to the sql server express attached database or vice versa. But you have to decide wheter you want to use the service of the direct attachdbfile way.

HTH, jens Suessmeyer.|||

Jens Suessmeyer wrote:
OK, strange thing. Seems that you connected with the attachdbfile option a database, but connect with another connection to the sql server express attached database or vice versa. But you have to decide wheter you want to use the service of the direct attachdbfile way.
HTH, jens Suessmeyer.

you are right. i attached ASPNETDB.net using attachdbfile. that is set on the web.config file.

|||

somehow i have resolved this issue but the problem keeps on coming after another.

from the suggestion of the people from www.asp.net ( http://forums.asp.net/1/904462/ShowPost.aspx#904462 ) here is what i got now:

error after disabling "Write" capability from ACL:
System.Data.SqlClient.SqlException: Failed to update database "C:\INETPUB\WWWROOT\TECHPAD\APP_DATA\ASPNETDB.MDF" because the database is read-only. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

error after ENABLING "Write" capability from ACL:
System.Data.SqlClient.SqlException: Cannot open user default database. Login failed. Login failed for user 'MANEC\ASPNET'. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

this makes me think its so hard to study VWD and SQLExpress for a newbie like me. when I run the webpages from the built-in webserver of VWD it may work fine but when on IIS it will not work (or vice-versa). so confusing. maybe bcoz im very new to this.

i find it hard to do all of these setups. i wanna learn this though. PLS HELP.

|||i posted the same issue to the other page here. pls help. pls check this out > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=68698&SiteID=1&PageID=1

Cant Connect

I have installed SQL 2005 and just done a normal install. I have opened
Server Management Studio and try and connect but I get the error;
...this failure may be caused buy the face that under the default settings
SQL server does not allow remote connections (provider: TCP Provider, error:
0 - No connection could be made because the target machine actively refused
it) (Microsoft SQL Server, error 10061)
Now this error only happens when connecting to the DB engine, it works fine
connecting to analysis services. I have chosen Windows Auth and also
specifying my sql account with the password with is a member of the SQL
groups in the users container but still doesn't work. I am logged in as
Administrator but I get this error.
I have installed SQL before and it worked fine, then it messed up so I
installed SQLExpress now I installed 2005 beta again to play some more and
its done this.
I am using server 2003 SP1
Thanks for your help
Chris
FIXED :D
I just needed to manually create the MSSQL ODBC connector and its fine
learn something new everyday
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co. uk...
>I have installed SQL 2005 and just done a normal install. I have opened
>Server Management Studio and try and connect but I get the error;
> ...this failure may be caused buy the face that under the default settings
> SQL server does not allow remote connections (provider: TCP Provider,
> error: 0 - No connection could be made because the target machine actively
> refused it) (Microsoft SQL Server, error 10061)
> Now this error only happens when connecting to the DB engine, it works
> fine connecting to analysis services. I have chosen Windows Auth and also
> specifying my sql account with the password with is a member of the SQL
> groups in the users container but still doesn't work. I am logged in as
> Administrator but I get this error.
> I have installed SQL before and it worked fine, then it messed up so I
> installed SQLExpress now I installed 2005 beta again to play some more and
> its done this.
> I am using server 2003 SP1
> Thanks for your help
> Chris
>
|||Going on from this however, if i wanted a desktop machine to connect, say,
Microsoft Access to my SQL database, do i need to create a MSSQL client
connection in the desktop ODBC?
Thanks
Chris
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:zsjQf.138255$DM.65219@.fe3.news.blueyonder.co. uk...
> FIXED :D
> I just needed to manually create the MSSQL ODBC connector and its fine
> learn something new everyday
> "kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
> news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co. uk...
>
|||> Going on from this however, if i wanted a desktop machine to connect,
> say, Microsoft Access to my SQL database, do i need to create a MSSQL
> client connection in the desktop ODBC?
This is one of two possible choices.
The other one is to create an ADP and use OLE DB provider.
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution
|||sorry to sound dumb, but could you dumb that down a bit please lol
thanks
chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bbff8c8132b72f2d7d6@.news.virgilio.it. ..
> This is one of two possible choices.
> The other one is to create an ADP and use OLE DB provider.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>
|||> sorry to sound dumb, but could you dumb that down a bit please lol
Sorry for my poor english, but I was not able to welle translate your sentence.
May you explain better, please?
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution
|||Can you explain what you mean by
"The other one is to create an ADP and use OLE DB provider."
I dont know what it is, also, would it be better to do it your way or my
way?
Thanks
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc088c813301ae47a36@.news.virgilio.it. ..
> Sorry for my poor english, but I was not able to welle translate your
> sentence. May you explain better, please?
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>
|||ADP is an Access Data Project - an Access front end that
uses SQL Server as the backend and doesn't involve Jet or
mdb files. You can find more information on this in the
Access help files - look for Access Project topics.
-Sue
On Sat, 11 Mar 2006 15:16:14 GMT, "kicken18"
<chrisflyer@.blueyonder.co.uk> wrote:

>Can you explain what you mean by
>"The other one is to create an ADP and use OLE DB provider."
>I dont know what it is, also, would it be better to do it your way or my
>way?
>Thanks
>Chris
>"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
>news:875ea355bc088c813301ae47a36@.news.virgilio.it ...
>
|||Ah yes I do remember now, I think I have tried to use these befor.
Thanks for your assistance
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:hr2612lvbhhr1teiojvhb7aba44nb3huoe@.4ax.com...
> ADP is an Access Data Project - an Access front end that
> uses SQL Server as the backend and doesn't involve Jet or
> mdb files. You can find more information on this in the
> Access help files - look for Access Project topics.
> -Sue
> On Sat, 11 Mar 2006 15:16:14 GMT, "kicken18"
> <chrisflyer@.blueyonder.co.uk> wrote:
>
|||Thank you for the good help there, I can now go and test this.
Thank you for your time
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc418c813581ba41986@.news.virgilio.it. ..
> From Access you have two possibilities to use a MS SQL database.
> 1) OLE DB provider
> 2) ODBC driver
> 1) this is the best choice, in conjuntion to an Access Data Project.
> Microsoft created ADPs in order to interface SQL Server databases by
> Access via OLE DB provider and Jet Data Provider. ADPs connect to a SQL
> instance and let you see tables, stored procedures, views, functions, and
> so on.
> 2) this method lets you use Access as simply as with any other MDB.
> Indeed, you have to define a system DSN in Windows Data Source, then you
> create an MDB and link tables from the ODBC source you defined. Yet, you
> are not able to exploit stored procedures, views, functions, and so on.
> I suggest you to use the first method.
> Bye.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>

Thursday, March 29, 2012

Can't connect from a vista client to SQL 2005 box,other machines work fine

Can't connect as SA through ODBC manager...why?

Cant Connect anymore

Can't connect after Windows XP SP2

Can't connect after changing IP address

Can't connect after change the security setting

Can't connect after change the security setting

can't connect 2005 reporting server...need help

Can't connect 2005 reporting server

Cant Connect - SQL Server does not exist

Cant Connect - SQL Server does not exist

Cant Connect - SQL Server does not exist

can't connect

Can't Connect

Can't Connect

Can't connect

Can't Connect

Can't Connect

Can't Connect

Can't Connect

Can't connect

Can't Connect

Cant connect

Cant Connect

cant connect

Cant Connect

Cannot restore database

Blog Archive

About Me