old_joyПри установке ASA 9.0.1 (DE) выскакивает ошибка, что невозможно зарегистрировать библиотеку dbctrs9.dll. Как лечить?
Набираем в Гугле dbctrs, получаем кучу информации к размышлению :)... Вот пара избранных ответов:

-------------------------------------------------------------------------
It's not normal & it's only a concern if you want to view ASA or Mobilink counters in perfmon.

The likely causes of failing to self-register are:
1) You are not running as an administrator
2) You registry is corrupt
3) You are running a really old version of NT, your DLL's path is long, *and* you have disabled 8.3 pathnames on your NTFS volume.

If you want to try to register dbctrs9.DLL without going through the installation process, just run

regsvr32 dbctrs9.dll

If you want to register dbmlctr9.dll, I believe you will need to be have a couple of files in the same directory (a .ini file and a .h file). I'm not sure if these files are installed or if they are just on the CD.
-------------------------------------------------------------------------

The organization for performance counter names that that MS chose is
extremely poor and error prone. All counter names for all objects are stored as one enormously long string in the registry. All counter help descriptions are stored as another enormously long string. These strings are so large that prior to XP you had to use regedt32 to see them (regedit wouldn't handle them). The keys are:

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Perflib\009\Counter"

and

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Perflib\009\Help"

These strings are in the format "string_number\nstring_text\n...". Counters are always even, Help text always odd, and the help text for counter N is given value N+1.

Utilities provided with the OS (lodctr & unlodctr) manage these keys as well as keys under each individual service's registry area (eg. the values under
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Adaptive_Server_Anywhere_9\Performance"

Good luck trying to correlate all of that information to find out if the registry is in fact correct. I have a perl script which attempts to correlate these values and maybe even fix them.

There was a bug in old versions of ASA unload scripts that failed to run unlodctr properly prior to deleting ASA's ...\Performance tree (in fact, we were missing a space and invoking "unlodctrAdaptive_Server_Anywhere"). That meant that ASA's counter names & help text were left in the registry. Installing & uninstalling ASA hundreds (or was it thousands) of times on the same machine would eventually cause so many copies of the ASA counter strings to be stored that the string indexes numbers (which are 16bit) in the ...009\Counter and Help values would wrap & corrupt the entire database of all counters on the system. Great.

Other things can go wrong too & we have a debug version of the dbctr9.dll which can help identify what is going wrong. Old versions of dbctrs insisted that an 8.3 version of the path to itself be generated and we found a number of systems have 8.3 names disabled (some non-ASA applications turn it off automatically during their installation procedure). Generating the 8.3 version of the name was an attempt to shorten the path to the DLL because old versions of perfmon couldn't handle long DLL pathnames.

Old versions of ASA had problems with counters when a client upgraded to a GA version of ASA that was older than the latest EBF that had been to the previous version (e.g. installing 8.0.1GA on top of a 8.0.0.latestEBF installation). The install process couldn't find a version number inside the text files as it would for a DLL so it used timestamps & it wouldn't clobber the "newer" (w.r.t. timestamp) .ini and .h files associated with the counter DLLs. This problem was fixed for dbctrsX.dll by embedding the .ini and .h files directly into the DLL. They are unpacked during the registration process and deleted at the end. No more mismatched DLL/.ini/.h for dbctrs. I don't think the same has been done yet for mlctrs.

I'm not sure if this gives you the information you want to know but it's pretty much everything I can think of that may be relevant.

If you have a reproducible case of a recent version of dbctrsX not registering, report it to techsupport and we can get you a debug version of the DLL. Maybe for 9.0.1 I can turn on the debug stuff by default and have it controlled by an environment variable or some such thing.
-------------------------------------------------------------------------

old_joyЖаль, что я набрал енто в yahoo
Что действительно забавно - набрав в Yahoo "dbctrs", я получил всего 1 ссылку именно на те же самые письма, что я привёл в предыдущем письме. Собсно, оно заработало или нет? В принципе, ничего критичного, но всё же...

Кстати, выгрузил у себя на компе с помощью Regedt32 ветку HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib. Файл ~800 к...