The Windows 10 Anniversary update has just rolled out and with it has come more problems for Infor's Smart Office.
When using a panel that has a JScript attached to it, the JScript does not load and an error message is logged within the Smart Office log e.g.
5/05/2016 9:29:30 PM ERROR MForms.Render.RenderEngine.PostRender Failed to run scripts
System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Users\user\AppData\Local\Temp\aibwfam0.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Users\user\AppData\Local\Temp\aibwfam0.dll'
Infor don't have a resolution to this yet, much like the problem with the Microsoft patch that on certain configurations broke Smart Office altogether, the current recommendation from IRD is to not install the Anniversary update.
Fantastic
ReplyDeleteThis is now resolved in the ISO 10.2.1 series as per:
Deletehttp://movexblog.blogspot.com/2016/10/smart-office-102-hotfix-17-resolves.html
There is also a workaround where you can compile to dll the JScripts on a working ISO instance, then use the compiled dlls in place of the JScripts.
Hi Alistair!
DeleteI still have this issue on ISO 10.2.1.0.141 on Windows 10. Has the bug been reintroduced?
Where can I find any info on how to do the workaround if that is the case?
You need to upgrade to 10.2.1.0.169 for the fix to be included.
DeleteThat's great if you're updated to that revision, but what about those of us still on 10.0?
ReplyDeleteHi Eddie. If you can't upgrade the ISO version then we can compile your jscripts to DLLs on a later version of ISO, then deploy these within the javascript directory in place of the .js files.
DeleteHi Alistair san,
ReplyDeleteWe have same problem on Windows10 and ISO10.0.
How can I compile from .js to .dll?
Hi Tomo san,
DeleteThe best way to handle this would be to upgrade your version of Smart Office and I'm sure that Deepak or another Infor-qualified System Engineer would be able to help you with that (we have people that do this too if you need someone).
However if that's not an option, then ISO compiles these every time you open a screen with the JScript. You need a PC that runs the scripts successfully. Open the screen with the script. A randomly named dll will be created in the %temp% directory on the PC. Rename that to JScriptName.dll (where it was JScriptName.js before). Copy the newly compiled dll to the JScript folder or zip and upload via personalisations manager and then attach it to the screen as JScriptName.dll instead of JScriptName. Most times this works, sometimes it doesn't and we have to debug the issue.
If you still run into problems please reach out via email - you should still have this?
Kind regards,
Al.
Hi Alistair san,
DeleteThanks for your quick response.
Currently I’m working with Deepak san to upgrade ISO targeting Middle of May. But we already started to upgrade users PC to Windows10 so I would like have workaround till the upgrade.
I will look into this solution and will reach you by email if any problem.
Thanks,
Tomo
Hello all,
ReplyDeleteI have had the same problem with the JScripts. I found out that simply installing Visual Basic Express 2008 did bring back the functionallity with the JScripts. I guess it has something to do with .NET runtimes. Anyway it works! Even uninstalling VB Express 2008 leaves the JScript functionality intact.
Just tried the VB Express 2008 recommendation, and it does NOT seem to work for me. Did you anything special on the install?
Delete