<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: initializeParameters Error started at Pro 3.2.1 in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1593763#M73889</link>
    <description>&lt;P&gt;Great tip!&lt;/P&gt;&lt;P&gt;Had the same problem, when updating to ArcGIS pro 3.4.2 and the error-code is not really helpful. Replaced "special characters" (ÆØÅ)&amp;nbsp; from parameter labels and names, and now no problems.&lt;/P&gt;&lt;P&gt;Weird that these different program updates makes tools not function by removing the use of special characters, but lesson learned: the age-old-arcgis saying of "Never use spaces or special characters..."&lt;/P&gt;</description>
    <pubDate>Mon, 10 Mar 2025 11:05:31 GMT</pubDate>
    <dc:creator>Espen</dc:creator>
    <dc:date>2025-03-10T11:05:31Z</dc:date>
    <item>
      <title>initializeParameters Error started at Pro 3.2.1</title>
      <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1371683#M69686</link>
      <description>&lt;P&gt;We have a python script wired to a toolbox that suddently started throwing the below error at 3.2.1. Pro 3.1.3 doesn't have any issues opening this tool in Pro, but 3.2.1 will not even open the tool for users to input parameters.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone experience this, how to diagnose?&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;&lt;SPAN&gt;initializeParameters Error: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x91 in position 8: invalid start byte&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;The above exception was the direct cause of the following exception:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Traceback (most recent call last):&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; File "C:\Users\david\QAP_Toolbox.tbx#CIPAutoQAPRound2.InitializeParameters.py", line 29, in &amp;lt;module&amp;gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; File "C:\Users\david\QAP_Toolbox.tbx#CIPAutoQAPRound2.InitializeParameters.py", line 8, in __init__&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\__init__.py", line 1603, in GetParameterInfo&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; return ParameterArray(gp.getParameterInfo(tool_name))&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 457, in getParameterInfo&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; self._gp.GetParameterInfo(*gp_fixargs(args, True)))&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;SystemError: &amp;lt;built-in method getparameterinfo of geoprocessing object object at 0x000001D11824C150&amp;gt; returned a result with an error set&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Thu, 18 Jan 2024 15:57:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1371683#M69686</guid>
      <dc:creator>danbecker</dc:creator>
      <dc:date>2024-01-18T15:57:06Z</dc:date>
    </item>
    <item>
      <title>Re: initializeParameters Error started at Pro 3.2.1</title>
      <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1371693#M69687</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;I have observed the same problem. I use the Validation Tool Class very intensively. Everything runs smoothly in ArcGIS Pro 3.1. As of 3.2 I get the same error as you. The error only disappears if I reset the Validation Tool Class to the default, i.e. I don't have my own code in it. Of course it doesn't make sense since I already need my code in there. I don't use a special character either.&lt;/P&gt;&lt;P&gt;I am also interested in a solution :).&lt;/P&gt;&lt;P&gt;Best&lt;/P&gt;&lt;P&gt;Sven&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 16:03:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1371693#M69687</guid>
      <dc:creator>Sven_Harpering</dc:creator>
      <dc:date>2024-01-18T16:03:50Z</dc:date>
    </item>
    <item>
      <title>Re: initializeParameters Error started at Pro 3.2.1</title>
      <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1373356#M69705</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;We had the same problem with some of our custom python scripts in ArcGIS Pro 3.2.1. Looks like the parameters name (not the label) must not contain any special characters (we're german, so we used ä,ö,ü,ß before). Worked for us.&lt;/P&gt;&lt;P&gt;Best&lt;/P&gt;&lt;P&gt;Holger&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 09:11:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1373356#M69705</guid>
      <dc:creator>HF_LBD</dc:creator>
      <dc:date>2024-01-23T09:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: initializeParameters Error started at Pro 3.2.1</title>
      <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1379089#M69800</link>
      <description>&lt;P&gt;Great tip, I found that in one of the tool's input parameters (a boolean in this case, not that it matters) Name had apostrophes and a dash like this: '-999' and once I retyped the '-' around the 999 it fixed the issue!&lt;/P&gt;</description>
      <pubDate>Wed, 07 Feb 2024 14:52:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1379089#M69800</guid>
      <dc:creator>SeanT</dc:creator>
      <dc:date>2024-02-07T14:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: initializeParameters Error started at Pro 3.2.1</title>
      <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1494800#M70853</link>
      <description>&lt;P&gt;Works with removing special characters from parameters names, thanks &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/539107"&gt;@HF_LBD&lt;/a&gt; !&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2024 08:10:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1494800#M70853</guid>
      <dc:creator>mmarkovic</dc:creator>
      <dc:date>2024-06-19T08:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: initializeParameters Error started at Pro 3.2.1</title>
      <link>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1593763#M73889</link>
      <description>&lt;P&gt;Great tip!&lt;/P&gt;&lt;P&gt;Had the same problem, when updating to ArcGIS pro 3.4.2 and the error-code is not really helpful. Replaced "special characters" (ÆØÅ)&amp;nbsp; from parameter labels and names, and now no problems.&lt;/P&gt;&lt;P&gt;Weird that these different program updates makes tools not function by removing the use of special characters, but lesson learned: the age-old-arcgis saying of "Never use spaces or special characters..."&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 11:05:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/initializeparameters-error-started-at-pro-3-2-1/m-p/1593763#M73889</guid>
      <dc:creator>Espen</dc:creator>
      <dc:date>2025-03-10T11:05:31Z</dc:date>
    </item>
  </channel>
</rss>

