The server running Citrix XenApp failed to connect to the data store

 

Citrix XenApp failed to connect to the Data Store

Recently ran in to an error where I couldn't connect to any XenApp server using the AppCenter and I was getting the following errors within the system event log.

Event ID 3989
Citrix XenApp failed to connect to the Data Store. ODBC error while connecting to the database: 28000 -> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

Event ID 3632
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: IMA_RESULT_ACCESS_DENIED  Indirect: 0  Server:   DSN file: C:\Program Files (x86)\Citrix\Independent Management Architecture\mf20.dsn

Event ID 3612
The server running Citrix XenApp failed to connect to the Data Store IMA_RESULT_ACCESS_DENIED. Invalid database user name or password. Please make sure they are correct. If not, use DSMAINT CONFIG to change them. 

Now it turns out that the farm was configured to use the administrator account for access to the datastore and when the domain administrator password was changed these errors start to appear.

To get resolve this issue run the following DSMAINT command and set the correct password for the administrator account. ---Preferably not the domain administrator account. 

DSMAINT CONFIG /user:domain\administrator /pwd:password

Ideally you should change the account used for this to a different account that is used for XenApp only.

Comments

Post a Comment

Popular posts from this blog

VMWare Quick stats not up-to-date

Image
VMWare Quick Stats Not Up-to-date Fix This message is only displayed when you connect to vCenter server using vSphere client or Web Client. However, the error does not show up if you connect to one of the VMware ESXi host(s) directly. This is a commonly known issue within vSphere version 5.5 and 6.0. The issue was fixed within update to VMware ESXi 5.5.0b and ESXi 6.0.0b. Not sure why VMware has not taken initiatives to fix the bug in it’s first release and had to release an update? In order to resolve this issue you will need to add few advanced parameters to vCenter server settings . The following parameters will need to be entered manually via vSphere client or Web client: vpxd.quickStats.HostStatsCheck vpxd.quickStats.ConfigIssues You can do these changes with these simple steps: Connect to your vCenter using IP or hostname along with your credentials. Typically the username will be administrator@vsphere.local and whatever your SSO...
Read more

MS Outlook: Can't See Manage Rules

MS Outlook:  Can't See Manage Rules Screen By: Danny Garner of Geaux Techie LLC geauxtechie.com Issue:  When you try to go into Outlook and select Manage Rules and Alerts, you get just a flash of the screen and it goes away. The Manage Rules won't fully open. Cause:  One of your rules is causing the module to hang.  Likely have too many rules defined. Fix: Go to Start>Search and type "outlook /cleanrules" and hit enter.  Relaunch Outlook and you should be able to select the Manage Rules screen. Reference: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_other/outlook-2010-manage-rules-dialog-box-wont-open-any/9f62b456-fbf8-4163-97d6-dd6c3143f6d4
Read more

Cisco Firepower FMC Wildcard SSL Certificate Remote Access AnyConnect VPN

                 Changing the Wildcard SSL on a Cisco Firepower FMC for a AnyConnect VPN   When changing or renewing a Wildcard SSL for Cisco AnyConnect on the FMC you want to use the appropriate export function on the originating device so you don't run into errors.   Exporting the Wildcard SSL can be tricky if you use the wrong process.  If you are exporting from a Windows based server, DON'T export from the IIS Console.  Open up the MMC and open the Certificates module and export from that method.  It will export the correct path with the cert into the pfx file.   Importing into FMC will be seamless and both the CA and ID will be correct.   Otherwise, if you use the IIS export method the path for the CA is incorrect and you will get a red X on the CA status.  Hope this helps someone save some time.  
Read more