Help on 2 Issues

I start SQL with startup parameters -eD:\MSSQL\Log\ERRORLog to put all
general SQL server logs here.
We experienced an error this morning, log entries follow;
2005-10-13 09:12:55.50 spid75 Open of fault log
E:\MSSQL\log\exception.log failed.
2005-10-13 09:12:55.54 spid75 Using 'dbghelp.dll' version '4.0.5'
2005-10-13 09:12:55.56 spid75 Error: 0, Severity: 19, State: 0
2005-10-13 09:12:55.56 spid75 SqlDumpExceptionHandler: Process 75
generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process..
One, any idea what this error could be casued by ... and two, noticed it is
trying to writte teh exception.log to E:\MSSQL\log which (the folder) did
not exist. Shouldn't it be writing to where the rest of the logs go? Is
the -e startup parameter configured wrong?
Also, yesterday during the middle of the day we lost the ability for domain
users to log in. Anyone with an exisitng login was fine. Any users using SQL
server logins were fine, but any domain users that needed to connect could
not.
We were getting the following error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
A restart of SQL service cleared up the issue, but any idea why this could
happen?
Any assistance is greatly appreciated.Hi
I assume that there is no exception.log in D:\MSSQL\Log\ERRORLog and the
message is incorrect?
You may want to contact PSS regarding this and possibly try running SQLdiag
during the day. Check the windows event log to see if there are any other
messages around this time, you lack of connectivity for windows
authentication may imply your network has a problem.
John
"Mike" wrote:
> I start SQL with startup parameters -eD:\MSSQL\Log\ERRORLog to put all
> general SQL server logs here.
> We experienced an error this morning, log entries follow;
> 2005-10-13 09:12:55.50 spid75 Open of fault log
> E:\MSSQL\log\exception.log failed.
> 2005-10-13 09:12:55.54 spid75 Using 'dbghelp.dll' version '4.0.5'
> 2005-10-13 09:12:55.56 spid75 Error: 0, Severity: 19, State: 0
> 2005-10-13 09:12:55.56 spid75 SqlDumpExceptionHandler: Process 75
> generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process..
> One, any idea what this error could be casued by ... and two, noticed it is
> trying to writte teh exception.log to E:\MSSQL\log which (the folder) did
> not exist. Shouldn't it be writing to where the rest of the logs go? Is
> the -e startup parameter configured wrong?
> Also, yesterday during the middle of the day we lost the ability for domain
> users to log in. Anyone with an exisitng login was fine. Any users using SQL
> server logins were fine, but any domain users that needed to connect could
> not.
> We were getting the following error.
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> A restart of SQL service cleared up the issue, but any idea why this could
> happen?
> Any assistance is greatly appreciated.
>
>sql