sql error 15138: windows

Showing posts with label windows. Show all posts

Thursday, March 29, 2012

Error 18456" error message when you specify configuration database

I appreciate if some one please help me to solve the following problem
SYMPTOMS
I am runnning the Setup program to install Microsoft Windows SharePoint
Services. After the Setup program is completed successfully, I configure
Windows SharePoint Services settings in SharePoint Central Administration. I
then specify configuration database settings on the Set Configuration
Database Server page of SharePoint Central Administration, and then I click
OK. Then, I receive one of the following error messages:
"Error 18456" error message when you specify configuration database settings
on the Set Configuration Database Server page of SharePoint Central
Administrator"
I have gone through the article on
http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me out.
Please let me know if some one came across this problem & i could solve it
with your support
Thanks in advance
RegardsError 18456
Severity Level 14
Message Text
Login failed for user '%ls'.
Make sure that the user you specified is correct and has the correct password.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Yakoob" wrote:
> I appreciate if some one please help me to solve the following problem
>
> SYMPTOMS
> I am runnning the Setup program to install Microsoft Windows SharePoint
> Services. After the Setup program is completed successfully, I configure
> Windows SharePoint Services settings in SharePoint Central Administration. I
> then specify configuration database settings on the Set Configuration
> Database Server page of SharePoint Central Administration, and then I click
> OK. Then, I receive one of the following error messages:
> "Error 18456" error message when you specify configuration database settings
> on the Set Configuration Database Server page of SharePoint Central
> Administrator"
> I have gone through the article on
> http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me out.
> Please let me know if some one came across this problem & i could solve it
> with your support
> Thanks in advance
> Regards|||Here it is not asking for any user, In database connection type, i have using
the option "user windows authentication" so i dont know which account its
going to use here to create the database.
Please help me out
Thanks
"Mike Epprecht (SQL MVP)" wrote:
> Error 18456
> Severity Level 14
> Message Text
> Login failed for user '%ls'.
>
> Make sure that the user you specified is correct and has the correct password.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Yakoob" wrote:
> > I appreciate if some one please help me to solve the following problem
> >
> >
> > SYMPTOMS
> >
> > I am runnning the Setup program to install Microsoft Windows SharePoint
> > Services. After the Setup program is completed successfully, I configure
> > Windows SharePoint Services settings in SharePoint Central Administration. I
> > then specify configuration database settings on the Set Configuration
> > Database Server page of SharePoint Central Administration, and then I click
> > OK. Then, I receive one of the following error messages:
> > "Error 18456" error message when you specify configuration database settings
> > on the Set Configuration Database Server page of SharePoint Central
> > Administrator"
> >
> > I have gone through the article on
> > http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me out.
> > Please let me know if some one came across this problem & i could solve it
> > with your support
> > Thanks in advance
> > Regards|||It's probably [NT AUTHORITY\NETWORK SERVICE]. You should be able to see the
error in the SQL Error log (Open SQL Enterprise Manager and connect to the
SQL Server instance in question and navigate to Management>SQL Server Logs)
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Yakoob" <Yakoob@.discussions.microsoft.com> wrote in message
news:D91EF3D6-7AE4-4707-9F60-FEEFB797B771@.microsoft.com...
> Here it is not asking for any user, In database connection type, i have
> using
> the option "user windows authentication" so i dont know which account its
> going to use here to create the database.
> Please help me out
> Thanks
> "Mike Epprecht (SQL MVP)" wrote:
>> Error 18456
>> Severity Level 14
>> Message Text
>> Login failed for user '%ls'.
>>
>> Make sure that the user you specified is correct and has the correct
>> password.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>>
>> "Yakoob" wrote:
>> > I appreciate if some one please help me to solve the following problem
>> >
>> >
>> > SYMPTOMS
>> >
>> > I am runnning the Setup program to install Microsoft Windows SharePoint
>> > Services. After the Setup program is completed successfully, I
>> > configure
>> > Windows SharePoint Services settings in SharePoint Central
>> > Administration. I
>> > then specify configuration database settings on the Set Configuration
>> > Database Server page of SharePoint Central Administration, and then I
>> > click
>> > OK. Then, I receive one of the following error messages:
>> > "Error 18456" error message when you specify configuration database
>> > settings
>> > on the Set Configuration Database Server page of SharePoint Central
>> > Administrator"
>> >
>> > I have gone through the article on
>> > http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me
>> > out.
>> > Please let me know if some one came across this problem & i could solve
>> > it
>> > with your support
>> > Thanks in advance
>> > Regards|||Thanks for your reply, yes i understand that it iw using NT AUTHORITY\NETWORK
SERVICE, but even this i didn't find in SQL server logs as you have
mentioned. If i have to check for correct password then where? because i am
not providing here any password during "set configuration database server". I
am selecting the following options which is mandatory as per installation
guide for MS project 2003 server.
1. Database server = "i give sql server name"
2. SQL server database name = "database name as sharepointdb"
3. selected the option "use windows authentication
4. then last option " users already have domain accounts. Do not creat
active directory accounts.
I dont see any NT AUTHORITY account in active directory to give permission
for database create or to see for its password, please let me know
Thanks & Regards
"Jasper Smith" wrote:
> It's probably [NT AUTHORITY\NETWORK SERVICE]. You should be able to see the
> error in the SQL Error log (Open SQL Enterprise Manager and connect to the
> SQL Server instance in question and navigate to Management>SQL Server Logs)
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Yakoob" <Yakoob@.discussions.microsoft.com> wrote in message
> news:D91EF3D6-7AE4-4707-9F60-FEEFB797B771@.microsoft.com...
> > Here it is not asking for any user, In database connection type, i have
> > using
> > the option "user windows authentication" so i dont know which account its
> > going to use here to create the database.
> > Please help me out
> >
> > Thanks
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> >> Error 18456
> >> Severity Level 14
> >> Message Text
> >> Login failed for user '%ls'.
> >>
> >>
> >> Make sure that the user you specified is correct and has the correct
> >> password.
> >>
> >> Regards
> >> --
> >> Mike Epprecht, Microsoft SQL Server MVP
> >> Zurich, Switzerland
> >>
> >> MVP Program: http://www.microsoft.com/mvp
> >>
> >> Blog: http://www.msmvps.com/epprecht/
> >>
> >>
> >>
> >> "Yakoob" wrote:
> >>
> >> > I appreciate if some one please help me to solve the following problem
> >> >
> >> >
> >> > SYMPTOMS
> >> >
> >> > I am runnning the Setup program to install Microsoft Windows SharePoint
> >> > Services. After the Setup program is completed successfully, I
> >> > configure
> >> > Windows SharePoint Services settings in SharePoint Central
> >> > Administration. I
> >> > then specify configuration database settings on the Set Configuration
> >> > Database Server page of SharePoint Central Administration, and then I
> >> > click
> >> > OK. Then, I receive one of the following error messages:
> >> > "Error 18456" error message when you specify configuration database
> >> > settings
> >> > on the Set Configuration Database Server page of SharePoint Central
> >> > Administrator"
> >> >
> >> > I have gone through the article on
> >> > http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me
> >> > out.
> >> > Please let me know if some one came across this problem & i could solve
> >> > it
> >> > with your support
> >> > Thanks in advance
> >> > Regards
>
>

Error 18456" error message when you specify configuration database

Error 18456 with logon using Windows accounts

Hi,
I've installed SQL 2000 SP3 on a Windows 2000 server with Active Directory (not the PDC), but when I try to logon using a Windows account (domain\user) I get the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
SQL State: 28000
DB error: 18456
The same happens when I try to logon with the Query Analyzer or register the server in Enterprise Manager. I looked around other forums to figure this one out but none of the tips there worked:
- Authentication is mixed mode
- IIS is not installed
- There is a login created in SQL for the Windows user

Any idea's?In the back of my mind somewhere, I have a recollection that when AD is installed the Local Users for that server are disabled. Was the user you were trying to log in as Local or Domain?

I think I would try creating a Domain User, adding that user into the Local Computer Administrators group and then logging in as that Domain User.

Regards,

Hugh Scott

Originally posted by dbJeff
Hi,
I've installed SQL 2000 SP3 on a Windows 2000 server with Active Directory (not the PDC), but when I try to logon using a Windows account (domain\user) I get the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
SQL State: 28000
DB error: 18456
The same happens when I try to logon with the Query Analyzer or register the server in Enterprise Manager. I looked around other forums to figure this one out but none of the tips there worked:
- Authentication is mixed mode
- IIS is not installed
- There is a login created in SQL for the Windows user

Any idea's?|||Hugh, you're right that Local Users are disabled with AD, but Local Groups are as well. Any other idea's?

Originally posted by hmscott
In the back of my mind somewhere, I have a recollection that when AD is installed the Local Users for that server are disabled. Was the user you were trying to log in as Local or Domain?

I think I would try creating a Domain User, adding that user into the Local Computer Administrators group and then logging in as that Domain User.

Regards,

Hugh Scott|||D'oh! That wasn't very smart of me!

Did you try using sp_grantaccess to ensure that the domain account you were trying to use can access the server?

I don't have much experience running SQL Server with AD; I am running a home network with AD and SQL running on the PDC. I am authenticating using a local account on my Windows XP notebook with no problems. Before I promoted the server to DC, I had a local account with identical credentials in the Administrators group. I have had no problems keeping that account up and running.

I'm afraid I don't have many other suggestions...sorry.

Regards,

Hugh

Originally posted by dbJeff
Hugh, you're right that Local Users are disabled with AD, but Local Groups are as well. Any other idea's?

error 18456 when trying to connect to 2005 using odbc

Hi all

I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

error 18456 when trying to connect to 2005 using odbc

Hi all

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

Error 18456 State 6

Hi,

I am trying to connect to a remote SQL server via Management Studio. I am using the windows credentials I use to log into the computer but when I enter the same domain\username and password I get error 18456. I check the logs and see it is a state 6 error. After checking http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx I see that means

Attempt to use a Windows login name with SQL Authentication

Is it possible for me to access a SQL server remotely?

Thanks

From your description, I would assume that you chose “SQL Server Authentication” and provided a user name that was a Windows user name, correct? “SQL Server Authentication” is used only for principals whose information is completely under the control of the SQL Server instance (i.e. the SID, login and password are only valid to SQL Server).

When using Windows authentication the server will use the Windows token from your client program (in this case Management Studio) to authenticate the connection, without the need to type any login or password.

When you connect to SQL Server using Management Studio, make sure you choose the option “Windows Authentication” for the “Authentication” value, the user name and password fields should be grayed out.

I hope this helps, but let us know if you still have any questions.

-Raul Garcia

SDE/T

SQL Server Engine

sql

Tuesday, March 27, 2012

Error 18452 Login failed for user <null>. The user account is not

We have a SQL 2005 installation using SQL and Windows Authentication. We
have a login that is mapped to a active directory group and has the
appropriate permissions to the database. However, when we try to create
an ODBC connection to the server from an XP client (and the user is a
member of the appropriate domain group) we get the above mentioned error.
Also logged on the SQL server is the following error:
SSPI handshake failed with error code 0x8009030c...
The only info I can find on this error has to do with IIS
configurations, but I don't see what IIS has to do with this as we are
only trying to make an ODBC connection.Maybe your service account is Local System.
You can change to AD Service account.
"Jan Leste"?? ??? ??:

> We have a SQL 2005 installation using SQL and Windows Authentication. We
> have a login that is mapped to a active directory group and has the
> appropriate permissions to the database. However, when we try to create
> an ODBC connection to the server from an XP client (and the user is a
> member of the appropriate domain group) we get the above mentioned error.
> Also logged on the SQL server is the following error:
> SSPI handshake failed with error code 0x8009030c...
> The only info I can find on this error has to do with IIS
> configurations, but I don't see what IIS has to do with this as we are
> only trying to make an ODBC connection.
>

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I added my domain\userName in sql with no problems and added the account to the sysadmin server role. However, I noticed my credentials on my pc are not listed as domain\userName but rather ComputerName\UserName. I think this is what is causing the problem but I am not sure. Can anyone lend a hand?

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

Also, to get additional information, please connect the SQL Server Profiler and monitor the Audit Login and Audit Login Failed events in the Security category. Check to see what are the credentials that appear for the login attempt.

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

This is strange - it should work without any problems if the machines are in the same domain and you attempt to connect as a domain user. Are you only seeing this issue with SQL Server? Can you access shares that are exclusively ACLed to a domain user from these 2000 machines?

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

User1 logs onto MachineA and uses SQL Managment Studio to connect to database engine on MachineA (Local SQL Server), everything works. Then tries to connect to database engine on MachineB everything works.

User1 logs onto MachineB and uses SQL Managment Studio to connect to database engine on MachineB (local SQL Server), everything works. Then tries to connect to database engine on MachineA (remote SQL Server) fails with error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsorft SQL Server, Error: 18452)

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

The Edition shouldn't make any difference. I don't know a reason for this behavior. Please open a bug by filling a report on the Product Feedback site at http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220 and we'll continue from there.

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||I get the exact same problem running the command "sqlcmd -E -S <RealIPAddressOrFullyQualifiedHostnameOfLocalHost>" (eg: "sqlcmd -E -S myhost.mydomain.com") on a clean machine where SQL Server 2005 Standard Edition has just been installed with mixed authentication and TCP/IP protocol enabled. The command however works if the local IP address 127.0.0.1, or the local hostname without the domain is being used. This command also works: "sqlcmd -E -S tcp:myhost". Any idea?|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

Go to Start > Programs > Microsoft SQL Server > Enterprise Manager
Right-click the Server name, select Properties > Security
Under Authentication, select SQL Server and Windows
The server must be stopped and re-started before this will take effect

SQL Server 2005:

Go to Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio
Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect..."

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

|||I had a similar problem after creating a new (SQL) logon. Having restarted the following services it was resolved:

SQL Server ($instancename)
SQL Server Browser

SQL Server Express 2005

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

sql

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452 (not associated with a trusted sql server connection)

Using sql2005 on a Novell network...

When attempting to log into Mgt Studio using windows authentication I am getting the error: Error 18452 (not associated with a trusted sql server connection) .

I'd appreciate any help,

Thanks.

Scott

Can you please post the exact error message from the SQL Server errorlog including the number and state of the error?

You'll probably not be able to login anyway if your credentials are different from the ones you specified in SQL Server, but I would expect to see a different error in that case.

Thanks
Laurentiu

|||

Hi,

switch on the login audits at SQL Server to see which user tries to logon to the server.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am having similar issue.

When using Management Studio, XP clients can connect using widows authentication but windows 2000 clients cannot connect using windows authentication.

Both XP and win2000 can connect using SQL Server authentication.

It replaces my domain name with the workstation number and tries to connect using workstation\user_id rather than domain_name\user_id.

I ran a profiler and this is what I got:

|||

Are all your machines in the same domain or are they in different domains?

Thanks
Laurentiu

|||

These are all part of the same domain....

Thanks

|||

Thanks
Laurentiu

|||

I am getting the same problem.

MachineA:
Windows XP Pro.
SQL Server 2005, Standard Edition
Machine on Domain XXX
User XXX\User1 is added to Administrators group

MachineB:
Windows XP Pro.
SQL Server 2005, Developer Edition
Machine on Domain XXX
User XXX\User1 is added to Adminitrators group

I have run the SQL Server Surface Area Configuration on both machines and tried to configure them exactly the same.

I have checked Name resolution on both machines, no issues found. I can connect to other resources (\\MachineA\C$ works from MachineB and \\MachineB\C$ works from MachineA).

I am going to try to install the Developer edition on Machine A to see if there is a difference, but I somehow don't think that it will make a difference...

Luis

|||

Thanks
Laurentiu

|||

Hi...I developed a small application using delphi to run queries on a SQL Server machine. This application worked well on my PC and via the network when I set the database name and server name.

However, as I tried to make this application work on another SQL Server Machine (which has the same database and I have modified the server name in the Install Express)...I get an error

"...not associated with trusted SQL connection"

then goes on to reference my Database object in the data module of the application...

I tried almost everything from hard-coding a username and password in the Database object in the application...to no avail.

Thanks again.

Blackwidow25

|||

Have you checked if the other SQL Server machine is using mixed mode authentication?

If it does, try troubleshooting the SQL authentication using Management Studio or sqlcmd.

Thanks
Laurentiu

|||

I think Laurentiu is right, I have found an article from IBM website:

"....Solution
To resolve this issue, follow the instructions to set User Authentication.
SQL Server 2000:

SQL Server 2005:

http://www-1.ibm.com/support/docview.wss?uid=swg21119906

It has solved my problem, so I hope it could be helpful for you too.

|||

I am also had these same problem and struggled for long period. Finally I got these forum and succeeded. Thank you very much.

Regards,

Jose

|||

I had the same message when trying to connect to a SQL 2005 instance through Windows authentication.

The client was written is VB 2005 and used OLEDB client access (not the SQL native client!)

Switching the server to both SQL and Windows authentication did not solve the problem.

I checked different parameters for the connection string and, finally, found the next one that works:

'Connection information to connect to the database server to retrieve data

'This is connecting to SQL server through OLEDB

Dim ConnectionString As String = ""

ConnectionString = "Provider=SQLNCLI;"

ConnectionString += "Server=YourServerName;Database=YourDatabaseName;"

ConnectionString += "Integrated Security=SSPI;"

Important to note that Integrated Security=True; does not work.

Horia

Error 18452

Hi,
If I connect to SQLServer Express via Windows Authentication it works fine. But if I use SQL Server Authentication it doesn't work with a new created user and sa (with a new password) too. I turned mixed mode on, registry key HKLM\Software\Microsoft\Microsoft Sql Server\MSSQL.1\\MSSQLServer\login has the value 2 and all ports are set to 1433 but there is still error 18452. Any suggestions?

Did you restart the server service ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Yes, severeal times.
|||I guess the system you configured and the system you are connecting to are tw different ones then.|||No, it's the same system and I have only this one in the moment.
|||

What is the exact error message that you are getting back? Take a look at the errorlog as well to see what message is logged there.

How are you trying to connect? If you're connecting through an application, make sure that you don't specify integrated authentication in the connection string.

Thanks
Laurentiu

|||Restarting the server process was not enough. I had to restart windows and now it works.
Thank you.
sql

Error 17883 in SQL error log

Hello,
We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
the following error recently:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 12 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
Scheduler 0.
We also get error like below daily:
SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [E:\Microsoft SQL
Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
handle is 0x0000053C. The offset of the latest long IO is: 0x00000000010000
The SQL server is used as data warhouse server, so there are a lots of IO.
I appreciate any suggestions or comments.
Thanks!
Sugarhigh,
For 17883 here is a whitepaper
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx#ELDAC
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
Basically, you need to investigate your hardware utilization, particularly
(as you might expect) measuring your IO subsystem which sounds like it is
strained. Most likely you will need to do some upgrades to your equipment.
RLF
"Sugarhigh" <sugarhigh@.community.nospam> wrote in message
news:EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com...
> Hello,
> We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
> the following error recently:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 12 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
> Scheduler 0.
> We also get error like below daily:
> SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [E:\Microsoft SQL
> Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
> handle is 0x0000053C. The offset of the latest long IO is:
> 0x00000000010000
> The SQL server is used as data warhouse server, so there are a lots of IO.
> I appreciate any suggestions or comments.
> Thanks!
|||Hello,
Thank you for posting here.
To better understand the error message, you must first understand how SQL
Server uses a User Mode Scheduling (UMS) Ums.dll helper file.
Microsoft SQL Server 2000 use logical schedulers. These schedulers help to
make sure that SQL Server maximizes operating system resource usage in
relation to key database action paths. The UMS layer makes sure that SQL
Server correctly uses Win32 events to strictly control thread and fiber (or
both) scheduling visibility to the operating system. By strictly
controlling the threads or fibers that can run, SQL Server can maximize CPU
usage as it relates to database primitives such as locking.
For example, logical scheduling permits lock waiters to sleep
(WaitForSingleObject on a Win32 event) until the lock owner releases the
lock and signals (SetEvent) them to wake up.
For more information, please refer to the following article:
New concurrency and scheduling diagnostics added to SQL Server (319892)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319892
Note: The format of the 17833 message is different for separate versions of
the SQL Server product; however, the meaning is the same.
However, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
At the same time, please also ensure that latest update for SQL Server 2000
Service Pack 4 has been installed. We can download it from the following
website:
Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86
and x64 Based Systems
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9c9a
b140-bdee-44df-b7a3-e6849297754a
More related information:
=======================
892840FIX: 17883 errors may be written to the SQL Server error log when
you run a query that generates many floating point exception errors in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;892840
810885High-end disk subsystems may experience error 17883
http://support.microsoft.com/default.aspx?scid=kb;EN-US;810885
888666You may receive a 17883 error message when you run full-text queries
in SQL Server 7.0 or SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;888666
890730FIX: You receive a 17883 error message when you perform large
in-memory sort operations in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;890730
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Error 17883 in SQL error log
| thread-index: AcfVM7K5Tj5qumliSs2GiuzWV3+hMQ==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?U3VnYXJoaWdo?= <sugarhigh@.community.nospam>
| Subject: Error 17883 in SQL error log
| Date: Thu, 2 Aug 2007 11:34:02 -0700
| Lines: 23
| Message-ID: <EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:21828
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hello,
|
| We have a SQL server 2000 enterprise edition on SP4 on windows NT, and
got
| the following error recently:
|
| Sleeping until external dump process completes.
| Resuming after waiting on external debug process for 12 seconds.
| Stack Signature for the dump is 0x00000000
| Error: 17883, Severity: 1, State: 0
| Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
| Scheduler 0.
|
| We also get error like below daily:
| SQL Server has encountered 5359 occurrence(s) of IO requests taking
longer
| than 15 seconds to complete on file [E:\Microsoft SQL
| Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
| handle is 0x0000053C. The offset of the latest long IO is:
0x00000000010000
|
| The SQL server is used as data warhouse server, so there are a lots of
IO.
|
| I appreciate any suggestions or comments.
|
| Thanks!
|

Error 17883 in SQL error log

Hello,
We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
the following error recently:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 12 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
Scheduler 0.
We also get error like below daily:
SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [E:\Microsoft SQL
Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
handle is 0x0000053C. The offset of the latest long IO is: 0x00000000010000
The SQL server is used as data warhouse server, so there are a lots of IO.
I appreciate any suggestions or comments.
Thanks!Sugarhigh,
For 17883 here is a whitepaper
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx#ELDAC
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
Basically, you need to investigate your hardware utilization, particularly
(as you might expect) measuring your IO subsystem which sounds like it is
strained. Most likely you will need to do some upgrades to your equipment.
RLF
"Sugarhigh" <sugarhigh@.community.nospam> wrote in message
news:EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com...
> Hello,
> We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
> the following error recently:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 12 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
> Scheduler 0.
> We also get error like below daily:
> SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [E:\Microsoft SQL
> Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
> handle is 0x0000053C. The offset of the latest long IO is:
> 0x00000000010000
> The SQL server is used as data warhouse server, so there are a lots of IO.
> I appreciate any suggestions or comments.
> Thanks!|||Hello,
Thank you for posting here.
To better understand the error message, you must first understand how SQL
Server uses a User Mode Scheduling (UMS) Ums.dll helper file.
Microsoft SQL Server 2000 use logical schedulers. These schedulers help to
make sure that SQL Server maximizes operating system resource usage in
relation to key database action paths. The UMS layer makes sure that SQL
Server correctly uses Win32 events to strictly control thread and fiber (or
both) scheduling visibility to the operating system. By strictly
controlling the threads or fibers that can run, SQL Server can maximize CPU
usage as it relates to database primitives such as locking.
For example, logical scheduling permits lock waiters to sleep
(WaitForSingleObject on a Win32 event) until the lock owner releases the
lock and signals (SetEvent) them to wake up.
For more information, please refer to the following article:
New concurrency and scheduling diagnostics added to SQL Server (319892)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319892
Note: The format of the 17833 message is different for separate versions of
the SQL Server product; however, the meaning is the same.
However, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
At the same time, please also ensure that latest update for SQL Server 2000
Service Pack 4 has been installed. We can download it from the following
website:
Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86
and x64 Based Systems
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9c9a
b140-bdee-44df-b7a3-e6849297754a
More related information:
=======================892840 FIX: 17883 errors may be written to the SQL Server error log when
you run a query that generates many floating point exception errors in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;892840
810885 High-end disk subsystems may experience error 17883
http://support.microsoft.com/default.aspx?scid=kb;EN-US;810885
888666 You may receive a 17883 error message when you run full-text queries
in SQL Server 7.0 or SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;888666
890730 FIX: You receive a 17883 error message when you perform large
in-memory sort operations in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;890730
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Thread-Topic: Error 17883 in SQL error log
| thread-index: AcfVM7K5Tj5qumliSs2GiuzWV3+hMQ==| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?U3VnYXJoaWdo?= <sugarhigh@.community.nospam>
| Subject: Error 17883 in SQL error log
| Date: Thu, 2 Aug 2007 11:34:02 -0700
| Lines: 23
| Message-ID: <EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:21828
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hello,
|
| We have a SQL server 2000 enterprise edition on SP4 on windows NT, and
got
| the following error recently:
|
| Sleeping until external dump process completes.
| Resuming after waiting on external debug process for 12 seconds.
| Stack Signature for the dump is 0x00000000
| Error: 17883, Severity: 1, State: 0
| Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
| Scheduler 0.
|
| We also get error like below daily:
| SQL Server has encountered 5359 occurrence(s) of IO requests taking
longer
| than 15 seconds to complete on file [E:\Microsoft SQL
| Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
| handle is 0x0000053C. The offset of the latest long IO is:
0x00000000010000
|
| The SQL server is used as data warhouse server, so there are a lots of
IO.
|
| I appreciate any suggestions or comments.
|
| Thanks!
|

Thursday, March 29, 2012

Error 18456" error message when you specify configuration database

Error 18456" error message when you specify configuration database

Error 18456" error message when you specify configuration database

Error 18456 with logon using Windows accounts

error 18456 when trying to connect to 2005 using odbc

error 18456 when trying to connect to 2005 using odbc

Error 18456 State 6

Tuesday, March 27, 2012

Error 18452 Login failed for user <null>. The user account is not

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452 (not associated with a trusted sql server connection)

Error 18452

Error 17883 in SQL error log

Error 17883 in SQL error log

sql error 15138

Blog Archive

About Me