This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connectwise Automate Feedback & Questions.

Elias Collins - Sophos Product Management over 5 years ago

Please use this space to create a new post for issues you are having if you do not see a post already created for your issue. We will also welcome feature functionality feedback, enhancement requests, and general questions.

This thread was automatically locked due to age.

Top Replies

WIlliam Nelson over 5 years ago in reply to WIlliam Nelson +3

Just wanted to give an update on this. I think this should be something that is added to the instructions.

The fix was after installing the plugin through Automate, you have to go assign the Sophos Plugin user class from within Automate.

There are two there. "Sophos Plugin Admin" and "Sophos Plugin User". I gave myself both, but I would think you have to have the admin one to configure the plugin.
Jump to answer

Parents

0 MattColford over 5 years ago

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
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 MattColford over 5 years ago

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
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Elias Collins - Sophos Product Management over 5 years ago in reply to MattColford

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 MattColford over 5 years ago in reply to Elias Collins - Sophos Product Management

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 MattColford over 5 years ago in reply to MattColford

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

Cancel
0 Elias Collins - Sophos Product Management over 5 years ago in reply to MattColford

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 Eric Schueler over 5 years ago in reply to Elias Collins - Sophos Product Management

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 MattColford over 5 years ago in reply to Elias Collins - Sophos Product Management

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.
Cancel
Vote Up 0 Vote Down

Cancel