To resolve, be sure to explicitly set the TCP/IP port of SQL Server (see below for instructions in SQL Server Configuration Manager). It appears having the dynamic port that comes as default SQL Server installation would cause the connection errors even though the tables and UDF's were generated successfully at the beginning of the installation but would fail towards the end when the system data gets loaded.
How to set the port using SQL Server Configuration Manager:
- open said app in your Windows machine (search for SQL Server Configuration Manager)
- expand "SQL Server Network Configuration"
- Click on "Protocols for <your Pega database>"
- On the right panel, under "Protocol Name" for "TCP/IP" entry, right-click then select "Properties."
- On the "Protocol" tab, set "Enabled" to "Yes"
- On the "IP Addresses" tab, scroll to the bottom, under the section "IPALL" set the "TCP Port" entry to an available port number for your machine (e.g. 6100).
- Restart the SQL Server process in the system's "Services" to have the port take effect
***Edited by Moderator: Lochan to convert post to discussion and tag as developer knowledge share***