Select to view content in your preferred language

Problem with creating InsertCursor

3727
14
09-15-2014 11:50 PM
ChristofLink
New Contributor II

Hi,

I want to write a small tool, which insert some data into an MS-Access database (.mdb). But i have a problem to initialize the cursor.

The Code is very simple :

strOutputPath = r"I:\Data\Test.mdb\FS_BASEMAP\FCL_B_COVERSHEET_A"

icur = arcpy.InsertCursor(strOutputPath)

There is some more code but it stoped at this point and I get this error message:

Traceback (most recent call last):

  File "I:\Skript\AddFeatureSkript.py", line 70, in <module>

    icur = arcpy.InsertCursor(strOutputPath)

  File "c:\program files (x86)\arcgis\desktop10.2\arcpy\arcpy\__init__.py", line 1214, in InsertCursor

    return gp.insertCursor(dataset, spatial_reference)

  File "c:\program files (x86)\arcgis\desktop10.2\arcpy\arcpy\geoprocessing\_base.py", line 369, in insertCursor

    self._gp.InsertCursor(*gp_fixargs(args, True)))

RuntimeError: ERROR 999999: Fehler beim Ausführen der Funktion.

COM-Komponente der Objektklassenerweiterung konnte nicht erstellt werden. [FCL_B_COVERSHEET_A]

The error message is in german so I translate it:

ERROR 999999: Error when executing the function.
COM component object class extension could not be created. [FCL_B_COVERSHEET_A]

I don't know what the problem is, so hopefully some can help me.

Thanks, Regards

0 Kudos
14 Replies
JoshuaBixby
MVP Esteemed Contributor

Do you have another machine to try it on?  Does this happen with all machines you are working on or just one?

0 Kudos
ChristofLink
New Contributor II

I have two other virtual maschines running on a server. One of them has ArcGIS v.10.2.2 installed, the other ArcGIS v 10.1.1 . I tried it on both maschines but this doesn't work either. The same error message...

0 Kudos
JoshuaBixby
MVP Esteemed Contributor

I was really thinking it might be something specific to that machine, but obviously that isn't the case.  I would say or suggest opening Support case, but best case scenario would be a bug that will be very low in terms of priority since it involves personal geodatabases.  This is where I would just find a workaround and say c'est la vie.

Good luck

ChristofLink
New Contributor II

Ok thank you very much for your help.

I will open a Support case and if I got an solution I will post it here.

0 Kudos
RandyKreuziger
Regular Contributor

Christof,

  Did you open a case and if you did is it a known bug?

0 Kudos