Welcome to dbFreaks.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.1..

  
   Database Help (Home) -> Programming RSS
Next:  Syntax error converting from a character string t..  
Author Message
david

External


Since: May 01, 2008
Posts: 3



(Msg. 1) Posted: Thu May 01, 2008 11:35 am
Post subject: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.168.16.2] & Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database
Archived from groups: microsoft>public>sqlserver>programming (more info?)
It's been suggested that I post here rather than in the windows.server.sbs

WIN2003SBS Premium R2

Help!

This error is appearing every one minute when SQL Server and SQL Server
Agent are running (but not when not):

Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Date: 30/04/2008
Time: 23:19:57
User: NT AUTHORITY\SYSTEM
Computer: xxxxxxxx
Description:
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]

This from the error logs:

2008-05-01 11:01:51.03 Logon Error: 18456, Severity: 14, State: 16.
2008-05-01 11:01:51.03 Logon Login failed for user 'NT
AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]



Also this error appears at 12 hourly intervals

Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 01/05/2008
Time: 01:55:25
User: N/A
Computer: xxxxxxxx
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report
server database.


NT Authority\System is in the Domain Admins group and has a sysadmin role.

The developer tells me that he has assigned a sysadmin password.

No idea whatsoever about SQL and I will need pretty explicit instructions.

Any assistance gratefully received.


--
David @ Solsletta

 >> Stay informed about: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.1.. 
Back to top
Login to vote
Uri Dimant

External


Since: Aug 24, 2003
Posts: 1744



(Msg. 2) Posted: Thu May 01, 2008 2:10 pm
Post subject: Re: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.168.16.2] & Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
David
Is it database (login tried connect to) exists in the database? What is a
default database to login for this account?


"David @ Solsletta" wrote in message

> It's been suggested that I post here rather than in the windows.server.sbs
>
> WIN2003SBS Premium R2
>
> Help!
>
> This error is appearing every one minute when SQL Server and SQL Server
> Agent are running (but not when not):
>
> Event Type: Failure Audit
> Event Source: MSSQLSERVER
> Event Category: (4)
> Event ID: 18456
> Date: 30/04/2008
> Time: 23:19:57
> User: NT AUTHORITY\SYSTEM
> Computer: xxxxxxxx
> Description:
> Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>
> This from the error logs:
>
> 2008-05-01 11:01:51.03 Logon Error: 18456, Severity: 14, State: 16.
> 2008-05-01 11:01:51.03 Logon Login failed for user 'NT
> AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>
>
>
> Also this error appears at 12 hourly intervals
>
> Event Type: Error
> Event Source: Report Server Windows Service (MSSQLSERVER)
> Event Category: Management
> Event ID: 107
> Date: 01/05/2008
> Time: 01:55:25
> User: N/A
> Computer: xxxxxxxx
> Description:
> Report Server Windows Service (MSSQLSERVER) cannot connect to the report
> server database.
>
>
> NT Authority\System is in the Domain Admins group and has a sysadmin role.
>
> The developer tells me that he has assigned a sysadmin password.
>
> No idea whatsoever about SQL and I will need pretty explicit instructions.
>
> Any assistance gratefully received.
>
>
> --
> David @ Solsletta

 >> Stay informed about: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.1.. 
Back to top
Login to vote
david

External


Since: May 01, 2008
Posts: 3



(Msg. 3) Posted: Thu May 01, 2008 2:10 pm
Post subject: Re: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.168.16.2] & Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Uri

Thanks for the prompt response.

I'm not sure I understand the first question. Does the database that the
user attempted to login to exist - how would I check?

I also don't know how to determine which is the default login.

I assume I'm supposed to looking in the SWL Server Management Studio?

Sorry - not very helpful.

--
David @ Solsletta
"Uri Dimant" wrote in message

> David
> Is it database (login tried connect to) exists in the database? What is a
> default database to login for this account?
>
>
> "David @ Solsletta" wrote in message
>
>> It's been suggested that I post here rather than in the
>> windows.server.sbs
>>
>> WIN2003SBS Premium R2
>>
>> Help!
>>
>> This error is appearing every one minute when SQL Server and SQL Server
>> Agent are running (but not when not):
>>
>> Event Type: Failure Audit
>> Event Source: MSSQLSERVER
>> Event Category: (4)
>> Event ID: 18456
>> Date: 30/04/2008
>> Time: 23:19:57
>> User: NT AUTHORITY\SYSTEM
>> Computer: xxxxxxxx
>> Description:
>> Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>>
>> This from the error logs:
>>
>> 2008-05-01 11:01:51.03 Logon Error: 18456, Severity: 14, State: 16.
>> 2008-05-01 11:01:51.03 Logon Login failed for user 'NT
>> AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>>
>>
>>
>> Also this error appears at 12 hourly intervals
>>
>> Event Type: Error
>> Event Source: Report Server Windows Service (MSSQLSERVER)
>> Event Category: Management
>> Event ID: 107
>> Date: 01/05/2008
>> Time: 01:55:25
>> User: N/A
>> Computer: xxxxxxxx
>> Description:
>> Report Server Windows Service (MSSQLSERVER) cannot connect to the report
>> server database.
>>
>>
>> NT Authority\System is in the Domain Admins group and has a sysadmin
>> role.
>>
>> The developer tells me that he has assigned a sysadmin password.
>>
>> No idea whatsoever about SQL and I will need pretty explicit
>> instructions.
>>
>> Any assistance gratefully received.
>>
>>
>> --
>> David @ Solsletta
>
>
>
 >> Stay informed about: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.1.. 
Back to top
Login to vote
Uri Dimant

External


Since: Aug 24, 2003
Posts: 1744



(Msg. 4) Posted: Thu May 01, 2008 4:11 pm
Post subject: Re: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.168.16.2] & Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
David
> I'm not sure I understand the first question. Does the database that the
> user attempted to login to exist - how would I check?
>
> I also don't know how to determine which is the default login.

BOL says
This example sets pubs as the default database for user Victoria.

EXEC sp_defaultdb 'Victoria', 'pubs'
"David @ Solsletta" wrote in message

> Uri
>
> Thanks for the prompt response.
>
> I'm not sure I understand the first question. Does the database that the
> user attempted to login to exist - how would I check?
>
> I also don't know how to determine which is the default login.
>
> I assume I'm supposed to looking in the SWL Server Management Studio?
>
> Sorry - not very helpful.
>
> --
> David @ Solsletta
> "Uri Dimant" wrote in message
>
>> David
>> Is it database (login tried connect to) exists in the database? What is a
>> default database to login for this account?
>>
>>
>> "David @ Solsletta" wrote in message
>>
>>> It's been suggested that I post here rather than in the
>>> windows.server.sbs
>>>
>>> WIN2003SBS Premium R2
>>>
>>> Help!
>>>
>>> This error is appearing every one minute when SQL Server and SQL Server
>>> Agent are running (but not when not):
>>>
>>> Event Type: Failure Audit
>>> Event Source: MSSQLSERVER
>>> Event Category: (4)
>>> Event ID: 18456
>>> Date: 30/04/2008
>>> Time: 23:19:57
>>> User: NT AUTHORITY\SYSTEM
>>> Computer: xxxxxxxx
>>> Description:
>>> Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>>>
>>> This from the error logs:
>>>
>>> 2008-05-01 11:01:51.03 Logon Error: 18456, Severity: 14, State:
>>> 16.
>>> 2008-05-01 11:01:51.03 Logon Login failed for user 'NT
>>> AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>>>
>>>
>>>
>>> Also this error appears at 12 hourly intervals
>>>
>>> Event Type: Error
>>> Event Source: Report Server Windows Service (MSSQLSERVER)
>>> Event Category: Management
>>> Event ID: 107
>>> Date: 01/05/2008
>>> Time: 01:55:25
>>> User: N/A
>>> Computer: xxxxxxxx
>>> Description:
>>> Report Server Windows Service (MSSQLSERVER) cannot connect to the report
>>> server database.
>>>
>>>
>>> NT Authority\System is in the Domain Admins group and has a sysadmin
>>> role.
>>>
>>> The developer tells me that he has assigned a sysadmin password.
>>>
>>> No idea whatsoever about SQL and I will need pretty explicit
>>> instructions.
>>>
>>> Any assistance gratefully received.
>>>
>>>
>>> --
>>> David @ Solsletta
>>
>>
>>
>
 >> Stay informed about: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.1.. 
Back to top
Login to vote
david

External


Since: May 01, 2008
Posts: 3



(Msg. 5) Posted: Tue May 20, 2008 11:32 pm
Post subject: Re: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.168.16.2] & Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Found it. SQL Reporting Services Configuration Manager hadn't been fully
configured.

--
David @ Solsletta
"Uri Dimant" wrote in message

> David
>> I'm not sure I understand the first question. Does the database that the
>> user attempted to login to exist - how would I check?
>>
>> I also don't know how to determine which is the default login.
>
> BOL says
> This example sets pubs as the default database for user Victoria.
>
> EXEC sp_defaultdb 'Victoria', 'pubs'
> "David @ Solsletta" wrote in message
>
>> Uri
>>
>> Thanks for the prompt response.
>>
>> I'm not sure I understand the first question. Does the database that the
>> user attempted to login to exist - how would I check?
>>
>> I also don't know how to determine which is the default login.
>>
>> I assume I'm supposed to looking in the SWL Server Management Studio?
>>
>> Sorry - not very helpful.
>>
>> --
>> David @ Solsletta
>> "Uri Dimant" wrote in message
>>
>>> David
>>> Is it database (login tried connect to) exists in the database? What is
>>> a default database to login for this account?
>>>
>>>
>>> "David @ Solsletta" wrote in message
>>>
>>>> It's been suggested that I post here rather than in the
>>>> windows.server.sbs
>>>>
>>>> WIN2003SBS Premium R2
>>>>
>>>> Help!
>>>>
>>>> This error is appearing every one minute when SQL Server and SQL Server
>>>> Agent are running (but not when not):
>>>>
>>>> Event Type: Failure Audit
>>>> Event Source: MSSQLSERVER
>>>> Event Category: (4)
>>>> Event ID: 18456
>>>> Date: 30/04/2008
>>>> Time: 23:19:57
>>>> User: NT AUTHORITY\SYSTEM
>>>> Computer: xxxxxxxx
>>>> Description:
>>>> Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>>>>
>>>> This from the error logs:
>>>>
>>>> 2008-05-01 11:01:51.03 Logon Error: 18456, Severity: 14, State:
>>>> 16.
>>>> 2008-05-01 11:01:51.03 Logon Login failed for user 'NT
>>>> AUTHORITY\SYSTEM'. [CLIENT: 192.168.16.2]
>>>>
>>>>
>>>>
>>>> Also this error appears at 12 hourly intervals
>>>>
>>>> Event Type: Error
>>>> Event Source: Report Server Windows Service (MSSQLSERVER)
>>>> Event Category: Management
>>>> Event ID: 107
>>>> Date: 01/05/2008
>>>> Time: 01:55:25
>>>> User: N/A
>>>> Computer: xxxxxxxx
>>>> Description:
>>>> Report Server Windows Service (MSSQLSERVER) cannot connect to the
>>>> report server database.
>>>>
>>>>
>>>> NT Authority\System is in the Domain Admins group and has a sysadmin
>>>> role.
>>>>
>>>> The developer tells me that he has assigned a sysadmin password.
>>>>
>>>> No idea whatsoever about SQL and I will need pretty explicit
>>>> instructions.
>>>>
>>>> Any assistance gratefully received.
>>>>
>>>>
>>>> --
>>>> David @ Solsletta
>>>
>>>
>>>
>>
>
>
>
 >> Stay informed about: Login failed for user 'NT AUTHORITYSYSTEM'. [CLIENT: 192.1.. 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Login failed for user 'sa' - I recently started to log failed login for sql server 2000. When I check the log, I get "Login failed for user 'sa'" about 25 times a day. The timings of failed login attempts are consistent (always occur at the same time of the day). This...

connect database user to security login user - After restore off a database the user under security logins was not created. The user under Database and users was created, but that user MUST bee the same user under security logins, if i try to make a new user with same name under logins, thats ok,....

Which User is the current user authenticating with ? - - This needs to work under SQL 2000 and SQL 2005. - Using Windows Authentication. I have an application which users SQL Users to provide additional security. When a user connect to the database using Windows Authentication, how can I found out which..

Write a BLOB failed - Hi, I have a problem with writing BLOB data into type of 'image' field. If the data size > ~280 MByte (< 2 GB) the operation failed. It is appear on SQL Server 2000 and 2005 (MSDE and express also). Detailes : column type : image Server : SQL Se...

SQL Login - Hi, Many thx for your advises duds, it is very helpful, now i when i login to the SQL Express I can't create database/table there is an error saying i don't permission to create a database, and when I'm going to logins to create another user with..
   Database Help (Home) -> Programming All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]