Inserting an Excel Worksheet Object May Fail Under Windows NT

View products that this article applies to.

This article was previously published under Q173191

SYMPTOMS

The insert object function of a container application may fail if the server application takes a long time to load. For example, if the autosave feature of Microsoft Excel is turned on and you attempt to insert an Excel Spreadsheet into a PowerPoint document, any of the following errors may occur:

Sorry, the source application is busy and cannot respond immediately. You can switch to the other application and try to resolve the problem.

-or-

The Server application, source file, or item cannot be found. You should reinstall the server application.

-or-

The Server Application, source file, or item cannot be found. Make sure the Application is properly installed and that it has not been deleted, moved, or renamed.

Back to the top

CAUSE

Excel takes more time to load when the Autosave ADDIN is enabled. The load delay in Excel results in RPC_E_SERVERCALL_RETRYLATER being returned. Windows NT is not properly handling the retry mechanism for OLE and therefore RPC_E_CALL_REJECTED is returned. This causes the operation to not succeed.

Back to the top

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

Back to the top

Windows NT 3.51

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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 usual 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      Time    Version      Size    File name     Platform
   -------------------------------------------------------------
   08/12/97  09:34p                48,112 scm.exe       x86
   08/12/97  08:33p                74,512 scm.exe       Alpha

Back to the top

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Back to the top