No, I presume when I move a package from one server to another it should work when the SQL version isn't changing

I thought once the account is in the local admins group for the server it should have all the required access to SQL directories iswell

I provided the account with explicit permission but still the same errors

User is part of the local admin group of the server so should have all the access

Yes it works when you script it

I was running it on the primary replica.

Seems like a bug as it works using the GUI

That doesn't work.

When I try adding the database back I get the following message

Database 'TEST' cannot be joined to or unjoined from availability group 'TEST-AG'. This operation is not supported...

OK thanks for your comments.

So I need to review the queries using the indexes, would this mean that the index are being used or not efficiently ?

Where is it configured at the instance level?
Can it be seen enabled using the GUI

select name, is_rpc_out_enabled
from sys.servers

Because sys.dm_cdc_errors gives me the same information 

Log Scan process failed in processing log records. Refer to previous errors in the current session to identify the cause and correct...

I understand all of this. 

My questions was how to identify if you are currently vulnerable to attacks and how to find the queries, stored procedures etc that might...

Yes but we support a number of databases and dont have time to check every query so would like someone way to check the databases for vulnerabilities

That is what i have been trying to run but its failing.

exec [ServerB].[master].dbo.[Test]
Could not find stored procedure 'master.dbo.Test'.

The stored procedure is located on Server A...

What is the command to do it?

I have tested some commands and its not working so I thought it wasn't possible