help with emergency sp4 on sql server 2000

Question

help with emergency sp4 on sql server 2000

Betty Sun

SSCrazy

Points: 2442
More actions
September 17, 2006 at 12:05 am

#174227

Hi everyone,
Our site is down, because of our hosting company applied sql server 2000 sp4 on windows 2000 server.
right after it applied the service pack, our sql server database is down and no conn etc. When one technical support restart the server,
the obejcts like tables in database cannot be recognized from our asp pages anymore, data cannot be inserted into any database table and data cannot be pulled out correctly from database table through asp program, but I can run query and look at data through sql analyzer.
what is the problem, is it because of connection string? before this service pack 4, everything runs fine and we never had this kind of disaster.
I have connection string like this:
conn.Open "dsn=XXXXXX;uid=XXXXX;pwd=XXXXXX"
Is there any problem with my connection string with sp4 applied?
Can you please help?
Betty

Viewing 5 posts - 1 through 4 (of 4 total)

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

Sreejith Sreedharan SSCertifiable Points: 5403 More actions · Answer 1

I think the problem has to do with the fact that it has changed the authentication mode to windows only instead of Mixed mode authentication(instead of SQL Server and Window). Please change it and restart the SQL Server.

Thanks

Sreejith

Betty Sun SSCrazy Points: 2442 More actions · Answer 2

I checked property in enterprise manager, on the security tab.

SQL server and windows mode is selected?

Oh, God what should I do?

Betty

Vik Nat Hall of Fame Points: 3930 More actions · Answer 3

Drop and recreate your DSN - test DSN connection when creating as well

Betty Sun SSCrazy Points: 2442 More actions · Answer 4

You are really brilliant. Acutally I fixed yesterday and the case is exactly what you think.

I don't really know what happened after they applied sp4 to my sql server 2000.

I told my myself, I need to take a look at my testing database, I suddenly I found out that my live data get into my testing database and that tell me why some my production program gives invalid object error messge. You can image what will happen when you have production code running against testing database.

So I look at the ODBC set up and the original DSN is pointing to testing database instance instead of my origianl set up --> production database.

We have two database instances on our server. I guess they were not aware of it. One is testing server(MSDE), one is production server(sql server 2000), after the service pack is applied, something happened, I still don't know they manually did it, or system set up?

Thank you so much for your great idea.

Betty