- A SQL Server stored procedure exists in one database that selects records from a table in a different database.
- The resulting recordset is returned to an application or service.
- That recordset is then passed out-of-process as a disconnected ADO (ActiveX Data Objects) recordset to another client application.
- An attempt is made to update the disconnected recordset.
If the recordset is never marshaled out of process but is delivered directly to the process that is attempting to update it instead, the UPDATE statement succeeds.
Examination of trace logs show that the correct database.owner.tablename syntax was used when selecting the records, but only the table name was used when constructing the UPDATE statement.
Because the Connection currently points to the database containing the stored procedure and the table does not exist in that database, "Invalid Object Name" errors are returned.
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:
Date Version Size File name
7/22/99 2.10.4321 203KB msdaprst.dll
This problem was corrected in MDAC 2.5.
For the latest version of Microsoft Data Access Components (MDAC), see the following Microsoft Web site:
IMPORTANT!It is not recommended that you install this hotfix on a machine that is currently running MDAC 2.1 SP2 (version 2.12.4202) or later. This hotfix should only be used with machines running MDAC 2.1 SP1 (version 2.10.3711) or earlier.
In order to alleviate memory fragmentation problems, significant code changes were made between MDAC 2.1 SP1 and MDAC 2.1 SP2. While it is not expected that any fatal errors occur if this hotfix is applied to MDAC 2.1 SP2, doing so is strongly discouraged.
A separate hotfix exists to address this problem in MDAC 2.1 SP2.
Please see the REFERENCES section of this article for more information.
- Close or stop any applications or services that are using Msdaprst.dll. This may include Internet Information Server (IIS), Microsoft Transaction Server (MTS), Microsoft Distributed Transaction Coordinator (DTC), and any ADO or OLE DB applications.
- Download the hotfix version of Msdaprst.dll into a temporary folder.
- Locate and rename the current version of Msdaprst.dll, which should be in the \Program Files\Common files\System\msadc folder.
- Copy the hotfix version of Msdaprst.dll into the same location and restart your services and applications.
Important Notice for Microsoft Windows 95/98 UsersIf you are installing this fix onto a computer running Windows 95 or a computer with the original release of Windows 98, you might need to install the Windows 98 Migration DLL included with this fix.
NOTE: Read the Migrate_qfe.txt file that is included in the Migration.exe file included with the download.
For information about this hotfix as it applies to MDAC 2.1 SP2, please refer to the following article found in the Microsoft Knowledge Base:
For more information on the memory fragmentation issue referenced above, please refer to the following article found in the Microsoft Knowledge Base::
Article ID: 238750 - Last Review: Jun 22, 2014 - Revision: 1