hi,
I recently added a new login/pwd for a database I couldnt connect through my
asp application. Now I can, which is nice. But, now I can't connect to other
databases. I have an adp project and when I try to pull it up, I get the
message that there's a problem connecting. I do get it , but it says
"disconnected" at the top of the Access application. My question is this:
can I have a database that requires windows and sql server authentication,
then one that only requires windows authentication connected to the same
server? Could this be where my problem is? Should I remove that sql server
authentication ?
thanks-Hi Leo,
Thank you for using MSDN Managed Newsgroup Support.
From you description, my understanding of this issue is: You want to use
the SQL authentication to connect to the SQL server in the access adp
project but all the application is disconnected. If I misunderstood your
concern, please feel free to let me know.
If you could connect to the SQL Server in ASP application with your SQL
account, this account should be OK. As for the disconnected issue in
Access, I would like to know some information:
1. What's the Office Version and if you have applied the latest Services
Pack of Office?
2. If you use other SQL login account, does this issue appeared? If you use
SA account, does this issue appeared? What about using Windows account?
3. What's the SQL Server Version? Is SQL 2000 or SQL 7.0 or SQL 2005?
Please let me know the information so that I can provide further assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
To answer your questions I am using:
1. Ms Office 2003 SP1
2. SQL Server 2000
I can't connect to any of the databases in Enterprise Manager today. I also
cannot connect to my database via the ASP application. Here's what I did:
1. I had a database that I could not connect to. Somebody suggested that I
set up a sql authentication for it and use that in the asp code. I did, it
worked. However,
after that, I could not open my other database ( which I use in an ade
application). This was working great before - I used windows authentication
only for this one.
2. Because of my problem, i thought if I added the user/password on my SQL
authentication access to my other database, I would be ok. Well, now I am in
worse shape. I tried to connect to each of the databases to Test the
connection in "Administrative Tools", but my test fails all the time. How d
o
I connect those databases back to Enterprise Manager, so I can see them? I
have a bad feeling that I had to start all over again from scratch.
thanks,
Maggie
"Wei Lu [MSFT]" wrote:
> Hi Leo,
> Thank you for using MSDN Managed Newsgroup Support.
> From you description, my understanding of this issue is: You want to use
> the SQL authentication to connect to the SQL server in the access adp
> project but all the application is disconnected. If I misunderstood your
> concern, please feel free to let me know.
> If you could connect to the SQL Server in ASP application with your SQL
> account, this account should be OK. As for the disconnected issue in
> Access, I would like to know some information:
> 1. What's the Office Version and if you have applied the latest Services
> Pack of Office?
> 2. If you use other SQL login account, does this issue appeared? If you us
e
> SA account, does this issue appeared? What about using Windows account?
> 3. What's the SQL Server Version? Is SQL 2000 or SQL 7.0 or SQL 2005?
> Please let me know the information so that I can provide further assistanc
e.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||Hi Maggie,
Thank you for the update.
From the symptom you meet, I suggest you to make sure the account you use
to connect to the sql server have proper permission to access all the
databases. Please try to login the computer which host SQL Server as the
local administrator and try to connect to the SQL Server to see does all
the database is there. Also, you could use the SA account to connect to the
SQL Server.
If so, please goto the Security section to add the SQL account to the
sysadmin server role to check does this issue appeared or not.
Please let me know the result so that I can provide further assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||hi Wei,
I had to uninstall Sql Server and reinstall it because I was never able to
access the server. Each time I tried to, it would give me an error message
and I didn't understand what I could have done anyway. It's very confusing t
o
me because I never worked with Sql before!
I do have one question though. If I set up Sql Server ( on the install ) as
windows authentication , then add another login/password to access a new
database, then attach it to this server, what changes do I make to the serve
r
properties?
Do I change it to mixed mode? How/where do I do that? Or do I set it up on
mixed mode first?
My second question is: if I do set up an additional login/password to
access a database( because I must do this in my ASP script ), what affect
does this have on the other databases? Do I give this new login/psswd acces
s
to the other pre-existing datbases?
thanks -
"Wei Lu [MSFT]" wrote:
> Hi Maggie,
> Thank you for the update.
> From the symptom you meet, I suggest you to make sure the account you use
> to connect to the sql server have proper permission to access all the
> databases. Please try to login the computer which host SQL Server as the
> local administrator and try to connect to the SQL Server to see does all
> the database is there. Also, you could use the SA account to connect to th
e
> SQL Server.
> If so, please goto the Security section to add the SQL account to the
> sysadmin server role to check does this issue appeared or not.
> Please let me know the result so that I can provide further assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Maggie,
Thank you for the update.
For the first question, you need to use Mixed Mode to enable to use the SQL
Authentication. You could set it up when you install the SQL Server. Also,
you could change it after installation.
To change the Authentication mode, please do the following:
1. Open the Enterprise Manager, expand the server group to find your
server, right-click and click Properties.
2. Click Security Tab, and in the Authentication section, check to select
SQL Server and Windows. Then Click OK.
3. Restart the SQL Server.
For your second question, when you set the Login to access a database, if
you do not add it to any Server Role, by default, it could not access
other databases.
But you could configure this in the Database Access Tab of the New Login
Dialogbox.
Here is the article for your reference:
SQL Server Login Properties - New Login
http://msdn.microsoft.com/library/d...-us/entrmgr/em_
76zy.asp
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment