Version 2022.1 → 2024.1
This topic covers tips, tricks and known issues for making the jump between the two above sessions.
Tips:
Running these two versions side-by-side on-prem is alive!
Had to add an http binding on port 80 in IIS to get it to stop giving 503s though
Known Issues:
-
As mentioned above - the initial build gave 503 errors and in IIS the Application Pool wouldn’t run.
-
Resolved by removing the AppServer, adding a binding for port 80
-
-
SalesOrder.MasterUpdate() has a few new arguments for BPMs to trip on.
- Resolved by adding strings representing the new args. No issues.
-
Ran into trouble when I added SSRS. There was no error upon deploying within my AppServer config, but the 503 errors came back and the Application Pool wouldn’t run anymore.
-
Tried restarting SQL Server, SSRS, etc; nothing. Rebooted everything. Rechecked all SSL and so on. Removed & re-registered. Nada.
-
Resolved! Basically you have to build your AppServer and deploy SSRS all in one operation. I was able to replicate this - possibly an on-prem bug @timshuwy ? On the other hand possibly related to running dual versions simultaneously. Either way, if you first bind your default site properly, and then build an AppServer with SSRS deployment on the first build, it works; but if you add SSRS deployment to an existing one, it seems to break something.
-