When running a package report on our production PROD Jamf Cloud server Object Info crashes as soon as it starts scanning for packages in PreStage enrollments. Our production Jamf Cloud server is running Jamf Pro 11.9.2. However, I have noticed this issue with older versions of Jamf Pro as well. This also happens with Object Info versions 2.x and 3.x. Version 1.5.2 does not crash since it does not scan for packages in PreStages. I used to just fall back to using the older 1.5.2 version of Object Info since our focus is on where packages are used in policies, however that older version has become less reliable and gets hundreds of "lookup failed" errors in our PROD environment.
We have a DEV Jamf Cloud instance that is currently running Jamf Pro 11.12.0 and I have not yet been able to reproduce the issue in that environment. However, it is not a clone of our production environment and has far far fewer objects than PROD.
I initially assumed it might be naming conventions we have established due to our heavy use of sites on our PROD environment. We ask our site admins to use [SITENAME] (with the square brackets in front of any object they create in Jamf Pro. On our DEV environment we do not have any naming requirements so there are very few special characters outside of dashes using in names.
I have tried creating a few PreStages and packages with the same naming conventions as our PROD environment, but have had no luck trying to get Object Info to crash at the PreStage scanning step.
However, in trying to replicate the problem on DEV I have come across a bug that I think could be related? I found that if I have a package and policy with the same Jamf ID, Object Info will report the name of the policy with that ID in the Package Name field, instead of the actual package name that belongs to that Jamf ID.
I am not sure where to go from here. The Object Info logs don't show any errors when the crash occurs on PROD and the application does not display any error messages, it just quits. If there is some sort of debug mode logging that I could do I am certainly willing to give it a try.
When running a package report on our production PROD Jamf Cloud server Object Info crashes as soon as it starts scanning for packages in PreStage enrollments. Our production Jamf Cloud server is running Jamf Pro 11.9.2. However, I have noticed this issue with older versions of Jamf Pro as well. This also happens with Object Info versions 2.x and 3.x. Version 1.5.2 does not crash since it does not scan for packages in PreStages. I used to just fall back to using the older 1.5.2 version of Object Info since our focus is on where packages are used in policies, however that older version has become less reliable and gets hundreds of "lookup failed" errors in our PROD environment.
We have a DEV Jamf Cloud instance that is currently running Jamf Pro 11.12.0 and I have not yet been able to reproduce the issue in that environment. However, it is not a clone of our production environment and has far far fewer objects than PROD.
I initially assumed it might be naming conventions we have established due to our heavy use of sites on our PROD environment. We ask our site admins to use [SITENAME] (with the square brackets in front of any object they create in Jamf Pro. On our DEV environment we do not have any naming requirements so there are very few special characters outside of dashes using in names.
I have tried creating a few PreStages and packages with the same naming conventions as our PROD environment, but have had no luck trying to get Object Info to crash at the PreStage scanning step.
However, in trying to replicate the problem on DEV I have come across a bug that I think could be related? I found that if I have a package and policy with the same Jamf ID, Object Info will report the name of the policy with that ID in the Package Name field, instead of the actual package name that belongs to that Jamf ID.
I am not sure where to go from here. The Object Info logs don't show any errors when the crash occurs on PROD and the application does not display any error messages, it just quits. If there is some sort of debug mode logging that I could do I am certainly willing to give it a try.