To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.
Date Time Version Size File name Platform
06/06/2000 04:24 7.00.872 4913 KB s70872i.exe Intel
06/06/2000 04:24 7.00.872 11,329 KB s70872a.exe Alpha
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.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
|DisallowAdhocAccess=1||Ad hoc access will always be denied on the provider.|
|DisallowAdhocAccess=0||Ad hoc access will always be allowed on the provider.|
|DisallowAdhocAccess does not exist (SQL Server 7.0 Service Pack 2 has not been applied yet)||Ad hoc access will always be allowed on the provider.|
|DisallowAdhocAccess does not exist (SQL Server 7.0 Service Pack 2 has been applied)||Ad hoc access will be allowed for members of the SysAdmin server role and for Windows NT security connections, and will be disallowed for normal users using standard security connections for this provider.|
Article ID: 266008 - Last Review: Jun 22, 2014 - Revision: 1