I am running a script in 5.6 that runs fine in the application but fails in the scheduler. The failure is "[Microsoft][ODBC Excel Driver]Invalid use of null pointer". This fails in the Import widgit on the third file I import. I have other scripts using similar files with no issue. This script has been moved to a new PC and it is the only one giving me issues. I am thinking I may just need to rebuild the script from scratch. Looking for ideas.
Hmmm... couple things come to mind.
- Microsoft Office was installed on the new PC in exactly the same location?
- Bitness of MS Office is same or different than TDP's bitness?
- Had you installed the MIcrosoft Database Access Engine on the new PC? (See TDP Help for details, in which you'll find a link to download/install the engine if you haven't already:
Download Microsoft Access Database Engine 2010 Redistributable from Official Microsoft Download Center )
Otherwise, if the automation script isn't too involved or lengthy, it might be best to re-define it on the new workstation. I've seen this on rare occasions where "something" gets cached/defined in the workflow file (like a non-existent ODBC driver) and the issue can be difficult to troubleshoot.