Re: Connecting to SQL from a Windows Service

Hi Rick, I ran the sql script and all looks fine, the Login hasaccess and
points to my DB. I looked into the Event Log and found that when my service
starts, it logsin (connects) twice. The 1st succeeds, the 2nd fails and SQL
does not open the DB. This situation occurs only from bootup.

If I start the service manually, the Event Log shows:
1. 1st Login succeeds.
2. SQL opens my DB.
3. 2ne Login succeeds.

I next added a Sleep for 10sec at the top of my OnStart() event of my
service. Now when I bbot and the service starts, all works fine. The Event
Log sequences like above.

I do have my service dependant on MSSQL$SQLEXPRESS, and I do see in the
Event Log that SQL Express is "Ready to accept client connections..." before
my service attempts to Login. What am I missing? Do I need to make my
service dependant on something else?

I did save off the Event Logs if you are interested.

RML





"Rick Byham, (MSFT)" wrote:

When you are connected to SQL Server as "Windows (XP Pro) as an Admin" and
you run the query:
USE master
GO
SELECT * FROM syslogins
WHERE name = 'NT AUTHORITY\SYSTEM'
GO
Does it return a row for that login?
And most of the values should look like your login: denylogin = 0, hasaccess
= 1, dbname is probably master or your desired database.
And after login, does the 'NT AUTHORITY\SYSTEM' has access to the correct
database as a user?

Also, You can try turning on login auditing in SQL Server and then check the
SQL Server error log. Maybe you will see more info about the login attempt.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"RML" <RML@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E21B3350-9477-4DCE-8E64-3690FFB2BAD3@xxxxxxxxxxxxxxxx
Hi all, I have written a Windows Service that attempts to connect to an
SQL
2005 Express Database when started. The login always fails. The login
uses
Windows Authentification (NT AUTHORITY/SYSTEM user).

I also tried connecting using the "sa" SQL Server login, and it still
fails.

If I log into Windows (XP Pro) as an Admin, and manually start the
service,
it connect Ok.

I thought that maybe the SQL Server service "MSSQL$SQLEXPRESS" may not be
started yet when my service attempts to connect, but the Evetn Log show it
is
started before my service starts. Also, my service is Dependant on
MSSQL$SQLEXPRESS.

Can anyone point me in the right direction.

RML

.

Relevant Pages

  • Re: catalog is empty after populating
    ... By chance did you or someone else remove the BUILTIN\Administrator login? ... Source: Microsoft Search ... SQL0002400005> because there is no access to the crawl ... >Hilary's referring to the Window's Application Event log ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Slow Login with Cached Credentials
    ... might relate to my issue of "Slow Login with Cached Credentials" ... Of course when they are on the network and there is a domain controller ... in the event log. ... REM Disconnect existing network mappings - do not prompt the user ...
    (microsoft.public.windowsxp.general)
  • Re: Windows XP Service Pack 2 SAS Application Error
    ... There is nothing else unusual in the event log at that time. ... We are having some trouble on Windows XP Service Pack 2. ... process of updating all our computers from Windows XP Service Pack 1 to ... When certain users attempt to login, they receive an error after they ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Connecting to SQL from a Windows Service
    ... There is probably some way to debug this, but that's deeper Windows knowledge than I can dredge up right now. ... I looked into the Event Log and found that when my service ... 1st Login succeeds. ... You can try turning on login auditing in SQL Server and then check the ...
    (microsoft.public.sqlserver.connect)
  • Re: Authentication problem continued
    ... application pool? ... Login failures are logged to the Application event log therefore try to ... SQL Server is configured for Windows Authentication only and not mixed ...
    (microsoft.public.dotnet.framework.aspnet)
Loading