ActiveX error for Scheduled Reports
Hi,
The Schedule reports were working okay before.
Recently, customer informed that Reports are not generating for since 1 week.
when i checked the details, the error log message indicates "Error Subscribing to automation object for type EX: ActiveX component can't create object".
As informed by Customer, there is no changes done in the system recently. I verified the Schedule report configuration & System disk space availability. Also, Searched for "*.EXD" files and deleted. But, it didn't helped.
I have seen similar problem reported by you. can you share the details for resolving the problem ?
Regards
Thazhai
The Schedule reports were working okay before.
Recently, customer informed that Reports are not generating for since 1 week.
when i checked the details, the error log message indicates "Error Subscribing to automation object for type EX: ActiveX component can't create object".
As informed by Customer, there is no changes done in the system recently. I verified the Schedule report configuration & System disk space availability. Also, Searched for "*.EXD" files and deleted. But, it didn't helped.
I have seen similar problem reported by you. can you share the details for resolving the problem ?
Regards
Thazhai
Asked 17 days ago
Answers
0
I will suggest you to reimport the template. Close the excel and then search for .EXD files and delete them. I suggest you to deleting the .EXD files each time when you have opened and closed the excel for a couple of times. later on this issue will not occurred. I have implemented this solution in 2017 and till now it is working absolutely fine.
Answered 17 days ago
by Yoginder.K.Singh Rank: 26 on 3/31/2021 10:23:12 PM | Like (0) | Report
just make sure customer has done no change in the template.
I will suggest you to reimport the template. Close the excel and then search for .EXD files and delete them. I suggest you to deleting the .EXD files each time when you have opened and closed the excel for a couple of times. later on this issue will not occurred. I have implemented this solution in 2017 and till now it is working absolutely fine.
Add new comment