Community
Showing results for 
Search instead for 
Do you mean 
Reply

Call was rejected by callee when attaching template to History

New Member
Posts: 3
Country: USA

Call was rejected by callee when attaching template to History

Running ACT! 2009 ( v11.1.183.0 ) and using Word 2007 ( sp3 ) on Windows XP Professional SP3.

 

When we create a new document from a template in ACT, Word will launch and we complete the template.  We then print and attempt to attach the document to history.  We are seeing ( inconsistently ) the following error:

 

Call was rejected by callee.  Exception from HRESULT: 0x800100001 RPC_E_CALL_REJECTED

 

I have searched the forums and attempted the following without success:

 

disabled extraneous ACT add-in in Word ( I need to keep the Act office Add-in, or I don't get prompted to add to history )

 

verify print spooler is running and set to restart on error

 

verify DCOM is enabled in registry

 

verified "display all windows" setting is checked in Word.

 

Needless to say, I am stumped.

 

Any suggestions would be GREATLY appeciated!

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Call was rejected by callee when attaching template to History

Hello Bunger,

Welcome to the Sage ACT! Online Community!

 

Did this ever work?

 

This may be caused by permissions on the templates folder; here is an article with instructions for adding permissions: KB Article 14380

 

You may also need to run maintenance on Office 2007.

Greg Martin
Sage
New Member
Posts: 3
Country: USA

Re: Call was rejected by callee when attaching template to History

No, we are still encountering the issue.

 

I am thinking it is not a permissions issue as we can process successfully 4 or 5 consecutive times, and then it will fail with the error....

New Member
Posts: 3
Country: USA

Re: Call was rejected by callee when attaching template to History

Anyone?

New Member
Posts: 3
Country: Australia

Re: Call was rejected by callee when attaching template to History

Bump.

 

Still experiecing this issue after suggestions above.