[tp widget="default/tpw_default.php"]

could not access the package manager is the system running

could not access the package manager is the system running

could not access the package manager is the system running插图

Why is my package not finding a file in SSIs?

This error occurs when package execution can’t find a file in the local disk in the SSIS integration runtime. Try these actions: Don’t use the absolute path in the package that’s being executed in the SSIS integration runtime. Use the current execution working directory (.) or the temp folder (%TEMP%) instead.

Why is my ADO package not working?

The potential cause is that the ADO.NET provider used in the package isn’t installed in the SSIS integration runtime. You can install the provider by using a custom setup. You can find more details about custom setup in Customize setup for the Azure-SSIS integration runtime.

How do I know if my package is consuming disk space?

Check whether your package or custom setup is consuming a lot of disk spaces: If the disk is consumed by your package, it will be freed up after the package execution finishes. If the disk is consumed by your custom setup, you’ll need to stop the SSIS integration runtime, modify your script, and start the integration runtime again.

mr-islam commented on Jul 26, 2017

Make sure you are running the latest version of Anbox before reporting an issue.
Yes.

morphis commented on Jul 26, 2017

If you have the system still running can you either use adb shell logcat -d to dump the Android container log or check if /var/snap/anbox/common/data/system.log is present and if attach it here? Thanks!

mr-islam commented on Jul 26, 2017

I had closed the system, but I just restarted it and reproduced the problem completely and got the same error.