Messages

Thank you! That's what I needed.

Thanks! The customer finally tracked down the issue and it is antivirus blocking bassmidi.dll from loading. It may be blocking any other DLL that you're extracting for use. They're using Cisco for the AV and they're checking with them to get the reputation of the file changed as it views it currently as malicious. Our customer's security department is looking for some kind of statement for how Audio Sound Suite uses this DLL (and other DLLs extracted) to help them justify whitelisting it and to provide Cisco AV.

Oh, one more question... you mentioned "for some reason the multimedia engine tries to extract one of the modules into the destination folder but when trying to load it the module is missing"

where is the multimedia engine trying to extract to? All of the files are in the install area our support person found. Is it needing specific access to a temp folder area or path?

Thank you. That's very helpful. Is there any code mechanism I could use to extract any more information or logging information? The customer claims they haven't changed anything and have re-imaged the box. So probably a virus checking problem. Is there anything that would be in the windows event logs that might help, too?

We're using Audio Sound Suite 2018 and one of our customers in the field suddenly got an error dialog from AdjMmsEng:

### Internal error, cannot load engine Number 7 due to error 126.

That's all the info I can get at the moment. Since it's a compiled app on the customer machine I'm not able to obtain more detailed information. Multiple users are reporting it and I'm suspecting the error 126 is about a failure to load a .NET module but I cannot find any references in the Audio Sound Suite documentation to this kind of error for not loading an engine. Can you provide any additional information?

Thanks!