just to add #metoo.
We're experiencing similar issues on our new 2016 DEV environment. The databse is also on a separate VM.
We upgraded from 9.0R2 to 9.1. It all seemed to go well, but now we are experiencing random Database disruptions. And the DB server service refuses to start. The Database service logs get COM -- ADO error: IDispatch error # 3149. Login failed for the user 'pharos'.
The error you mentioned explicitly implies that the user in which Uniprint is configured to use to connect to the SQL Server is not able to login to the server to access the Uniprint database. We have seen in the past when the SQL Server utilized is some form of HA Clustered setup that the account credentials used by Uniprint to connect are not correct on each node.
Good morning Jeff
thanks for following up on my comment.
The Pharos DB is housed on a clustered SQL. Coincidentally, yesterday noon
we copied the Pharos account and password to the other cluster nodes and
are currently testing. Hopefully this will the answer to our issue.