Skip to main content
Visitor II
March 27, 2014
Question

st8 Discovery gdi-error [40201]: can't access configuration database

  • March 27, 2014
  • 30 replies
  • 15185 views
Posted on March 27, 2014 at 20:09

Hi,

I'm trying to use the ST Visual Develop with the Cosmic st8 32k compiler.  I install everything and build the project.  That all works fine.  When I try to connect to the Discovery board with the debugger using Swim ST-link, I receive the following error:

Starting debug session...

 

 -> Emulator reset (usb://usb)...

 

  ** Connection error (usb://usb): gdi-error [40201]: can't access configuration database

 

 

 

 -> Failed to connect target.

I have tried uninstalling and re-installing everything including the drivers.  I've tried other target settings.  The only one that works is the simulator.

When I connect the Discovery board, my computer sees it as an external HD.  I get the pop-up window and can look at the links stored on the board.  I'm using Windows 7 64bit.

I should also add that after the above error message a windows 7 pop-up appears saying that gdb7 has stopped working and a red LED glows on the board.

Any help would be appreciated.

Regards,

Marc

#stm8-discovery #i-also-get-same-error-so-please
    This topic has been closed for replies.

    30 replies

    ST Employee
    March 28, 2014
    Posted on March 28, 2014 at 09:54

    Hello Marc,

    this is symptomatic for badly installed DAO-3.5 files. May you please try to recover by running ST Toolset.msi from <Program Files (x86)>/STMicroelectronics/st_toolset/stvd/dao.

    Do you have admin rights on your PC ?

    Best regards

    SC
    Visitor II
    December 13, 2016
    Posted on December 13, 2016 at 14:51

    Thanks SC for your valuable support.

    I also faced similar issue in Windows 8.1 Pro based system. I installed the toolset with a admin account and then was able to debug with a normal account login. thanks.

    Visitor II
    April 15, 2014
    Posted on April 16, 2014 at 01:04

    I had the same problem and running ''C:\Program Files (x86)\STMicroelectronics\st_toolset\stvd\dao\ST Toolset.msi'' fixed it. Thank you.

    Visitor II
    October 12, 2014
    Posted on October 12, 2014 at 16:28

    Thank you for support.

    Visitor II
    May 18, 2015
    Posted on May 18, 2015 at 19:21

    Thank-you, Christopher.

    I'm so glad to have found this information.

    Visitor II
    May 29, 2015
    Posted on May 29, 2015 at 12:53

    SC,

    Truly excellent suggestion.  It worked perfectly!  Thank you.  I have two x64 systems I installed STTOOLS on to and had the same gdi error.  Your suggestion fixed it.  The problem never appeared when I installed STTOOLS on 32-bit systems.

    Now for my subtext:  Is there plans for STMicro to provide this same fix into the STTOOLS distribution?  I was just smart enough to go looking for this page web to find your fix.  Not everyone puts in that energy.  They usually just give up.

    Len

    Visitor II
    August 11, 2015
    Posted on August 11, 2015 at 05:57

    Hi, 

    I have tried this fix but am still having this issue.

    I am able to program via ST Visual Programmer but cant use the Debug.. Please help

    thanks

    ST Employee
    August 13, 2015
    Posted on August 13, 2015 at 15:27

    Hello,

    To Ilia: what happens when running manually ST Toolset.msi (does it end with a message of success or not) ? Which is your operating system ? Perhaps a reboot after the install might fix the issue if the objects have not been correctly registered immediately

    To poma.len: yes I agree it would be very nice ! The toolset installshield setup is already expected to run it automatically, it is not understood why it is not always the case (or why it fails)... Then additionally in the installation setup script of most recent versions an explicit call to msiexec.exe is done but it looks like, so far, it is still not enough for fixing all cases
    Visitor II
    August 24, 2015
    Posted on August 24, 2015 at 18:28

    I also have run ST Toolset.msi (Repair option, I assume).  It succeeded (at least no error pop-up appeared).  This did not resolve the problem.

    I am running Windows 8.1 64-bit.  I have tried uninstalling and re-installing as Admin, with no success.

    Programmer (STVP) works correctly to communicate via ST LV Discovery board (I can read and write Options bytes).

    In the STVD ''Debug Instrument Settings'' dialog I have ''usb://usb'' for ''Target Port Selection.''  I have followed the Discovery Tutorials steps exactly, and always get his error.

    What exactly does the ''40201'' error (''can't access configuration database'') mean?  Read/write permision?  Missing database?  What is the configuration database for?  

    Thanks!

    Visitor II
    November 28, 2019

    Hi there. I am facing same issue. Did you find any fix?

    Explorer
    September 16, 2020

    I tried the STtoolset.msi repair - not fixed

    Did an uninstall / reinstall - fixed it.

    Visitor II
    August 25, 2015
    Posted on August 25, 2015 at 17:38

    I'm having the same problem.  Running ST Toolset.msi  does not fix it.  What is the configuration database?  where is it?

    I've uninstallled and reinstalled everything without effect.

    ST Employee
    August 26, 2015
    Posted on August 26, 2015 at 14:16

    Hello,

    it seems there is another issue on some Windows 8 systems with the DAO-3.5.0 Jet engine. I was able to reproduce the issue on one machine. On this machine, I got the error ''Unable to initialize DAO/Jet db engine'' in stvd/swim/error.log. You might check this file in order to know if you are facing the same issue.

    If yes, I was able to recover by doing the following sequence:

    1. run a DOS command prompt (%Windir%\system32\cmd.exe) in administrator mode

    2. launch the command Regsvr32 /u ''C:\Program Files (x86)\Common Files\Microsoft Shared\DAO\DAO350.DLL''. This should unregister the dll; note that on my machine this step was mandatory to recover, despite the registry values seem correct before ...

    3. launch the command Regsvr32 ''C:\Program Files (x86)\Common Files\Microsoft Shared\DAO\DAO350.DLL''. This should register again the DLL. Note that doing step 3 without step 2 was not enough for recovering in my case.

    Launching again STVD should allow connection to the SWIM target.

    Please tell me if this also fixes your case.

    The root cause for this is still not understood; it's perhaps because of missing rights during the first installing process, which is not recovered by subsequent installation ?? We will investigate this.

    Best regards
    Visitor II
    May 16, 2017
    Posted on May 16, 2017 at 23:26

    Thank you very much! Your solution solved my problem!

    My system: Win7 x64