st8 Discovery gdi-error [40201]：无法访问配置数据库

你好马克，
 
 
 这是安装严重的DAO-3.5文件的症状。您可以尝试通过从＆lt; Program Files（x86）＆gt; / STMicroelectronics / st_toolset / stvd / dao运行ST Toolset.msi来恢复。
 你的PC上有管理员权限吗？
 最好的祝福
 SC



以下为原文






Hello Marc,


this is symptomatic for badly installed DAO-3.5 files. May you please try to recover by running ST Toolset.msi from /STMicroelectronics/st_toolset/stvd/dao.
Do you have admin rights on your PC ?
Best regards
SC

我有同样的问题，并运行''C： Program Files（x86） STMicroelectronics  st_toolset  stvd  dao  ST Toolset.msi''修复它。谢谢。



以下为原文







I had the same problem and running ''C:Program Files (x86)STMicroelectronicsst_toolsetstvddaoST Toolset.msi'' fixed it. Thank you.

谢谢你的支持。



以下为原文





Thank you for support.

谢谢你，克里斯托弗。
 
 
 我很高兴找到这些信息。



以下为原文





Thank-you, Christopher.


I'm so glad to have found this information.

SC，
 
 
 真的很棒的建议。它工作得很好！谢谢。我有两个x64系统我安装了STTOOLS并且有相同的gdi错误。你的建议修好了。当我在32位系统上安装STTOOLS时，问题从未出现过。
 
 现在我的潜台词：是否有计划让STMicro在STTOOLS发行版中提供相同的修复程序？我很聪明，可以去寻找这个网页来找到你的修复。不是每个人都投入了这种能量。他们通常只是放弃。
 
 莱恩



以下为原文





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

嗨，
 
 
我试过这个修复程序，但仍然遇到这个问题。
我可以通过ST Visual Programmer编程，但不能使用Debug ..请帮忙
 
谢谢



以下为原文





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

你好，
 
 
 致Ilia：手动运行ST Toolset.msi会发生什么（它是否以成功消息结束）？哪个是你的操作系统？如果对象未立即正确注册，则安装后重新启动可能会解决问题
 
 对于poma.len：是的，我同意这将是非常好的！工具集installshield设置已经预计会自动运行它，不明白为什么并非总是如此（或者为什么它失败）...然后另外在最新版本的安装设置脚本中显式调用msiexec.exe已经完成，但看起来，到目前为止，仍然不足以修复所有案件



以下为原文





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

我也运行了ST Toolset.msi（修复选项，我假设）。它成功了（至少没有出现错误弹出窗口）。这并没有解决问题。
 
 
我正在运行Windows 8.1 64位。我尝试卸载并重新安装为Admin，但没有成功。
 
编程器（STVP）正常通过ST LV Discovery板进行通信（我可以读写Options字节）。
 
在STVD的“调试仪器设置”对话框中，我有''u***：// u***''用于''目标端口选择'。'我完全按照Discovery Tutorials步骤操作，并始终得到他的错误。
 
''40201''错误究竟是什么意思（''无法访问配置数据库''）？读/写permision？缺少数据库？什么是配置数据库？
 
谢谢！



以下为原文





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 ''u***://u***'' 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!

我遇到了同样的问题。运行ST Toolset.msi无法修复它。什么是配置数据库？它在哪里？
 
我卸载并重新安装了一切没有效果。



以下为原文







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.

你好，
 
 在使用DAO-3.5.0 Jet引擎的某些Windows 8系统上似乎还有另一个问题。我能够在一台机器上重现这个问题。在这台机器上，我在stvd / swim / error.log中收到错误''无法初始化DAO / Jet数据库引擎''。您可以检查此文件以了解您是否面临同样的问题。
 
 如果是，我可以通过执行以下顺序恢复：
 1.以管理员模式运行DOS命令提示符（％Windir％ system32  cmd.exe）
 
 2.启动命令Regsvr32 / u''C： Program Files（x86） Common Files  Microsoft Shared  DAO  DAO350.DLL''。这应该取消注册dll;请注意，在我的机器上，此步骤必须恢复，尽管之前注册表值似乎正确...
 
 3.启动命令Regsvr32''C： Program Files（x86） Common Files  Microsoft Shared  DAO  DAO350.DLL''。这应该再次注册DLL。请注意，在没有步骤2的情况下执行步骤3不足以在我的情况下进行恢复。
 
 再次启动STVD应允许连接到SWIM目标。
 请告诉我这是否也能解决你的问题。
 造成这种情况的根本原因仍未得到理解;这可能是因为在第一次安装过程中缺少权限，后续安装无法恢复？我们将对此进行调查。
 
 最好的祝福



以下为原文





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%system32cmd.exe) in administrator mode

2. launch the command Regsvr32 /u ''C:Program Files (x86)Common FilesMicrosoft SharedDAODAO350.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 FilesMicrosoft SharedDAODAO350.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

请帮帮我。
 
 
我正在尝试使用STM8S Discovery开发板，当我尝试使用ST-Link进行调试时，我不断收到错误。
无法访问配置数据库。我不知道为什么？或配置数据库是什么？我已经尝试安装所有东西，重新安装一切。我试过两台不同的电脑和4块不同的电路板，以及两条不同的ST链路？我正在使用Windows 8.任何想法？



以下为原文





Please help me.


I'm trying to use the STM8S Discovery dev board  and I keep getting errors when I try to use the ST-Link to debug it.
can't access configuration database.  I have no idea why? or what the config database is?  I've tried installing everything, reinstalling everything.  I've tried two different computers and 4 different boards, and two different ST-links? I'm using windows 8.  Any ideas?

你好斯蒂芬，
 
 
 你试过我在上一篇文章（8月26日）中解释过的吗？
 有关的数据库是stvd / swim / config / swim_conf.mdb。它需要将DAO-3.5喷气发动机安装在系统上。预计这将由ST Toolset.msi完成，如之前的帖子所述。也许您正面临其他一些问题：确保，请在错误后查看文件stvd / swim / error.log。如果它与我之前的假设不同，请发布。
 
 最好的祝福



以下为原文





Hello Stephen,


Did you try what I explained in the previous post (26 august) ?
The concerned database is stvd/swim/config/swim_conf.mdb. It requires the DAO-3.5 jet engine to be installed on the system. This is expected to be done by ST Toolset.msi, as explained in previous posts. Perhaps are you facing some other issue: to ensure, please have a look at the file stvd/swim/error.log after the error. If it differs from my previous hypothesis, please post it.

Best regards

亲爱的SC，
 
我在Windows 10上有类似的东西。注册DAO与管理员权限工作完美。
 
感谢你并致以真诚的问候，
alongkorn



以下为原文





Dear SC,

i got similar on windows 10. register DAO with admin right work perfect.  

thank you and best regards,
alongkorn

我尝试在Windows 10上建议这个解决方案并且工作得很好。谢谢！



以下为原文





I tried this solution suggested on Windows 10 and works perfectly. Thanks!

你好，
 
我试图在Windows 7系统上按照你的指示来解决GDI错误[40201]：无法访问配置数据库。请注意，Windows系统安装在驱动器F中：
 
我尝试使用恢复模式在DAO文件夹中运行''ST Toolset.msi'';安装似乎没问题。但错误仍然存​​在。
 
error.log文件附加到此帖子。
 
取消注册DAO350.DLL;但当我尝试再次注册DLL时发生错误：
''模块F： Program Files  Common Files  Microsoft shared  DAO  DAO350.DLL已加载，但对DllRegisterServer的调用失败。错误代码0x80004005''
 
我可以尝试其他方式吗？
 
谢谢
毛里齐奥



以下为原文





Hello,

I tried to follow your indication on a Windows 7 system in order to solve the GDI error [40201]: can't access configuration database. Note that Windows system is installed in drive F:

I tried to run ''ST Toolset.msi'' fron DAO folder, using recovery mode; the installation seems OK. But the error remains.

The error.log file is attached to this post.

After  unregistered the DAO350.DLL; but when I tried to register again the DLL an error occurred:
''The module F:Program FileCommon FilesMicrosoft sharedDAODAO350.DLL has been loaded but the call to a DllRegisterServer failed. Error code 0x80004005''

May I try some other way?

Thank You
Maurizio

你好，
 
我试图在Windows 7系统上按照你的指示来解决GDI错误[40201]：无法访问配置数据库。请注意，Windows系统安装在驱动器F中：
 
我尝试使用恢复模式在DAO文件夹中运行''ST Toolset.msi'';安装似乎没问题。但错误仍然存​​在。
 
error.log文件附加到此帖子。
 
取消注册DAO350.DLL;但当我尝试再次注册DLL时发生错误：
''模块F： Program Files  Common Files  Microsoft shared  DAO  DAO350.DLL已加载，但对DllRegisterServer的调用失败。错误代码0x80004005''
 
我尝试其他方式吗？
 
谢谢
毛里齐奥



以下为原文





Hello,

I tried to follow your indication on a Windows 7 system in order to solve the GDI error [40201]: can't access configuration database. Note that Windows system is installed in drive F:

I tried to run ''ST Toolset.msi'' fron DAO folder, using recovery mode; the installation seems OK. But the error remains.

The error.log file is attached to this post.

After  unregistered the DAO350.DLL; but when I tried to register again the DLL an error occurred:
''The module F:Program FileCommon FilesMicrosoft sharedDAODAO350.DLL has been loaded but the call to a DllRegisterServer failed. Error code 0x80004005''

My I try some other way?

Thank You
Maurizio

嗨，
 
 
 我和Maurizio有同样的问题。我已经按照这篇文章中详述的所有内容（包括大量的重新安装），我仍然得到了gdi错误。删除DLL并再次添加时，我收到与Maurizio相同的错误。
 
 这是使用Windows 8 64位的C：上的库存安装。



以下为原文





Hi,


I am having the same problem as Maurizio. I've followed everything detailed in this post (including numerous reinstalls) and I still get the gdi-error. When removing the DLL and adding it again, I receive the same error as Maurizio.

It's a stock installation on C: using Windows 8 64 bit.

''DllRegisterServer失败了。错误代码0x80004005''
 
 
 我通过以管理员身份运行命令提示符来解决这个问题（我之前不知道我没有这样做），Win-button - ＆gt;搜索命令 - ＆gt;右键单击命令提示符 - ＆gt;单击以管理员身份运行DLL现在注册和调试工作，问题是固定的。



以下为原文





''DllRegisterServer failed. Error code 0x80004005''


I solved this by running the command prompt as administrator (I wasn't aware that I didn't do this before), Win-button -> search for command -> right click Command Prompt -> click Run as administrator. DLL now registers and debug works, issue is fixed.

以下为原文