Error: fcb::close-flush: Operating system error 21(The device is not ready.) encountered

We are using sql server 2005 Enterprise Edition with service pack1

I got the following error messages in the SQL log

The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000090000 in file '....mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. fcb::close-flush: Operating system error 21(The device is not ready.) encountered.

I got these errors for about 2 hrs and after that I see these messages in the sql log

Starting up database ' ' 1 transactions rolled forward in database '' (). This is an informational message only. No user action is required. 0 transactions rolled back in database ' ' (). This is an informational message only. No user action is required. Recovery is writing a checkpoint in database ' ' ( ). This is an informational message only. No user action is required. CHECKDB for database '' finished without errors on (local time). This is an informational message only; no user action is required.

Can anyone please help me in troubleshooting this issue. Why this migh have happened.

any help would be appreciated.

Thanks

This sounds like an IO subsystem issue, i.e. SQL Server is having difficulty talking to one of your drives. Are you using direct attached storage or a SAN?|||

Thanks for the reply. We have Netapp SCSI disk storage. Could you please tell me how do I troubleshoot this so that I wont get such errors in future.

Thanks

|||Based on this and what you describe in your other post, you really ought to give Microsoft PSS a call.|||

Do read this kb before contacting PSS. You might be running on an unsupported device.

http://support.microsoft.com/kb/304261

Error: Could not find an entry for table or index with partition ID xxxxxx in database & Ser

Hello! guys

I am using sql server 2005 enterprise edition (x64) with sp1

Periodically, the sql server is crashing. Before crashing i am getting these messages in the error log

1) During undoing of a logged operation in database 'msdb', an error occurred at log record ID (). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

2) Could not find an entry for table or index with partition ID xxxxxx in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

3) Unable to drop worktable with partition ID xxxxx after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.

4) Error occurred while attempting to drop worktable with partition ID xxxxx.

5) SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.

6)The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Usually i get (2),(3),(4) (5) error message. But last time i also got (1) and (6)
Why msdb database is mentioned in error messages? Whats wrong with msdb dattabase?

Can someone tell me how to fix this issue?

I have seen this hotfix -

http://support.microsoft.com/kb/916086
( FIX: Errors may be generated in the tempdb database when you create and then drop many temporary tables in SQL Server 2005 BUG #: 518 sql )

Should i apply this hotfix? or should apply SP2? I checked SP2 bug list but i dont see anywhere about above bug. Does that mean it is not included in SP2?

Has anyone experienced such an issue? How you have resolved it?

Please any help would be apprecited.

Thanks

Database id:1 is master, :2 is tempdb. msdb database id should be 4.

It's a good thing to apply that hotfix. Also, please post the sql log. It gives us a lot more info than windows event log.

|||
Thanks so much for the reply.

All the above errors are from sql log only. I looked at the event log and it shows the same error messages.

Also that hotfix says-

This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

So is it safe to apply that hotfix? and if not does sp2 includes this hotfix bug?

Also wondering why the error message showing msdb database?

Thanks

|||

All hotfixes have that disclaimer. Basically, hotfixes are released to customers who truly need the fix before a formal release of a service pack (which they could wait for a long time for).

Sql2k5 sp2 does have this fix included. You can tell by looking at the build number (hotfix: 1533 and sp2: 3042).

The "missing log for msdb" error implies your sqlserver can't get to the log file (*.ldf) which implies a storage problem. Please check system event log for any indication of hardware failure.

sql

Error: Could not find an entry for table or index with partition ID xxxxxx in database & Ser

Hello! guys

I am using sql server 2005 enterprise edition (x64) with sp1

Periodically, the sql server is crashing. Before crashing i am getting these messages in the error log

1) During undoing of a logged operation in database 'msdb', an error occurred at log record ID (). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

2) Could not find an entry for table or index with partition ID xxxxxx in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

3) Unable to drop worktable with partition ID xxxxx after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.

4) Error occurred while attempting to drop worktable with partition ID xxxxx.

5) SQL Server must shut down in order to recover a database (database ID 1). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.

6)The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

Usually i get (2),(3),(4) (5) error message. But last time i also got (1) and (6)
Why msdb database is mentioned in error messages? Whats wrong with msdb dattabase?

Can someone tell me how to fix this issue?

I have seen this hotfix -

http://support.microsoft.com/kb/916086
( FIX: Errors may be generated in the tempdb database when you create and then drop many temporary tables in SQL Server 2005 BUG #: 518 sql )

Should i apply this hotfix? or should apply SP2? I checked SP2 bug list but i dont see anywhere about above bug. Does that mean it is not included in SP2?

Has anyone experienced such an issue? How you have resolved it?

Please any help would be apprecited.

Thanks

Database id:1 is master, :2 is tempdb. msdb database id should be 4.

It's a good thing to apply that hotfix. Also, please post the sql log. It gives us a lot more info than windows event log.

|||
Thanks so much for the reply.

All the above errors are from sql log only. I looked at the event log and it shows the same error messages.

Also that hotfix says-

This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

So is it safe to apply that hotfix? and if not does sp2 includes this hotfix bug?

Also wondering why the error message showing msdb database?

Thanks

|||

All hotfixes have that disclaimer. Basically, hotfixes are released to customers who truly need the fix before a formal release of a service pack (which they could wait for a long time for).

Sql2k5 sp2 does have this fix included. You can tell by looking at the build number (hotfix: 1533 and sp2: 3042).

The "missing log for msdb" error implies your sqlserver can't get to the log file (*.ldf) which implies a storage problem. Please check system event log for any indication of hardware failure.

error: 26 - error locating server/instance specified

My machine is WinXP with SP2. I installed SQL Server 2005 Developer
Edition on my machine last week, and I could bring up the Microsoft
SQL Server Management Studio fine, no error.
Today in Microsoft SQL Server Management Studio when I tried to
connect to machinename\SQL2005 (the SQL 2005 instance), I got the
error:
"An error has occured while establishing a connection to the server.
when connecting to sql server 2005, this failure may be caused by the
fact that under the default settings sql server does not allow remote
connections. (provider: sql network interfaces, error: 26 - error
locating server/instance specified)(microsoft sql server)"
But, I am not trying to connect to it remotely, the SQL Server 2005 is
on my machine.
In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
Configuration for Services and connections
"Local and remote connections" is not selected.
How can I fix this problem ?
Thank you.Never mind.
On the "Server name", i click on Browse more and select the instance
from there, I guess the machinename is different today than last week.
So, I selected that one and now it works.
THanks
On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
> My machine is WinXP with SP2. I installed SQL Server 2005 Developer
> Edition on my machine last week, and I could bring up the Microsoft
> SQL Server Management Studio fine, no error.
> Today in Microsoft SQL Server Management Studio when I tried to
> connect to machinename\SQL2005 (the SQL 2005 instance), I got the
> error:
> "An error has occured while establishing a connection to the server.
> when connecting to sql server 2005, this failure may be caused by the
> fact that under the default settings sql server does not allow remote
> connections. (provider: sql network interfaces, error: 26 - error
> locating server/instance specified)(microsoft sql server)"
> But, I am not trying to connect to it remotely, the SQL Server 2005 is
> on my machine.
> In the Start >> Programs >> Microsoft SQL Server 2005 >> Configuration
> Tools >> SQL Server 2005 Surface Area Configuration >> Surface Area
> Configuration for Services and connections
> "Local and remote connections" is not selected.
> How can I fix this problem ?
> Thank you.|||On Jun 10, 1:27 pm, fiefie.ni...@.gmail.com wrote:
> Never mind.
> On the "Server name", i click on Browse more and select the instance
> from there, I guess the machinename is different today than last week.
> So, I selected that one and now it works.
> THanks
> On Jun 10, 1:25 pm, fiefie.ni...@.gmail.com wrote:
> > My machine is WinXP with SP2. I installedSQLServer 2005 Developer
> > Edition on my machine last week, and I could bring up the Microsoft
> >SQLServer Management Studio fine, noerror.
> > Today in MicrosoftSQLServer Management Studio when I tried to
> > connect to machinename\SQL2005 (theSQL2005 instance), I got the
> >error:
> > "Anerrorhas occured while establishing a connection to the server.
> > when connecting tosqlserver 2005, this failure may be caused by the
> > fact that under the default settingssqlserver does not allow remote
> > connections. (provider:sqlnetwork interfaces,error:26-error
> > locating server/instance specified)(microsoftsqlserver)"
> > But, I am not trying to connect to it remotely, theSQLServer 2005 is
> > on my machine.
> > In the Start >> Programs >> MicrosoftSQLServer 2005 >> Configuration
> > Tools >>SQLServer 2005 Surface Area Configuration >> Surface Area
> > Configuration for Services and connections
> > "Local and remote connections" is not selected.
> > How can I fix this problem ?
> > Thank you.
I get the same error. Please advise.

error: 25 - Connection string is not valid -- HELP Please!

I have been having a problem trying to connect to a SQL Server. I have installed the Developer edition on an MS Small Business edition 2003 server

I also installed MS Sql Manager and I was able to create a database and connect to it. The database server is in the same PC. I used the surface configuration to enable remote connections using TCP /IP and pipe lines.

My application runs without a problem on my development machine but when I deployed on this server I get theprovider: SQL Network Interfaces, error: 25 - Connection string is not valid Error.

this is my config file setup

<connectionStrings>
<add name="Diamond_dbConnectionString" connectionString="Data Source=192.168.1.104\MSSQLSERVER;Initial Catalog=Diamond_db;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>

I have google and yahoo this error I found a lot of information I've tried many of them but still having the problem. I will appreciate your help solving this problem. I have a customer waiting since last week to see this site and I'm still stuck.

Tia

Charles

PS. Below I pasted the complete error info I get.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734995 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121 System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior) +162 System.Data.Common.DbDataAdapter.Fill(DataTable dataTable) +107 DiamondTableAdapters.COUNTRIES_TEMPLATETableAdapter.GetContriesTemplate() +108[TargetInvocationException: Exception has been thrown by the target of an invocation.] System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +0 System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +72 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) +296 System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +29 System.Web.UI.WebControls.ObjectDataSourceView.InvokeMethod(ObjectDataSourceMethod method, Boolean disposeInstance, Object& instance) +482 System.Web.UI.WebControls.ObjectDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +2040 System.Web.UI.WebControls.BaseDataList.GetData() +53 System.Web.UI.WebControls.DataList.CreateControlHierarchy(Boolean useDataSource) +284 System.Web.UI.WebControls.BaseDataList.OnDataBinding(EventArgs e) +56 System.Web.UI.WebControls.BaseDataList.DataBind() +72 System.Web.UI.WebControls.BaseDataList.EnsureDataBound() +55 System.Web.UI.WebControls.BaseDataList.CreateChildControls() +63 System.Web.UI.Control.EnsureChildControls() +87 System.Web.UI.Control.PreRenderRecursiveInternal() +41 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360

---

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

Do you have ISA running on the server? Can you connect through Server Manager to the server using the same credentials?

Jeff

|||

Jeff,

I'm using EMS SQL Manager for SQL Server

http://sqlmanager.net/products/mssql/manager/

to create and manage my SQL server. I can connect to the server using windows credentials but when I try with the ASP application I can't

Thanks

Charles

|||

Is the ASP.NET app using the same Windows account to access the database, or is it using the ASP.NET process account?

Jeff

|||

Jeff,

Honestly I'm very green regarding ASP.NET and MS-SQL Server

When I installed the server I asigned the Windows account to gain access to the SQL Server. When I created the database in question I also used the Windows Account.

When I registered the database with MS Server manager tool I also used the same Windows Account.

How can I check If I'm using the ASP.NET process account instead of the Windows Account?

I will appreciate your inputs.

Tia

Charles

|||

The ASP.NET process account, unless you have set it or changed it, is ASPNET or NETWORK SERVICE depending on operatiing system. It is unlikely you chose this account for access to SQL. But normally you would get a mdifferent error if that was the problem.

Take a look at connectionstrings.com for some possibilities in changing your connection string. You may want to use a standard authentication with SQL user and password rather than rely on a trusted connection.

Is your SQL on a different server than the web server? I wouldn't think so but you use the IP address of the SQL server in your connection. You should just need to enable TCP/IP, which you said you've done.

Jeff

|||Are you sure the MSSQLSERVER is the name of the named (not default) instance? It seems to be the SQL service name of default instance. If you're trying to connect to a default SQL instance on a remote server, just set the Data Source to the IP address of the remote server is ok.sql

Error: 18456, Severity: 14, State: 16

Hi All,
I am getting the following error in the ERRORLOG File when I am trying
to connect to SQL Server 2005 Express Edition from the command line.
2007-03-23 07:30:05.54 Logon Error: 18456, Severity: 14, State:
16.
2007-03-23 07:30:05.54 Logon Login failed for user 'sa'.
[CLIENT: xx.xx.xx.xx]
I have a fresh install of SQL Server on my local machine, which is
probably the source of my angst, but I am trying to create a database
from scratch through using a batch file that is run from the command
line, the batch file looks like this:
<snip>
SQLCMD -U %USR% -P %PWD% -S %SVR% -d %DBF% -i CreateDatabase.sql
<snip>
The values of %USR% and %PWD% are correct as I frequently log into
Management Studio with the details, %SVR% is "<ComputerName>
\SQLEXPRESS,1433" and %DBF% is <DatabaseName>. The contents of
CreateDatabase.sql when run in Management Studio successfully creates
the database that I require so I know the error doesn't lie there.
The command line error that is showing reads as the following:
Msg 4060, Level 11, State 1, Server <ComputerName>\SQLEXPRESS, Line 1
Cannot open database "<DatabaseName>" requested by the login. The
login failed.
Msg 18456, Level 14, State 1, Server <ComputerName>\SQLEXPRESS, Line 1
Login failed for user 'sa'.
I have a feeling that it is related to 'sa' not having the correct
permissions with regards to logging into or creating a database from
scratch, but I find it odd that I can login as 'sa' in Management
Studio and create the database from there, but when I try it from the
command-line (despite having TCP/IP enabled) it won't let me connect
to create a database.
Is there something I am missing here? I have been banging my head off
of walls for days over this and am unsure of the next steps to take.
If any of this screams "why the hell are you doing this?" then please
let me know as at the moment I am punching in the dark with this
problem, I have searched Usenet, Google Groups, the Web and although I
have found potential solutions to this particular problem I am having,
nothing I have done so far has actually managed to fix the issue.
Related articles I have followed are:
Login failed for user 'x'
http://msdn2.microsoft.com/en-us/library/ms366351.aspx
Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx
Upgrading MSDE 2000 to SQL Server 2005 Express [Enabling network
protocols section]
http://www.microsoft.com/technet/pr...sqlexpress.mspx
NOTE: I just listed these articles to show what path I am currently
looking at with regards to this problem, but again I stress I have
found nothing yet to get round this problem, and any further articles
or direction would be much appreciated.
Yours Distressingly
AlastairDoes the password have any blank spaces or double quotes ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Alastair" <alastair_anderson@.hotmail.com> wrote in message
news:1174642161.471601.110030@.y80g2000hsf.googlegroups.com...
> Hi All,
> I am getting the following error in the ERRORLOG File when I am trying
> to connect to SQL Server 2005 Express Edition from the command line.
> 2007-03-23 07:30:05.54 Logon Error: 18456, Severity: 14, State:
> 16.
> 2007-03-23 07:30:05.54 Logon Login failed for user 'sa'.
> [CLIENT: xx.xx.xx.xx]
> I have a fresh install of SQL Server on my local machine, which is
> probably the source of my angst, but I am trying to create a database
> from scratch through using a batch file that is run from the command
> line, the batch file looks like this:
> <snip>
> SQLCMD -U %USR% -P %PWD% -S %SVR% -d %DBF% -i CreateDatabase.sql
> <snip>
> The values of %USR% and %PWD% are correct as I frequently log into
> Management Studio with the details, %SVR% is "<ComputerName>
> \SQLEXPRESS,1433" and %DBF% is <DatabaseName>. The contents of
> CreateDatabase.sql when run in Management Studio successfully creates
> the database that I require so I know the error doesn't lie there.
> The command line error that is showing reads as the following:
> Msg 4060, Level 11, State 1, Server <ComputerName>\SQLEXPRESS, Line 1
> Cannot open database "<DatabaseName>" requested by the login. The
> login failed.
> Msg 18456, Level 14, State 1, Server <ComputerName>\SQLEXPRESS, Line 1
> Login failed for user 'sa'.
> I have a feeling that it is related to 'sa' not having the correct
> permissions with regards to logging into or creating a database from
> scratch, but I find it odd that I can login as 'sa' in Management
> Studio and create the database from there, but when I try it from the
> command-line (despite having TCP/IP enabled) it won't let me connect
> to create a database.
> Is there something I am missing here? I have been banging my head off
> of walls for days over this and am unsure of the next steps to take.
> If any of this screams "why the hell are you doing this?" then please
> let me know as at the moment I am punching in the dark with this
> problem, I have searched Usenet, Google Groups, the Web and although I
> have found potential solutions to this particular problem I am having,
> nothing I have done so far has actually managed to fix the issue.
> Related articles I have followed are:
> Login failed for user 'x'
> http://msdn2.microsoft.com/en-us/library/ms366351.aspx
> Change Server Authentication Mode
> http://msdn2.microsoft.com/en-us/library/ms188670.aspx
> Upgrading MSDE 2000 to SQL Server 2005 Express [Enabling network
> protocols section]
> http://www.microsoft.com/technet/pr...sqlexpress.mspx
> NOTE: I just listed these articles to show what path I am currently
> looking at with regards to this problem, but again I stress I have
> found nothing yet to get round this problem, and any further articles
> or direction would be much appreciated.
> Yours Distressingly
> Alastair
>|||On 23 Mar, 13:00, "Jens K. Suessmeyer" <J...@.NoSpamhere-
sqlserver2005.de> wrote:
> Does the password have any blank spaces or double quotes ?
> Jens K. Suessmeyer.
> --http://www.sqlserver2005.de
> --
> "Alastair" <alastair_ander...@.hotmail.com> wrote in message
> news:1174642161.471601.110030@.y80g2000hsf.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
The only double quotes that it contains are those that surround the
password in the .bat file.
Should these be single quotes?|||Normally this should work, did you try conencting with the same syntax that
you are using in the batch file via an interactive commandprompt ? Did you
try to leave out the quotes ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Alastair" <alastair_anderson@.hotmail.com> wrote in message
news:1174655306.297982.325260@.b75g2000hsg.googlegroups.com...
> On 23 Mar, 13:00, "Jens K. Suessmeyer" <J...@.NoSpamhere-
> sqlserver2005.de> wrote:
> The only double quotes that it contains are those that surround the
> password in the .bat file.
> Should these be single quotes?
>|||On 23 Mar, 21:26, "Jens K. Suessmeyer" <J...@.NoSpamhere-
sqlserver2005.de> wrote:
> Normally this should work, did you try conencting with the same syntax tha
t
> you are using in the batch file via an interactive commandprompt ? Did you
> try to leave out the quotes ?
> Jens K. Suessmeyer.
> --http://www.sqlserver2005.de
> --
> "Alastair" <alastair_ander...@.hotmail.com> wrote in message
> news:1174655306.297982.325260@.b75g2000hsg.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi Jens,
Thanks for the input on this it is very much appreciated,
I tried running the batch file without quotations around the strings
and I still get the same error, I also tried single quotes, but the
command-line processor was interpreting them as part of the strings.
I took your advice and tried running it straight from the command-line
without using the .bat file, and still the same error came screaming
back at me.
Alastair|||On 23 Mar, 21:26, "Jens K. Suessmeyer" <J...@.NoSpamhere-
sqlserver2005.de> wrote:
> Normally this should work, did you try conencting with the same syntax tha
t
> you are using in the batch file via an interactive commandprompt ? Did you
> try to leave out the quotes ?
> Jens K. Suessmeyer.
> --http://www.sqlserver2005.de
> --
> "Alastair" <alastair_ander...@.hotmail.com> wrote in message
> news:1174655306.297982.325260@.b75g2000hsg.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
I've done some further hunting around for solutions, could it
potentially be related to "sa" not having any permissions in the
SYS.DATABASE_PERMISSIONS table?|||No, sa has by default access to everything, including the internal data.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Alastair" <alastair_anderson@.hotmail.com> wrote in message
news:1174779869.212689.303860@.o5g2000hsb.googlegroups.com...
> On 23 Mar, 21:26, "Jens K. Suessmeyer" <J...@.NoSpamhere-
> sqlserver2005.de> wrote:
> I've done some further hunting around for solutions, could it
> potentially be related to "sa" not having any permissions in the
> SYS.DATABASE_PERMISSIONS table?
>

Error: 18456, Severity: 14, State: 11

We have SQL Server 2005 Developer Edition with SP2 installed on Windows
Server 2003 Standard Edition SP1. When one of our programmers tries to
connect to the SQL instance he receives the 'Error: 18456, Severity: 14,
State: 11' error.
I found where this refers to a connect to server error and have checked, he
does have connect priviliges. I deleted both the server account and database
account and recreated them but he still receives the error. The only way he
can get access is to be a member of the sysadmin role. This was done for
testing but cannot be given as normal practice.
Does anyone have any ideas or solutions?
Thank You,
Bertbert
CREATE LOGIN test
WITH PASSWORD = 'balabalabala';USE AdventureWorks;
CREATE USER 'test' FOR LOGIN test;
GO Note , you can use ALTER LOGIN ... WITH default_database=..."-bert"
<bert@.discussions.microsoft.com> wrote in message
news:C9CDD261-B1AD-48BC-B821-9DCC80F64480@.microsoft.com...
> We have SQL Server 2005 Developer Edition with SP2 installed on Windows
> Server 2003 Standard Edition SP1. When one of our programmers tries to
> connect to the SQL instance he receives the 'Error: 18456, Severity: 14,
> State: 11' error.
> I found where this refers to a connect to server error and have checked,
> he
> does have connect priviliges. I deleted both the server account and
> database
> account and recreated them but he still receives the error. The only way
> he
> can get access is to be a member of the sysadmin role. This was done for
> testing but cannot be given as normal practice.
> Does anyone have any ideas or solutions?
> Thank You,
> Bert

Error: 18456 Severity: 14, State: 11

I have a SQL 2005 SP1 test server running Developer Edition on top of Windows Server 2003 SP1. We're testing out a 3rd party application that is using Windows Authentication to connect to SQL 2005. The SQL Error Log is saturated with the error message listed in the subject line. The text accompanying the message alternates between "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: <named pipe>]" and "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: xxx.xxx.xxx.xxx]".

There are two strange parts to this: 1) The application appears to be working fine on the surface, and, 2) The MYDOMAIN\TESTDA1$ account mentioned in the error text is not the user account that we are using to connect the application to SQL 2005. TESTDA1 is the server name that the 3rd party software is running remotely from.

I've looked up "error state 11" using the following resource:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

It describes error states 11 and 12 as "Valid login but server access failure" but I'm not sure what that means. Why would SQL care about the computer account hosting the application?

Thanks in advance for any help.

From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks Raul. You were correct - the software was indeed trying to connect using the "Local System" account. We changed this to a domain account that had permission to login to SQL and now everything is working well. No more errors in the SQL Error Log.

Thanks again!

|||I have the same error message in my logs for SQL Server 2005. I've set up a report, gave both the user and the group she belongs to full access to the reports and Content Manager and Browser. She can go through the folders, but if she gets the report and clicks on the link to open the report (on http://servername/reports etc) she gets the error message "cannot create connection to data source 'databasename' and in the error logs it says:

Error: 18456, Severity: 14, State: 11.
Login failed for user 'DOMAIN\User.Name'. [CLIENT: <local machine>]

where domain = an active directory (not local box) domain and User.Name is the actual name of the user who is in that domain.

The error being state 11 means Valid login but server access failure so where do I look to figure out why she can't get into the report? She's trying to access across the network so she's not physically logging onto that computer. Any idea what I need to check?

Thanks!

Linda
|||

Connect to SQL server using a sysadmin account and look if the Windows user has access to SQL Server. You can look first in sys.server_principals for example:

SELECT * FROM sys.server_principals

Go

And look for your Windows principal name directly, or for a group she belongs to and grants permission to connect. If you cannot find the proper entry, you can grant permission to connect to SQL Server by adding a login.

On the other hand, if the login exists, it may be possible that that particular user doesn’t have permissions to connect in the right endpoint. To see all the permissions on the endpoints you can run the following query:

SELECT endpnt.name,

suser_name(perms.grantee_principal_id) as grantee_principal,

perms.permission_name, perms.state_desc

FROM

sys.server_permissions perms,

sys.endpoints endpnt

WHERE

perms.class = 105

AND perms.major_id = endpnt.endpoint_id

go

If there is a permission missing for this principal, just grant the CONNECT permission at the correct endpoint.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul Garcia - MS wrote:

From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

Hello there,

I got exactly the same scenario. Unfortunately I am not able to change the service account to any other thing than local system.

If I would like to add access to my database for the machine$ accounts, what exactly would I have to do ?

Could anyone give me a hint please ?

Thanks in advance

Gordon

|||

You can use the CREATE LOGIN DDL to create the login for the machine account, for example:

CREATE LOGIN [DOMAIN\machine_name$] FROM WINDOWS

Let us know if this information helped and/or if you have any additional questions.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||Thanks for the hint. This didn't solve my problem. Do I have to grant any special rights after creating those logins ?|||

After creating the logins I forgot to map a role to the users for my database.

I just followed the instructions found in another article here :

navigate through Security > Logins > Properties > User Mapping > Choose the Database > Map the user to the database (you will see that he will get the public role by default)

Error: 18456 Severity: 14, State: 11

I have a SQL 2005 SP1 test server running Developer Edition on top of Windows Server 2003 SP1. We're testing out a 3rd party application that is using Windows Authentication to connect to SQL 2005. The SQL Error Log is saturated with the error message listed in the subject line. The text accompanying the message alternates between "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: <named pipe>]" and "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: xxx.xxx.xxx.xxx]".

There are two strange parts to this: 1) The application appears to be working fine on the surface, and, 2) The MYDOMAIN\TESTDA1$ account mentioned in the error text is not the user account that we are using to connect the application to SQL 2005. TESTDA1 is the server name that the 3rd party software is running remotely from.

I've looked up "error state 11" using the following resource:

http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

It describes error states 11 and 12 as "Valid login but server access failure" but I'm not sure what that means. Why would SQL care about the computer account hosting the application?

Thanks in advance for any help.

From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

|||

Thanks Raul. You were correct - the software was indeed trying to connect using the "Local System" account. We changed this to a domain account that had permission to login to SQL and now everything is working well. No more errors in the SQL Error Log.

Thanks again!

|||I have the same error message in my logs for SQL Server 2005. I've set up a report, gave both the user and the group she belongs to full access to the reports and Content Manager and Browser. She can go through the folders, but if she gets the report and clicks on the link to open the report (on http://servername/reports etc) she gets the error message "cannot create connection to data source 'databasename' and in the error logs it says:

Error: 18456, Severity: 14, State: 11.
Login failed for user 'DOMAIN\User.Name'. [CLIENT: <local machine>]

where domain = an active directory (not local box) domain and User.Name is the actual name of the user who is in that domain.

The error being state 11 means Valid login but server access failure so where do I look to figure out why she can't get into the report? She's trying to access across the network so she's not physically logging onto that computer. Any idea what I need to check?

Thanks!

Linda
|||

Connect to SQL server using a sysadmin account and look if the Windows user has access to SQL Server. You can look first in sys.server_principals for example:

SELECT * FROM sys.server_principals

Go

And look for your Windows principal name directly, or for a group she belongs to and grants permission to connect. If you cannot find the proper entry, you can grant permission to connect to SQL Server by adding a login.

On the other hand, if the login exists, it may be possible that that particular user doesn’t have permissions to connect in the right endpoint. To see all the permissions on the endpoints you can run the following query:

SELECT endpnt.name,

suser_name(perms.grantee_principal_id) as grantee_principal,

perms.permission_name, perms.state_desc

FROM

sys.server_permissions perms,

sys.endpoints endpnt

WHERE

perms.class = 105

AND perms.major_id = endpnt.endpoint_id

go

If there is a permission missing for this principal, just grant the CONNECT permission at the correct endpoint.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Raul Garcia - MS wrote:

From your description it seems like the 3^rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.

Check the 3^rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).

Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.

I hope this information helps,

-Raul Garcia

SDE/T

SQL Server Engine

Hello there,

I got exactly the same scenario. Unfortunately I am not able to change the service account to any other thing than local system.

If I would like to add access to my database for the machine$ accounts, what exactly would I have to do ?

Could anyone give me a hint please ?

Thanks in advance

Gordon

|||

You can use the CREATE LOGIN DDL to create the login for the machine account, for example:

CREATE LOGIN [DOMAIN\machine_name$] FROM WINDOWS

Let us know if this information helped and/or if you have any additional questions.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

|||Thanks for the hint. This didn't solve my problem. Do I have to grant any special rights after creating those logins ?|||

After creating the logins I forgot to map a role to the users for my database.

I just followed the instructions found in another article here :

navigate through Security > Logins > Properties > User Mapping > Choose the Database > Map the user to the database (you will see that he will get the public role by default)

Error: 17883 - problem with Scheduler

Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
Igor
Hi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>
|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>
|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>
|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>

Error: 17883 - problem with Scheduler

Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
IgorHi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>

Error: 17883 - problem with Scheduler

Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
IgorHi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We are running SQL Server 200 SP Enterprise Edition on Windows 2003
>> with SAN components. Just recently, we got an error message in SQL Server
>> error log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be
>> non-yielding on Scheduler 0.'
>> I found a couple of articles on MS website:
>> http://support.microsoft.com/kb/319892
>> http://support.microsoft.com/kb/810885
>> http://support.microsoft.com/kb/890637
>> One of the articles refers to High-End disk system as possible source. I
>> am wondering whether anyone had similar problem and had been able to
>> detect the cause of this type of error message.
>>
>> Thanks,
>> Igor
>>
>|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> We had the issue as our SANs are very fast.
>> Once we identified the problem, we went to hotfix build 818 and then 952
>> and as soon as SP4 came out, we applied it.
>> The problems do not occur anymore.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
>> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We are running SQL Server 200 SP Enterprise Edition on Windows 2003
>> with SAN components. Just recently, we got an error message in SQL
>> Server error log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to
>> be non-yielding on Scheduler 0.'
>> I found a couple of articles on MS website:
>> http://support.microsoft.com/kb/319892
>> http://support.microsoft.com/kb/810885
>> http://support.microsoft.com/kb/890637
>> One of the articles refers to High-End disk system as possible source. I
>> am wondering whether anyone had similar problem and had been able to
>> detect the cause of this type of error message.
>>
>> Thanks,
>> Igor
>>
>>
>|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>> Did you happen to remember when exactly problem disappear? We are on
>> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
>> AWE related issues with SP4 that's why I am reluctant to install SP4.
>> Thanks,
>> Igor
>>
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>> Hi
>> We had the issue as our SANs are very fast.
>> Once we identified the problem, we went to hotfix build 818 and then 952
>> and as soon as SP4 came out, we applied it.
>> The problems do not occur anymore.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
>> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> We are running SQL Server 200 SP Enterprise Edition on Windows 2003
>> with SAN components. Just recently, we got an error message in SQL
>> Server error log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to
>> be non-yielding on Scheduler 0.'
>> I found a couple of articles on MS website:
>> http://support.microsoft.com/kb/319892
>> http://support.microsoft.com/kb/810885
>> http://support.microsoft.com/kb/890637
>> One of the articles refers to High-End disk system as possible source.
>> I am wondering whether anyone had similar problem and had been able to
>> detect the cause of this type of error message.
>>
>> Thanks,
>> Igor
>>
>>
>>
>

Error: 17883

8.00.818, SP3, Standard Edition
After installing SP3, the server hangs with Error: 17883, Severity: 0,
State: 1. Process 0:0 (a04) UMS Context 0x105BB428 appears to be
non-yielding on Scheduler 0.
MS03-031 does not resolve this problem.
Any suggestions?Correction: Severity: 1, State 0.
"TLW" <tlw@.oceanlighthouse.com> wrote in message
news:eSomf6FKEHA.1760@.TK2MSFTNGP10.phx.gbl...
> 8.00.818, SP3, Standard Edition
> After installing SP3, the server hangs with Error: 17883, Severity: 0,
> State: 1. Process 0:0 (a04) UMS Context 0x105BB428 appears to be
> non-yielding on Scheduler 0.
> MS03-031 does not resolve this problem.
> Any suggestions?
>|||I'm having the same issue. I was able to discuss it with a MS
instructor at Sql Connections last week. He said the error is too
internal for troubleshooting other than by MS.
I have setup a black box trace and an alert. The alert will fire on
17883 stopping the black box trace and doing a dbcc stackdump. When
it happens again I'll open a ticket with Microsoft and send off the
files.

Error: 17803, Severity: 20, State: 17

I have an application connected to a machine running MSSQL Server 2000 SP3a
Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
extensive query periodically. Over a period of time, I notice through Task
Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this happen,
the application experience slowdown and eventually hang out.
SQL ERRORLog show
2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers found.
2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182 Free=0
Procedures=22931
Inram=0 Dirty=24545 Kept=0
I/O=0, Latched=2022, Other=0
2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
Target=208680 Hashed=26567
InternalReservation=2130 ExternalReservation=57 Min Free=512
2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
TotalPages=22931 InUsePages=22931
2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
Reserved=2544
OS Committed=2487
OS In Use=2468
Query Plan=166599 Optimizer=3
General=14803
Utilities=7 Connection=2910
2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
Locks=147
SQLCache=1236 Replication=2
LockBytes=2 ServerGlobal=43
Xact=1862
2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
Maximum=13450 Available=13392
2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
2005-04-22 07:16:36.70 server Insufficient memory available..
I'm currently using SQL Server 2000 Driver for JDBC (with
SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
calls that don't have a corresponding sp_cursorclose.
Help is greatly appreaciated here!SQL ran out of free buffers (Free=0). You should probably apply the latest
SQL Server hotfix and update JDBC drivers to prevent problems such as 818095
and 837957. In addition, there are changes in the latest SQL hotfixes which
allow Lazy Writer to run more aggressively when it detects a low number of
free buffers.
If the problems persist engage MS product support and have them check your
server for additional leaks.
Adrian
"SS" <SS@.discussions.microsoft.com> wrote in message
news:884EB064-D4C5-4454-A8B4-A151EBC0ED11@.microsoft.com...
>I have an application connected to a machine running MSSQL Server 2000 SP3a
> Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
> extensive query periodically. Over a period of time, I notice through Task
> Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this
> happen,
> the application experience slowdown and eventually hang out.
> SQL ERRORLog show
> 2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers
> found.
> 2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182
> Free=0
> Procedures=22931
> Inram=0 Dirty=24545 Kept=0
> I/O=0, Latched=2022, Other=0
> 2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
> Target=208680 Hashed=26567
> InternalReservation=2130 ExternalReservation=57 Min Free=512
> 2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
> TotalPages=22931 InUsePages=22931
> 2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
> Reserved=2544
> OS Committed=2487
> OS In Use=2468
> Query Plan=166599 Optimizer=3
> General=14803
> Utilities=7 Connection=2910
> 2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
> Locks=147
> SQLCache=1236 Replication=2
> LockBytes=2 ServerGlobal=43
> Xact=1862
> 2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
> Maximum=13450 Available=13392
> 2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
> 2005-04-22 07:16:36.70 server Insufficient memory available..
> I'm currently using SQL Server 2000 Driver for JDBC (with
> SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
> calls that don't have a corresponding sp_cursorclose.
> Help is greatly appreaciated here!
>

Error: 17803, Severity: 20, State: 17

I have an application connected to a machine running MSSQL Server 2000 SP3a
Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
extensive query periodically. Over a period of time, I notice through Task
Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this happen,
the application experience slowdown and eventually hang out.
SQL ERRORLog show
2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers found.
2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182 Free=0
Procedures=22931
Inram=0 Dirty=24545 Kept=0
I/O=0, Latched=2022, Other=0
2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
Target=208680 Hashed=26567
InternalReservation=2130 ExternalReservation=57 Min Free=512
2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
TotalPages=22931 InUsePages=22931
2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
Reserved=2544
OS Committed=2487
OS In Use=2468
Query Plan=166599 Optimizer=3
General=14803
Utilities=7 Connection=2910
2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
Locks=147
SQLCache=1236 Replication=2
LockBytes=2 ServerGlobal=43
Xact=1862
2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
Maximum=13450 Available=13392
2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
2005-04-22 07:16:36.70 server Insufficient memory available..
I'm currently using SQL Server 2000 Driver for JDBC (with
SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
calls that don't have a corresponding sp_cursorclose.
Help is greatly appreaciated here!SQL ran out of free buffers (Free=0). You should probably apply the latest
SQL Server hotfix and update JDBC drivers to prevent problems such as 818095
and 837957. In addition, there are changes in the latest SQL hotfixes which
allow Lazy Writer to run more aggressively when it detects a low number of
free buffers.
If the problems persist engage MS product support and have them check your
server for additional leaks.
Adrian
"SS" <SS@.discussions.microsoft.com> wrote in message
news:884EB064-D4C5-4454-A8B4-A151EBC0ED11@.microsoft.com...
>I have an application connected to a machine running MSSQL Server 2000 SP3a
> Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
> extensive query periodically. Over a period of time, I notice through Task
> Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this
> happen,
> the application experience slowdown and eventually hang out.
> SQL ERRORLog show
> 2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers
> found.
> 2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182
> Free=0
> Procedures=22931
> Inram=0 Dirty=24545 Kept=0
> I/O=0, Latched=2022, Other=0
> 2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
> Target=208680 Hashed=26567
> InternalReservation=2130 ExternalReservation=57 Min Free=512
> 2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
> TotalPages=22931 InUsePages=22931
> 2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
> Reserved=2544
> OS Committed=2487
> OS In Use=2468
> Query Plan=166599 Optimizer=3
> General=14803
> Utilities=7 Connection=2910
> 2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
> Locks=147
> SQLCache=1236 Replication=2
> LockBytes=2 ServerGlobal=43
> Xact=1862
> 2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
> Maximum=13450 Available=13392
> 2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
> 2005-04-22 07:16:36.70 server Insufficient memory available..
> I'm currently using SQL Server 2000 Driver for JDBC (with
> SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
> calls that don't have a corresponding sp_cursorclose.
> Help is greatly appreaciated here!
>

Error: 17803, Severity: 20, State: 17

I have an application connected to a machine running MSSQL Server 2000 SP3a
Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
extensive query periodically. Over a period of time, I notice through Task
Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this happen,
the application experience slowdown and eventually hang out.
SQL ERRORLog show
2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers found.
2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182 Free=0
Procedures=22931
Inram=0 Dirty=24545 Kept=0
I/O=0, Latched=2022, Other=0
2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
Target=208680 Hashed=26567
InternalReservation=2130 ExternalReservation=57 Min Free=512
2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
TotalPages=22931 InUsePages=22931
2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
Reserved=2544
OS Committed=2487
OS In Use=2468
Query Plan=166599 Optimizer=3
General=14803
Utilities=7 Connection=2910
2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
Locks=147
SQLCache=1236 Replication=2
LockBytes=2 ServerGlobal=43
Xact=1862
2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
Maximum=13450 Available=13392
2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
2005-04-22 07:16:36.70 server Insufficient memory available..
I'm currently using SQL Server 2000 Driver for JDBC (with
SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
calls that don't have a corresponding sp_cursorclose.
Help is greatly appreaciated here!
SQL ran out of free buffers (Free=0). You should probably apply the latest
SQL Server hotfix and update JDBC drivers to prevent problems such as 818095
and 837957. In addition, there are changes in the latest SQL hotfixes which
allow Lazy Writer to run more aggressively when it detects a low number of
free buffers.
If the problems persist engage MS product support and have them check your
server for additional leaks.
Adrian
"SS" <SS@.discussions.microsoft.com> wrote in message
news:884EB064-D4C5-4454-A8B4-A151EBC0ED11@.microsoft.com...
>I have an application connected to a machine running MSSQL Server 2000 SP3a
> Std Edition. Machine is 2.8GHZ, Windows Server 2000. This application runs
> extensive query periodically. Over a period of time, I notice through Task
> Manager the sqlservr.exe memory usage has grow to ~1.6GB. When this
> happen,
> the application experience slowdown and eventually hang out.
> SQL ERRORLog show
> 2005-04-22 07:16:36.45 spid1 LazyWriter: warning, no free buffers
> found.
> 2005-04-22 07:16:36.45 spid1 Buffer Distribution: Stolen=159182
> Free=0
> Procedures=22931
> Inram=0 Dirty=24545 Kept=0
> I/O=0, Latched=2022, Other=0
> 2005-04-22 07:16:36.45 spid1 Buffer Counts: Commited=208680
> Target=208680 Hashed=26567
> InternalReservation=2130 ExternalReservation=57 Min Free=512
> 2005-04-22 07:16:36.45 spid1 Procedure Cache: TotalProcs=3969
> TotalPages=22931 InUsePages=22931
> 2005-04-22 07:16:36.45 spid1 Dynamic Memory Manager: Stolen=182112 OS
> Reserved=2544
> OS Committed=2487
> OS In Use=2468
> Query Plan=166599 Optimizer=3
> General=14803
> Utilities=7 Connection=2910
> 2005-04-22 07:16:36.45 spid1 Global Memory Objects: Resource=11637
> Locks=147
> SQLCache=1236 Replication=2
> LockBytes=2 ServerGlobal=43
> Xact=1862
> 2005-04-22 07:16:36.45 spid1 Query Memory Manager: Grants=1 Waiting=0
> Maximum=13450 Available=13392
> 2005-04-22 07:16:36.70 server Error: 17803, Severity: 20, State: 17
> 2005-04-22 07:16:36.70 server Insufficient memory available..
> I'm currently using SQL Server 2000 Driver for JDBC (with
> SelectMethod=Cursor). From SQL Profiler, I do see alot of sp_cursorfetch
> calls that don't have a corresponding sp_cursorclose.
> Help is greatly appreaciated here!
>

Error: "grantor does not have grant permission"

Hi all,

Before using SQL Server 2000 Developer Edition I did not get this error message. I had been using the trial edition of SQL Server 2000.

I only get it with stored procedures.

I solved my problem by giving the ASPNET login "db_owner" privs, which I didn't need to with the trial edition and is not best practice from a security angle.

I login under the Windows based admin account. (not using mixed mode).

Hope someone can shed some light.

Thanks.Placing a statement like:

"grant exec to dbo.testProc for {role}"

Inside the procedure can cause this problem, and was the culprit in this case.

Of course the ASPNET account (executing the sp) does not have grant permission!

Error, while connecting with SQL Server 2005 express edition

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact under the default settings of SQL SERver does not allow remote connections.
(provider:Named Pipes Provider, error: 40-Could not open a connection to SQL Server)

Hi,

Did you enabled setting to allow remote connection? Please see the blog for setup Remote connection

http://blogs.msdn.com/sqlexpress/

Hope that helps,

Lan

|||abrahampackiaraj
thank you, I already verified the tick mark in the check box of"allow remote connections" and I restarted the system. but this errorfollows up|||

did you manage to solve this problem as i have the same issue

Thanks

|||but while installing asp.net 2.0 , it doesn't even ask for that option. where from i can get that...|||whre from you got the option to tick the check box of "allow remote connections", i dont find that..|||

You can find it in SQL Server Surface Area Configuration. You may take a look at this post:

http://forums.asp.net/thread/1347652.aspx

Error with install of sept CTP Enterprise edition

Does SQL Server 2005 Sept CTP not support installation on XP? When I am installing, it gives me a warning that some things may not work with this OS, then when I get to the next screen I can't install anything.

Have you checked the pre-requisites such as .NET framework and IE version etc.
BTW what is the edition of XP & edition of CTP used?|||I am trying to install the september ctp enterprise edition on a machine with xp/sp2. I have reviewed the prereqs and I meet all of them. It says XP with sp2 and 512 ram; both are satisfied. I don't see any prereqs for .NET and I think that is because it installs .NET 2.0 when it installs. Any other ideas?|||Here is the warning I get when starting the install of the september CTP Enterprise version on a machine with XP/SP2 installed. If i continue to the components available for install, then the only thing enabled is 'Workstation components, ...'. All the actual database stuff is disable for install.

- SQL Server Edition Operating System Compatibility (Warning)

Messages

SQL Server Edition Operating System Compatibility

Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.

|||Enterprise Edition needs a server OS. You can install Express, Workgroup, Std and Developer Editions on XP, ie Desktop OS's|||I figured that was the problem. However, the download site does list XP/SP2 as a compatible OS for the enterprise edition. The bullet below was copied directly from the download page.

Supported Operating Systems: Microsoft Windows 2000 Service Pack 4; Windows Server 2003 Service Pack 1; Windows XP Service Pack 2

Error while trying to execute a user defined function

Hi,

I'm working on SQL SERVER 2005 Standard edition.

I created a user defined function on the dbo schema.

Is it possible to invoke a user defined function in a select clause only with the name of this function without precising the name of the schema.

if my function is called TOTO(), can i execute the command :

SELECT TOTO()

go

Actually when i try to execute this command i have the following error message :

Message 195, level 15, state 10 :

'TOTO' is not a known built-in function name option.

Can someone help me to solve this issue ?

try

select dbo.toto()

|||

I know that it works but i want to know if it's possible to execute this function without specifying the schema just like this :

SELECT toto()

go

|||

Locolito:

The response to your question is no: WIth a scalar function you must supply the "schema" qualifier -- such as dbo; however, the schema qualifier is not required with a table function.

Dave