Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 817845 - Last Review: April 6, 2004 - Revision: 9.1
FIX: "Login Failed for User 'SYSTEM'" Error When You Use OPENROWSET Function Without UserName
When you run a query with the
OPENROWSET function, and you do not specify the username and password in the
function, you receive the following error message:
Login failed for user 'SYSTEM'
An authenticated standard SQL user who executes ad hoc
queries in SQL server, and does not specify a username and a password (or an
application that runs over Microsoft SQL OLE DB Provider, and does not specify
a username and a password), can cause a connection to occur that has SQL Server
Service account as the username, and has a blank password. Therefore, when the
SQL Server Service is running under the SYSTEM account, you receive the error
message that is listed in the "Symptoms" section that specifies "SYSTEM" as the
user.
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
This bug was corrected in MDAC 2.7 Service Pack 1 Refresh.
Steps to Reproduce the Behavior
- In SQL Query Analyzer, run the following statement:
select * from openrowset('sqloledb','';;,'select * from pubs.dbo.authors') - You receive the error message that is described in the
"Symptoms" section of this article.
For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base:
269587Â
(http://kbalertz.com/Feedback.aspx?kbNumber=269587/EN-US/
)
INF: Windows Authentication is the Default Security Mode After a SQL Server 2000 Typical Installation
APPLIES TO
- Microsoft Data Access Components 2.7
- Microsoft SQL Server 2000 Service Pack 3
| kbserver kbuser kbquery kbservice kbbug KB817845 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate