Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
wepe
Starting Member
2 Posts |
Posted - 2002-07-05 : 11:39:09
|
Hi dear reader,I have a problem with the MSDE. I can not create a login for an other user. It is possible to contact MSDE via ACCESS 2000 in the network under my account (I installed MSDE on an other computer also under my account). When I try to administer the MSDE with the help of a little tool which is using SQL-DMO, I receive the answer 'Invalid procedure call or argument' to any system stored procedure. Do you have an idea what is wrong there.Some additional and helpful information for you:- The tool is running on the same PC (Windows 2000) as MSDE - I am logged in as 'sa' without password- E.g. a statement which fails: EXEC sp_grantlogin '<domain>\<user>'- If I do not enter the correct names, the server answers with the proper error message.- It must be MSDE 1.0 (see the header of the error log below) >> 2002-07-05 13:27:55.70 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) >> Nov 27 1998 22:20:07 >> Copyright (c) 1988-1998 Microsoft Corporation >> MSDE on Windows NT 5.0 (Build 2195: Service Pack 2)I would appreciate any help to this matter. Many thanks in advance.wepe |
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-07-05 : 14:11:12
|
Maybe the tool has a bug with quotes?Try connecting using something you have written yourself or use query analyser to run the query.Try something simple like sp_who.==========================================Cursors are useful if you don't know sql.Beer is not cold and it isn't fizzy. |
|
|
wepe
Starting Member
2 Posts |
Posted - 2002-07-15 : 06:57:56
|
Thank you for your hints. The quotes were ok. But even the simple procedure sp_who return the answer 'Invalid procedure ...'. I used a tool loaded down from the page of swynk.com. Maybe I have to invest some more minutes to get familiar with this tool.Anyway, I got some idea from dBforums.com that helped me solving my problem. So I changed the login authentication to 'Mixed Authentication Mode' and administered SQL server with 'osql'. It worked quite well. wepe |
|
|
|
|
|