"Unable To Connect to SQL Server" from Crystal 8.0

Hi All,

I am using Crystal Report 8.0 to create report on MSDE sp3a , but when I try to make connection Natively :
More Data Source->MiCrosoft SQL Server-> [Dialog opens]
then I type the ServerName, UserID and Password.

System hangs for a while, then I get this error :
"Unable To Connect to Sql server MyServer"

BUT IF I create system DSN (ODBC) then create the report, it works.

Why can't I create report Natively on MSDE ??

Thank you very much for any help,
KristWhat are you typing for ServerName? Is this database on a base or named instance? Also, don't it ask you for the database name?|||Hi,
Thanks for your response.

>What are you typing for ServerName?
I type 'XTANTO', it is my computer name, as I can see on service manager.

>Is this database on a base or named instance?
This is a base instance. FYI, this is a test computer, sp many 'install & uninstall' here, previously there is SQL Server personal edition there, but I already uninstalled it.
After that I install 'Client Connectivity only', and there is No way I can uninstall it. Then I install MSDE SP3a. and I get the error.
Does this give us any clue ?

>Also, don't it ask you for the database name?
Only after I type ServerName, UserID and Password correctly.
In this case, it doesn't give me list of database to choose because its error "Unable To Connect to SQL Server"

My last try will be reinstall win 98.
Do you think that will help ?

Thank you for your help,
Krist|||Go to Control Panel/Administrative Tools/Services. There should be a service that starts with MSSQL. Is it started? What is the full name of the service (or all the services that start with MSSQL)?|||Hi,

I am on Win98, there is NO services on control panel.
What else should I try ?

Thank you,
Krist|||Actually, here's a better question. Why are you running this on a Windows 98 machine??? Do a search for SQLScan on http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&displaylang=en

Run that on your machine. See what it says the name of the instance is.|||Hi Derrick,
Thanks for keep on helping..

>Actually, here's a better question. Why are you running this on a Windows >98 machine???
We are software developer company, we want to reach as wide market as possible, we want to keep on supporting windows 98.

The docs said Windows 98 is supported. Is there any known issue of MSDE 2000 on WIn 98 ?

Thank you,
Krist|||No that I know of. Did you run that tool on your computer?

"The process could not connect to Distributor"

Hi, i have the following problem:
i have a publisher and a subscriber in the same sql server 2005 machine. All
the process (the Log Reader Agent and the Snapshot Agent) works fine. Even
the snapshot files are being created in the UNC path (\\Desa5el1\Paso), but
when attempt to run synchronization, the Replication Monitor show me an error
in the Subscription. When i see the details of the error, i see the following:
Error messages:
The process could not read file
'\\Desa5el1\Paso\unc\DESA5EL1$CASCABEL_MC_AREASQL_ PUB_MC_AREASQL_PRUEBA\20070719170351\prueba_2.pre'
due to OS error 5. (Source: MSSQL_REPL, Error number: MSSQL_REPL20024)
Get help: http://help/MSSQL_REPL20024
The account under which the agent runs is db_owner (is an sql account, not
an Windows account) and member of the Publication Access List. I think maybe
the problem it is in this:
"Have read permissions on the snapshot share."
Could someone explain me this point? i need to configure some thing extra?
some permissions to the unc path?
I really appreciate any help.
Thanks in advance
Locate your snapshot share. Do that by issue the following on your
distributor
sp_helpdistributor
The name of your snapshot share should be in the directory column.
Also on your publisher in your publication database do this
sp_helppublication 'pubs' -- where pubs is your publication name
Note the value for alt_snapshot_folder column. If this value is null your
snapshot share is the value for the directory column returned by
sp_helpdistributor. If it is not null the snapshot share is in the
alt_snapshot_folder column.
Using file explorer navigate to this folder and right click on it, select
sharing and security and then make sure that the account which the sql
server agent account runs under has read and list files and folders rights
on this folder. The share permissions are by default always read.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"byteman" <byteman@.discussions.microsoft.com> wrote in message
news:9E69C2AD-9AA6-4B12-8B1A-B118123E9F3D@.microsoft.com...
> Hi, i have the following problem:
> i have a publisher and a subscriber in the same sql server 2005 machine.
> All
> the process (the Log Reader Agent and the Snapshot Agent) works fine. Even
> the snapshot files are being created in the UNC path (\\Desa5el1\Paso),
> but
> when attempt to run synchronization, the Replication Monitor show me an
> error
> in the Subscription. When i see the details of the error, i see the
> following:
> Error messages:
> The process could not read file
> '\\Desa5el1\Paso\unc\DESA5EL1$CASCABEL_MC_AREASQL_ PUB_MC_AREASQL_PRUEBA\20070719170351\prueba_2.pre'
> due to OS error 5. (Source: MSSQL_REPL, Error number: MSSQL_REPL20024)
> Get help: http://help/MSSQL_REPL20024
> The account under which the agent runs is db_owner (is an sql account, not
> an Windows account) and member of the Publication Access List. I think
> maybe
> the problem it is in this:
> "Have read permissions on the snapshot share."
> Could someone explain me this point? i need to configure some thing extra?
> some permissions to the unc path?
> I really appreciate any help.
> --
> Thanks in advance
>
|||Thanks for your help, Hilary.
I executed both sp_helpdistributor and sp_helppublication, and the snapshot
share that appears is correct (\\Desa5el1\Paso).
How can i set sharing and security rights for the account under which the
agent runs? The account exists only in sql server. I need to "register" this
account in somewhere out of sql server? How can i do that?
Thanks again.
"Hilary Cotter" wrote:

> Locate your snapshot share. Do that by issue the following on your
> distributor
> sp_helpdistributor
> The name of your snapshot share should be in the directory column.
> Also on your publisher in your publication database do this
> sp_helppublication 'pubs' -- where pubs is your publication name
> Note the value for alt_snapshot_folder column. If this value is null your
> snapshot share is the value for the directory column returned by
> sp_helpdistributor. If it is not null the snapshot share is in the
> alt_snapshot_folder column.
> Using file explorer navigate to this folder and right click on it, select
> sharing and security and then make sure that the account which the sql
> server agent account runs under has read and list files and folders rights
> on this folder. The share permissions are by default always read.
>
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "byteman" <byteman@.discussions.microsoft.com> wrote in message
> news:9E69C2AD-9AA6-4B12-8B1A-B118123E9F3D@.microsoft.com...
>
>

"Suddently" can't connect to sql server (SP security prob, maybe?)

Hi! I'm running sql server 2003 on a network for my small business; I'm
having probs connecting to the server from my desktop. What's odd is that
this prob sudently occured yesterday...I had been connecting before that
(like, for several years?) and now I can't hit the box thorugh either Query
Analyzer or Enterprise manager.
The server is online because I can map to it and see the directories. Also:
I have a notebook which still can see the SQL Server box with NO Problems!
Which begs the question: what changed over the weekend? I seem to remember
that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
these two computers recently. Are you aware of any security changes that may
have been slipped in on either the server or the client side to explain this?
I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
Thanks in advance for your help. I rally appreciate it!
Roger,

> I have a notebook which still can see the SQL Server box with NO Problems!
The box or the SQL Server i.e., the databases, tables and data. Can you
acesss the SQL Server by IP address? Does the OSQL utility work? What if
you try creating a DSN and 'test the connection' - just to rule out the SQL
tools as a possible cause? Have you tried restarting this client?
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> Hi! I'm running sql server 2003 on a network for my small business; I'm
> having probs connecting to the server from my desktop. What's odd is that
> this prob sudently occured yesterday...I had been connecting before that
> (like, for several years?) and now I can't hit the box thorugh either
> Query
> Analyzer or Enterprise manager.
> The server is online because I can map to it and see the directories.
> Also:
> I have a notebook which still can see the SQL Server box with NO Problems!
> Which begs the question: what changed over the weekend? I seem to remember
> that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> of
> these two computers recently. Are you aware of any security changes that
> may
> have been slipped in on either the server or the client side to explain
> this?
> I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> Thanks in advance for your help. I rally appreciate it!
|||Roger,
So if I read your e-mail correctly from your desktop you can login via
Query Analyzer or Enterprise Manager but from another box you can login
to the SQL Server box using another tool? Could there have been a
network change the happened on the weekend where you box got a new IP or
the network security changed?
If the SQL Server is up [you can login via another client or directly on
the box itself] then the problem has to be with your computer or network
permissions. You may check to see if your IP changed or perhaps they
access from your IP to the server was removed.
Shahryar
Roger Willcode wrote:

>Hi! I'm running sql server 2003 on a network for my small business; I'm
>having probs connecting to the server from my desktop. What's odd is that
>this prob sudently occured yesterday...I had been connecting before that
>(like, for several years?) and now I can't hit the box thorugh either Query
>Analyzer or Enterprise manager.
>The server is online because I can map to it and see the directories. Also:
>I have a notebook which still can see the SQL Server box with NO Problems!
>Which begs the question: what changed over the weekend? I seem to remember
>that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
>these two computers recently. Are you aware of any security changes that may
>have been slipped in on either the server or the client side to explain this?
>I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
>Thanks in advance for your help. I rally appreciate it!
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohi
bited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. Thank you.

"Suddently" can't connect to sql server (SP security prob, maybe?)

Hi! I'm running sql server 2003 on a network for my small business; I'm
having probs connecting to the server from my desktop. What's odd is that
this prob sudently occured yesterday...I had been connecting before that
(like, for several years?) and now I can't hit the box thorugh either Query
Analyzer or Enterprise manager.
The server is online because I can map to it and see the directories. Also:
I have a notebook which still can see the SQL Server box with NO Problems!
Which begs the question: what changed over the weekend? I seem to remember
that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
these two computers recently. Are you aware of any security changes that may
have been slipped in on either the server or the client side to explain this?
I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
Thanks in advance for your help. I rally appreciate it!Roger,
> I have a notebook which still can see the SQL Server box with NO Problems!
The box or the SQL Server i.e., the databases, tables and data. Can you
acesss the SQL Server by IP address? Does the OSQL utility work? What if
you try creating a DSN and 'test the connection' - just to rule out the SQL
tools as a possible cause? Have you tried restarting this client?
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> Hi! I'm running sql server 2003 on a network for my small business; I'm
> having probs connecting to the server from my desktop. What's odd is that
> this prob sudently occured yesterday...I had been connecting before that
> (like, for several years?) and now I can't hit the box thorugh either
> Query
> Analyzer or Enterprise manager.
> The server is online because I can map to it and see the directories.
> Also:
> I have a notebook which still can see the SQL Server box with NO Problems!
> Which begs the question: what changed over the weekend? I seem to remember
> that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> of
> these two computers recently. Are you aware of any security changes that
> may
> have been slipped in on either the server or the client side to explain
> this?
> I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> Thanks in advance for your help. I rally appreciate it!|||Roger,
So if I read your e-mail correctly from your desktop you can login via
Query Analyzer or Enterprise Manager but from another box you can login
to the SQL Server box using another tool? Could there have been a
network change the happened on the weekend where you box got a new IP or
the network security changed?
If the SQL Server is up [you can login via another client or directly on
the box itself] then the problem has to be with your computer or network
permissions. You may check to see if your IP changed or perhaps they
access from your IP to the server was removed.
Shahryar
Roger Willcode wrote:
>Hi! I'm running sql server 2003 on a network for my small business; I'm
>having probs connecting to the server from my desktop. What's odd is that
>this prob sudently occured yesterday...I had been connecting before that
>(like, for several years?) and now I can't hit the box thorugh either Query
>Analyzer or Enterprise manager.
>The server is online because I can map to it and see the directories. Also:
>I have a notebook which still can see the SQL Server box with NO Problems!
>Which begs the question: what changed over the weekend? I seem to remember
>that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
>these two computers recently. Are you aware of any security changes that may
>have been slipped in on either the server or the client side to explain this?
>I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
>Thanks in advance for your help. I rally appreciate it!
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. Thank you.|||Jerry, Shahryar:
First: Thanks to both you you for replying! It works now -- although I'm not
exactly sure what changed.
If it helps for anyone else reading this post; I did restart both the client
and the server to no avail. Also, I don't think there was a change in the
network permissions; I'm the only user on this network! I *did* try
connecting with the IP address and that was also a dead end.
Just for TheHalibut, I tried Jerry's suggestion of creating a ODBC
connection. When I selected TCP/IP as the connection it failed to connect.
But when I clicked the "named pipes" radio button it worked. Even more
puzzling was that I can now go back to Enterprise Manager -- and without any
further changes -- it works again.
Any body have any clues as to what happened? Also, Jerry refered to a "OSQL
utility." Sorry to be dense, but what is that?
Thanks again for your help. I'm good for now, and if you get a chance to
post any thouughts you have on my questions, I'll be even better next time!
Take care.
"Jerry Spivey" wrote:
> Roger,
> > I have a notebook which still can see the SQL Server box with NO Problems!
> The box or the SQL Server i.e., the databases, tables and data. Can you
> acesss the SQL Server by IP address? Does the OSQL utility work? What if
> you try creating a DSN and 'test the connection' - just to rule out the SQL
> tools as a possible cause? Have you tried restarting this client?
> HTH
> Jerry
> "Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
> news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> > Hi! I'm running sql server 2003 on a network for my small business; I'm
> > having probs connecting to the server from my desktop. What's odd is that
> > this prob sudently occured yesterday...I had been connecting before that
> > (like, for several years?) and now I can't hit the box thorugh either
> > Query
> > Analyzer or Enterprise manager.
> >
> > The server is online because I can map to it and see the directories.
> > Also:
> > I have a notebook which still can see the SQL Server box with NO Problems!
> >
> > Which begs the question: what changed over the weekend? I seem to remember
> > that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> > of
> > these two computers recently. Are you aware of any security changes that
> > may
> > have been slipped in on either the server or the client side to explain
> > this?
> >
> > I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> >
> > Thanks in advance for your help. I rally appreciate it!
>
>|||Roger,
The OSQL utility is the CMD line utility for querying SQL Server.
See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_osql_1wxl.asp
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:1031B9B4-3AF4-4BF3-8B7D-A0A97E92057A@.microsoft.com...
> Jerry, Shahryar:
> First: Thanks to both you you for replying! It works now -- although I'm
> not
> exactly sure what changed.
> If it helps for anyone else reading this post; I did restart both the
> client
> and the server to no avail. Also, I don't think there was a change in the
> network permissions; I'm the only user on this network! I *did* try
> connecting with the IP address and that was also a dead end.
> Just for TheHalibut, I tried Jerry's suggestion of creating a ODBC
> connection. When I selected TCP/IP as the connection it failed to connect.
> But when I clicked the "named pipes" radio button it worked. Even more
> puzzling was that I can now go back to Enterprise Manager -- and without
> any
> further changes -- it works again.
> Any body have any clues as to what happened? Also, Jerry refered to a
> "OSQL
> utility." Sorry to be dense, but what is that?
> Thanks again for your help. I'm good for now, and if you get a chance to
> post any thouughts you have on my questions, I'll be even better next
> time!
> Take care.
>
> "Jerry Spivey" wrote:
>> Roger,
>> > I have a notebook which still can see the SQL Server box with NO
>> > Problems!
>> The box or the SQL Server i.e., the databases, tables and data. Can you
>> acesss the SQL Server by IP address? Does the OSQL utility work? What
>> if
>> you try creating a DSN and 'test the connection' - just to rule out the
>> SQL
>> tools as a possible cause? Have you tried restarting this client?
>> HTH
>> Jerry
>> "Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in
>> message
>> news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
>> > Hi! I'm running sql server 2003 on a network for my small business; I'm
>> > having probs connecting to the server from my desktop. What's odd is
>> > that
>> > this prob sudently occured yesterday...I had been connecting before
>> > that
>> > (like, for several years?) and now I can't hit the box thorugh either
>> > Query
>> > Analyzer or Enterprise manager.
>> >
>> > The server is online because I can map to it and see the directories.
>> > Also:
>> > I have a notebook which still can see the SQL Server box with NO
>> > Problems!
>> >
>> > Which begs the question: what changed over the weekend? I seem to
>> > remember
>> > that a OS SP/Hotfix/etc was automatically downloaded and installed on
>> > one
>> > of
>> > these two computers recently. Are you aware of any security changes
>> > that
>> > may
>> > have been slipped in on either the server or the client side to explain
>> > this?
>> >
>> > I'm running Win Server 2003 on the server and XP Prof SP2 on the
>> > desktop.
>> >
>> > Thanks in advance for your help. I rally appreciate it!
>>

"Suddently" can't connect to sql server (SP security prob, maybe?)

Hi! I'm running sql server 2003 on a network for my small business; I'm
having probs connecting to the server from my desktop. What's odd is that
this prob sudently occured yesterday...I had been connecting before that
(like, for several years?) and now I can't hit the box thorugh either Query
Analyzer or Enterprise manager.
The server is online because I can map to it and see the directories. Also:
I have a notebook which still can see the SQL Server box with NO Problems!
Which begs the question: what changed over the weekend? I seem to remember
that a OS SP/Hotfix/etc was automatically downloaded and installed on one of
these two computers recently. Are you aware of any security changes that may
have been slipped in on either the server or the client side to explain this
?
I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
Thanks in advance for your help. I rally appreciate it!Roger,

> I have a notebook which still can see the SQL Server box with NO Problems!
The box or the SQL Server i.e., the databases, tables and data. Can you
acesss the SQL Server by IP address? Does the OSQL utility work? What if
you try creating a DSN and 'test the connection' - just to rule out the SQL
tools as a possible cause? Have you tried restarting this client?
HTH
Jerry
"Roger Willcode" <RogerWillcode@.discussions.microsoft.com> wrote in message
news:FA1EA7E3-B9D7-4E06-96B9-D619A211088D@.microsoft.com...
> Hi! I'm running sql server 2003 on a network for my small business; I'm
> having probs connecting to the server from my desktop. What's odd is that
> this prob sudently occured yesterday...I had been connecting before that
> (like, for several years?) and now I can't hit the box thorugh either
> Query
> Analyzer or Enterprise manager.
> The server is online because I can map to it and see the directories.
> Also:
> I have a notebook which still can see the SQL Server box with NO Problems!
> Which begs the question: what changed over the weekend? I seem to remember
> that a OS SP/Hotfix/etc was automatically downloaded and installed on one
> of
> these two computers recently. Are you aware of any security changes that
> may
> have been slipped in on either the server or the client side to explain
> this?
> I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
> Thanks in advance for your help. I rally appreciate it!|||Roger,
So if I read your e-mail correctly from your desktop you can login via
Query Analyzer or Enterprise Manager but from another box you can login
to the SQL Server box using another tool? Could there have been a
network change the happened on the weekend where you box got a new IP or
the network security changed?
If the SQL Server is up [you can login via another client or directly on
the box itself] then the problem has to be with your computer or network
permissions. You may check to see if your IP changed or perhaps they
access from your IP to the server was removed.
Shahryar
Roger Willcode wrote:

>Hi! I'm running sql server 2003 on a network for my small business; I'm
>having probs connecting to the server from my desktop. What's odd is that
>this prob sudently occured yesterday...I had been connecting before that
>(like, for several years?) and now I can't hit the box thorugh either Query
>Analyzer or Enterprise manager.
>The server is online because I can map to it and see the directories. Also:
>I have a notebook which still can see the SQL Server box with NO Problems!
>Which begs the question: what changed over the weekend? I seem to remember
>that a OS SP/Hotfix/etc was automatically downloaded and installed on one o
f
>these two computers recently. Are you aware of any security changes that ma
y
>have been slipped in on either the server or the client side to explain thi
s?
>I'm running Win Server 2003 on the server and XP Prof SP2 on the desktop.
>Thanks in advance for your help. I rally appreciate it!
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is
legally privileged. The information is solely for the use of the intended
recipient(s); any disclosure, copying, distribution, or other use of this in
formation is strictly prohi
bited. If you have received this e-mail in error, please notify the sender
by return e-mail and delete this message. Thank you.

"SQL Server does not exist or access denied" error when trying to connect from a Windows S

Hi!

I understand that this topic is one of the most discussed topics ever. However i could not find the relevant information after going through (almost) all the posts so far. Hence this post.

I am getting the 'SQL Server does not exist or access denied' error when I am trying to access SQL Server from a WINDOWS SERVICE. SQL Server and the Windows service are running on two different machines. (When they are on the same machine, it works). All the solutions I found so far are related to web apps. What should I do in the case of a windows service? My connection string uses SQL server authentication. (I tried with windows authentication. Its not working either.). Under what login does windows services run and how can I add it to valid SQL server logins?

what version of sql server you are using SQL 2000 or SQL 2005. If sql 2005 have you enabled remote connection on sql server|||I am using SQL Server 2000. My Connection String is "Data Source=Proficio3;Initial Catalog=PRO-TMS_2.5;User ID=service_login;Password=service"|||

Hi,

Please try to check if the SQL Server you're connecting to is the default instance on that server. If not, you will need to add instance name after the server name like:

Data Source=Proficio3\SQLInstance

"Server does not exist or access is denied"

Hi,
I am trying to connect a web service to an SQL Server 2000 database. SQL
Server is installed and started and the database appears on the Enterprise
MAnager window but it does not appear in the Server Explorer in VS2003.NET
IDE window.It gives the error "Server does not exist or access is denied".
I have re-installed both SQL server and VS but have not being able to solve
this problem.
Can someone help me out ? A prompt reply will be highly appreciated.
Regards
Kapila
Where is the Server Explorer installed? Is it on a different machine or
different network? Based on the error message, it looks like the Server
Explorer is unable to find your SQL Server on the network. A network issue
is more likey to be the case. Can you ping the SQL Server computer from the
Server Explorer box?
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
SERVER EXPL@.discussions.microsoft.com> wrote in message
news:B122F925-40E5-4CFA-AA57-279E47242E4F@.microsoft.com...
> Hi,
> I am trying to connect a web service to an SQL Server 2000 database. SQL
> Server is installed and started and the database appears on the Enterprise
> MAnager window but it does not appear in the Server Explorer in VS2003.NET
> IDE window.It gives the error "Server does not exist or access is denied".
> I have re-installed both SQL server and VS but have not being able to
solve
> this problem.
> Can someone help me out ? A prompt reply will be highly appreciated.
> Regards
> Kapila
|||The server explorer is installed on the same system. I am not on a network.
The services are running.
Thanks
Kapila
"Narayana Vyas Kondreddi" wrote:

> Where is the Server Explorer installed? Is it on a different machine or
> different network? Based on the error message, it looks like the Server
> Explorer is unable to find your SQL Server on the network. A network issue
> is more likey to be the case. Can you ping the SQL Server computer from the
> Server Explorer box?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
> SERVER EXPL@.discussions.microsoft.com> wrote in message
> news:B122F925-40E5-4CFA-AA57-279E47242E4F@.microsoft.com...
> solve
>
>

"Server does not exist or access is denied"

Hi,
I am trying to connect a web service to an SQL Server 2000 database. SQL
Server is installed and started and the database appears on the Enterprise
MAnager window but it does not appear in the Server Explorer in VS2003.NET
IDE window.It gives the error "Server does not exist or access is denied".
I have re-installed both SQL server and VS but have not being able to solve
this problem.
Can someone help me out ? A prompt reply will be highly appreciated.
Regards
Kapila
Is the SQL Server running?
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
SERVER EXPL@.discussions.microsoft.com> wrote in message
news:61B0D79D-A657-4D25-AC9C-69349C3286B3@.microsoft.com...
> Hi,
> I am trying to connect a web service to an SQL Server 2000 database. SQL
> Server is installed and started and the database appears on the Enterprise
> MAnager window but it does not appear in the Server Explorer in VS2003.NET
> IDE window.It gives the error "Server does not exist or access is denied".
> I have re-installed both SQL server and VS but have not being able to
> solve
> this problem.
> Can someone help me out ? A prompt reply will be highly appreciated.
> Regards
> Kapila
|||Yes, it does. It is shown on the status bar and also in Services. However, it
is not appearing in the computer management console of MS Server 2003.
Best wishes.
Kapila
"Kalen Delaney" wrote:

> Is the SQL Server running?
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
> SERVER EXPL@.discussions.microsoft.com> wrote in message
> news:61B0D79D-A657-4D25-AC9C-69349C3286B3@.microsoft.com...
>
>
|||It is possible for the SQL Enterprise or iSQL applications to see and work
with SQL server instances while other non-SQL tools such as VS.Net may not
see your SQL servers at all. (based on your problem description)
1. Check to see how the SQL Security is configured on the server. The best
practice is to configure it with Windows Integrated.
2. I always configure SQL Server with Mixed modes (W and Sql). Reason: My
developer PC may not always log on to the Windows Server/Domain where my SQL
Instance is hosted. If such condition exists, then SQL Authentication mode
kicks in to allow me to log on to it.
3. Another suggestion is that if your server is not in the DNS system, then
it is safe to put it in your Windows/HOSTS file. This way everybody
(applications) on your PC can see it.
John Webb

"Server does not exist or access is denied"

Hi,
I am trying to connect a web service to an SQL Server 2000 database. SQL
Server is installed and started and the database appears on the Enterprise
MAnager window but it does not appear in the Server Explorer in VS2003.NET
IDE window.It gives the error "Server does not exist or access is denied".
I have re-installed both SQL server and VS but have not being able to solve
this problem.
Can someone help me out ? A prompt reply will be highly appreciated.
Regards
KapilaIs the SQL Server running?
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
SERVER EXPL@.discussions.microsoft.com> wrote in message
news:61B0D79D-A657-4D25-AC9C-69349C3286B3@.microsoft.com...
> Hi,
> I am trying to connect a web service to an SQL Server 2000 database. SQL
> Server is installed and started and the database appears on the Enterprise
> MAnager window but it does not appear in the Server Explorer in VS2003.NET
> IDE window.It gives the error "Server does not exist or access is denied".
> I have re-installed both SQL server and VS but have not being able to
> solve
> this problem.
> Can someone help me out ? A prompt reply will be highly appreciated.
> Regards
> Kapila|||Yes, it does. It is shown on the status bar and also in Services. However, i
t
is not appearing in the computer management console of MS Server 2003.
Best wishes.
Kapila
"Kalen Delaney" wrote:

> Is the SQL Server running?
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
> SERVER EXPL@.discussions.microsoft.com> wrote in message
> news:61B0D79D-A657-4D25-AC9C-69349C3286B3@.microsoft.com...
>
>|||It is possible for the SQL Enterprise or iSQL applications to see and work
with SQL server instances while other non-SQL tools such as VS.Net may not
see your SQL servers at all. (based on your problem description)
1. Check to see how the SQL Security is configured on the server. The best
practice is to configure it with Windows Integrated.
2. I always configure SQL Server with Mixed modes (W and Sql). Reason: My
developer PC may not always log on to the Windows Server/Domain where my SQL
Instance is hosted. If such condition exists, then SQL Authentication mode
kicks in to allow me to log on to it.
3. Another suggestion is that if your server is not in the DNS system, then
it is safe to put it in your Windows/HOSTS file. This way everybody
(applications) on your PC can see it.
John Webb

"Server does not exist or access is denied"

Hi,
I am trying to connect a web service to an SQL Server 2000 database. SQL
Server is installed and started and the database appears on the Enterprise
MAnager window but it does not appear in the Server Explorer in VS2003.NET
IDE window.It gives the error "Server does not exist or access is denied".
I have re-installed both SQL server and VS but have not being able to solve
this problem.
Can someone help me out ? A prompt reply will be highly appreciated.
Regards
KapilaWhere is the Server Explorer installed? Is it on a different machine or
different network? Based on the error message, it looks like the Server
Explorer is unable to find your SQL Server on the network. A network issue
is more likey to be the case. Can you ping the SQL Server computer from the
Server Explorer box?
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
SERVER EXPL@.discussions.microsoft.com> wrote in message
news:B122F925-40E5-4CFA-AA57-279E47242E4F@.microsoft.com...
> Hi,
> I am trying to connect a web service to an SQL Server 2000 database. SQL
> Server is installed and started and the database appears on the Enterprise
> MAnager window but it does not appear in the Server Explorer in VS2003.NET
> IDE window.It gives the error "Server does not exist or access is denied".
> I have re-installed both SQL server and VS but have not being able to
solve
> this problem.
> Can someone help me out ? A prompt reply will be highly appreciated.
> Regards
> Kapila|||The server explorer is installed on the same system. I am not on a network.
The services are running.
Thanks
Kapila
"Narayana Vyas Kondreddi" wrote:

> Where is the Server Explorer installed? Is it on a different machine or
> different network? Based on the error message, it looks like the Server
> Explorer is unable to find your SQL Server on the network. A network issue
> is more likey to be the case. Can you ping the SQL Server computer from th
e
> Server Explorer box?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
> SERVER EXPL@.discussions.microsoft.com> wrote in message
> news:B122F925-40E5-4CFA-AA57-279E47242E4F@.microsoft.com...
> solve
>
>

"Server does not exist or access is denied"

Hi,
I am trying to connect a web service to an SQL Server 2000 database. SQL
Server is installed and started and the database appears on the Enterprise
MAnager window but it does not appear in the Server Explorer in VS2003.NET
IDE window.It gives the error "Server does not exist or access is denied".
I have re-installed both SQL server and VS but have not being able to solve
this problem.
Can someone help me out ? A prompt reply will be highly appreciated.
Regards
KapilaWhere is the Server Explorer installed? Is it on a different machine or
different network? Based on the error message, it looks like the Server
Explorer is unable to find your SQL Server on the network. A network issue
is more likey to be the case. Can you ping the SQL Server computer from the
Server Explorer box?
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
SERVER EXPL@.discussions.microsoft.com> wrote in message
news:B122F925-40E5-4CFA-AA57-279E47242E4F@.microsoft.com...
> Hi,
> I am trying to connect a web service to an SQL Server 2000 database. SQL
> Server is installed and started and the database appears on the Enterprise
> MAnager window but it does not appear in the Server Explorer in VS2003.NET
> IDE window.It gives the error "Server does not exist or access is denied".
> I have re-installed both SQL server and VS but have not being able to
solve
> this problem.
> Can someone help me out ? A prompt reply will be highly appreciated.
> Regards
> Kapila|||The server explorer is installed on the same system. I am not on a network.
The services are running.
Thanks
Kapila
"Narayana Vyas Kondreddi" wrote:
> Where is the Server Explorer installed? Is it on a different machine or
> different network? Based on the error message, it looks like the Server
> Explorer is unable to find your SQL Server on the network. A network issue
> is more likey to be the case. Can you ping the SQL Server computer from the
> Server Explorer box?
> --
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "CAN'T SEE THE SERVER FROM VS SERVER EXPL" <CAN'T SEE THE SERVER FROM VS
> SERVER EXPL@.discussions.microsoft.com> wrote in message
> news:B122F925-40E5-4CFA-AA57-279E47242E4F@.microsoft.com...
> > Hi,
> >
> > I am trying to connect a web service to an SQL Server 2000 database. SQL
> > Server is installed and started and the database appears on the Enterprise
> > MAnager window but it does not appear in the Server Explorer in VS2003.NET
> > IDE window.It gives the error "Server does not exist or access is denied".
> >
> > I have re-installed both SQL server and VS but have not being able to
> solve
> > this problem.
> >
> > Can someone help me out ? A prompt reply will be highly appreciated.
> >
> > Regards
> >
> > Kapila
>
>

"Restore Database" when unable to "Connect"?

Hey

Quick question for the experts here! Wink

We have the issue of wanting to restore an MSSQL database (.BAK) but are unable to "Connect" to the existing database; but we are able to "Start" the database currently.

When we are unable to perform a "Connect", then under "All Tasks" you don't get the option to "Restore Database"

I am hoping there is a way around this and still a possibility of doing a restore without having to do an entire install of MSSQL again and then a restore?

Thanks!When you say you are unable to "connect" do you mean with the application, or with the SQL Server tools?

Also, when you say "start the database" do you mean the MSSQLServer service?

Sorry for the questions, I just want to make sure we are talking the same language.|||Please disregard, seems that there was a registration issue with admin rights, so I have since connected as Administrator and am abale to do a "Restore Database" again.

Thanks a lot

"Read Only" problem from Access 2003 to SQL Server

I am unable to add/update/delete data in the SQL Server database from Access
2003. I can connect just fine using either an ODBC link or via an ADO
connection in VBA. However, any time I try to change any SQL Server data (or
run a stored procedure) it either "times out" or gives me a message to the
effect that "...another user is attempting to change the data at the same
time...". Since I am the only one on the network, I know this is not the
real problem. I have SQL Profiler running in order to see what may be
happening when I try to run a stored procedure. The SQL Server doesn't get
the request at all. Access seems to be blocking any calls to stored
procedures and blocking any attempt to change data.
I can change data with no problem from within Enterprise Manager. The SQL
Server User (in the ADO connection) has db owner rights and rights to all
objects being accessed.
Here is the configuration: I am running Win 2K Pro with SQL Server 2000 on
PC-1 and Win XP Pro and Access 2003 on PC-2. I have an Access 2003 database
application on PC-2 that needs to modify the SQL data on PC-1. I have tried
Windows authentication and SQL Server Authentication (modifying the SQL
Server settings and ADO connection string settings as needed). Both ways of
connecting give the same result - read only.
When I installed Access 2003 I saw a message relating to security and Access
not allowing potentially destructive code to run. I took no action on the
message although I did remember seeing something about a necessary update to
2003 for the issue (I figured I'd revisit it later). This issue may be
related to the problem, but I don't know. There are no outstanding updates
available for Access 2003 from MS. Now I can't figure out what it was
talking about. I may uninstall the software and reinstall to see if I can
catch it again.
I have tried everything I can think of, including soliciting help from
peers, searching the knowledge databases and reading many posts. No luck.
It appears as though no one has had this particular issue come up. I tried
to ask Microsoft (using my one free question) but my (valid) Product ID was
rejected by their system.
Anyone out there have any experience with this one? Three days stuck on one
issue is getting old.
Thanks and regards,
--
Ken Wells
President
Smart Computing Solutions, LLCAll it took was a post. I have, for all intents and purposes, solved this
problem myself.
I broke down and rewrote the code (inherited from another developer), basing
it on code that I had done in the past. I can now execute a stored procedure
and update or add records in the SQL database from Access 2003 using an ADO
connection and SQL Server Authentication.
I still cannot directly modify ODBC-linked SQL table data from the database
window, but that is a minor consideration at this point.
"SmartComputing" wrote:
> I am unable to add/update/delete data in the SQL Server database from Access
> 2003. I can connect just fine using either an ODBC link or via an ADO
> connection in VBA. However, any time I try to change any SQL Server data (or
> run a stored procedure) it either "times out" or gives me a message to the
> effect that "...another user is attempting to change the data at the same
> time...". Since I am the only one on the network, I know this is not the
> real problem. I have SQL Profiler running in order to see what may be
> happening when I try to run a stored procedure. The SQL Server doesn't get
> the request at all. Access seems to be blocking any calls to stored
> procedures and blocking any attempt to change data.
> I can change data with no problem from within Enterprise Manager. The SQL
> Server User (in the ADO connection) has db owner rights and rights to all
> objects being accessed.
> Here is the configuration: I am running Win 2K Pro with SQL Server 2000 on
> PC-1 and Win XP Pro and Access 2003 on PC-2. I have an Access 2003 database
> application on PC-2 that needs to modify the SQL data on PC-1. I have tried
> Windows authentication and SQL Server Authentication (modifying the SQL
> Server settings and ADO connection string settings as needed). Both ways of
> connecting give the same result - read only.
> When I installed Access 2003 I saw a message relating to security and Access
> not allowing potentially destructive code to run. I took no action on the
> message although I did remember seeing something about a necessary update to
> 2003 for the issue (I figured I'd revisit it later). This issue may be
> related to the problem, but I don't know. There are no outstanding updates
> available for Access 2003 from MS. Now I can't figure out what it was
> talking about. I may uninstall the software and reinstall to see if I can
> catch it again.
> I have tried everything I can think of, including soliciting help from
> peers, searching the knowledge databases and reading many posts. No luck.
> It appears as though no one has had this particular issue come up. I tried
> to ask Microsoft (using my one free question) but my (valid) Product ID was
> rejected by their system.
> Anyone out there have any experience with this one? Three days stuck on one
> issue is getting old.
> Thanks and regards,
> --
> Ken Wells
> President
> Smart Computing Solutions, LLC|||"SmartComputing" <kennethwells@.NO_SPAM_yahoo.com> wrote in message
news:9F4BA364-B69B-4026-AD67-CF024DE7FEDD@.microsoft.com...
> All it took was a post. I have, for all intents and purposes, solved this
> problem myself.
> I broke down and rewrote the code (inherited from another developer),
> basing
> it on code that I had done in the past. I can now execute a stored
> procedure
> and update or add records in the SQL database from Access 2003 using an
> ADO
> connection and SQL Server Authentication.
> I still cannot directly modify ODBC-linked SQL table data from the
> database
> window, but that is a minor consideration at this point.
I reckon it's the connection parameters are most likely the problem.
Go into the linked table manager.
If you hover over the connected tables you should see a connection string in
there.
Whilst you're there, refresh the connections and check that doesn't help.
Check out your DSN or connection strings.
Oh...
Access wants unique keys to allow updates.
Looking at the table definition in access, you see a primary key on the
tables?
There's also joins can make a query not updateable but if nothing works this
seems unlikely.
--
Regards,
Andy O'Neill

"Read Only" problem from Access 2003 to SQL Server

I am unable to add/update/delete data in the SQL Server database from Access
2003. I can connect just fine using either an ODBC link or via an ADO
connection in VBA. However, any time I try to change any SQL Server data (or
run a stored procedure) it either "times out" or gives me a message to the
effect that "...another user is attempting to change the data at the same
time...". Since I am the only one on the network, I know this is not the
real problem. I have SQL Profiler running in order to see what may be
happening when I try to run a stored procedure. The SQL Server doesn't get
the request at all. Access seems to be blocking any calls to stored
procedures and blocking any attempt to change data.
I can change data with no problem from within Enterprise Manager. The SQL
Server User (in the ADO connection) has db owner rights and rights to all
objects being accessed.
Here is the configuration: I am running Win 2K Pro with SQL Server 2000 on
PC-1 and Win XP Pro and Access 2003 on PC-2. I have an Access 2003 database
application on PC-2 that needs to modify the SQL data on PC-1. I have tried
Windows authentication and SQL Server Authentication (modifying the SQL
Server settings and ADO connection string settings as needed). Both ways of
connecting give the same result - read only.
When I installed Access 2003 I saw a message relating to security and Access
not allowing potentially destructive code to run. I took no action on the
message although I did remember seeing something about a necessary update to
2003 for the issue (I figured I'd revisit it later). This issue may be
related to the problem, but I don't know. There are no outstanding updates
available for Access 2003 from MS. Now I can't figure out what it was
talking about. I may uninstall the software and reinstall to see if I can
catch it again.
I have tried everything I can think of, including soliciting help from
peers, searching the knowledge databases and reading many posts. No luck.
It appears as though no one has had this particular issue come up. I tried
to ask Microsoft (using my one free question) but my (valid) Product ID was
rejected by their system.
Anyone out there have any experience with this one? Three days stuck on one
issue is getting old.
Thanks and regards,
Ken Wells
President
Smart Computing Solutions, LLC
All it took was a post. I have, for all intents and purposes, solved this
problem myself.
I broke down and rewrote the code (inherited from another developer), basing
it on code that I had done in the past. I can now execute a stored procedure
and update or add records in the SQL database from Access 2003 using an ADO
connection and SQL Server Authentication.
I still cannot directly modify ODBC-linked SQL table data from the database
window, but that is a minor consideration at this point.
"SmartComputing" wrote:

> I am unable to add/update/delete data in the SQL Server database from Access
> 2003. I can connect just fine using either an ODBC link or via an ADO
> connection in VBA. However, any time I try to change any SQL Server data (or
> run a stored procedure) it either "times out" or gives me a message to the
> effect that "...another user is attempting to change the data at the same
> time...". Since I am the only one on the network, I know this is not the
> real problem. I have SQL Profiler running in order to see what may be
> happening when I try to run a stored procedure. The SQL Server doesn't get
> the request at all. Access seems to be blocking any calls to stored
> procedures and blocking any attempt to change data.
> I can change data with no problem from within Enterprise Manager. The SQL
> Server User (in the ADO connection) has db owner rights and rights to all
> objects being accessed.
> Here is the configuration: I am running Win 2K Pro with SQL Server 2000 on
> PC-1 and Win XP Pro and Access 2003 on PC-2. I have an Access 2003 database
> application on PC-2 that needs to modify the SQL data on PC-1. I have tried
> Windows authentication and SQL Server Authentication (modifying the SQL
> Server settings and ADO connection string settings as needed). Both ways of
> connecting give the same result - read only.
> When I installed Access 2003 I saw a message relating to security and Access
> not allowing potentially destructive code to run. I took no action on the
> message although I did remember seeing something about a necessary update to
> 2003 for the issue (I figured I'd revisit it later). This issue may be
> related to the problem, but I don't know. There are no outstanding updates
> available for Access 2003 from MS. Now I can't figure out what it was
> talking about. I may uninstall the software and reinstall to see if I can
> catch it again.
> I have tried everything I can think of, including soliciting help from
> peers, searching the knowledge databases and reading many posts. No luck.
> It appears as though no one has had this particular issue come up. I tried
> to ask Microsoft (using my one free question) but my (valid) Product ID was
> rejected by their system.
> Anyone out there have any experience with this one? Three days stuck on one
> issue is getting old.
> Thanks and regards,
> --
> Ken Wells
> President
> Smart Computing Solutions, LLC
|||"SmartComputing" <kennethwells@.NO_SPAM_yahoo.com> wrote in message
news:9F4BA364-B69B-4026-AD67-CF024DE7FEDD@.microsoft.com...
> All it took was a post. I have, for all intents and purposes, solved this
> problem myself.
> I broke down and rewrote the code (inherited from another developer),
> basing
> it on code that I had done in the past. I can now execute a stored
> procedure
> and update or add records in the SQL database from Access 2003 using an
> ADO
> connection and SQL Server Authentication.
> I still cannot directly modify ODBC-linked SQL table data from the
> database
> window, but that is a minor consideration at this point.
I reckon it's the connection parameters are most likely the problem.
Go into the linked table manager.
If you hover over the connected tables you should see a connection string in
there.
Whilst you're there, refresh the connections and check that doesn't help.
Check out your DSN or connection strings.
Oh...
Access wants unique keys to allow updates.
Looking at the table definition in access, you see a primary key on the
tables?
There's also joins can make a query not updateable but if nothing works this
seems unlikely.
Regards,
Andy O'Neill

"Read Only" problem from Access 2003 to SQL Server

I am unable to add/update/delete data in the SQL Server database from Access
2003. I can connect just fine using either an ODBC link or via an ADO
connection in VBA. However, any time I try to change any SQL Server data (o
r
run a stored procedure) it either "times out" or gives me a message to the
effect that "...another user is attempting to change the data at the same
time...". Since I am the only one on the network, I know this is not the
real problem. I have SQL Profiler running in order to see what may be
happening when I try to run a stored procedure. The SQL Server doesn't get
the request at all. Access seems to be blocking any calls to stored
procedures and blocking any attempt to change data.
I can change data with no problem from within Enterprise Manager. The SQL
Server User (in the ADO connection) has db owner rights and rights to all
objects being accessed.
Here is the configuration: I am running Win 2K Pro with SQL Server 2000 on
PC-1 and Win XP Pro and Access 2003 on PC-2. I have an Access 2003 database
application on PC-2 that needs to modify the SQL data on PC-1. I have tried
Windows authentication and SQL Server Authentication (modifying the SQL
Server settings and ADO connection string settings as needed). Both ways of
connecting give the same result - read only.
When I installed Access 2003 I saw a message relating to security and Access
not allowing potentially destructive code to run. I took no action on the
message although I did remember seeing something about a necessary update to
2003 for the issue (I figured I'd revisit it later). This issue may be
related to the problem, but I don't know. There are no outstanding updates
available for Access 2003 from MS. Now I can't figure out what it was
talking about. I may uninstall the software and reinstall to see if I can
catch it again.
I have tried everything I can think of, including soliciting help from
peers, searching the knowledge databases and reading many posts. No luck.
It appears as though no one has had this particular issue come up. I tried
to ask Microsoft (using my one free question) but my (valid) Product ID was
rejected by their system.
Anyone out there have any experience with this one? Three days stuck on one
issue is getting old.
Thanks and regards,
--
Ken Wells
President
Smart Computing Solutions, LLCAll it took was a post. I have, for all intents and purposes, solved this
problem myself.
I broke down and rewrote the code (inherited from another developer), basing
it on code that I had done in the past. I can now execute a stored procedur
e
and update or add records in the SQL database from Access 2003 using an ADO
connection and SQL Server Authentication.
I still cannot directly modify ODBC-linked SQL table data from the database
window, but that is a minor consideration at this point.
"SmartComputing" wrote:

> I am unable to add/update/delete data in the SQL Server database from Acce
ss
> 2003. I can connect just fine using either an ODBC link or via an ADO
> connection in VBA. However, any time I try to change any SQL Server data
(or
> run a stored procedure) it either "times out" or gives me a message to the
> effect that "...another user is attempting to change the data at the same
> time...". Since I am the only one on the network, I know this is not the
> real problem. I have SQL Profiler running in order to see what may be
> happening when I try to run a stored procedure. The SQL Server doesn't ge
t
> the request at all. Access seems to be blocking any calls to stored
> procedures and blocking any attempt to change data.
> I can change data with no problem from within Enterprise Manager. The SQL
> Server User (in the ADO connection) has db owner rights and rights to all
> objects being accessed.
> Here is the configuration: I am running Win 2K Pro with SQL Server 2000 o
n
> PC-1 and Win XP Pro and Access 2003 on PC-2. I have an Access 2003 databa
se
> application on PC-2 that needs to modify the SQL data on PC-1. I have tri
ed
> Windows authentication and SQL Server Authentication (modifying the SQL
> Server settings and ADO connection string settings as needed). Both ways
of
> connecting give the same result - read only.
> When I installed Access 2003 I saw a message relating to security and Acce
ss
> not allowing potentially destructive code to run. I took no action on the
> message although I did remember seeing something about a necessary update
to
> 2003 for the issue (I figured I'd revisit it later). This issue may be
> related to the problem, but I don't know. There are no outstanding update
s
> available for Access 2003 from MS. Now I can't figure out what it was
> talking about. I may uninstall the software and reinstall to see if I can
> catch it again.
> I have tried everything I can think of, including soliciting help from
> peers, searching the knowledge databases and reading many posts. No luck.
> It appears as though no one has had this particular issue come up. I trie
d
> to ask Microsoft (using my one free question) but my (valid) Product ID wa
s
> rejected by their system.
> Anyone out there have any experience with this one? Three days stuck on o
ne
> issue is getting old.
> Thanks and regards,
> --
> Ken Wells
> President
> Smart Computing Solutions, LLC|||"SmartComputing" <kennethwells@.NO_SPAM_yahoo.com> wrote in message
news:9F4BA364-B69B-4026-AD67-CF024DE7FEDD@.microsoft.com...
> All it took was a post. I have, for all intents and purposes, solved this
> problem myself.
> I broke down and rewrote the code (inherited from another developer),
> basing
> it on code that I had done in the past. I can now execute a stored
> procedure
> and update or add records in the SQL database from Access 2003 using an
> ADO
> connection and SQL Server Authentication.
> I still cannot directly modify ODBC-linked SQL table data from the
> database
> window, but that is a minor consideration at this point.
I reckon it's the connection parameters are most likely the problem.
Go into the linked table manager.
If you hover over the connected tables you should see a connection string in
there.
Whilst you're there, refresh the connections and check that doesn't help.
Check out your DSN or connection strings.
Oh...
Access wants unique keys to allow updates.
Looking at the table definition in access, you see a primary key on the
tables?
There's also joins can make a query not updateable but if nothing works this
seems unlikely.
Regards,
Andy O'Neill

"non-trusted connection" what does it mean?

What does it mean when a users is connected but it is a "non-trusted connection". This is showing up in the log file after my users connect. How does this effect the system/user? We have been experiencing speed issues and I was wondering if this might be a possible source of the problem.

Thanks in advance.A "trusted connection" is made using Windoze authentication. A "non-trusted connection" is made using SQL authentication. That is is the only difference that I know of between the two kinds of connections.

-PatP

"Logon failed" when attempting to connect to cube.

Greetings. I am brand new to SRS, so please bear with me. I'm trying to
create a Report Model in SRS 2005 against an Analysis Services 2005 cube. I
am an admin on the AS box. I am using this tutorial:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/8e5d2bd3-48ec-45f3-afee-6d86797c8f28.htm
I set up the data source, then I hit "generate model". I type in my model
name, hit "OK", and get the "Logon failed (rsLogonFailed)" message. I am
using "credentials supplied by the user running the report" dialog box with
the "Use as Windows..." checkbox checked. For good measure I have even added
myself to a cube Role with admin privelages. Alos, I can in fact browse and
manipulate the cube.
Any ideas?
TIA, ChrisRHi
I think the issue here is not the users priviliges in SSAS , rather
the priviliges in SSRS. Try using report manager to configure
permissions for the user in question .
Cheers
Shai
On Nov 20, 12:34 am, ChrisR <Chr...@.discussions.microsoft.com> wrote:
> Greetings. I am brand new to SRS, so please bear with me. I'm trying to
> create a Report Model in SRS 2005 against an Analysis Services 2005 cube. I
> am an admin on the AS box. I am using this tutorial:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/8e5d2bd3-48ec-45f3-afee--6d86797c8f28.htm
> I set up the data source, then I hit "generate model". I type in my model
> name, hit "OK", and get the "Logon failed (rsLogonFailed)" message. I am
> using "credentials supplied by the user running the report" dialog box with
> the "Use as Windows..." checkbox checked. For good measure I have even added
> myself to a cube Role with admin privelages. Alos, I can in fact browse and
> manipulate the cube.
> Any ideas?
> TIA, ChrisR

"Login Failed" for SQL Express

Whenever I try to connect to my SQL Express Database with C# code,(.net 2.0), it says "Login failed for user 'TUser'. The user is not associated with a trusted SQL Server connection."

But I can connect with SQL Express Manager.

I've heard somewhere this is a SQL authentication problem, I didn't enable it during installation.

So is there a way to fix this? How can I enable SQL authentication without uninstalling it?

Is there anyone to help me?

"cannot open user default database. Login failed"

When attempting to connect to my local instance of SQL server I am getting t
his error message: "cannot open user default database. Login failed".
My OS is WinXp v2002 SP2. This issue started after I deleted a database on
my local server, prior to that it was working fine.
ThanksIt looks like you deleted the database that was the default database for
your login. One method to fix the problem is to connect using the OSQL
command-line utility, overriding the default database. You can then change
the default DB to one that exists.
The example below connects to the local server with SQL authentication and
changes the default database to 'master':
OSQL -d master -U MyLogin -P MyPassword -Q"EXEC sp_defaultdb 'MyLogin'
,'master'"
Hope this helps.
Dan Guzman
SQL Server MVP
"Brent Stevenson" <essexbs@.insightbb.com> wrote in message
news:u6aIYXRwFHA.3864@.TK2MSFTNGP12.phx.gbl...
When attempting to connect to my local instance of SQL server I am getting
this error message: "cannot open user default database. Login failed".
My OS is WinXp v2002 SP2. This issue started after I deleted a database on
my local server, prior to that it was working fine.
Thanks|||Dan,
Thanks for the reply! But infortunaley that fails with a "login failed for
'user' error."
According to OSQL help: "If neither the -U or -P options are used, SQL
Server 2000 attempts to connect using Windows Authentication Mode." Well
that would be my network account & password and if I just enter OSQL -d
master and then my network account password at the prompt, it fails (login
failed for user). I know I'm correctly entering my current network account
password.
Any ideas?
Thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:Oex4GfRwFHA.464@.TK2MSFTNGP15.phx.gbl...
> It looks like you deleted the database that was the default database for
> your login. One method to fix the problem is to connect using the OSQL
> command-line utility, overriding the default database. You can then
> change the default DB to one that exists.
> The example below connects to the local server with SQL authentication and
> changes the default database to 'master':
> OSQL -d master -U MyLogin -P MyPassword -Q"EXEC sp_defaultdb 'MyLogin'
> ,'master'"
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Brent Stevenson" <essexbs@.insightbb.com> wrote in message
> news:u6aIYXRwFHA.3864@.TK2MSFTNGP12.phx.gbl...
> When attempting to connect to my local instance of SQL server I am getting
> this error message: "cannot open user default database. Login failed".
> My OS is WinXp v2002 SP2. This issue started after I deleted a database
> on my local server, prior to that it was working fine.
> Thanks
>|||My machines gives an error if I don't use -U or -E. Did you try using the -E
switch to login using
your Windows account?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brent Stevenson" <essexbs@.insightbb.com> wrote in message
news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
> Dan,
> Thanks for the reply! But infortunaley that fails with a "login failed for
'user' error."
> According to OSQL help: "If neither the -U or -P options are used, SQL Ser
ver 2000 attempts to
> connect using Windows Authentication Mode." Well that would be my network
account & password and
> if I just enter OSQL -d master and then my network account password at the
prompt, it fails (login
> failed for user). I know I'm correctly entering my current network account
password.
> Any ideas?
> Thanks
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:Oex4GfRwFHA.464@.TK2MSFTNGP15.phx.gbl...
>|||Using the -E go me in & allowed me to change my default DB & resolve the
issue.
Thanks a million!! Have a good day.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23vKLtxdwFHA.3556@.TK2MSFTNGP12.phx.gbl...
> My machines gives an error if I don't use -U or -E. Did you try using
> the -E switch to login using your Windows account?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Brent Stevenson" <essexbs@.insightbb.com> wrote in message
> news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
>|||The example I posted assumed a SQL login. Like Tibor mentioned, you can
specify '-E' to establish a trusted connection using your current Windows
account. You never need to specify a Windows account with the '-E'
parameter but you still need to specify the name of the account to
sp_defaultdb. For a local Windows account:
OSQL -d master -E -Q"EXEC sp_defaultdb 'MyMachine\MyAccount','master'"
or for a domain account:
OSQL -d master -E -Q"EXEC sp_defaultdb 'MyDomain\MyAccount','master'"
If your SQL Server access is via membership of the local Administrators
group, you'll need to change the default database for that group instead:
OSQL -d master -E -Q"EXEC sp_defaultdb 'BUILTIN\Administrators','master'"
Hope this helps.
Dan Guzman
SQL Server MVP
"Brent Stevenson" <essexbs@.insightbb.com> wrote in message
news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
> Dan,
> Thanks for the reply! But infortunaley that fails with a "login failed for
> 'user' error."
> According to OSQL help: "If neither the -U or -P options are used, SQL
> Server 2000 attempts to connect using Windows Authentication Mode." Well
> that would be my network account & password and if I just enter OSQL -d
> master and then my network account password at the prompt, it fails (login
> failed for user). I know I'm correctly entering my current network account
> password.
> Any ideas?
> Thanks
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:Oex4GfRwFHA.464@.TK2MSFTNGP15.phx.gbl...
>|||I just had the same problem, and used this same solution. Deleted a
database, didn't realise it was my default DB (or that it mattered), and
couldn't figure out the account credentials problem I was having using the
command line suggestions found elsewhere. Was using a domain admin account.
Thanks very much!
Bryan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u9z7NBewFHA.2540@.TK2MSFTNGP09.phx.gbl...
> The example I posted assumed a SQL login. Like Tibor mentioned, you can
> specify '-E' to establish a trusted connection using your current Windows
> account. You never need to specify a Windows account with the '-E'
> parameter but you still need to specify the name of the account to
> sp_defaultdb. For a local Windows account:
> OSQL -d master -E -Q"EXEC sp_defaultdb 'MyMachine\MyAccount','master'"
> or for a domain account:
> OSQL -d master -E -Q"EXEC sp_defaultdb 'MyDomain\MyAccount','master'"
> If your SQL Server access is via membership of the local Administrators
> group, you'll need to change the default database for that group instead:
> OSQL -d master -E -Q"EXEC sp_defaultdb 'BUILTIN\Administrators','master'"
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Brent Stevenson" <essexbs@.insightbb.com> wrote in message
> news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
>

"cannot open user default database. Login failed"

When attempting to connect to my local instance of SQL server I am getting this error message: "cannot open user default database. Login failed".
My OS is WinXp v2002 SP2. This issue started after I deleted a database on my local server, prior to that it was working fine.
Thanks
It looks like you deleted the database that was the default database for
your login. One method to fix the problem is to connect using the OSQL
command-line utility, overriding the default database. You can then change
the default DB to one that exists.
The example below connects to the local server with SQL authentication and
changes the default database to 'master':
OSQL -d master -U MyLogin -P MyPassword -Q"EXEC sp_defaultdb 'MyLogin'
,'master'"
Hope this helps.
Dan Guzman
SQL Server MVP
"Brent Stevenson" <essexbs@.insightbb.com> wrote in message
news:u6aIYXRwFHA.3864@.TK2MSFTNGP12.phx.gbl...
When attempting to connect to my local instance of SQL server I am getting
this error message: "cannot open user default database. Login failed".
My OS is WinXp v2002 SP2. This issue started after I deleted a database on
my local server, prior to that it was working fine.
Thanks
|||Dan,
Thanks for the reply! But infortunaley that fails with a "login failed for
'user' error."
According to OSQL help: "If neither the -U or -P options are used, SQL
Server 2000 attempts to connect using Windows Authentication Mode." Well
that would be my network account & password and if I just enter OSQL -d
master and then my network account password at the prompt, it fails (login
failed for user). I know I'm correctly entering my current network account
password.
Any ideas?
Thanks
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:Oex4GfRwFHA.464@.TK2MSFTNGP15.phx.gbl...
> It looks like you deleted the database that was the default database for
> your login. One method to fix the problem is to connect using the OSQL
> command-line utility, overriding the default database. You can then
> change the default DB to one that exists.
> The example below connects to the local server with SQL authentication and
> changes the default database to 'master':
> OSQL -d master -U MyLogin -P MyPassword -Q"EXEC sp_defaultdb 'MyLogin'
> ,'master'"
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Brent Stevenson" <essexbs@.insightbb.com> wrote in message
> news:u6aIYXRwFHA.3864@.TK2MSFTNGP12.phx.gbl...
> When attempting to connect to my local instance of SQL server I am getting
> this error message: "cannot open user default database. Login failed".
> My OS is WinXp v2002 SP2. This issue started after I deleted a database
> on my local server, prior to that it was working fine.
> Thanks
>
|||My machines gives an error if I don't use -U or -E. Did you try using the -E switch to login using
your Windows account?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brent Stevenson" <essexbs@.insightbb.com> wrote in message
news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
> Dan,
> Thanks for the reply! But infortunaley that fails with a "login failed for 'user' error."
> According to OSQL help: "If neither the -U or -P options are used, SQL Server 2000 attempts to
> connect using Windows Authentication Mode." Well that would be my network account & password and
> if I just enter OSQL -d master and then my network account password at the prompt, it fails (login
> failed for user). I know I'm correctly entering my current network account password.
> Any ideas?
> Thanks
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:Oex4GfRwFHA.464@.TK2MSFTNGP15.phx.gbl...
>
|||Using the -E go me in & allowed me to change my default DB & resolve the
issue.
Thanks a million!! Have a good day.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23vKLtxdwFHA.3556@.TK2MSFTNGP12.phx.gbl...
> My machines gives an error if I don't use -U or -E. Did you try using
> the -E switch to login using your Windows account?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Brent Stevenson" <essexbs@.insightbb.com> wrote in message
> news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
>
|||The example I posted assumed a SQL login. Like Tibor mentioned, you can
specify '-E' to establish a trusted connection using your current Windows
account. You never need to specify a Windows account with the '-E'
parameter but you still need to specify the name of the account to
sp_defaultdb. For a local Windows account:
OSQL -d master -E -Q"EXEC sp_defaultdb 'MyMachine\MyAccount','master'"
or for a domain account:
OSQL -d master -E -Q"EXEC sp_defaultdb 'MyDomain\MyAccount','master'"
If your SQL Server access is via membership of the local Administrators
group, you'll need to change the default database for that group instead:
OSQL -d master -E -Q"EXEC sp_defaultdb 'BUILTIN\Administrators','master'"
Hope this helps.
Dan Guzman
SQL Server MVP
"Brent Stevenson" <essexbs@.insightbb.com> wrote in message
news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
> Dan,
> Thanks for the reply! But infortunaley that fails with a "login failed for
> 'user' error."
> According to OSQL help: "If neither the -U or -P options are used, SQL
> Server 2000 attempts to connect using Windows Authentication Mode." Well
> that would be my network account & password and if I just enter OSQL -d
> master and then my network account password at the prompt, it fails (login
> failed for user). I know I'm correctly entering my current network account
> password.
> Any ideas?
> Thanks
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:Oex4GfRwFHA.464@.TK2MSFTNGP15.phx.gbl...
>
|||I just had the same problem, and used this same solution. Deleted a
database, didn't realise it was my default DB (or that it mattered), and
couldn't figure out the account credentials problem I was having using the
command line suggestions found elsewhere. Was using a domain admin account.
Thanks very much!
Bryan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:u9z7NBewFHA.2540@.TK2MSFTNGP09.phx.gbl...
> The example I posted assumed a SQL login. Like Tibor mentioned, you can
> specify '-E' to establish a trusted connection using your current Windows
> account. You never need to specify a Windows account with the '-E'
> parameter but you still need to specify the name of the account to
> sp_defaultdb. For a local Windows account:
> OSQL -d master -E -Q"EXEC sp_defaultdb 'MyMachine\MyAccount','master'"
> or for a domain account:
> OSQL -d master -E -Q"EXEC sp_defaultdb 'MyDomain\MyAccount','master'"
> If your SQL Server access is via membership of the local Administrators
> group, you'll need to change the default database for that group instead:
> OSQL -d master -E -Q"EXEC sp_defaultdb 'BUILTIN\Administrators','master'"
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Brent Stevenson" <essexbs@.insightbb.com> wrote in message
> news:OCxkkudwFHA.1028@.TK2MSFTNGP12.phx.gbl...
>