Re: Script sends App Mgr to Partial service in 11.6 but not 12.5

Timothy Riley · ‎11-07-2022

Friends, This one is making me scratch my head. I have a script that was built and tested in out 12.5 lab and works as designed. When I upload the same script to 11.6 script editor, validate and place in service, the "Application Manager" goes into Partial Service until I swap the script out. RTR gives a Valid = False and a side by side stare and compare does not reveal anything that is in 12.5 but not 11.6. Would anyone have a suggestion of what (besides MIVR logs) I can look at? We can bounce the service to get the logs but not until a maintenance window in a few days. Thanks in advance for reading and any ideas you might have. -Tim

Jonathan Schulenberg · ‎11-08-2022

CCX scripts are not backward compatible. You will need to build it in 11.6.

Timothy Riley · ‎11-08-2022

Jonathan, thank you for your time to reach out. I incorrectly stated that the script was created in 12.5, it was in fact built in 11.6 and only tested in 12.5. When built in 11.6, it was validated successfully and then uploaded to 12.5 where it tested okay. Only when it was uploaded to the 11.6 Script folder and moved to production did the service go in to Partial Service. -Tim

Jonathan Schulenberg · ‎11-08-2022

Are you certain that only the 11.6 version of the CRS Editor was used to open, validate, and save the AEF file? Because if you opened/saved it in the 12.5 version of the CRS Editor you're stuck.

Timothy Riley · ‎11-08-2022

Since this began we have taken the original script in to the 11.6 editor, changed the closing time of day and saved it under a new name. Am I still stuck with the 12.5 stigma?

Jonathan Schulenberg · ‎11-10-2022

I honestly don't know at this point. Usually an older version of the CRS Editor flat out refuses to open a script saved by a newer version. Since it opened it and saved successfully, you might as well try uploading it to CCX to see if it still takes APP_MGR out of service. Assuming it doesn't, I'd test extensively to look for problems - especially anything you touched while it was in the 12.5 editor.