hi all - wonder if there is anyone out there who experiances what i am
experiancing? i run sql server 2005 on a machine with windows server 2003.
very small database collecting radius accounting data for about 40 adsl
users. the server has 2 gig ram on a 3ghz dual core machine 180gig drive
space on a raid 10 array and i constantly het the follwing error in the error
log

Access request for user ashcott@gomdsl.co.za was discarded.
Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
NAS-IP-Address = 196.43.27.23
NAS-Identifier = <not present>
Called-Station-Identifier = <not present>
Calling-Station-Identifier = <not present>
Client-Friendly-Name = Telkom8
Client-IP-Address = 196.43.3.86
NAS-Port-Type = Virtual
NAS-Port = 1110769935
Proxy-Policy-Name = Use Windows authentication for all users
Authentication-Provider = Windows
Authentication-Server = <undetermined>
Reason-Code = 80
Reason = The authentication or accounting record could not be written to
the log file location. Ensure that the log file location is accessible, has
available space, can be written to, and that the directory or SQL server name
is valid.

the radius packet it then discarded and any accounting data is lost. then a
minute or so later it is fine again. can then go ok for a day or so the oops
- all is lost for the space of a minute or two. times are very random and
pertains to random user information

i dont know if i am posting into the correct place even becasue i dont know
if it is an sql problem or server problem but any advice would be apretiated

thanks
--
Paul - South Africa

Well the app is obviously translating the error so it could be almost
anything. But my guess would be that the log file is autogrowing and it is
taking too long to grow and times out. Ensure that both the database and
transaction log files have plenty of free space in them at all times. Don't
shrink the files or turn on autoshrink or it will continue to happen. Also
change the autogrowth from a % to a fixed amount that can be grown in under
15 seconds.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> hi all - wonder if there is anyone out there who experiances what i am
> experiancing? i run sql server 2005 on a machine with windows server 2003.
> very small database collecting radius accounting data for about 40 adsl
> users. the server has 2 gig ram on a 3ghz dual core machine 180gig drive
> space on a raid 10 array and i constantly het the follwing error in the
> error
> log
>
> Access request for user ashcott@gomdsl.co.za was discarded.
> Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> NAS-IP-Address = 196.43.27.23
> NAS-Identifier = <not present>
> Called-Station-Identifier = <not present>
> Calling-Station-Identifier = <not present>
> Client-Friendly-Name = Telkom8
> Client-IP-Address = 196.43.3.86
> NAS-Port-Type = Virtual
> NAS-Port = 1110769935
> Proxy-Policy-Name = Use Windows authentication for all users
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Reason-Code = 80
> Reason = The authentication or accounting record could not be written to
> the log file location. Ensure that the log file location is accessible,
> has
> available space, can be written to, and that the directory or SQL server
> name
> is valid.
>
> the radius packet it then discarded and any accounting data is lost. then
> a
> minute or so later it is fine again. can then go ok for a day or so the
> oops
> - all is lost for the space of a minute or two. times are very random and
> pertains to random user information
>
> i dont know if i am posting into the correct place even becasue i dont
> know
> if it is an sql problem or server problem but any advice would be
> apretiated
>
> thanks
> --
> Paul - South Africa

Hi Andrew
Thanks for the advice
have changed the log file from 10% to 1 gig for its autogrowth, autoshrink
is not enabled unless it is enabled by default. it does have a restricted
growth in begabytes currently set at 2,097,152
the database itself is still set at 10 persent but unrestricted. the current
size on disk for these two files are database=47meg log=84meg and that is
with almost a year worth of data so you can see it is not a very busy database
i will monitor it now with the change and see if the problem improves

thanks again
paul
--
Paul - South Africa


"Andrew J. Kelly" wrote:

> Well the app is obviously translating the error so it could be almost
> anything. But my guess would be that the log file is autogrowing and it is
> taking too long to grow and times out. Ensure that both the database and
> transaction log files have plenty of free space in them at all times. Don't
> shrink the files or turn on autoshrink or it will continue to happen. Also
> change the autogrowth from a % to a fixed amount that can be grown in under
> 15 seconds.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> > hi all - wonder if there is anyone out there who experiances what i am
> > experiancing? i run sql server 2005 on a machine with windows server 2003.
> > very small database collecting radius accounting data for about 40 adsl
> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig drive
> > space on a raid 10 array and i constantly het the follwing error in the
> > error
> > log
> >
> > Access request for user ashcott@gomdsl.co.za was discarded.
> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> > NAS-IP-Address = 196.43.27.23
> > NAS-Identifier = <not present>
> > Called-Station-Identifier = <not present>
> > Calling-Station-Identifier = <not present>
> > Client-Friendly-Name = Telkom8
> > Client-IP-Address = 196.43.3.86
> > NAS-Port-Type = Virtual
> > NAS-Port = 1110769935
> > Proxy-Policy-Name = Use Windows authentication for all users
> > Authentication-Provider = Windows
> > Authentication-Server = <undetermined>
> > Reason-Code = 80
> > Reason = The authentication or accounting record could not be written to
> > the log file location. Ensure that the log file location is accessible,
> > has
> > available space, can be written to, and that the directory or SQL server
> > name
> > is valid.
> >
> > the radius packet it then discarded and any accounting data is lost. then
> > a
> > minute or so later it is fine again. can then go ok for a day or so the
> > oops
> > - all is lost for the space of a minute or two. times are very random and
> > pertains to random user information
> >
> > i dont know if i am posting into the correct place even becasue i dont
> > know
> > if it is an sql problem or server problem but any advice would be
> > apretiated
> >
> > thanks
> > --
> > Paul - South Africa
>
>

If the files are really that small then my assumption was probably wrong.
10% of 84MB would only be a growth of about 8MB and that should only take a
second or less. If the files were 10 or 20 GB's then that may be a
different story as the growth of even 1GB can take a while. So I recommend
you change that 1GB to around 50MB on a file that small. As for the
original issue that is hard to say since the app is translating the real
error message from SQL Server. I think you need to gather more details if
possible.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
news:B2729701-12CA-4133-8479-23036F6E3E81@microsoft.com...
> Hi Andrew
> Thanks for the advice
> have changed the log file from 10% to 1 gig for its autogrowth, autoshrink
> is not enabled unless it is enabled by default. it does have a restricted
> growth in begabytes currently set at 2,097,152
> the database itself is still set at 10 persent but unrestricted. the
> current
> size on disk for these two files are database=47meg log=84meg and that is
> with almost a year worth of data so you can see it is not a very busy
> database
> i will monitor it now with the change and see if the problem improves
>
> thanks again
> paul
> --
> Paul - South Africa
>
>
> "Andrew J. Kelly" wrote:
>
>> Well the app is obviously translating the error so it could be almost
>> anything. But my guess would be that the log file is autogrowing and it
>> is
>> taking too long to grow and times out. Ensure that both the database and
>> transaction log files have plenty of free space in them at all times.
>> Don't
>> shrink the files or turn on autoshrink or it will continue to happen.
>> Also
>> change the autogrowth from a % to a fixed amount that can be grown in
>> under
>> 15 seconds.
>>
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>>
>> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
>> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
>> > hi all - wonder if there is anyone out there who experiances what i am
>> > experiancing? i run sql server 2005 on a machine with windows server
>> > 2003.
>> > very small database collecting radius accounting data for about 40 adsl
>> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
>> > drive
>> > space on a raid 10 array and i constantly het the follwing error in the
>> > error
>> > log
>> >
>> > Access request for user ashcott@gomdsl.co.za was discarded.
>> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
>> > NAS-IP-Address = 196.43.27.23
>> > NAS-Identifier = <not present>
>> > Called-Station-Identifier = <not present>
>> > Calling-Station-Identifier = <not present>
>> > Client-Friendly-Name = Telkom8
>> > Client-IP-Address = 196.43.3.86
>> > NAS-Port-Type = Virtual
>> > NAS-Port = 1110769935
>> > Proxy-Policy-Name = Use Windows authentication for all users
>> > Authentication-Provider = Windows
>> > Authentication-Server = <undetermined>
>> > Reason-Code = 80
>> > Reason = The authentication or accounting record could not be written
>> > to
>> > the log file location. Ensure that the log file location is accessible,
>> > has
>> > available space, can be written to, and that the directory or SQL
>> > server
>> > name
>> > is valid.
>> >
>> > the radius packet it then discarded and any accounting data is lost.
>> > then
>> > a
>> > minute or so later it is fine again. can then go ok for a day or so the
>> > oops
>> > - all is lost for the space of a minute or two. times are very random
>> > and
>> > pertains to random user information
>> >
>> > i dont know if i am posting into the correct place even becasue i dont
>> > know
>> > if it is an sql problem or server problem but any advice would be
>> > apretiated
>> >
>> > thanks
>> > --
>> > Paul - South Africa
>>
>>

Hello again Andrew

made the changes as you suggested.
as far as gathering more details i would if i knew where to get them from ?
is it from within sql itself - log files perhaps. i dont quite know where to
look for any more detail

regards

paul
--
Paul - South Africa


"Andrew J. Kelly" wrote:

> If the files are really that small then my assumption was probably wrong.
> 10% of 84MB would only be a growth of about 8MB and that should only take a
> second or less. If the files were 10 or 20 GB's then that may be a
> different story as the growth of even 1GB can take a while. So I recommend
> you change that 1GB to around 50MB on a file that small. As for the
> original issue that is hard to say since the app is translating the real
> error message from SQL Server. I think you need to gather more details if
> possible.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> news:B2729701-12CA-4133-8479-23036F6E3E81@microsoft.com...
> > Hi Andrew
> > Thanks for the advice
> > have changed the log file from 10% to 1 gig for its autogrowth, autoshrink
> > is not enabled unless it is enabled by default. it does have a restricted
> > growth in begabytes currently set at 2,097,152
> > the database itself is still set at 10 persent but unrestricted. the
> > current
> > size on disk for these two files are database=47meg log=84meg and that is
> > with almost a year worth of data so you can see it is not a very busy
> > database
> > i will monitor it now with the change and see if the problem improves
> >
> > thanks again
> > paul
> > --
> > Paul - South Africa
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Well the app is obviously translating the error so it could be almost
> >> anything. But my guess would be that the log file is autogrowing and it
> >> is
> >> taking too long to grow and times out. Ensure that both the database and
> >> transaction log files have plenty of free space in them at all times.
> >> Don't
> >> shrink the files or turn on autoshrink or it will continue to happen.
> >> Also
> >> change the autogrowth from a % to a fixed amount that can be grown in
> >> under
> >> 15 seconds.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
> >>
> >> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> >> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> >> > hi all - wonder if there is anyone out there who experiances what i am
> >> > experiancing? i run sql server 2005 on a machine with windows server
> >> > 2003.
> >> > very small database collecting radius accounting data for about 40 adsl
> >> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
> >> > drive
> >> > space on a raid 10 array and i constantly het the follwing error in the
> >> > error
> >> > log
> >> >
> >> > Access request for user ashcott@gomdsl.co.za was discarded.
> >> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> >> > NAS-IP-Address = 196.43.27.23
> >> > NAS-Identifier = <not present>
> >> > Called-Station-Identifier = <not present>
> >> > Calling-Station-Identifier = <not present>
> >> > Client-Friendly-Name = Telkom8
> >> > Client-IP-Address = 196.43.3.86
> >> > NAS-Port-Type = Virtual
> >> > NAS-Port = 1110769935
> >> > Proxy-Policy-Name = Use Windows authentication for all users
> >> > Authentication-Provider = Windows
> >> > Authentication-Server = <undetermined>
> >> > Reason-Code = 80
> >> > Reason = The authentication or accounting record could not be written
> >> > to
> >> > the log file location. Ensure that the log file location is accessible,
> >> > has
> >> > available space, can be written to, and that the directory or SQL
> >> > server
> >> > name
> >> > is valid.
> >> >
> >> > the radius packet it then discarded and any accounting data is lost.
> >> > then
> >> > a
> >> > minute or so later it is fine again. can then go ok for a day or so the
> >> > oops
> >> > - all is lost for the space of a minute or two. times are very random
> >> > and
> >> > pertains to random user information
> >> >
> >> > i dont know if i am posting into the correct place even becasue i dont
> >> > know
> >> > if it is an sql problem or server problem but any advice would be
> >> > apretiated
> >> >
> >> > thanks
> >> > --
> >> > Paul - South Africa
> >>
> >>
>
>

Paul,

Well you can check the Windows Event log and there may be an error message
there depending on the severity and how the app works. I would also look in
the SQL Error log as well. But you may have to use profiler with the error
and attention events to see what is actually generated. I would also ping
the makers of the app and see what they have to say.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
news:4C771DC0-2FFE-4AA0-AE0C-ACDD71310A2A@microsoft.com...
> Hello again Andrew
>
> made the changes as you suggested.
> as far as gathering more details i would if i knew where to get them from
> ?
> is it from within sql itself - log files perhaps. i dont quite know where
> to
> look for any more detail
>
> regards
>
> paul
> --
> Paul - South Africa
>
>
> "Andrew J. Kelly" wrote:
>
>> If the files are really that small then my assumption was probably wrong.
>> 10% of 84MB would only be a growth of about 8MB and that should only take
>> a
>> second or less. If the files were 10 or 20 GB's then that may be a
>> different story as the growth of even 1GB can take a while. So I
>> recommend
>> you change that 1GB to around 50MB on a file that small. As for the
>> original issue that is hard to say since the app is translating the real
>> error message from SQL Server. I think you need to gather more details if
>> possible.
>>
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>>
>> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
>> news:B2729701-12CA-4133-8479-23036F6E3E81@microsoft.com...
>> > Hi Andrew
>> > Thanks for the advice
>> > have changed the log file from 10% to 1 gig for its autogrowth,
>> > autoshrink
>> > is not enabled unless it is enabled by default. it does have a
>> > restricted
>> > growth in begabytes currently set at 2,097,152
>> > the database itself is still set at 10 persent but unrestricted. the
>> > current
>> > size on disk for these two files are database=47meg log=84meg and that
>> > is
>> > with almost a year worth of data so you can see it is not a very busy
>> > database
>> > i will monitor it now with the change and see if the problem improves
>> >
>> > thanks again
>> > paul
>> > --
>> > Paul - South Africa
>> >
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Well the app is obviously translating the error so it could be almost
>> >> anything. But my guess would be that the log file is autogrowing and
>> >> it
>> >> is
>> >> taking too long to grow and times out. Ensure that both the database
>> >> and
>> >> transaction log files have plenty of free space in them at all times.
>> >> Don't
>> >> shrink the files or turn on autoshrink or it will continue to happen.
>> >> Also
>> >> change the autogrowth from a % to a fixed amount that can be grown in
>> >> under
>> >> 15 seconds.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>> >>
>> >> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
>> >> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
>> >> > hi all - wonder if there is anyone out there who experiances what i
>> >> > am
>> >> > experiancing? i run sql server 2005 on a machine with windows server
>> >> > 2003.
>> >> > very small database collecting radius accounting data for about 40
>> >> > adsl
>> >> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
>> >> > drive
>> >> > space on a raid 10 array and i constantly het the follwing error in
>> >> > the
>> >> > error
>> >> > log
>> >> >
>> >> > Access request for user ashcott@gomdsl.co.za was discarded.
>> >> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
>> >> > NAS-IP-Address = 196.43.27.23
>> >> > NAS-Identifier = <not present>
>> >> > Called-Station-Identifier = <not present>
>> >> > Calling-Station-Identifier = <not present>
>> >> > Client-Friendly-Name = Telkom8
>> >> > Client-IP-Address = 196.43.3.86
>> >> > NAS-Port-Type = Virtual
>> >> > NAS-Port = 1110769935
>> >> > Proxy-Policy-Name = Use Windows authentication for all users
>> >> > Authentication-Provider = Windows
>> >> > Authentication-Server = <undetermined>
>> >> > Reason-Code = 80
>> >> > Reason = The authentication or accounting record could not be
>> >> > written
>> >> > to
>> >> > the log file location. Ensure that the log file location is
>> >> > accessible,
>> >> > has
>> >> > available space, can be written to, and that the directory or SQL
>> >> > server
>> >> > name
>> >> > is valid.
>> >> >
>> >> > the radius packet it then discarded and any accounting data is lost.
>> >> > then
>> >> > a
>> >> > minute or so later it is fine again. can then go ok for a day or so
>> >> > the
>> >> > oops
>> >> > - all is lost for the space of a minute or two. times are very
>> >> > random
>> >> > and
>> >> > pertains to random user information
>> >> >
>> >> > i dont know if i am posting into the correct place even becasue i
>> >> > dont
>> >> > know
>> >> > if it is an sql problem or server problem but any advice would be
>> >> > apretiated
>> >> >
>> >> > thanks
>> >> > --
>> >> > Paul - South Africa
>> >>
>> >>
>>
>>

Hi Andrew

couple of things in responce to your last post
the original error i posted where it mentions the user name, ip address
cannot contact log file etc, is from the windows event manager. Sql does not
appear to log anything about the event - its like it doesnt get to sql in the
first place
as far as the app is concerned it is extremely basic, it just collects the
incoming radius packet and stores it in the database. i have writen my own
set of web based pages in php just to query the data stored for a few numbers
- nothing complex at all.
since i made those first changes you suggested the database has received 239
new records of those, 3 did not get there and showed as errors in my event
log that is in the space of 2 days 2 hours

regards - paul
--
Paul - South Africa


"Andrew J. Kelly" wrote:

> Paul,
>
> Well you can check the Windows Event log and there may be an error message
> there depending on the severity and how the app works. I would also look in
> the SQL Error log as well. But you may have to use profiler with the error
> and attention events to see what is actually generated. I would also ping
> the makers of the app and see what they have to say.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> news:4C771DC0-2FFE-4AA0-AE0C-ACDD71310A2A@microsoft.com...
> > Hello again Andrew
> >
> > made the changes as you suggested.
> > as far as gathering more details i would if i knew where to get them from
> > ?
> > is it from within sql itself - log files perhaps. i dont quite know where
> > to
> > look for any more detail
> >
> > regards
> >
> > paul
> > --
> > Paul - South Africa
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> If the files are really that small then my assumption was probably wrong.
> >> 10% of 84MB would only be a growth of about 8MB and that should only take
> >> a
> >> second or less. If the files were 10 or 20 GB's then that may be a
> >> different story as the growth of even 1GB can take a while. So I
> >> recommend
> >> you change that 1GB to around 50MB on a file that small. As for the
> >> original issue that is hard to say since the app is translating the real
> >> error message from SQL Server. I think you need to gather more details if
> >> possible.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
> >>
> >> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> >> news:B2729701-12CA-4133-8479-23036F6E3E81@microsoft.com...
> >> > Hi Andrew
> >> > Thanks for the advice
> >> > have changed the log file from 10% to 1 gig for its autogrowth,
> >> > autoshrink
> >> > is not enabled unless it is enabled by default. it does have a
> >> > restricted
> >> > growth in begabytes currently set at 2,097,152
> >> > the database itself is still set at 10 persent but unrestricted. the
> >> > current
> >> > size on disk for these two files are database=47meg log=84meg and that
> >> > is
> >> > with almost a year worth of data so you can see it is not a very busy
> >> > database
> >> > i will monitor it now with the change and see if the problem improves
> >> >
> >> > thanks again
> >> > paul
> >> > --
> >> > Paul - South Africa
> >> >
> >> >
> >> > "Andrew J. Kelly" wrote:
> >> >
> >> >> Well the app is obviously translating the error so it could be almost
> >> >> anything. But my guess would be that the log file is autogrowing and
> >> >> it
> >> >> is
> >> >> taking too long to grow and times out. Ensure that both the database
> >> >> and
> >> >> transaction log files have plenty of free space in them at all times.
> >> >> Don't
> >> >> shrink the files or turn on autoshrink or it will continue to happen.
> >> >> Also
> >> >> change the autogrowth from a % to a fixed amount that can be grown in
> >> >> under
> >> >> 15 seconds.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >> Solid Quality Mentors
> >> >>
> >> >>
> >> >> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> >> >> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> >> >> > hi all - wonder if there is anyone out there who experiances what i
> >> >> > am
> >> >> > experiancing? i run sql server 2005 on a machine with windows server
> >> >> > 2003.
> >> >> > very small database collecting radius accounting data for about 40
> >> >> > adsl
> >> >> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
> >> >> > drive
> >> >> > space on a raid 10 array and i constantly het the follwing error in
> >> >> > the
> >> >> > error
> >> >> > log
> >> >> >
> >> >> > Access request for user ashcott@gomdsl.co.za was discarded.
> >> >> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> >> >> > NAS-IP-Address = 196.43.27.23
> >> >> > NAS-Identifier = <not present>
> >> >> > Called-Station-Identifier = <not present>
> >> >> > Calling-Station-Identifier = <not present>
> >> >> > Client-Friendly-Name = Telkom8
> >> >> > Client-IP-Address = 196.43.3.86
> >> >> > NAS-Port-Type = Virtual
> >> >> > NAS-Port = 1110769935
> >> >> > Proxy-Policy-Name = Use Windows authentication for all users
> >> >> > Authentication-Provider = Windows
> >> >> > Authentication-Server = <undetermined>
> >> >> > Reason-Code = 80
> >> >> > Reason = The authentication or accounting record could not be
> >> >> > written
> >> >> > to
> >> >> > the log file location. Ensure that the log file location is
> >> >> > accessible,
> >> >> > has
> >> >> > available space, can be written to, and that the directory or SQL
> >> >> > server
> >> >> > name
> >> >> > is valid.
> >> >> >
> >> >> > the radius packet it then discarded and any accounting data is lost.
> >> >> > then
> >> >> > a
> >> >> > minute or so later it is fine again. can then go ok for a day or so
> >> >> > the
> >> >> > oops
> >> >> > - all is lost for the space of a minute or two. times are very
> >> >> > random
> >> >> > and
> >> >> > pertains to random user information
> >> >> >
> >> >> > i dont know if i am posting into the correct place even becasue i
> >> >> > dont
> >> >> > know
> >> >> > if it is an sql problem or server problem but any advice would be
> >> >> > apretiated
> >> >> >
> >> >> > thanks
> >> >> > --
> >> >> > Paul - South Africa
> >> >>
> >> >>
> >>
> >>
>
>

Paul,

I was just re-reading your error message and I still don't think this is a
SQL Server error message at all but I am not sure what is generating this.
One thing I did notice this time is that this appears to be using a NAS unit
for the storage. SQL Server is not supported on a NAS with one exception
when using a trace flag and the NAS must support certain features as shown
in this KB.
http://support.microsoft.com/default.aspx/kb/304261

Even with the trace flag the use of a NAS is not recommended and I have seen
nothing but trouble in using them with SQL Server. In any case this part of
the error message along with it looks like it is on a NAS leads me to
believe there are issues with the NAS itself or it is in an unsupported
configuration.
> the log file location. Ensure that the log file location is accessible,
> has
> available space, can be written to, and that the directory or SQL server
> name


--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> hi all - wonder if there is anyone out there who experiances what i am
> experiancing? i run sql server 2005 on a machine with windows server 2003.
> very small database collecting radius accounting data for about 40 adsl
> users. the server has 2 gig ram on a 3ghz dual core machine 180gig drive
> space on a raid 10 array and i constantly het the follwing error in the
> error
> log
>
> Access request for user ashcott@gomdsl.co.za was discarded.
> Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> NAS-IP-Address = 196.43.27.23
> NAS-Identifier = <not present>
> Called-Station-Identifier = <not present>
> Calling-Station-Identifier = <not present>
> Client-Friendly-Name = Telkom8
> Client-IP-Address = 196.43.3.86
> NAS-Port-Type = Virtual
> NAS-Port = 1110769935
> Proxy-Policy-Name = Use Windows authentication for all users
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Reason-Code = 80
> Reason = The authentication or accounting record could not be written to
> the log file location. Ensure that the log file location is accessible,
> has
> available space, can be written to, and that the directory or SQL server
> name
> is valid.
>
> the radius packet it then discarded and any accounting data is lost. then
> a
> minute or so later it is fine again. can then go ok for a day or so the
> oops
> - all is lost for the space of a minute or two. times are very random and
> pertains to random user information
>
> i dont know if i am posting into the correct place even becasue i dont
> know
> if it is an sql problem or server problem but any advice would be
> apretiated
>
> thanks
> --
> Paul - South Africa

Hi Again Andrew

I think you are misinterpreting NAS for network attached storeage but not in
this case it is Network Access Server as in a big cisco access router with
multiple incoming lines to one ethernet.
as far as the sql goes it is all contained in one machine a windows 2003
server running sql 2005 it is a domain controller and runs dns for dial in
users (this is africa - we still use dial up quite extensively) let me try
give you the whole picture in a frame work you may follow a little easier.

immagine you have a large wide area network with 10 ADSL users in each of
ten towns (100 users) dotted accross the country. each user needs to
authenticate in his closest town so a Network Access Server "NAS" is located
in each of the ten towns. Each access server is connected via the internet to
one central user database or authentication server and requests for access to
the internet are all processed form there respective towns to this one
machine. So as to keep a record of who logged on and when, each request for
access (allowed or rejected) is stored in the sql database wich also runs on
the same central authentication server.
so the records for who logged on and when, from anywhere in the country and
the amount of data they transmitted are all stored here. The access requests
are just that, access request packets and the amount of data they transfer
comes in an accounting packet. All these packets are sent using the standard
RADIUS (Remote Access Dial In User Service) protocol from The NAS to the
authentication server. And this is my problem. I can see the packets arrive
at the server because the event log tells me so but it also (within the same
event) tells me they cannot be handed on to the sql hence

> The authentication or accounting record could not be written to
the log file location. Ensure that the log file location is accessible, has
available space, can be written to, and that the directory or SQL server name
is valid.

The log file being where Windows IAS sends the packet after it has received
it and authenticated the user against the active directory - In our case, SQL

It is still doing it periodically. I set up the profiler and left it running
till an error occured but have not had a chance to examine the results yet (
I am about to)

Hope this s you to me and i really appretiate your

regards paul

PS are you with microsoft or just a group user ?

--
Paul - South Africa


"Andrew J. Kelly" wrote:

> Paul,
>
> I was just re-reading your error message and I still don't think this is a
> SQL Server error message at all but I am not sure what is generating this.
> One thing I did notice this time is that this appears to be using a NAS unit
> for the storage. SQL Server is not supported on a NAS with one exception
> when using a trace flag and the NAS must support certain features as shown
> in this KB.
> http://support.microsoft.com/default.aspx/kb/304261
>
> Even with the trace flag the use of a NAS is not recommended and I have seen
> nothing but trouble in using them with SQL Server. In any case this part of
> the error message along with it looks like it is on a NAS leads me to
> believe there are issues with the NAS itself or it is in an unsupported
> configuration.
> > the log file location. Ensure that the log file location is accessible,
> > has
> > available space, can be written to, and that the directory or SQL server
> > name
>
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> > hi all - wonder if there is anyone out there who experiances what i am
> > experiancing? i run sql server 2005 on a machine with windows server 2003.
> > very small database collecting radius accounting data for about 40 adsl
> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig drive
> > space on a raid 10 array and i constantly het the follwing error in the
> > error
> > log
> >
> > Access request for user ashcott@gomdsl.co.za was discarded.
> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> > NAS-IP-Address = 196.43.27.23
> > NAS-Identifier = <not present>
> > Called-Station-Identifier = <not present>
> > Calling-Station-Identifier = <not present>
> > Client-Friendly-Name = Telkom8
> > Client-IP-Address = 196.43.3.86
> > NAS-Port-Type = Virtual
> > NAS-Port = 1110769935
> > Proxy-Policy-Name = Use Windows authentication for all users
> > Authentication-Provider = Windows
> > Authentication-Server = <undetermined>
> > Reason-Code = 80
> > Reason = The authentication or accounting record could not be written to
> > the log file location. Ensure that the log file location is accessible,
> > has
> > available space, can be written to, and that the directory or SQL server
> > name
> > is valid.
> >
> > the radius packet it then discarded and any accounting data is lost. then
> > a
> > minute or so later it is fine again. can then go ok for a day or so the
> > oops
> > - all is lost for the space of a minute or two. times are very random and
> > pertains to random user information
> >
> > i dont know if i am posting into the correct place even becasue i dont
> > know
> > if it is an sql problem or server problem but any advice would be
> > apretiated
> >
> > thanks
> > --
> > Paul - South Africa
>
>

OK I get it now, thanks for the explanation. So the NAS has nothing really
to do with the db itself per say. I am still going by my original story
in that the error message is not from SQL Server and that makes it very hard
to determine the actual issue. It appears that the Authentication server has
a problem and this message is somewhat generic. It may be that the
connection is lost or it could be anything really. The only way to know for
sure is to find the code that is invoking this message to see under what
conditions it does so. Since these are both on he same server make sure
there is enough memory for both. SQL Server loves memory. How much memory is
there on the server and what is the SQL configuration like? You may need to
set the MAX memory to ensure there is always some available for the OS and
the other apps. Check the Windows event logs along with the SQL Server
error logs to see if there is anything out of the ordinary that may give a
clue as well.
No I do not work for Microsoft but I do consult for them a lot. I am also a
MS SQL Server MVP which confuses some people as to who I work for.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
news:09E5D9B0-361D-408B-B4BE-D4F8FFF83CD1@microsoft.com...
> Hi Again Andrew
>
> I think you are misinterpreting NAS for network attached storeage but not
> in
> this case it is Network Access Server as in a big cisco access router with
> multiple incoming lines to one ethernet.
> as far as the sql goes it is all contained in one machine a windows 2003
> server running sql 2005 it is a domain controller and runs dns for dial in
> users (this is africa - we still use dial up quite extensively) let me try
> give you the whole picture in a frame work you may follow a little easier.
>
> immagine you have a large wide area network with 10 ADSL users in each of
> ten towns (100 users) dotted accross the country. each user needs to
> authenticate in his closest town so a Network Access Server "NAS" is
> located
> in each of the ten towns. Each access server is connected via the internet
> to
> one central user database or authentication server and requests for access
> to
> the internet are all processed form there respective towns to this one
> machine. So as to keep a record of who logged on and when, each request
> for
> access (allowed or rejected) is stored in the sql database wich also runs
> on
> the same central authentication server.
> so the records for who logged on and when, from anywhere in the country
> and
> the amount of data they transmitted are all stored here. The access
> requests
> are just that, access request packets and the amount of data they transfer
> comes in an accounting packet. All these packets are sent using the
> standard
> RADIUS (Remote Access Dial In User Service) protocol from The NAS to the
> authentication server. And this is my problem. I can see the packets
> arrive
> at the server because the event log tells me so but it also (within the
> same
> event) tells me they cannot be handed on to the sql hence
>
>> The authentication or accounting record could not be written to
> the log file location. Ensure that the log file location is accessible,
> has
> available space, can be written to, and that the directory or SQL server
> name
> is valid.
>
> The log file being where Windows IAS sends the packet after it has
> received
> it and authenticated the user against the active directory - In our case,
> SQL
>
> It is still doing it periodically. I set up the profiler and left it
> running
> till an error occured but have not had a chance to examine the results yet
> (
> I am about to)
>
> Hope this s you to me and i really appretiate your
>
> regards paul
>
> PS are you with microsoft or just a group user ?
>
> --
> Paul - South Africa
>
>
> "Andrew J. Kelly" wrote:
>
>> Paul,
>>
>> I was just re-reading your error message and I still don't think this is
>> a
>> SQL Server error message at all but I am not sure what is generating
>> this.
>> One thing I did notice this time is that this appears to be using a NAS
>> unit
>> for the storage. SQL Server is not supported on a NAS with one exception
>> when using a trace flag and the NAS must support certain features as
>> shown
>> in this KB.
>> http://support.microsoft.com/default.aspx/kb/304261
>>
>> Even with the trace flag the use of a NAS is not recommended and I have
>> seen
>> nothing but trouble in using them with SQL Server. In any case this part
>> of
>> the error message along with it looks like it is on a NAS leads me to
>> believe there are issues with the NAS itself or it is in an unsupported
>> configuration.
>> > the log file location. Ensure that the log file location is accessible,
>> > has
>> > available space, can be written to, and that the directory or SQL
>> > server
>> > name
>>
>>
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>>
>> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
>> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
>> > hi all - wonder if there is anyone out there who experiances what i am
>> > experiancing? i run sql server 2005 on a machine with windows server
>> > 2003.
>> > very small database collecting radius accounting data for about 40 adsl
>> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
>> > drive
>> > space on a raid 10 array and i constantly het the follwing error in the
>> > error
>> > log
>> >
>> > Access request for user ashcott@gomdsl.co.za was discarded.
>> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
>> > NAS-IP-Address = 196.43.27.23
>> > NAS-Identifier = <not present>
>> > Called-Station-Identifier = <not present>
>> > Calling-Station-Identifier = <not present>
>> > Client-Friendly-Name = Telkom8
>> > Client-IP-Address = 196.43.3.86
>> > NAS-Port-Type = Virtual
>> > NAS-Port = 1110769935
>> > Proxy-Policy-Name = Use Windows authentication for all users
>> > Authentication-Provider = Windows
>> > Authentication-Server = <undetermined>
>> > Reason-Code = 80
>> > Reason = The authentication or accounting record could not be written
>> > to
>> > the log file location. Ensure that the log file location is accessible,
>> > has
>> > available space, can be written to, and that the directory or SQL
>> > server
>> > name
>> > is valid.
>> >
>> > the radius packet it then discarded and any accounting data is lost.
>> > then
>> > a
>> > minute or so later it is fine again. can then go ok for a day or so the
>> > oops
>> > - all is lost for the space of a minute or two. times are very random
>> > and
>> > pertains to random user information
>> >
>> > i dont know if i am posting into the correct place even becasue i dont
>> > know
>> > if it is an sql problem or server problem but any advice would be
>> > apretiated
>> >
>> > thanks
>> > --
>> > Paul - South Africa
>>
>>

Hi Andrew
You are quite correct in assuming the NAS has nothing to do with the
database. The NAS communicates with Internet Authentication Service and this
talks to the database (the IAS is on the same machine as the SQL though so
any communication is all internal)
After running the profiler it appears that the error stops at IAS because
not even the profiler shows the error (altough there is a lot of ticks to
configure in there and i dont know wha to monitor exactly) So it appears that
this may not even be an SQL problem in which case, my appologies for being in
the wrong news group.
As far as ram is concerned my machine has 2 gig in total, if i loog at task
manager at any given time it's useage normally sits around 900 meg (half of
what is available) The code that is invoking the message would be part of IAS
(which itself is part of ms server 2003 and has been available since ver.
2000) even the little script in sql that is used to accept the data (XML
format if i am not mistaken) from IAS is writen by microsoft
--
Paul - South Africa


"Andrew J. Kelly" wrote:

> OK I get it now, thanks for the explanation. So the NAS has nothing really
> to do with the db itself per say. I am still going by my original story
> in that the error message is not from SQL Server and that makes it very hard
> to determine the actual issue. It appears that the Authentication server has
> a problem and this message is somewhat generic. It may be that the
> connection is lost or it could be anything really. The only way to know for
> sure is to find the code that is invoking this message to see under what
> conditions it does so. Since these are both on he same server make sure
> there is enough memory for both. SQL Server loves memory. How much memory is
> there on the server and what is the SQL configuration like? You may need to
> set the MAX memory to ensure there is always some available for the OS and
> the other apps. Check the Windows event logs along with the SQL Server
> error logs to see if there is anything out of the ordinary that may give a
> clue as well.
> No I do not work for Microsoft but I do consult for them a lot. I am also a
> MS SQL Server MVP which confuses some people as to who I work for.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> news:09E5D9B0-361D-408B-B4BE-D4F8FFF83CD1@microsoft.com...
> > Hi Again Andrew
> >
> > I think you are misinterpreting NAS for network attached storeage but not
> > in
> > this case it is Network Access Server as in a big cisco access router with
> > multiple incoming lines to one ethernet.
> > as far as the sql goes it is all contained in one machine a windows 2003
> > server running sql 2005 it is a domain controller and runs dns for dial in
> > users (this is africa - we still use dial up quite extensively) let me try
> > give you the whole picture in a frame work you may follow a little easier.
> >
> > immagine you have a large wide area network with 10 ADSL users in each of
> > ten towns (100 users) dotted accross the country. each user needs to
> > authenticate in his closest town so a Network Access Server "NAS" is
> > located
> > in each of the ten towns. Each access server is connected via the internet
> > to
> > one central user database or authentication server and requests for access
> > to
> > the internet are all processed form there respective towns to this one
> > machine. So as to keep a record of who logged on and when, each request
> > for
> > access (allowed or rejected) is stored in the sql database wich also runs
> > on
> > the same central authentication server.
> > so the records for who logged on and when, from anywhere in the country
> > and
> > the amount of data they transmitted are all stored here. The access
> > requests
> > are just that, access request packets and the amount of data they transfer
> > comes in an accounting packet. All these packets are sent using the
> > standard
> > RADIUS (Remote Access Dial In User Service) protocol from The NAS to the
> > authentication server. And this is my problem. I can see the packets
> > arrive
> > at the server because the event log tells me so but it also (within the
> > same
> > event) tells me they cannot be handed on to the sql hence
> >
> >> The authentication or accounting record could not be written to
> > the log file location. Ensure that the log file location is accessible,
> > has
> > available space, can be written to, and that the directory or SQL server
> > name
> > is valid.
> >
> > The log file being where Windows IAS sends the packet after it has
> > received
> > it and authenticated the user against the active directory - In our case,
> > SQL
> >
> > It is still doing it periodically. I set up the profiler and left it
> > running
> > till an error occured but have not had a chance to examine the results yet
> > (
> > I am about to)
> >
> > Hope this s you to me and i really appretiate your
> >
> > regards paul
> >
> > PS are you with microsoft or just a group user ?
> >
> > --
> > Paul - South Africa
> >
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Paul,
> >>
> >> I was just re-reading your error message and I still don't think this is
> >> a
> >> SQL Server error message at all but I am not sure what is generating
> >> this.
> >> One thing I did notice this time is that this appears to be using a NAS
> >> unit
> >> for the storage. SQL Server is not supported on a NAS with one exception
> >> when using a trace flag and the NAS must support certain features as
> >> shown
> >> in this KB.
> >> http://support.microsoft.com/default.aspx/kb/304261
> >>
> >> Even with the trace flag the use of a NAS is not recommended and I have
> >> seen
> >> nothing but trouble in using them with SQL Server. In any case this part
> >> of
> >> the error message along with it looks like it is on a NAS leads me to
> >> believe there are issues with the NAS itself or it is in an unsupported
> >> configuration.
> >> > the log file location. Ensure that the log file location is accessible,
> >> > has
> >> > available space, can be written to, and that the directory or SQL
> >> > server
> >> > name
> >>
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
> >>
> >> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
> >> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
> >> > hi all - wonder if there is anyone out there who experiances what i am
> >> > experiancing? i run sql server 2005 on a machine with windows server
> >> > 2003.
> >> > very small database collecting radius accounting data for about 40 adsl
> >> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
> >> > drive
> >> > space on a raid 10 array and i constantly het the follwing error in the
> >> > error
> >> > log
> >> >
> >> > Access request for user ashcott@gomdsl.co.za was discarded.
> >> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
> >> > NAS-IP-Address = 196.43.27.23
> >> > NAS-Identifier = <not present>
> >> > Called-Station-Identifier = <not present>
> >> > Calling-Station-Identifier = <not present>
> >> > Client-Friendly-Name = Telkom8
> >> > Client-IP-Address = 196.43.3.86
> >> > NAS-Port-Type = Virtual
> >> > NAS-Port = 1110769935
> >> > Proxy-Policy-Name = Use Windows authentication for all users
> >> > Authentication-Provider = Windows
> >> > Authentication-Server = <undetermined>
> >> > Reason-Code = 80
> >> > Reason = The authentication or accounting record could not be written
> >> > to
> >> > the log file location. Ensure that the log file location is accessible,
> >> > has
> >> > available space, can be written to, and that the directory or SQL
> >> > server
> >> > name
> >> > is valid.
> >> >
> >> > the radius packet it then discarded and any accounting data is lost.
> >> > then
> >> > a
> >> > minute or so later it is fine again. can then go ok for a day or so the
> >> > oops
> >> > - all is lost for the space of a minute or two. times are very random
> >> > and
> >> > pertains to random user information
> >> >
> >> > i dont know if i am posting into the correct place even becasue i dont
> >> > know
> >> > if it is an sql problem or server problem but any advice would be
> >> > apretiated
> >> >
> >> > thanks
> >> > --
> >> > Paul - South Africa
> >>
> >>
>
>

I've been following this thread, but didn't want to jump in since I didn't have anything conclusive
to say. But I do agree that this looks like an error from the RADIUS application, trying to access
SQL Server for some logging operation (or similar) but cannot do that. I'd troubleshoot this apps
connectivity to SQL Server as a starter...

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
news:CB49F22C-BD89-4158-A289-4AFCD470C584@microsoft.com...
> Hi Andrew
> You are quite correct in assuming the NAS has nothing to do with the
> database. The NAS communicates with Internet Authentication Service and this
> talks to the database (the IAS is on the same machine as the SQL though so
> any communication is all internal)
> After running the profiler it appears that the error stops at IAS because
> not even the profiler shows the error (altough there is a lot of ticks to
> configure in there and i dont know wha to monitor exactly) So it appears that
> this may not even be an SQL problem in which case, my appologies for being in
> the wrong news group.
> As far as ram is concerned my machine has 2 gig in total, if i loog at task
> manager at any given time it's useage normally sits around 900 meg (half of
> what is available) The code that is invoking the message would be part of IAS
> (which itself is part of ms server 2003 and has been available since ver.
> 2000) even the little script in sql that is used to accept the data (XML
> format if i am not mistaken) from IAS is writen by microsoft
> --
> Paul - South Africa
>
>
> "Andrew J. Kelly" wrote:
>
>> OK I get it now, thanks for the explanation. So the NAS has nothing really
>> to do with the db itself per say. I am still going by my original story
>> in that the error message is not from SQL Server and that makes it very hard
>> to determine the actual issue. It appears that the Authentication server has
>> a problem and this message is somewhat generic. It may be that the
>> connection is lost or it could be anything really. The only way to know for
>> sure is to find the code that is invoking this message to see under what
>> conditions it does so. Since these are both on he same server make sure
>> there is enough memory for both. SQL Server loves memory. How much memory is
>> there on the server and what is the SQL configuration like? You may need to
>> set the MAX memory to ensure there is always some available for the OS and
>> the other apps. Check the Windows event logs along with the SQL Server
>> error logs to see if there is anything out of the ordinary that may give a
>> clue as well.
>> No I do not work for Microsoft but I do consult for them a lot. I am also a
>> MS SQL Server MVP which confuses some people as to who I work for.
>>
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>>
>> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
>> news:09E5D9B0-361D-408B-B4BE-D4F8FFF83CD1@microsoft.com...
>> > Hi Again Andrew
>> >
>> > I think you are misinterpreting NAS for network attached storeage but not
>> > in
>> > this case it is Network Access Server as in a big cisco access router with
>> > multiple incoming lines to one ethernet.
>> > as far as the sql goes it is all contained in one machine a windows 2003
>> > server running sql 2005 it is a domain controller and runs dns for dial in
>> > users (this is africa - we still use dial up quite extensively) let me try
>> > give you the whole picture in a frame work you may follow a little easier.
>> >
>> > immagine you have a large wide area network with 10 ADSL users in each of
>> > ten towns (100 users) dotted accross the country. each user needs to
>> > authenticate in his closest town so a Network Access Server "NAS" is
>> > located
>> > in each of the ten towns. Each access server is connected via the internet
>> > to
>> > one central user database or authentication server and requests for access
>> > to
>> > the internet are all processed form there respective towns to this one
>> > machine. So as to keep a record of who logged on and when, each request
>> > for
>> > access (allowed or rejected) is stored in the sql database wich also runs
>> > on
>> > the same central authentication server.
>> > so the records for who logged on and when, from anywhere in the country
>> > and
>> > the amount of data they transmitted are all stored here. The access
>> > requests
>> > are just that, access request packets and the amount of data they transfer
>> > comes in an accounting packet. All these packets are sent using the
>> > standard
>> > RADIUS (Remote Access Dial In User Service) protocol from The NAS to the
>> > authentication server. And this is my problem. I can see the packets
>> > arrive
>> > at the server because the event log tells me so but it also (within the
>> > same
>> > event) tells me they cannot be handed on to the sql hence
>> >
>> >> The authentication or accounting record could not be written to
>> > the log file location. Ensure that the log file location is accessible,
>> > has
>> > available space, can be written to, and that the directory or SQL server
>> > name
>> > is valid.
>> >
>> > The log file being where Windows IAS sends the packet after it has
>> > received
>> > it and authenticated the user against the active directory - In our case,
>> > SQL
>> >
>> > It is still doing it periodically. I set up the profiler and left it
>> > running
>> > till an error occured but have not had a chance to examine the results yet
>> > (
>> > I am about to)
>> >
>> > Hope this s you to me and i really appretiate your
>> >
>> > regards paul
>> >
>> > PS are you with microsoft or just a group user ?
>> >
>> > --
>> > Paul - South Africa
>> >
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Paul,
>> >>
>> >> I was just re-reading your error message and I still don't think this is
>> >> a
>> >> SQL Server error message at all but I am not sure what is generating
>> >> this.
>> >> One thing I did notice this time is that this appears to be using a NAS
>> >> unit
>> >> for the storage. SQL Server is not supported on a NAS with one exception
>> >> when using a trace flag and the NAS must support certain features as
>> >> shown
>> >> in this KB.
>> >> http://support.microsoft.com/default.aspx/kb/304261
>> >>
>> >> Even with the trace flag the use of a NAS is not recommended and I have
>> >> seen
>> >> nothing but trouble in using them with SQL Server. In any case this part
>> >> of
>> >> the error message along with it looks like it is on a NAS leads me to
>> >> believe there are issues with the NAS itself or it is in an unsupported
>> >> configuration.
>> >> > the log file location. Ensure that the log file location is accessible,
>> >> > has
>> >> > available space, can be written to, and that the directory or SQL
>> >> > server
>> >> > name
>> >>
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>> >>
>> >> "Paul Taylor" <PaulTaylor@discussions.microsoft.com> wrote in message
>> >> news:07DDA54F-DCF7-4977-A9A1-338B7AEC620D@microsoft.com...
>> >> > hi all - wonder if there is anyone out there who experiances what i am
>> >> > experiancing? i run sql server 2005 on a machine with windows server
>> >> > 2003.
>> >> > very small database collecting radius accounting data for about 40 adsl
>> >> > users. the server has 2 gig ram on a 3ghz dual core machine 180gig
>> >> > drive
>> >> > space on a raid 10 array and i constantly het the follwing error in the
>> >> > error
>> >> > log
>> >> >
>> >> > Access request for user ashcott@gomdsl.co.za was discarded.
>> >> > Fully-Qualified-User-Name = goms.co.za/ADSL/Ashley Cotterrel
>> >> > NAS-IP-Address = 196.43.27.23
>> >> > NAS-Identifier = <not present>
>> >> > Called-Station-Identifier = <not present>
>> >> > Calling-Station-Identifier = <not present>
>> >> > Client-Friendly-Name = Telkom8
>> >> > Client-IP-Address = 196.43.3.86
>> >> > NAS-Port-Type = Virtual
>> >> > NAS-Port = 1110769935
>> >> > Proxy-Policy-Name = Use Windows authentication for all users
>> >> > Authentication-Provider = Windows
>> >> > Authentication-Server = <undetermined>
>> >> > Reason-Code = 80
>> >> > Reason = The authentication or accounting record could not be written
>> >> > to
>> >> > the log file location. Ensure that the log file location is accessible,
>> >> > has
>> >> > available space, can be written to, and that the directory or SQL
>> >> > server
>> >> > name
>> >> > is valid.
>> >> >
>> >> > the radius packet it then discarded and any accounting data is lost.
>> >> > then
>> >> > a
>> >> > minute or so later it is fine again. can then go ok for a day or so the
>> >> > oops
>> >> > - all is lost for the space of a minute or two. times are very random
>> >> > and
>> >> > pertains to random user information
>> >> >
>> >> > i dont know if i am posting into the correct place even becasue i dont
>> >> > know
>> >> > if it is an sql problem or server problem but a