Hi,
I have written a VBS script to parse a csv which requires use of a 32-bit COM object.
If I run manually from command line on a 64-bit server: wscript script.vbs, the following error is generated:
ADODB.Connection Provider cannot be found. It may not be properly installed.
I know that the manual workaround is to manually run: C:\Windows\SysWOW64\wscript.exe script.vbs, which works successfully.
I have not yet created a new script-based SCOM monitor using the script as I expect SCOM will, by default, launch the script using the 64-bit version of wscript, which will fail.
Is there any way to "force" SCOM to use the 32-bit SysWOW64 version of wscript, either through config or script?
If not, does this mean that custom scripts written for SCOM monitors cannot use any ADO objects?
BTW, I know SCOM has a built-in csv parser, but I cannot use it. The folder contains csv files from multiple days and I only want to parse the current day's file. Even though SCOM allows use of a wildcard in the filename, there is no wildcard combination that will result in a single file. So the monitor will end up parsing all files. It would be helpful if the SCOM csv file parser GUI allowed me to use a date variable which would provide me with a solution :)
Thanks,
Jason