I was using PowerShell to create Excel object and run multiple linked tables and pivot refresh operations. I was randomly getting errors on the commands for different tables after a refresh operation or the pivot refresh operation. And one of such errors was:
Call was rejected by callee. (0x80010001 (RPC_E_CALL_REJECTED))
Setting the Excel Visible property to true stopped the errors, but I did not want the Excel window to be visible. I tried using Excel other properties — Ready, CalculationState to add pause, but did not solve the issue. Tried adding pause up to 10 seconds also (just to test), but still erros were there. If I tried manually, all refresh were completed in less than a second, so 10 second was a very long time but still it did not solve the issue, though it seemed to reduce the number of errors.
Finally I tried setting the ScreenUpdating property to true before refresh operations and set it back to false later. This solved the issue for me.
Sample PowerShell code ($xlapp is the variable for Excel COM Application object):
$xlapp.ScreenUpdating = $true
.
.<commands that cause issues>
.
$xlapp.ScreenUpdating = $false
Even though the Excel Visible property was set to false, setting ScreenUpdating to true helped and errors stopped.
I was using PowerShell to create Excel object and run multiple linked tables and pivot refresh operations. I was randomly getting errors on the commands for different tables after a refresh operation or the pivot refresh operation. And one of such errors was:
Call was rejected by callee. (0x80010001 (RPC_E_CALL_REJECTED))
Setting the Excel Visible property to true stopped the errors, but I did not want the Excel window to be visible. I tried using Excel other properties — Ready, CalculationState to add pause, but did not solve the issue. Tried adding pause up to 10 seconds also (just to test), but still erros were there. If I tried manually, all refresh were completed in less than a second, so 10 second was a very long time but still it did not solve the issue, though it seemed to reduce the number of errors.
Finally I tried setting the ScreenUpdating property to true before refresh operations and set it back to false later. This solved the issue for me.
Sample PowerShell code ($xlapp is the variable for Excel COM Application object):
$xlapp.ScreenUpdating = $true
.
.<commands that cause issues>
.
$xlapp.ScreenUpdating = $false
Even though the Excel Visible property was set to false, setting ScreenUpdating to true helped and errors stopped.
Hey Everyone hoping someone can help me I am at a dead end. Here is the scenario:
When we merge a document thru our database to send to efiling we are getting an error message stating Call was rejected by callee (RPC_E_CALL_REJECTED).
Now we only get this error message if we have any images in the document. If we take the state seal and the signature box out of the document everything works fine.
We have tried with only image different images different file types of images. Any image fails and creates this error.
What is happening is the document is being created in Word on the local machine, then once created and the save button is selected the database program uses the word 2010 export to pdf and creates the pdf which it them saves. This is where the error happens, and only happens with images in the documents.
We cannot change the way the pdf is exported as that is coded into the program we use.
Attached is the entire error we are getting. The client tool is what helps us get the efiling done and is part of the database program.
Any ideas would be welcomed
Thanks,
Phil
attach_file
Attachment
error.png
250 KB
- Remove From My Forums
-
Question
-
Hi All,
When I dealing with excel using our system following message is display
«OLE error code 0x80010001: Call was rejected by callee.»
Do you know what is cause it..?
Rachitha
Answers
-
Hi Rachitha,
This error usually shows up, if you’re doing not COM, but DCOM based automation. DCOM means: you’re adressing Excel on a different computer, over the network? It’s normally either caused by soem security settings or by misconfiguration of the DCOM
permissions.If you’re pasting your errormesage into Google, you’ll get some hints on how to resolve it.
wOOdy
Microsoft
Visual FoxPro Technology Advisor
Microsoft «Most Valuable Professional» from 1996 to 2009
Visit my XING profile!
*´¨)
¸.·´¸.·*´¨) ¸.·*¨)
(¸.·´. (¸.·` *
.·`.Visual FoxPro: It’s magic !
(¸.·«··*-
Proposed as answer by
Saturday, January 8, 2011 5:27 PM
-
Marked as answer by
Kee Poppy
Tuesday, January 11, 2011 11:22 AM
-
Proposed as answer by
Problem
When importing a RequisitePro® document a runtime error appears causing the import to fail.
Symptom
The full error message is as follows:
Runtime error: Automation error
Call was rejected by callee.
(RqWordServices.WordWrapper,656,-2147418111)
Cause
This issue is often the result of the Word normal.dot becoming corrupt.
Resolving The Problem
To resolve this issue, perform the following to recreate the normal.dot:
- Close RequisitePro, and Microsoft Word.
- Search the system for all instances of the normal.dot
- Delete all copies of normal.dot.
- Open Microsoft Word and save a new document as a test.
- Once the test document has been created, a new copy of the normal.dot will be created.
- Try to import the document again.
[{«Product»:{«code»:»SSSHCT»,»label»:»Rational RequisitePro»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Wizards: Import»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»2003.06.13;2003.06.14;2003.06.15;2003.06.16;7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.1;7.0.1.1;7.0.1.2″,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]