When installing XenApp on a new server, the installation goes smoothly until it gets to the part where it needs to join the SQL database. This could be a new or an existing database.
Looking in the event log of the XenApp server will show an error with the account being used.
Event ids seen can vary here are a few.
Event ID: 3612
Message: The server running Citrix XenApp failed to connect to the Data Store
<Error Message>. Invalid database user name or password. Please
make sure they are correct.
Event ID: 3615
Message: The server running Citrix XenApp failed to connect to the Data Store.
Error - <Error Message> An unknown failure occurred while connecting
to the database.
Event ID: 3632
Message: The server running Citrix XenApp failed to connect to the data store.
Invalid database user name or password. Please make sure they are
correct. If not, use DSMAINT CONFIG to change them.
Error: <Error Message> Indirect: <0 or 1> Server: <Server Name>
DSN file: <DSN File Name>
Event ID: 3633
Message: The server running Citrix XenApp failed to connect to the data store.
Invalid database user name or password. Please make sure they are
correct. If not, use DSMAINT CONFIG to change them.
Error: <Error Message> Indirect: <0 or 1> Server: <Server Name>
DSN file: <DSN File Name>
The user account being used to connect to the Microsoft SQL Server Database is not a Database Owner (db_owner). The account being used to install a new server into the farm or an existing farm must have db_owner rights or it can cause the installation to fail as seen below from our edocs.
Microsoft SQL Server Database
The default database installation settings and database sizes usually suffice for XenApp data store needs.
Microsoft SQL Server supports Windows and Microsoft SQL Server authentication. For high-security environments, Citrix recommends using Windows authentication only.
The user account for installing, upgrading, or applying hotfixes to the data store must have database owner (db_owner) rights to the database. When you finish installing the database with database owner rights, set the user permissions to read/write only to increase the security of the database. Change the rights back to database owner before installing service packs or feature releases; installations can fail if the user account used to authenticate to the data store during Setup does not have database owner rights.
When using Microsoft SQL Server in a replicated environment, use the same user account for the data store on each Microsoft SQL Server.
Each farm requires a dedicated database. However, multiple databases can be running on a single server running Microsoft SQL Server. Do not configure the farm to use a database that is shared with any other client/server applications.
Back up the database regularly and follow Microsoft recommendations for configuring database and transaction logs for recovery (for example, setting the Truncate log on Checkpoint option to control log space).