The strange thing is I had this working before, and now it just ... isn't and I'm not sure how to troubleshoot
It's throwing exception on second line here
outlook = new winax.Object('Outlook.Application', {activate: false});
const namespace = outlook.Application.GetNamespace('mapi');
The exception is that GetNamespace is not a function.
When I use a debugger on this I can see that outlook is being assigned properties but none of the methods are able to act as methods.
I've done an npm rebuild.
I've tried this with both 22.11.0 and 22.14.0
It's truly strange as I had tested this earlier with both MS Access and Outlook and it was ok, and I'm not too sure what changed.
package.json has winax version as "winax": "^3.6.1"
Further exploration of the problem seems to indicate a problem with Outlook specifically. It works fine with Access.Application and Excel.Application. So perhaps this is some kind of registration issue with com objects in Outlook. It's just odd because it worked on the same machine perhaps a week ago, and then stopped working today.
Unfortunately I can't reinstall the software or run regsvr32 to try to re-register components so I'll have to get assistance to see if that's a solution.
The strange thing is I had this working before, and now it just ... isn't and I'm not sure how to troubleshoot
It's throwing exception on second line here
The exception is that GetNamespace is not a function.
When I use a debugger on this I can see that outlook is being assigned properties but none of the methods are able to act as methods.
I've done an npm rebuild.
I've tried this with both 22.11.0 and 22.14.0
It's truly strange as I had tested this earlier with both MS Access and Outlook and it was ok, and I'm not too sure what changed.
package.json has winax version as "winax": "^3.6.1"
Further exploration of the problem seems to indicate a problem with Outlook specifically. It works fine with Access.Application and Excel.Application. So perhaps this is some kind of registration issue with com objects in Outlook. It's just odd because it worked on the same machine perhaps a week ago, and then stopped working today.
Unfortunately I can't reinstall the software or run regsvr32 to try to re-register components so I'll have to get assistance to see if that's a solution.