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 |
|
Lester Vincent
Starting Member
22 Posts |
 Posted - 2005-12-26 : 07:46:23
|
 Help needed urgently, people! I have upsized an Access app to SQL Server and have just started working on creating Stored procedures, User-defined functions, etc.My database is on my laptop only, and in the SQL Server group, (local) (Windows NT). I tried to get the Query Analyser/Debug process working, so I could set break points and step through the code. However, these were greyed out and I was getting the SQL Query Analyser Message, "SP debugging may not work properly if you log on as 'Local System Account' while SQL Server is configured to run as a service.. You can open Event Viwer to see details. Do you wish to continue?" (Buttons for Yes, No, and Cancel).I consulted Robert Vieira's book, "SQL Server 2000 Programming" (pages 418-420) on 'Setting up SQL Server for Debugging", which stated I should "use an actual login account" instead of the LocalSystem account. I followed his instructions, and 1. In Enterprise Manager, right-clicked on "(local) (Windows NT)" server, selected "Properties" and clicked on the "Security" tab.2. At Start and run SQL Server in the following Account, I followed advice, (using "Windows Authentication") and selected the "This Account" option and proceeded to try and enter an account and password. The end result is that this somehow failed and NOW, I cannot get SQL Server Agent to open at all.SQL Server Agent shows the Red square instead of green and when I try to open it, THE FOLLOWING ERROR MESSAGE DISPLAYS: -[SERVICE CONTROL FAILURE]"An error 1069 - (The service did not start due to a logon failure) occurred while performing this service operation on the MSSQL Service."If I open Enterprise Manager, I can get to SQL Server Group, and it displays "(local) (Windows NT)" , but with the red (ie Closed) sqare instead of Green. Is this a matter of deleting a registration and re-creating it? If so, does this destroy my upsized database?Can somebody please advise what I should do to recover the situation.PS, I also tried changing from Windows Authentication to SQL Server password, without effect.(When this database is completed and running, I plan to install it on a Server with 12-15 workstation clients. Not a good start to SQL Server!!!) |
|
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2005-12-26 : 08:15:52
|
| 1) GO to Run2) Type services.msc3) Right click MSSQLSERVER and choose properties4) Go to Logon Tab5) Check "This account" and type-in the same passwprd And Try again.RegardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
 |
|
|
Lester Vincent
Starting Member
22 Posts |
Posted - 2005-12-26 : 08:51:42
|
| Thank you very much Sachin.I tried the steps you stated. At first, I selected "This Account" and entered my password, but it still kicked me out. I think I may not have properly set up a User Account, but thought I had done so correctly.I then selected "Local System Account" and within that, clicked "Allow ststem to interact with desktop".This, at least got me back in (thanks for that! big relief!).However, I still cannot use the Query Analyser Debug features within "Local System Account", which is a pity.Can you suggest a way that I can achieve this please?By the way, I do appreciate your prompt reply, especially the day after Christmas, when most people would be in holiday mode. Kind regards,Lester Vincent |
|
|
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2005-12-26 : 23:49:32
|
| Hi Lester,This should have worked as it works when I change from my machine. Hope u type-in the same passwrd which u have for user. If not lets repeat the task from scratch1) Open enterprise manager.2) Expand local registration3) Expand the security folder4) Click in Login5) Choose sa as login for which u want to change the password. 6) Right Click and go to properties7) Type in the password for example "abcde". It will ask for confirmation, so type again "abcde".If you are not able to do this as the sql server agent is coming as stopped (red). Right click sql server agent and go to properties and check if its using sql server account. Also change the password here to "abcde" for the sa. Ignore in case of error. Now go to the services by the same steps which I have specified in my early thread above.1) Right click MSSQLSERVER and choose properties2) Go to Logon Tab3) Check "This account" and type-in "abcde" in password.Now try to login to sql query analyser for sa login id. Also check if the SQL server agent in Enterprise manager is working now after changes.regardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
|
|
|
Lester Vincent
Starting Member
22 Posts |
Posted - 2006-01-04 : 23:25:57
|
| Thank you, Sachin. I did exactly as you said, but got no further with it. Tried multiple times, tried exiting the machine, tried stopping and re-starting SQL Server Agent. It doesn't lock me out now, but I'm still getting the following dialog window: -"SP debugging may not work properly if you log on as 'Local System Account' while SQL Server is configured to run as a service.. You can open Event Viwer to see details. Do you wish to continue?" (Buttons for Yes, No, and Cancel).I have just completed a Stored Proc which calls a 120-line function whicvh looks quite OK (reproduced from a VBA function that has worked for me for years!) butas UDFs do not allow using "PRINT" statements, I'm stopped in my tracks without being able to use the DEBUG in Query Analyser to step through the code line-by-line, as I can in VBA code. Is there something else I'm not doing, or that I should check on, to get the debugger going?It's getting very urgent now. Have gone as far as I can go without the debugger.Thanks so far, Sachin.Lester Vincent |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
|
|
|
|
|
|
|
Kicked Out of SQL Server - Help Please !! Urgent