Users Cannot Access DB

Question

Post reply

Users Cannot Access DB

Richard L. Lichvar

SSC Enthusiast

Points: 190
More actions
August 16, 2005 at 11:30 am

#152514

We have a 3rd party application which uses a SQL Server 2000 DB. I recently ported/replicated this application to a new server. Last week the user was having no problems with the application. Today, the user can't even log into the app (which uses SQL Server authorization). The user used to use sa; however, that isn't even working now. I also added this user's domain login account to the user list. User still can't log in. Being a SQL Server admin relative newbie, I'm not sure where to look next. Could this be a permssions problem somewhere?
Oh, yes, I did use DTS to copy over some stored procedures; but other than that, nothing has changed from when the user could access the db.

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 1

Check if the users/login are still on the server. What's the server's authentication mode?

Richard L. Lichvar SSC Enthusiast Points: 190 More actions · Answer 2

Mode is mixed. Not sure what you mean "if users/login are still on the server." No users are logged into that server right now.

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 3

When you transfer objects, you also transfer the logins by default, so the old ones might have been dropped. Can't you login to the server yourself using the sa account?

Anurag Nayar Mr or Mrs. 500 Points: 515 More actions · Answer 4

Hi, I agree with Remi. The most possible cause is that while running DTS logins also get transferred which may have deleted your logins.

Try setting up a new login, give access to the database and try login from query analyser. If it works then there is no problem with SQL Server.

Next step should be to setup a new login and user account for usage through application. If this fails , your application may have a problem.

Also, check if the setting of network library is matching on Client machine with Server. (Use Client Network utility at client machine and server network utility at srever machine)

Hope this helps..

Anurag

Richard L. Lichvar SSC Enthusiast Points: 190 More actions · Answer 5

Problem resolved. Turned out to be another issue. Some how the contents of the entire DB got wiped. In any case, we had a recent backup from which everything was restored and we are now operating correctly.

Many thanks to all for the help! I actually learned a great deal through this! I may become a SQL DBA yet!

Rich

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 6

Can you rerun the dts package and see if that's what whipped out the db in the first place?

Richard L. Lichvar SSC Enthusiast Points: 190 More actions · Answer 7

I guess I could, but I wouldn't want to do so right now. It's the old "if it ain't broke, don't fix it" thing.

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 8

You're not trying to fix it... maybe you'd be better off trying it as soons as you can without disrupting normal activities.

homebrew01 SSC Guru Points: 55548 More actions · Answer 9

" ..... The user used to use sa ..... "

I assume this isn't allowed anymore ? The sa password should be secure & available to the DBA only

Richard L. Lichvar SSC Enthusiast Points: 190 More actions · Answer 10

uh, ummm, well, when I can finally wrest the application away from the main user (who is also the application administrator since that is where the users for the app are actually managed rather than directly in SQL Server) again, I will do so.