Latest Contributions by MichaelVolz

You need to update the SDE connection in the Pro project that is the source of the mapservice as well. ... View more

Server logs identify this issue as SEVERE, but ESRI tech support says that it has no impact on AGS services.  If that is the case as per ESRI tech support, why report this error as SEVERE (Just make it a warning)? ... View more

Did it matter what version of SQL Server that the input data was originating from? I ask because I am dealing with this issue with ESRI tech support on python scripts to bring SQL Server data into GIS and ESRI tech support is able to use arcpy.env.useCompatibleFieldTypes = True in Pro 3.2.2 on  SQL Server v2022 data, but this same code is not reverting date fields to standard precision for me with data from SQL Server v2019. ... View more

Can you try creating a simple script just importing arcpy with a print statement before and after the import statement in the standard python environment, that is called from a bat file? This is what I needed to do at my org to determine that anti-virus software was interfering with running a python script thru Task Scheduler even though it ran fine when just running directly from the bat file. ... View more

Are you running Task Scheduler with highest privilege? ... View more

Does your script fail every time or is it more of a random failure in Task Scheduler? Check your Event Viewer as that helped me find issues with python scripts. ... View more

The bug was supposedly fixed at Pro 3.0 as it was initially reported at Pro 2.9.1. ... View more

So I am doing similar automated  operations using python where I am trying to revert to Pro 3.1 field types using useCompatibleFieldTypes, but this code just gets ignored. I am wondering if you can bring the table into a file gdb in Pro 3.3.1 with the Pro 3.1 field types checked and then see if you can view that file gdb table in ArcMap after it was initially created in Pro 3.3.1. ... View more

Do you think the new data types are being added with the tabular data that is being joined to your SDE data, even though you have that setting checked? Have you verified that the data is still in Pro 3.1 compatible format where it is not using the high precision data field type or big integer field type (I would suggest seeing if you can load the table into ArcMap as a test)? ... View more

Dylan: How did you ensure that your field types are compatible with 3.1 and earlier versions? ... View more

Have you tried publishing other data from the same database? ... View more

Do you have any idea what corrupted the properties.json file? I was using ESRI's auto patching tool and that had also caused corruption with this file. ... View more

Have you tried looking at AGOL Assistant to see if you can remove the code from the Measurement widget you just added and see if that fixes the Experience? ... View more

Did ESRI give you a deadline for when concurrent use licenses would no longer be available to you? ... View more

Did you try to just publish the individual layer from the original Pro project from Table of Contents context menu? ... View more