Connectwise Automate Feedback & Questions.

Running the latest 1.0.0.134.

The log still shows near constant 403 errors with no reasons. 

The computer pane is currently empty; if I try to force a sync it fails with "Object reference not set to an instance of an object"

Overall seems like a step backwards in usability from .132

Running the latest 1.0.0.134.

The log still shows near constant 403 errors with no reasons. 

The computer pane is currently empty; if I try to force a sync it fails with "Object reference not set to an instance of an object"

Overall seems like a step backwards in usability from .132

Hello Matt, First, let me say Happy New Year!  Thank your for reaching out and I'm sorry you have been experiencing some issues with the latest version.  Could you just confirm for me that .132 was indeed working and now .134 is throwing the 403 errors?

If this assumption is the case, we have seen this behavior on occasion with a subset of upgrades.  The fix so far, has been to apply the below SQL statement to drop the Sophos tables from the Connectwise database, from within your Connector admin console, and then reboot the machine the Connecttwise instance runs from.  Upon reboot the tables will be re-created and should populate with data once confirmation of the API key is present.

SQL Command: “drop tables plugin_sophos_central_cls_basic, plugin_sophos_central_cs_basic, plugin_sophos_central_ls_basic;”

Please do let me know if this corrects your issue or if we'll need to schedule a remote session to further troubleshoot.

Thanks for the response. .132 also threw 403 errors, however it appeared to be otherwise functional, computers/locations appeared and could run commands against them. I will give that table drop a try and see what happens.

Quick followup, after running the SQL query, I can now see computers/locations again. Still getting a lot of 403 errors though

We've made some good progress at least!  403 errors are also typical when you have trial accounts as it attempts to pull the endpoints for those tenants, but then doesn't have the permissions as we have barred trial accounts from API access.  Would you be able to confirm if this is the case?  If so, I have an enhancement on the backlog to better handle this situation.

I have 403 errors as well.  From what I've seen it's for accounts that we don't have partner access to.  In a future release I'd like to see it smart enough to recognize this and not try to sync these accounts.  I'd settle for a manual process of de-selecting accounts we don't want to attempt to sync.

I didnt think I did, but just took a look and theres one customer we no longer have licenses with that somehow has a trial.