I may have drawn the wrong conclusion, and the original poster provided possibly ambiguous details. However, mentioning server datasets and providing an error message that I have only ever seen from a foreign DBMS suggested to me that the issue was recognition of the server user on something like SQLServer or Oracle.
Where ODBC is used as the connecting method, the user name and password need to be known to the database either as a specific DBMS user, or as a user authenticated by the domain. So SASSRV needs a record in the Active Directory for the domain.
The relevant user groups will then be those on the domain, not those on the management console.
Tha hazard lies in making the SASSRV user available to all users on the SAS application server, which means someone who cannot authenticate to a given DBMS can then use the SASSRV permissions to gain cloaked access. This remains one of the biggest hurdles for our using the Stored Process server in the future.
Kind regards
David