WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.


Control Manager

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Error 263 cWndGetWndSpec


While running running AnalysisEx against Windows 2003 Server (fully patched) Internet Explorer Version 6.0.3790.1830 SP1 and received the following error:-
wErrFile = AnalysisEx 1.0.5b
wError = 263
wErrStr =
wErrLine = Spec = cWndGetWndSpec(hwndChk)
wErrOffset = 13818
wErrAssign = spec
Believing that the issue was with AnalysisEx I have worked with the author to develop a solution. During this analysis however I received the same error number via Roboscripter. I am running WinBatch V 2006B with all extenders to the latest versions.

This error is not exposed when running against Internet Explorer running on Windows XP.

The question is whether this is specific to IE or a problem with Control Manager and W2K3.


Don't think it is a problem with IE, Roboscriptor, or control manager. And it is only tangentially related to the OS flavor.

CWndGetWndSpec requires access to certain registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009
NOTICE: The default setup for Win2K3 restricts access to this key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009

If the process running the WB script that calls the function does not have permission to access these keys, you will get the 263 error.

You will want to make sure this system doesn't have Performance Monitoring Disabled! The Windows Resource Kit Performance tool called Extensible Counter List (exctrlst.exe) can be used to check for all Perflib DLLs that are disabled.

I should add that while the extender uses a registry key to access a window's "wndspec", I am not sure where the permissions on the key are set because the key is a sort of pseudo key. It may be set in the Default Domain Controller Group Policy object or in the local security policy of the server or perhaps using a registry template. You could simply test the wntAccess*() functions against HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 and see what the current permissions are and whether or not additional permissions can be assigned to that pseudo-hive to allow less privileged users to access the performance data.

I suspect that if the "009" key's permissions were to be "relaxed" then less-privileged users would be able to obtain performance monitoring data.

Article ID:   W16822
File Created: 2017:07:28:13:58:25
Last Updated: 2014:07:18:09:43:57