Thank you. I have submitted a SAS Track. I'm thinking it is unrelated to licensing. I will update the solution here once I get back from them. ... View more

We are using unixODBC - FreeTDS. Thank you. This helps understand the situation. Are you aware of any workaround for this situation? ... View more

Hello All, Techsupport couldn't help me as they did not have technical resources to help me over the weekend. But since this is a production environment, I had to work straight 10 to 12 hours before Monday to get this resolved. Here are the steps that I tried. (It might be lengthy, please bear with me) 1. I replaced the below files from the backup ../WebServer/conf/sas.conf ../WebServer/conf/httpd.conf ../WebServer/conf/extra/httpd-ssl.conf ../WebAppServer/SASServerm_n/conf/server.xml ../WebAppServer/SASServerm_n/bin/setenv.sh   2. I verified all the customizations done for SSL, load balancing etc (I built this environment initially from the scratch, so I was aware of the steps and I had that documented too. Likewise in your case please refer your initial build document and see for customizations done to midtier. The depot upgrade basically reverts most of this to the initial state, so this is much needed) Examples: proxyName, proxyPort, scheme etc   3. In some cases, you may want to check the gemfire-locator.sh, gemfire-start-locator-sas.sh too   4. Check your internal and external connections for all the web applications in the SAS Management console and change them if you find any discrepancies. Below sascode might help you with that getttcpipconnections    5. Please refer this SAS note - https://support.sas.com/kb/66/003.html   6. After verifying all the above things, while you have the error, restart your midtier services on another window and then click on retry   7. In my case, this also failed. And All I did was, restart everything one by one. WebServer first and then I restarted the WebAppServers one by one by using tcruntime-ctl.sh and I observed catalina.out and waited for the "Server Startup in xx ms" message and then proceeded with the next WebAppServer.   8. After doing this, I clicked retry and observed the "webinfpltfm_updateContent_<TimeStamp>" log in ../Lev1/Logs/Configure (It should run lines similar to below) updateContent:      [echo] +-------------------------------------------------------------------------------------+      [echo] |**************CHECKING CURRENT VERSION TO DETERMINE IF UPDATE IS REQUIRED************|      [echo] |Current ConfigureVersion ${webinfpltfm.configobj.version}=9.4_M6      [echo] |Previous Order Customer Version = 9.4_M6      [echo] |Current Order Customer Version  = 9.4_M6      [echo] +-------------------------------------------------------------------------------------+      [echo] SAS Web Infrastructure Platform is not at the version required for this order so it will be updated      [echo] +-------------------------------------------------------------------------------------+      [echo] |Updating content for SAS Web Infrastructure Platform at 2020-11-09-04.08.06      [echo] |From Version = 9.4_M6      [echo] |To Version   = 9.4_M6      [echo] +-------------------------------------------------------------------------------------+ [createObjectTypes.groovy]      [echo] Processing object type Machine (50) [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Encoded password [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Will update object type at <url_comes_here> [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Encoded password [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Opened connection [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Setting icon for type: 50 at url <url_comes_here> [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Encoded password [createObjectTypes.groovy] [createObjectTypes.groovy]      [echo] Setting localized names for type: 50 at url <url_comes_here>   9. If it processes all the objects one by one, you are good. If it is stuck at a particular object for a long time and if you get the error again, restart your webapp services and try again   And one last tip: After making all the customizations and restarting all the midtier services, make sure your web applications are accessible. Try to test one application per webappserver. If yes, you will definitely get past this error after few restarts and retries.   Hope this helps 🙂 ... View more

Is this resolved? Im having the same issue. ... View more