sql error 15138: log

Showing posts with label log. Show all posts

Thursday, March 29, 2012

Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

1923 is an RPC error that translates to "The specified profile entry could not be added." You'll need to search through the SQL Server Setup log files for more detail on what went wrong. Start by looking here and in the subdirectory:

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

|||I have found NO answer to this question anywhere online. I got mine working last night here is what I did:
I was trying to install it on a VPS I only have licensing for one terminal server session and I noticed that earlier in the day my RDP connection had timed out and I was still logged in so I kicked the old connection uninstalled all instances of SQL and tried again. Guess what? it didn't work...lol So I uninstalled everything again and restarted the VPS and then it installed. I have no idea exactly what was wrong but that is how I solved it. Hope it helps someone else out.
sql

Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

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

Error 18456 - domain admins only users that can authenticate

Server 2003
SQL 2000 SP3a
I have my server set up and my ODBC client configured. When I log in as
myself, as a domain admin, I can set my authentication to Windows (in my
ODBC), when I log on as a Domain Users, I cannot.
I get and error 18456. My server properties show SQL Server and Windows
authentication is allowed and there is no semi-colon in my password. What
security setting am I missing to allow my domain users to authenticate via
Windows authentication?
TIAHi,
Did you gave domain OS user access to SQL Server?
If not; open Enterprise manager and use Security option to add the Domain
user/group to SQL Server.
Thanks
Hari
SQL Server MVP
"dsb" <dsb@.discussions.microsoft.com> wrote in message
news:F7A3CA7A-1012-4673-8CDF-9B4B66583A3A@.microsoft.com...
> Server 2003
> SQL 2000 SP3a
> I have my server set up and my ODBC client configured. When I log in as
> myself, as a domain admin, I can set my authentication to Windows (in my
> ODBC), when I log on as a Domain Users, I cannot.
> I get and error 18456. My server properties show SQL Server and Windows
> authentication is allowed and there is no semi-colon in my password. What
> security setting am I missing to allow my domain users to authenticate via
> Windows authentication?
> TIA

Tuesday, March 27, 2012

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 18204 on backup of Transaction log

I have used SQL Server 2005 Database Maintenance Plans to establish full backups and hourly transaction log backups. The jobs that stem from the DB Subplans run fine and report no errors when I view the history on them, however I have noticed the following error in my SQL Server error log. I am not seeing a similar error for my database backups, only the hourly log backups. Space is not an issue. Any guidance on this one would be greatly appreciated.

18204 :
BackupDiskFile::CreateMedia: Backup device <'Path\logname'> failed to create. Operating system
error = 2(The system cannot find the file specified.).

Thanks,

Jason

Have you checked that all directories exists that are used in your maintenance plan?

Daan

|||Is the job which to take full and log backups succeeds ? if not check check if the sql startup account has modify privileges to the path mentioned in the maintenanance plan....

Thanxx
Deepak
|||

Please check if you have all the necessary permissions on the destination driver as Deepak said. Also, please check if this KB is applicable to you: http://support.microsoft.com/kb/255235

HTH

Error 18204 on backup of Transaction log

18204 :
BackupDiskFile::CreateMedia: Backup device <'Path\logname'> failed to create. Operating system
error = 2(The system cannot find the file specified.).

Thanks,

Jason

Have you checked that all directories exists that are used in your maintenance plan?

Daan

|||Is the job which to take full and log backups succeeds ? if not check check if the sql startup account has modify privileges to the path mentioned in the maintenanance plan....

Thanxx
Deepak
|||

Please check if you have all the necessary permissions on the destination driver as Deepak said. Also, please check if this KB is applicable to you: http://support.microsoft.com/kb/255235

HTH

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!
|

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
C" target="_blank">http://www.microsoft.com/technet/pr...x#ELDA
C
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstor.../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 fil
e
> 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/defaul...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/...n&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/defaul...kb;EN-US;892840
810885 High-end disk subsystems may experience error 17883
http://support.microsoft.com/defaul...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/defaul...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/defaul...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: examnotes <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 fil
e
| 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!
|sql

Monday, March 26, 2012

Error 17805

Error 17805 Severity 20 State 3 Invalid Buffer received
from client, logged in SQL Server (2K) Log.
Please help.Hi Allan,
I have SQL Server 2K with Service Pack 3 running on WIN
2K Advanced Server Plus Service Pack 3. The server is
accessed by clients over the internet.(Database engine
for an e-commerce site.)
The Error 17805 Severity 20 State 3 invalid buffer
recieved from client suggest the client is sending a
corrupt packet to the SQL server(only a guess).
Please help.
Regards
>--Original Message--
>I have no idea when you are seeing this as you do not
say but if it is after
>trying to pass data to SQL Server through a client app
then make sure that
>things like parameter definitions to stored procs etc
are the correct type
>i.e
>varchar not nvarchar etc etc
>
>
>--
>--
>Allan Mitchell (Microsoft SQL Server MVP)
>MCSE,MCDBA
>www.SQLDTS.com
>I support PASS - the definitive, global community
>for SQL Server professionals - http://www.sqlpass.org
>
>"Olutimi" <Olutimi@.hotmail.com> wrote in message
>news:09c001c366f6$c95ed850$a401280a@.phx.gbl...
>> Error 17805 Severity 20 State 3 Invalid Buffer received
>> from client, logged in SQL Server (2K) Log.
>> Please help.
>
>.
>|||You could also try making sure the clients are communicating through the
same API. Where I have seen mention of this error before is as I said in
command parameter (ADO) datatype mismatches
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Olutimi" <olutimi@.hotmail.com> wrote in message
news:0a0801c366fc$f930e9f0$a401280a@.phx.gbl...
> Hi Allan,
> I have SQL Server 2K with Service Pack 3 running on WIN
> 2K Advanced Server Plus Service Pack 3. The server is
> accessed by clients over the internet.(Database engine
> for an e-commerce site.)
> The Error 17805 Severity 20 State 3 invalid buffer
> recieved from client suggest the client is sending a
> corrupt packet to the SQL server(only a guess).
> Please help.
> Regards
>
> >--Original Message--
> >I have no idea when you are seeing this as you do not
> say but if it is after
> >trying to pass data to SQL Server through a client app
> then make sure that
> >things like parameter definitions to stored procs etc
> are the correct type
> >i.e
> >
> >varchar not nvarchar etc etc
> >
> >
> >
> >
> >--
> >
> >--
> >Allan Mitchell (Microsoft SQL Server MVP)
> >MCSE,MCDBA
> >www.SQLDTS.com
> >I support PASS - the definitive, global community
> >for SQL Server professionals - http://www.sqlpass.org
> >
> >
> >
> >"Olutimi" <Olutimi@.hotmail.com> wrote in message
> >news:09c001c366f6$c95ed850$a401280a@.phx.gbl...
> >> Error 17805 Severity 20 State 3 Invalid Buffer received
> >> from client, logged in SQL Server (2K) Log.
> >> Please help.
> >
> >
> >.
> >

Error 17055

Getting the following in the event log after starting the
sql services.
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17055
Date: 1/22/2004
Time: 2:37:21 PM
User: N/A
Computer: SMSPRIMARY
Description:
18456 :
Login failed for user 'smslab\smsadmin'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 0b 00 00 00 53 00 4d 00 ...S.M.
0010: 53 00 50 00 52 00 49 00 S.P.R.I.
0018: 4d 00 41 00 52 00 59 00 M.A.R.Y.
0020: 00 00 07 00 00 00 6d 00 .....m.
0028: 61 00 73 00 74 00 65 00 a.s.t.e.
0030: 72 00 00 00 r...
This is a SMS 2003 server.
Any info would be helpful. Thanks.Piedmont,
This is actually error 18456. It appears that smslab\smsadmin does not have
rights to login. From the BOL:
Error 18456
Severity Level 14
Message Text
Login failed for user '%ls'.
Explanation
You do not have permission to log in to the server.
Action
Contact a member of the sysadmin fixed server role to request login
permission.
Russell Fields
"Piedmont" <anonymous@.discussions.microsoft.com> wrote in message
news:26c401c3e11d$7e06ec70$a001280a@.phx.gbl...

quote:

> Getting the following in the event log after starting the
> sql services.
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (4)
> Event ID: 17055
> Date: 1/22/2004
> Time: 2:37:21 PM
> User: N/A
> Computer: SMSPRIMARY
> Description:
> 18456 :
> Login failed for user 'smslab\smsadmin'.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H.....
> 0008: 0b 00 00 00 53 00 4d 00 ...S.M.
> 0010: 53 00 50 00 52 00 49 00 S.P.R.I.
> 0018: 4d 00 41 00 52 00 59 00 M.A.R.Y.
> 0020: 00 00 07 00 00 00 6d 00 .....m.
> 0028: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0030: 72 00 00 00 r...
>
> This is a SMS 2003 server.
> Any info would be helpful. Thanks.

|||In enterprise manager under logins the user is listed and
has the right to login to the database.

quote:

>--Original Message--
>Piedmont,
>This is actually error 18456. It appears that

smslab\smsadmin does not have

quote:

>rights to login. From the BOL:
>Error 18456
>Severity Level 14
>Message Text
>Login failed for user '%ls'.
>Explanation
>You do not have permission to log in to the server.
>Action
>Contact a member of the sysadmin fixed server role to

request login

quote:

>permission.
>
>Russell Fields
>"Piedmont" <anonymous@.discussions.microsoft.com> wrote in

message

quote:

>news:26c401c3e11d$7e06ec70$a001280a@.phx.gbl...
the[QUOTE]
>
>.
>

|||Then I have no help for you, I am afraid. My only suggestions are clerical:
-- Double check the spelling of the login that you see in SEM just in case.
-- Doube check the server you are investigating, the domain of the login is
smslab, do you have an smsprd?
Sorry,
Russell Fields
"Piedmont" <anonymous@.discussions.microsoft.com> wrote in message
news:2bd501c3e126$2c249e30$a601280a@.phx.gbl...[QUOTE]
> In enterprise manager under logins the user is listed and
> has the right to login to the database.
>
> smslab\smsadmin does not have
> request login
> message
> the|||Perhaps the SMSAdmin password was changed. Make sure you can stop n start
this account from Control panel services. Also verify that it is a member
of the Builtin admin group via the local administrators group on the
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

Thursday, March 29, 2012

Error 1923 while installing SQL 2005 Express

Error 1923 while installing SQL 2005 Express

Error 18456 State 6

Error 18456 - domain admins only users that can authenticate

Tuesday, March 27, 2012

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 18204 on backup of Transaction log

Error 18204 on backup of Transaction log

Error 17883 in SQL error log

Error 17883 in SQL error log

Error 17883 in SQL error log

Monday, March 26, 2012

Error 17805

Error 17055

sql error 15138

Blog Archive

About Me