Article ID: 266008 - View products that this article applies to.
This article was previously published under Q266008
BUG #: 57901 (SQLBUG_70)
After applying SQL Server 7.0 Service Pack 2, a user may receive the following error message when using the OPENROWSET Transact-SQL function:
This can occur even when Ad Hoc Query Access has been explicitly allowed for the OLE DB provider being used.
7415 - Ad hoc access to OLE DB provider '%ls' has been denied. You must access this provider through a linked server.
The OPENROWSET function will succeed most of the time, but the error may occur a small amount of the time. The registry value DisallowAdhocAccess may also have to be added, depending on how the clients are connecting to SQL Server; see the table in the "More Information" section of this article for additional information.
A change was made in SQL Server 7.0 Service Pack 2 as detailed in the following article in the Microsoft Knowledge Base:
256052This altered the security behavior of the OPENROWSET function depending on the registry value of DisallowAdhocAccess for each OLE DB provider.
(http://support.microsoft.com/kb/256052/EN-US/ )FIX: Sqlservr.exe Non-Trusted Connection Through OPENROWSET
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799For more information, contact your primary support provider.
(http://support.microsoft.com/kb/274799/ )INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information on the OPENROWSET function, see the "OPENROWSET (T-SQL)" topic in SQL Server 7.0 Books Online. For more information on the DisallowAdhocAccess registry value, see the "Configuring OLE DB Providers for Distributed Queries" topic in SQL Server 7.0 Books Online. The following are the rules governing the behavior of the DisAllowAdhocAccess registry key:
Collapse this tableExpand this table
Contact us for more help
Connect with Answer Desk for expert help.