XenDesktop 7.6 Studio Failed to Connect to Database, Error Id:XDDS:9B560459

Step1.Check the event log of SQL server, because large transaction log may cause such error message. If transaction log is full, try to shrink transaction log

  1. Use BACKUP LOG [databasename] to disk = ‘nul’. For reference please turn to http://www.cnblogs.com/TeyGao/p/3519954.html or http://realit1.blogspot.com/2016/02/shrinking-database-log-files-in.html. This method may take a lot of time depending on the size of the log , so please be patient
  2. Break the mirror configuration to shrink the transaction log quickly. This method may have a higher risk, since we make too many changes to the environment and Citrix has no professional database support to deal with anything urgent caused by such big changes.

Remove mirror from the primary SQL Server

Modify the recovery model to simple

Right click the database and shrink the transaction log

Backup the database and transactionlog, copy them to Mirror database server

Restore the backup with NORECOVERY option on Mirror database server

select the database and select mirror task on primary database server

click ConfigureSecurity to start Mirroring wizard

Select Yes on Witnessserver page

Step2: Try to restart SQL Server and DDC if possible

Step3: Use ODBC to connect to database to test if database can accept remote connection

Open ODBC on any windows system, Click Add and select SQL Server and click Finish to create a New Data Source to SQL Server.

User-added image
Give a name of the Data Source and select the SQL server name you want to connect, then click Next > Next > Finish > Test Data Source. If the DB can accept remote connection, TESTS COMPLETED SUCCESSFULLY message is displayed.

User-added image
User-added image

Other troubleshooting steps including but not limited to checking the 1433 port of SQL Server and “Allow remote connection to this server configurations” Configuration of Database.

Related:

XenDesktop 7.6 Studio Failed to Connect to Database Error Id:XDDS:9B560459

Step1.Check the event log of SQL server, because large transaction log may cause such error message. If transaction log is full, please try to shrink transaction log

  • For only one database environment,use the method in this KB to shrink transaction log:https://support.citrix.com/article/CTX126916
  • For Mirror or AlwayOn database environment
  1. Use BACKUP LOG [databasename] to disk = ‘nul’. For reference please turn to http://www.cnblogs.com/TeyGao/p/3519954.html or http://realit1.blogspot.com/2016/02/shrinking-database-log-files-in.html. This method may take a lot of time depending on the size of the log , so please be patient
  2. Break the mirror configuration to shrink the transaction log quickly. This method may have a higher risk, since we make too many changes to the environment and Citrix has no professional database support to deal with anything urgent caused by such big changes.

Remove mirror from the primary SQL Server

Modify the recovery model to simple

Right click the database and shrink the transaction log

Backup the database and transactionlog, copy them to Mirror database server

Restore the backup with NORECOVERY option on Mirror database server

select the database and select mirror task on primary database server

click ConfigureSecurity to start Mirroring wizard

Select Yes on Witnessserver page

Step2: Try to restart SQL Server and DDC if possible

Step3: Use ODBC to connect to database to test if database can accept remote connection

Open ODBC on any windows system, Click Add and select SQL Server and Click Finish to Creat a New Data Source to SQL Server.

User-added image
Give a name of the Data Source and select the SQL server name you want to connect, then Click Next->Next->Finish->Test Data Source. If the DB can accept remote connection, TESTS COMPLETED SUCCESSFULLY message will show up.

User-added image
User-added image

Other troubleshooting steps including but not limited to checking the 1433 port of SQL Server and “Allow remote connection to this server configurations” Configuration of Database.

Related:

EXCI resp 88 resp2 203, IRP return code x’5C’ (IRERRNLG)

I have a batch EXCI program that uses MRO to communicate to your CICS Transaction Server region. My Batch program is able to issue the
Batch EXCI requests to my Production CICS regions successfully but when the same batch program tries to issue the EXCI requests to my Test
CICS regions, the program receives EXCI response of RESP=00000088 and RESP2=00000203 (meaning NO_CICS) and IRP return code of
x’5C’ (IRERRNLG) meaing the other system is not logged on to DFHIRP.

Related:

DFHHC0102I CICS Failed to register with z/OS Health Checker

After applying CICS Transaction Server 5.2 RSU 1708 on z/OS 2.2. We noticed the following message being issued when CICS tries to register to Health Checker:

DFHHC0102 I CICS failed to register with the z/OS Health Checker: code( X’00000003′) reason( X’00000008′) response( X’0000081C’).

Following the hold action of UI49542, we ensured that UA91583 for zOS 2.2 is applied. We also added CHCK to RACF profile for CICS Category 1 transactions but the message still appears.
What am I missing?

Related:

IZE0160E Connect failed with error “Unexpected content type text/html; charset=utf-8,Forbidden” ()

I am setting up a standalone CICS Transaction Server for z/OS (CICS TS) V5.4 region to allow a CICS management client interface (CMCI) connection from the CICS Explorer V5.4 plugin. When I attempt to connect CICS Explorer to CICS TS using CMCI I get the following message in the CICS Explorer:

IZE0160E Connect failed with error “Unexpected content type text/html;
charset=utf-8,Forbidden” ()
I am not seeing any EYU prefix messages in our CICS TS 5.4 region.

Do you have any suggestions on how I can proceed?

Related: