March 7, 2004 at 10:34 am
I have been able to sucessfully register new server registrations with Win 98 and Win 2000 and SQL Server 2000 . We just replaced some of those computers with Win XP, and now cannot seem to complete the registration process (using NEW SQL Server Registration wizard). We are using the same login name and password, Windows Authentication...and contiually get an error message that says the user name is "null". I know the answer has to be simple, I have searched the MS knowledgebase with no luck. Can anyone help, or point me in a good direction. Thanks
March 7, 2004 at 10:56 am
Just so I understand, did you replace the machine that SQL server was on? Or just the client machines?
------------
Ray Higdon MCSE, MCDBA, CCNA
March 7, 2004 at 11:41 am
Only the client machines were replaced.
March 7, 2004 at 11:48 am
Are you able to register with a different known-good SQL account?
------------
Ray Higdon MCSE, MCDBA, CCNA
March 7, 2004 at 11:56 am
This might make you tremble. We are a small office, with 8 computers connected to SQL server. 4 clients are Win 98 second edition, 4 are Win 2000 Professional. All of the clients are logging on to SQL with the SAME username and password. It has worked for us for a long time. I can't seem to make this login work wiht the new XP clients. I did create a new SQL Server Authorization login (instead of the Windows Authorization), and try to register using that user name, but still couldn't logon using the wizard. It said the user was not authorized.
March 7, 2004 at 3:59 pm
Just for kicks I would update the MDAC's, you can get the latest from MS website.
Also, this may help - http://support.microsoft.com/default.aspx?scid=kb;en-us;812817
------------
Ray Higdon MCSE, MCDBA, CCNA
March 8, 2004 at 12:10 am
<<We are using the same login name and password, Windows Authentication...and contiually get an error message that says the user name is "null". >>
So, are you using SQL-authentication _or_ Windows-authentication ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 8, 2004 at 2:35 am
what about:
1- installing SP1 on win XP clients
2- and installing SQL Server sp3a on server
3- install MDAC 2.7 RTM refresh on Server and clients machine ... and see what is happened ..
does the user you logon in EM on clients is in a domain admins group or not ? if not you must log in with one of the domain admins
I hope this help u.
Alamir Mohamed
Alamir_mohamed@yahoo.com
March 8, 2004 at 5:35 am
I ran into a problem with XP and SQL 2000. I installed MDAC 2.8 and it resolved some issues. Onr thing i did run into with XP is restoring a database. It became suspect after i restored from a previous nights backup. just a heads up.
March 8, 2004 at 6:09 am
of course to install MDAC and its SP to connect correctly to SQL Server..
also there is a topic in SQL BOL that is "Resetting the Suspect Status" that tells you how to get again into Normal production mode .. by using this :
sp_resetstatus database_name
also are you sure that your ldf is found ?? because database go into suspect also if ldf file is moved.
I hope this help u
Alamir Mohamed
Alamir_mohamed@yahoo.com
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply