icon

Das Wissen aller Anwender nutzen

Im Allplan Connect Forum tauschen sich Anwender aus, geben wertvolle Tipps oder beraten sich bei ganz konkreten Aufgabenstellungen − auch international.
Und damit wirklich keine Frage unbeantwortet bleibt, unterstützen die Mitarbeiter des Technischen Supports ebenfalls aktiv das Forum.

Es erwarten Sie:

  • Foren-Vielfalt aus CAD Architektur, CAD Ingenieurbau uvm.
  • Tipps von User für User
  • international: Deutsch, Englisch, Italienisch, Französisch und Tschechisch

Melden Sie sich jetzt an und diskutieren Sie mit!

Zur Registrierung

[Frage] PyythonPartsSDK installation error [Gelöst]

Schlagworte:
  • Allplan
  • 2025
  • PythonParts

Hello,
For some reason the the PythonPartsSDK is not working for me; instead of the successful installation i get the message in picture (1). I tried the same drag and drop installation on my co-worker's computer and there are no issues there.
Thanks

Anhänge (3)

Typ: image/png
36-mal heruntergeladen
Größe: 365,58 KiB
Typ: image/png
16-mal heruntergeladen
Größe: 22,48 KiB
Typ: image/png
14-mal heruntergeladen
Größe: 19,91 KiB

Lösung anzeigen Lösung verbergen

Hi,

looks for me like (for whatever reason) the path to the script was not correctly adapted during the installation of the SDK on your computer. Maybe it has sth to do with the location of your usr directory, which is in a network.

Open the file

\\172.20.3.113\Dati\Allplan\usr\Riccardo\Library\AllepPlugins\AllplanGmbH\PythonPartSDK\StartPythonDebug.pyp
and have a look at line 3. It should look like:
<Name>AllepPlugins\AllplanGmbH\PythonPartSDK\StartPythonDebug.py</Name>
But it probably looks like:
<Name>StartPythonDebug.py</Name>
If that's the case, please change it. Do the same with all other .pyp files in this directory.

Let me know, if that helped and if the path was really like I suspected.

Best,
Bart

Hello,

The SDK seems to be installed correctly, judging from the 1st screenshot. Can you please:

  • turn the ALLPLAN trace window of (CTRL+F3 and then "Write to: window")
  • restart ALLPLAN
  • try to run the "Start Python Debug" again
  • Copy the output you see in the trace (beginning from "Traceback: most recent calls...")

Best,
Bart

Thank you, this is the output from the trace:

Traceback (most recent call last):
File "C:\ProgramData\Nemetschek\Allplan\2025\Etc\PythonPartsFramework\GeneralScripts\BuildingElementUtil.py", line 78, in import_building_element_script
script = __import__(script_name)
^^^^^^^^^^^^^^^^^^^^^^^
File "\\172.20.3.113\Dati\Allplan\usr\Riccardo\PythonPartsScripts\AllepPlugins\AllplanGmbH\PythonPartSDK\reloader.py", line 199, in _import
base = _baseimport(name, globals, locals, fromlist, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'CreateVisualStudioCodeWorkspace'
Traceback (most recent call last):
File "C:\ProgramData\Nemetschek\Allplan\2025\Etc\PythonPartsFramework\GeneralScripts\DeleteObsoleteFiles.py", line 48, in delete_obsolete_files
os.remove(del_file_name)
PermissionError: [WinError 5]Accesso negato: 'C:\\ProgramData\\Nemetschek\\Allplan\\2025\\Etc\\Examples\\PythonParts\\BasisExamples\\Text.png'

=======================================================================================================

String table error:

Filename \\172.20.3.113\Dati\Allplan\usr\Riccardo\Library\AllepPlugins\AllplanGmbH\PythonPartSDK\StartPythonDebug_ita.xml does not exist

=======================================================================================================

Traceback (most recent call last):
File "C:\ProgramData\Nemetschek\Allplan\2025\Etc\PythonPartsFramework\GeneralScripts\BuildingElementUtil.py", line 78, in import_building_element_script
script = __import__(script_name)
^^^^^^^^^^^^^^^^^^^^^^^
File "\\172.20.3.113\Dati\Allplan\usr\Riccardo\PythonPartsScripts\AllepPlugins\AllplanGmbH\PythonPartSDK\reloader.py", line 199, in _import
base = _baseimport(name, globals, locals, fromlist, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'StartPythonDebug'

Hi,

looks for me like (for whatever reason) the path to the script was not correctly adapted during the installation of the SDK on your computer. Maybe it has sth to do with the location of your usr directory, which is in a network.

Open the file

\\172.20.3.113\Dati\Allplan\usr\Riccardo\Library\AllepPlugins\AllplanGmbH\PythonPartSDK\StartPythonDebug.pyp
and have a look at line 3. It should look like:
<Name>AllepPlugins\AllplanGmbH\PythonPartSDK\StartPythonDebug.py</Name>
But it probably looks like:
<Name>StartPythonDebug.py</Name>
If that's the case, please change it. Do the same with all other .pyp files in this directory.

Let me know, if that helped and if the path was really like I suspected.

Best,
Bart

Thank you very much, now it works as it should.