"Ken Powers" <KenPowers@discussions.microsoft.com> wrote in message
news:C5AD756A-F4C6-4252-8CCB-48DCF0C04108@microsoft.com...
>I have what I think is an issue with Reporting Services. We have installed
> SQL Server 2005 Reporting Services on a Windows 2003 Server. Both SQL
> Server
> and Windows 2003 have been upgraded to SP1.
>
> My SQL Server is set to report failed login attempts. My EventViewer is
> constantly reporting the following error:
>
> Event Type: Failure Audit
> Event Source: MSSQLSERVER
> Event Category: (4)
> Event ID: 18456
> Date: 07/28/2006
> Time: 09:42:52
> User: NT AUTHORITY\ANONYMOUS LOGON
> Computer: YKCLNSC
> Description:
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.7.54.59]
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H......
> 0008: 08 00 00 00 59 00 4b 00 ....Y.K.
> 0010: 43 00 4c 00 4e 00 53 00 C.L.N.S.
> 0018: 43 00 00 00 07 00 00 00 C.......
> 0020: 6d 00 61 00 73 00 74 00 m.a.s.t.
> 0028: 65 00 72 00 00 00 e.r...
>
>
> IIS is also installed on this server, and anonymous access has been
> disabled.
>
> Here are the steps I have tried to resolve this error:
>
> 1) Grant the following accounts access to the instance of SQL Server:
>
> "NT AUTHORITY\ANONYMOUS LOGON", "NT AUTHORITY\NETWORK SERVICE", "NT
> AUTHORITY\SYSTEM", "YKCLNSC\IUSR_YKCLNSC", "YKCLNSC\IWAM_YKCLNSC"
>
> 2) Grant these same accounts membership in the "public" role in the master
> database
>
> 3) Grant these accounts membership in the "db_datareader" role in the
> master
> database
>
> 4) Grant these accounts membership in the "db_datareader" and
> "db_datawriter" roles in the master database
>
> 4) Grant these accounts membership in the "db_datareader", "db_datawriter"
> and "RSExecRole" roles in the master database
>
> 5) Grant these accounts membership in the "db_owner" role in the master
> database.
>
> None of these steps has stopped this error from occurring. Can anyone out
> there give me additional suggestions?

"Bruce L-C [MVP]" wrote:

> Trying to get RS to work anonymously is a problem. The reason is that you
> will lose administration rights with Report Manager, because even though you
> might be an adminstrator it won't know that because you have set the website
> to be anonymous.
>
> Most domains have a group for all the users in the domain (in our domain it
> is called .... Users). I add that domain to a local group on the server and
> then add that into the appropriate role in Report Manager (RS uses roll
> based security).
>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Ken Powers" <KenPowers@discussions.microsoft.com> wrote in message
> news:C5AD756A-F4C6-4252-8CCB-48DCF0C04108@microsoft.com...
> >I have what I think is an issue with Reporting Services. We have installed
> > SQL Server 2005 Reporting Services on a Windows 2003 Server. Both SQL
> > Server
> > and Windows 2003 have been upgraded to SP1.
> >
> > My SQL Server is set to report failed login attempts. My EventViewer is
> > constantly reporting the following error:
> >
> > Event Type: Failure Audit
> > Event Source: MSSQLSERVER
> > Event Category: (4)
> > Event ID: 18456
> > Date: 07/28/2006
> > Time: 09:42:52
> > User: NT AUTHORITY\ANONYMOUS LOGON
> > Computer: YKCLNSC
> > Description:
> > Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.7.54.59]
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 18 48 00 00 0e 00 00 00 .H......
> > 0008: 08 00 00 00 59 00 4b 00 ....Y.K.
> > 0010: 43 00 4c 00 4e 00 53 00 C.L.N.S.
> > 0018: 43 00 00 00 07 00 00 00 C.......
> > 0020: 6d 00 61 00 73 00 74 00 m.a.s.t.
> > 0028: 65 00 72 00 00 00 e.r...
> >
> >
> > IIS is also installed on this server, and anonymous access has been
> > disabled.
> >
> > Here are the steps I have tried to resolve this error:
> >
> > 1) Grant the following accounts access to the instance of SQL Server:
> >
> > "NT AUTHORITY\ANONYMOUS LOGON", "NT AUTHORITY\NETWORK SERVICE", "NT
> > AUTHORITY\SYSTEM", "YKCLNSC\IUSR_YKCLNSC", "YKCLNSC\IWAM_YKCLNSC"
> >
> > 2) Grant these same accounts membership in the "public" role in the master
> > database
> >
> > 3) Grant these accounts membership in the "db_datareader" role in the
> > master
> > database
> >
> > 4) Grant these accounts membership in the "db_datareader" and
> > "db_datawriter" roles in the master database
> >
> > 4) Grant these accounts membership in the "db_datareader", "db_datawriter"
> > and "RSExecRole" roles in the master database
> >
> > 5) Grant these accounts membership in the "db_owner" role in the master
> > database.
> >
> > None of these steps has stopped this error from occurring. Can anyone out
> > there give me additional suggestions?
>
>