We have already configured our firewall to allow VPN client connections. It is also setup to authenticate to our Active Directory but I still get this error on my vpn client software when trying to access my office.
I do not believe that you are getting as far as Active Directory for authentication. The messages suggest that there is a mismatch between what is configured in your VPN client and what is configured on the ASA:
Hash verification failed... may be configured with invalid group password.
This would be a key configured on your client along with the group name of abc. The ASA shows that a pre shared key is configured for group authentication:
but it does not show what that key value is. You need to be sure that the values are the same.
Are other people with VPN client able to connect? If so this would suggest a problem in configuration of your client and you need to re-configure your client. If you are the first person and are testing then it is possible to test this by changing the value on the ASA, changing the value on your client, or by changing both (which is the approach I would suggest).
does the group name configured in the client match the abc used in the config (and does it match upper/lower case)?
I would suggest changing the shared key to something very simple (you can go to a more complex key when you have it working). change it on both the client and the ASA and see if the behavior changes.
If that does not help then I suggest setting the logging level in the client to high (at least for IKE and perhaps for others such as connection manager. test again and post the log output. perhaps it will have some better clue about the problem.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...