Scheduled map fails after adding an assembly to the SmartConnect script namespace.
Friday, January 27, 2017
SmartConnect has a feature that allows users to add scripting namespaces to enhance the scripting capabilities in any of the coding windows within SmartConnect. This feature is accessed by going to the Maintenance Tab and then selecting Script Name Spaces.
When you add a script namespace and manually run the map, the assembly needs to get placed in the main SmartConnect folder. However when you run the map via the scheduler, it does not look in the SmartConnect folder. You will get an error in the Windows Event Viewer that says, “SmartConnect Scheduler : Could not run the scheduled map MAPNAME Exception has been thrown by the target of an invocation.”.
In order to run the same map scheduled, the assembly needs to get copied into the following folders on the machine that is hosting the SmartConnect scheduling service.:
C:\Windows\SysWOW64
C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
When you add a script namespace and manually run the map, the assembly needs to get placed in the main SmartConnect folder. However when you run the map via the scheduler, it does not look in the SmartConnect folder. You will get an error in the Windows Event Viewer that says, “SmartConnect Scheduler : Could not run the scheduled map MAPNAME Exception has been thrown by the target of an invocation.”.
In order to run the same map scheduled, the assembly needs to get copied into the following folders on the machine that is hosting the SmartConnect scheduling service.:
C:\Windows\SysWOW64
C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
