Technical Description

Common Licensing Problems

Products Concerned – Products that use the Central Licensing Server and Client. Including
Process Portal A, Process Portal B, and Composer.

Description: What follows is a listing of the most common errors encountered by users and the
corrective action taken.
1. Login Account for Client License Provider.........................................................................................................3

2. Assignment of Licenses.......................................................................................................................................3

3. ASP.NET missing..................................................................................................................................................3

4. Reboot After Uninstall..........................................................................................................................................3

5. SOAP missing.......................................................................................................................................................3

6. More than one license file is entered...................................................................................................................3

7. Wrong SFA_ID.......................................................................................................................................................3

8. No SFA_ID..............................................................................................................................................................3

9. FP6lm.....................................................................................................................................................................4

10. IIS / HTTP error 411...............................................................................................................................................4

11. DNS Error...............................................................................................................................................................4

12. CLS Client Components Not Installed.................................................................................................................4

13. Internet Startup Error............................................................................................................................................5

14. "Method '~' of object '~' failed--2147177479" or 0x8004ABF9............................................................................5

15. Stored Passwords.................................................................................................................................................5

16. IIS/proxy configuration.........................................................................................................................................5

17. "Service Unavailable" error message from an IIS 6.0 Web Page......................................................................5

18. CLS Server Web Settings.....................................................................................................................................6

19. PNSM Keepalive error...........................................................................................................................................6

20. IIS settings if Multiple Network Adapters are in the machine............................................................................6

21. Failed Machine ID..................................................................................................................................................7

22. License Failure After Loading Visual Studio 6 SP 6...........................................................................................7

23. XML may be unregistered in the uninstall of McAffee.......................................................................................8

24. License Assignment Editor - Object Error 800A41b6........................................................................................8

ABB Inc.

Doc. Id. Rev. B Date. 4/11/2025 1 (21)

 25. 0x0004AB89 The LCC making the feature request is not in the same system as the active SFA..................8

26. Reboot After Uninstall (A Different Error)...........................................................................................................9

27. Not all License Clients behaving the same.........................................................................................................9

28. Not all License Clients behaving the same (another way).................................................................................9

29. FF Import displays a license error.......................................................................................................................9

A. IIS Errors..............................................................................................................................................................10

B. Warning Codes Returned From CLS 0x0004xxxx.............................................................................................15

C. Error Codes Returned From CLS 0x8004xxxx..................................................................................................17

D. Error Codes Returned From Microsoft IIS 0x80072xxxx..................................................................................19

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 2 (21)

1. Login Account for Client License Provider
The ABB Client License Provider Service must have the 800xA service account as the launching user.

2. Assignment of Licenses
If a license quantity problem occurs but the quantity that is defined in the SLA is known to be sufficient, the user
may have unnecessarily reserved licenses to nodes or applications. Check the License Assignment Editor and
remove any unnecessary reservations.

3. ASP.NET missing
This can occur on systems that were not loaded with all prerequisites (Composer). Shows up as WSDL read errors
on a popup when running the license assignment editor. Also will show File Not Found (404) errors in the IIS log.

4. Reboot After Uninstall

If the system (license client or server) is not rebooted after uninstalling the following errors may occur:
80070433 – Automation error – Service does not exist or is marked for deletion
1075 - Service does not exist or is marked for deletion.

The server must be rebooted after CLS has been uninstalled.

5. SOAP missing
Not very many obvious symptoms except licensing doesn’t work. Shows up in the IIS log (Remember to enable
visits. Instructions can be found later in this document.). Will log with error 500 and messages like “80070005 Could
not create Soap Serializer Object”

6. More than one license file is entered

This is legal on systems that have SLA’s from products not related to 800xA, but is more likely to happen on
systems that mix demo and regular licenses. Check in “C:\Program Files\ABB Industrial IT\ABBLicense\Licenses\
Cache”. There should only be one file here. (unless the system has SLA’s from products not related to 800xA) .
Correct by deleting all of the files in the directory and reload the correct one with license entry.

7. Wrong SFA_ID
System Feature Agent (SFA) ID does not match the version expected by the license server. Most likely on demo or
development systems. Also occurs with some SOFA licenses generated between August and September 2005.
Will create errors on SFA tester (diagnostic tool included with the CLS install). Will cause also cause errors in
license counts but only after an application has requested them or they were assigned to an application. Assigning
to a node does not seem to cause the same problem. Some licenses may not be enforced. Get a new license file.

8. No SFA_ID
May allow multiple licenses to be loaded. Most likely on demo or development systems. Will create errors on some
license test SFA tester. See also Wrong SFA_ID.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 3 (21)

9. FP6lm
Most likely on demo or development systems. The SLA file will contain the string FP6lm instead of EBPAlm. Get a
new license file.

10. IIS / HTTP error 411

This happens in 2003 systems that are CLS servers. Look at the default application pool settings.
From Computer Management->Services and Applications->Internet Information Services->Application Pools-
>DefaultAppPool (right click) PropertiesRT (tab) Identity

It the user sets up increased security they may have changed this setting (possibly indirectly, caused by a security
update). See also "Service Unavailable" error message from an IIS 6.0 Web Page.

Symptoms: License Assignment editor unable to load licenses and throws the "Failed to load license feature file"
error.
To Fix change the identity
from: Configurable “Machine\IWAM_DR_DC1”
to: Predefined "Network Service".

11. DNS Error

Will display as a 0x80072ee7 in the event log with the client license provider as the offending task. This may be a
problem with the system DNS or connection between the client and server.

12. CLS Client Components Not Installed

A user may want to only install the CLS Server components on a machine that will not be used as an 800xA node
(DNS Server, Domain Controller). During the CLS install they will uncheck the “Client” portion. The Client pieces
are needed even for the server. This will be fixed in the install but is possible with existing systems using the
current distribution media. Fix: uninstall (reboot) reinstall licensing with both pieces checked.

One example of this error is:

13. Internet Startup Error

Will display as a 0x80072efd in the event log and popup warning. This is normal if the CLS gets ahead of IIS
completing startup. Should automatically reconnect on next cycle (20 sec).

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 4 (21)

14. "Method '~' of object '~' failed--2147177479" or 0x8004ABF9
This error can be a result of returning licenses when there are none checked out or from a license query for a
license not in use.

15. Stored Passwords

Windows XP implements stored passwords to help (not really) access other nodes. In 800xA we should not use
stored passwords. If they are used the stored credentials used to connect to a node will be reused on other
connections to that node, even if they are not appropriate.
For additional information on stored passwords:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281660

16. IIS/proxy configuration.

1) Will show up as communication errors to the CLS server. After updating the operating system with Service packs
and hot fixes it may be necessary to run proxycfg. To use the proxy settings from IE for WinHTTP:
proxycfg –u

If an empty (Default) proxy list is desired for the WinHTTP use :

proxycfg –d –p “ “ “*”

2) It is not typical to access the CLS through a proxy. You may want to look at the connections page of IE. The
bypass proxy for local addresses should be checked. IIS may need to be restarted complete this change. Then run
proxycfg to set the proxy for the WinHTTP communications path.
For additional information on the 407 error:
http://support.microsoft.com/default.aspx?scid=kb;en-us;248020

3) If proxycfg will not run because of a shared library or DLL problem (Known Microsoft bug), the default proxy
configuration can be set with regedit. Be careful with regedit!!! The location and data are as follows:

HKEY_LOCAL_MACHINE
SOFTWARE
Microsoft
Windows
CurrentVersion
Internet Settings
Connections
"WinHttpSettings"=hex:18,00,00,00,00,00,00,00,03,00,00,00,01,00,00,00,20,01,00,00,00,2a

17. "Service Unavailable" error message from an IIS 6.0 Web Page
You receive a "Service Unavailable" error message when you browse an IIS 6.0 Web page on a Windows Server
2003-based domain controller. This issue may occur if the server that is running Microsoft Internet Information
Services (IIS) 6.0 is also a domain controller. The problem occurs because the Application pool is using the NT
Authority\Network Service account, and the NT Authority\Network Service account may not have permissions to
access the required folders. However since the CLS Service does not display a user interface on the service calls,
this may be hard to see directly.
http://support.microsoft.com/default.aspx?scid=kb;en-us;842493
http://support.microsoft.com/default.aspx?scid=kb;en-us;885654

18. CLS Server Web Settings

1) Check CLS Virtual Directories and Properties. On the CLS machine;
From Computer Mangement->Services and Applications->Internet Information Services->Web Sites->Default Web
Site
Select ABBLicence (right click) select Properties

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 5 (21)

"Local Path" should be the path to the installation directory with read access
"Application Name" should be "" (blank)
"Execute Permissions" should be Scripts and Executables
"Application Protection" should be Medium(Pooled) (XP machines)
2) Select the "Configuration..." box from "Application Settings" section “Options” page and check that the options
match these:
Enable session state Checked
Session timeout 20 minutes
Enable Buffering Checked
Default ASP language VBScript
ASP Script Timeout 90 Seconds

3) From the ABBLicense Properties page, select the "Directory Security" tab
Check that only “Integrated Windows Authentication” is enabled.

19. PNSM Keepalive error

VBRuntime error in the Application Event Log:
The VB Application identified by the event source logged this Application KeepAliveApp:
Thread ID: 3788 ,Logged: -2147221020b
KeepAliveComp.BuildNameArray Automation error Invalid syntax
Indicates that either SNMP, WMI or WBEM is not installed or is mis-configured (not registered)

20. IIS settings if Multiple Network Adapters are in the machine

If multiple adapters are used in the CLS server machine, IIS must be configured to select the proper network for the
Default Web. See the illustration below.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 6 (21)

21. Failed Machine ID
If the following message is displayed, check to make sure the Dongel (Hardware Key) has not fallen off, been
knocked loose or went home in someone’s pocket. Reattach and the messages should clear in a minute or two.

22. License Failure After Loading Visual Studio 6 SP 6

When you try to view an ASP page after you have installed Microsoft Visual Studio 6.0 Service Pack 6 (SP6),
licensing may stop replying to client requests. This is documented in Microsoft KB842329. This problem occurs
because the Visual Studio 6.0 SP6 Setup program removes the Everyone group from the list of authorized users
and groups for the Mfc42.dll file. Microsoft Internet Information Services (IIS) uses the IWAM_ComputerName user
account to start out-of-process applications.To resolve this problem, grant the IWAM_ComputerName user account
the Read & Execute permission for the Mfc42.dll file. The Mfc42.dll file is located in the %WINDIR%\System32
folder. Since licensing uses program to program communication, the error generated by IIS will not be visible to the

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 7 (21)

user. To trouble shoot, turn on message logging (see section A.1). The message requests will show an error 500 in
the log.
To fix this problem, grant the Read & Execute permission, follow these steps:
1. In Windows Explorer, locate the Mfc42.dll file.
2. Right-click the Mfc42.dll file, and then click Properties. The Properties dialog box appears.
3. Click the Security tab, and then click Add. The Select Users or Groups dialog box appears.
4. In the Name field, locate and then click IWAM_ComputerName.
5. Click Add, and then click OK.

23. XML may be unregistered in the uninstall of McAffee

After uninstalling some versions of McAffee Anti-Virus Licensing may stop working. This is because one XML
interface has become unregistered. To repair run:
Regsvr32 C:\WINNT\system32\msxml3.

24. License Assignment Editor - Object Error 800A41b6

If an error dialog is displayed like the one below the system is missing a dll. Most likely SOAP. This is normally
installed as part of system installer. This occurs if licensing is installed on a new machine without the
800xA/PPA prerequisites. To repair, run the SOAP install from the distribution disks.

25. 0x0004AB89 The LCC making the feature request is not in the same system as the active
SFA
This error typically comes from one of three causes.

 You are trying to use one license server for more than one 800xA system. This can work but
you need to use the non-sfa internal license.
 You have re-created the system but have not re-added the nodes to it.
 A machine somewhere in the network that is not part of this PPA system has this CLS as its
license server.

The CLS will take the first PPA system name that connects as its SFA ID to validate all other
connections.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 8 (21)

26. Reboot After Uninstall (A Different Error)
If the system (server only) is not rebooted after uninstalling the following errors may occur:
 Clients will be issued temporary licenses
 In the License Status Viewer the status (bottom of window) will show 0x00000001
 Running the License Assignment Editor will show dialogues with one of the following errors:
0x800A01A8, 0x80040154 (could be others).
Check the license directory, C:\Program Files\ABB Industrial IT\ABBLicense, to see if ABBLicenseService.dll is
present. If not, the DLL was probably locked by IIS during the uninstall. To repair: uninstall, reboot, reinstall.

27. Not all License Clients behaving the same

If the system has already been checked for consistent PPA system names and the SFA ID’s are not an issue
the problem may be with the hosts file on one or more machines. The hosts file defines name to IP address
translation locally for each machine and should only be used if system DNS capabilities are insufficient. The file
is located in: C:\Windows\system32\drivers\etc. By default it contains one entry for local host.

28. Not all License Clients behaving the same (another way)
If two or more network cards are configured in the license server the main connection for CLS must be the IP
address that is resolved by the network DNS and all clients must be able to contact this port. Also the server
itself must recognize that this IP address corresponds to the machine name.

29. FF Import displays a license error

If an FF import is attempted, a dialog may be displayed showing a license error. This is probably not a license
error. It may indicate that Asset Optimization (AO) is not installed.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 9 (21)

A. IIS Errors

A.1 IIS Log File Locations

By default, IIS places its log files in %WINDIR\System32\Logfiles. This directory contains separate
directories for each World Wide Web (WWW) and FTP site. By default, logs are created in the directories
daily and are named with the date (for example, exYYMMDD.log). However the logging must be enabled
“Log Visits” (turn off after troubleshooting or license performance may be impaired).

A.2 HTTP Errors found in IIS log

1xx - Informational
These status codes indicate a provisional response. The client should be prepared to receive one or
more 1xx responses before receiving a regular response.
• 100 - Continue.
• 101 - Switching protocols.

2xx - Success
This class of status codes indicates that the server successfully accepted the client request.
• 200 - OK. The client request has succeeded.
• 201 - Created.
• 202 - Accepted.
• 203 - Non-authoritative information.
• 204 - No content.
• 205 - Reset content.
• 206 - Partial content.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 10 (21)

 3xx - Redirection
The client browser must take more action to fulfill the request. For example, the browser may have
to request a different page on the server or repeat the request by using a proxy server.
• 302 - Object moved.
• 304 - Not modified.
• 307 - Temporary redirect.

4xx - Client Error

An error occurs, and the client appears to be at fault. For example, the client may request a page
that does not exist, or the client may not provide valid authentication information.
• 400 - Bad request.
401 - Access denied. IIS defines a number of different 401 errors that indicate a more specific cause of the
error. These specific error codes are displayed in the browser but are not displayed in the IIS log:
• 401.1 - Logon failed.
• 401.2 - Logon failed due to server configuration.
• • 401.3 - Unauthorized due to ACL on resource.
• 401.4 - Authorization failed by filter.
• 401.5 - Authorization failed by ISAPI/CGI application.
401.7 – Access denied by URL authorization policy on the Web server. This error code is specific to IIS
•
6.0.
403 - Forbidden. IIS defines a number of different 403 errors that indicate a more specific cause of the
error:
• 403.1 - Execute access forbidden.
• 403.2 - Read access forbidden.
• 403.3 - Write access forbidden.
• 403.4 - SSL required.
• 403.5 - SSL 128 required.
• 403.6 - IP address rejected.
• 403.7 - Client certificate required.
• 403.8 - Site access denied.
• 403.9 - Too many users.
• • 403.10 - Invalid configuration.
• 403.11 - Password change.
• 403.12 - Mapper denied access.
• 403.13 - Client certificate revoked.
• 403.14 - Directory listing denied.
• 403.15 - Client Access Licenses exceeded.
• 403.16 - Client certificate is untrusted or invalid.
• 403.17 - Client certificate has expired or is not yet valid.
403.18 - Cannot execute requested URL in the current application pool. This error code is specific to IIS
•
6.0.
• 403.19 - Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.
• 403.20 - Passport logon failed. This error code is specific to IIS 6.0.
404 - Not found.
• 404.0 - (None) – File or directory not found.
• • 404.1 - Web site not accessible on the requested port.
• 404.2 - Web service extension lockdown policy prevents this request.
• 404.3 - MIME map policy prevents this request.
• 405 - HTTP verb used to access this page is not allowed (method not allowed.)
• 406 - Client browser does not accept the MIME type of the requested page.
• 407 - Proxy authentication required.
• 412 - Precondition failed.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 11 (21)

• 413 – Request entity too large.
• 414 - Request-URI too long.
• 415 – Unsupported media type.
• 416 – Requested range not satisfiable.
• 417 – Execution failed.
• 423 – Locked error.

5xx - Server Error

The server cannot complete the request because it encounters an error.
500 - Internal server error.
• 500.12 - Application is busy restarting on the Web server.
• 500.13 - Web server is too busy.
• • 500.15 - Direct requests for Global.asa are not allowed.
• 500.16 – UNC authorization credentials incorrect. This error code is specific to IIS 6.0.
• 500.18 – URL authorization store cannot be opened. This error code is specific to IIS 6.0.
• 500.100 - Internal ASP error.
• 501 - Header values specify a configuration that is not implemented.
502 - Web server received an invalid response while acting as a gateway or proxy.
• • 502.1 - CGI application timeout.
• 502.2 - Error in CGI application.
• 503 - Service unavailable. This error code is specific to IIS 6.0.
• 504 - Gateway timeout.
• 505 - HTTP version not supported.

A.3 Common HTTP Status Codes and Their Causes

• 200 - Success. This status code indicates that IIS has successfully processed the request.
304 - Not Modified. The client requests a document that is already in its cache and the document has not
• been modified since it was cached. The client uses the cached copy of the document, instead of
downloading it from the server.
401.1 - Logon failed. The logon attempt is unsuccessful, probably because of a user name or password
•
that is not valid.
401.3 - Unauthorized due to ACL on resource. This indicates a problem with NTFS permissions. This
error may occur even if the permissions are correct for the file that you are trying to access. For example,
you see this error if the IUSR account does not have access to the C:\Winnt\System32\Inetsrv directory.
•
For additional information about how to resolve this problem, click the following article number to view the
article in the Microsoft Knowledge Base:
187506 (http://support.microsoft.com/kb/187506/) INFO: Basic NTFS permissions for IIS 4.0
403.1 - Execute access forbidden. The following are two common causes of this error message:
You do not have enough Execute permissions. For example, you may receive this error message if you
try to access an ASP page in a directory where permissions are set to None, or you try to execute a CGI
script in a directory with Scripts Only permissions. To modify the Execute permissions, right-click the
•
directory in the Microsoft Management Console (MMC), click Properties, click the Directory tab, and
• make sure that the Execute Permissions setting is appropriate for the content that you are trying to
access.
The script mapping for the file type that you are trying to execute is not set up to recognize the verb that
you are using (for example, GET or POST). To verify this, right-click the directory in the MMC, click
•
Properties, click the Directory tab, click Configuration, and verify that the script mapping for the
appropriate file type is set up to allow the verb that you are using.
403.2 - Read access forbidden. Verify that you have set up IIS to allow Read access to the directory.
Also, if you are using a default document, verify that the document exists. For additional information about
how to resolve this problem, click the article number below to view the article in the Microsoft Knowledge
•
Base:
247677 (http://support.microsoft.com/kb/247677/EN-US/) Error Message: 403.2 Forbidden: Read Access
Forbidden

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 12 (21)

 403.3 - Write access forbidden. Verify that the IIS permissions and the NTFS permissions are set up
to grant Write access to the directory. For additional information about how to resolve this problem,
• click the article number below to view the article in the Microsoft Knowledge Base:
248072 (http://support.microsoft.com/kb/248072/EN-US/) Error Message: 403.3 Forbidden: Write
Access Forbidden
403.4 - SSL required. Disable the Require secure channel option, or use HTTPS instead of HTTP to
access the page. If you receive this error for a Web site that does not have a certificate installed,
• click the article number below to view the article in the Microsoft Knowledge Base:
224389 (http://support.microsoft.com/kb/224389/EN-US/) Err Msg: HTTP Error 403, 403.4, 403.5
Forbidden: SSL Required
403.5 - SSL 128 required. Disable the Require 128-bit encryption option, or use a browser that
supports 128-bit encryption to view the page. If you receive this error for a Web site that does not
have a certificate installed, click the article number below to view the article in the Microsoft
•
Knowledge Base:
224389 (http://support.microsoft.com/kb/224389/EN-US/) Err Msg: HTTP Error 403, 403.4, 403.5
Forbidden: SSL Required
403.6 - IP address rejected. You have configured your server to deny access to your current IP
address. For additional information about how to resolve this problem, click the article number
• below to view the article in the Microsoft Knowledge Base:
248043 (http://support.microsoft.com/kb/248043/EN-US/) Error Message: 403.6 - Forbidden: IP
Address Rejected
403.7 - Client certificate required. You have configured your server to require a certificate for client
authentication, but you do not have a valid client certificate installed. For additional information,
click the article numbers below to view the articles in the Microsoft Knowledge Base:
• 190004 (http://support.microsoft.com/kb/190004/EN-US/) Error 403.7 or 'Connection to Server Could
Not Be Established'
186812 (http://support.microsoft.com/kb/186812/EN-US/) PRB: Error Message: 403.7 Forbidden:
Client Certificate Required
403.8 - Site access denied. You have set up a domain name restriction for the domain that you are
using to access your server. For additional information about how to resolve this problem, click the
• article number below to view the article in the Microsoft Knowledge Base:
248032 (http://support.microsoft.com/kb/248032/EN-US/) Error Message: Forbidden: Site Access
Denied 403.8
403.9 - Too many users. The number of users who are connected to the server exceeds the
connection limit that you have set. For additional information about how to change this limit, click
the article number below to view the article in the Microsoft Knowledge Base:
• 248074 (http://support.microsoft.com/kb/248074/EN-US/) Error Message: Access Forbidden: Too
Many Users Are Connected 403.9
NOTE: Microsoft Windows 2000 Professional and Microsoft Windows XP Professional automatically
impose a 10-connection limit on IIS. You cannot change this limit.
403.12 - Mapper denied access. The page that you want to access requires a client certificate, but
the user ID that is mapped to your client certificate has been denied access to the file. For
additional information, click the article number below to view the article in the Microsoft Knowledge
•
Base:
248075 (http://support.microsoft.com/kb/248075/EN-US/) Error: HTTP 403.12 - Access Forbidden:
Mapper Denied Access
404 - Not found. This error may occur if the file that you are trying to access has been moved or
deleted. It can also occur if you try to access a file that has a restricted file name extension after
•
you install the URLScan tool. In this case, you see "Rejected by URLScan" in the log file entry for
that request.
500 - Internal server error. You see this error message for a wide variety of server-side errors. Your
event viewer logs may contain more information about why this error occurs. Additionally, you can
disable friendly HTTP error messages to receive a detailed description of the error. For additional
• information about how to disable friendly HTTP error messages, click the article number below to
view the article in the Microsoft Knowledge Base:
294807 (http://support.microsoft.com/kb/294807/EN-US/) HOWTO: Disable Internet Explorer 5 'Show
Friendly HTTP Error Messages' Feature on the Server Side

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 13 (21)

500.12 - Application restarting. This indicates that you tried to load an ASP page while IIS was in the
process of restarting the application. This message should disappear when you refresh the page. If you
refresh the page and the message appears again, it may be caused by antivirus software that is scanning
your Global.asa file. For additional information, click the article number below to view the article in the
Microsoft Knowledge Base:
248013 (http://support.microsoft.com/kb/248013/EN-US/) Err Msg: HTTP Error 500-12 Application
Restarting
500-100.ASP - ASP error. You receive this error message when you try to load an ASP page that has
errors in the code. To obtain more specific information about the error, disable friendly HTTP error
messages. By default, this error is only enabled on the default Web site.For additional information about
how to see this error on non-default Web sites, click the article number below to view the article in the
Microsoft Knowledge Base:
261200 (http://support.microsoft.com/kb/261200/EN-US/) HTTP 500 Error Message Displays Instead of
ASP Error Message from 500-100.asp
502 - Bad gateway. You receive this error message when you try to run a CGI script that does not return a
valid set of HTTP headers.

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 14 (21)

 B. Warning Codes Returned From CLS 0x0004xxxx
Could be in popups, system event logs and C:\Program Files\ABB Industrial IT\ABBLicense\Licenses\
CLSErrors.log

Can't find license file AB_S_LC_NOCONFFILE 0x0004AB01

License file corrupted AB_S_LC_BADFILE 0x0004AB02
Could not search for keys AB_S_LC_NOMIDS 0x0004AB03
Maximum number of users reached AB_S_LC_MAXUSERS 0x0004AB04
No such feature exists AB_S_LC_NOFEATURE 0x0004AB05
No licenses checked out yet AB_S_LC_NONEUSEDYET 0x0004AB06
Format of Feature line is invalid AB_S_LC_FORMATERR 0x0004AB07
Bad encryption code AB_S_LC_BADCODE 0x0004AB08
Feature found, but wrong Machine ID AB_S_LC_WRONGMID 0x0004AB09
Feature found with a wrong version number AB_S_LC_WRONGVERSION 0x0004AB0A
Feature found, but wrong option string AB_S_LC_WRONGOPTION 0x0004AB0B
Software/Feature Expired AB_S_LC_FEATUREEXPIRED 0x0004AB0C
Bad date in license file AB_S_LC_BADDATE 0x0004AB0D
duplicate license entry AB_S_LC_DUPLICATE 0x0004AB0E
Software Key does not match parameters AB_S_LC_BADSWKEY 0x0004AB0F
License entry not found AB_S_LC_NOTFOUND 0x0004AB10
Cannot write to server AB_S_LC_CANTWRITE 0x0004AB11
Request for more licenses than supported AB_S_LC_TOOMANY 0x0004AB12
Cannot read license file AB_S_LC_NOREADLIC 0x0004AB13
Start date for feature not reached AB_S_LC_TOOEARLY 0x0004AB14
Machine ID not found AB_S_LC_MIDNOTFOUND 0x0004AB15
Machine ID type not found AB_S_LC_NOKEYDATA 0x0004AB16
Machine ID type not supported AB_S_LC_KEYNOTSUPPORTED 0x0004AB17
ETHERNET MAC Address not found AB_S_LC_NOETHERNET 0x0004AB18
Could not open net device AB_S_LC_NETOPENFAIL 0x0004AB19
Error getting Hard Disk Drive info AB_S_LC_HDDVOLINFOFAIL 0x0004AB1A
Disk is not a fixed disk AB_S_LC_HDDNOTFIXEDDRV 0x0004AB1B
Error in registry entry for license file AB_S_LC_LICFILE_REG 0x0004AB1C
Error in registry setting for HW Key AB_S_LC_MID_REG 0x0004AB1D
The nmapi32.dll is not in the path AB_S_LC_PWDLLNOTFOUND 0x0004AB1E
The ethernet address functions cannot be found in AB_S_LC_PWFUNCNOTFOUND 0x0004AB1F
nmapi32.dll
Problem encountered while retrieving ethernet AB_S_LC_PWFUNCPROBLEM 0x0004AB20
address using Pathworks
The LCC making the feature request is not in the AB_S_CLS_INVALID_SYSTEM 0x0004AB89
same system as the active SFA.
The client has been granted temporary licenses. AB_S_LCC_TEMPORARY_CAPTION 0x0004ABC0
The client has invalid licenses. AB_S_LCC_INVALID_CAPTION 0x0004ABC1
Success: Some licenses could not be granted due to AB_S_LCC_GLOBAL_CAPTION 0x0004ABC2
insufficient quantity
The caption on the message box displayed when a AB_S_LCC_REQUEST_FAILURE_CAPTION 0x0004ABC3
request for licenses has failed
Message box text displayed when a request for AB_S_LCC_LICENSE_REQUEST_TEXT 0x0004ABC4
licenses has failed

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 15 (21)

Message box text displayed when a request for AB_S_LCC_INVALID_LICENSE_TEXT 0x0004ABC5
licenses has failed
Success: Global invalid licenses have been granted. AB_S_LCC_GLOBAL_INVALID_TEXT 0x0004ABC6
Success: Global license errors have occurred. AB_S_LCC_GLOBAL_ERRORS_TEXT 0x0004ABC7
Success: Please refer to the license error log by AB_S_LCC_GLOBAL_DETAILS_TEXT 0x0004ABC8
running:
Success: Start->Programs->ABB Industrial IT->ABB AB_S_LCC_GLOBAL_PATH_TEXT 0x0004ABC9
Licensing->License Log
Message Box text for bad MID annoyance AB_S_LCC_GLOBAL_BAD_MID_TEXT 0x0004ABCA
The client has been granted temporary licenses. AB_S_LCC_TEMPORARY_LICENSE 0x0004ABF0
The client has been granted invalid licenses. AB_S_LCC_LICENSE_COUNT_EXCEEDED 0x0004ABF1
Success: Some licenses could not be granted due to AB_S_LCC_PARTIAL_QUANTITY 0x0004ABF2
insufficient quantity

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 16 (21)

 C. Error Codes Returned From CLS 0x8004xxxx
Could be in popups, system event logs and C:\Program Files\ABB Industrial IT\ABBLicense\Licenses\
CLSErrors.log

Can't find license file AB_E_LC_NOCONFFILE 0x8004AB01

License file corrupted AB_E_LC_BADFILE 0x8004AB02
Could not search for keys AB_E_LC_NOMIDS 0x8004AB03
Maximum number of users reached AB_E_LC_MAXUSERS 0x8004AB04
No such feature exists AB_E_LC_NOFEATURE 0x8004AB05
No licenses checked out yet AB_E_LC_NONEUSEDYET 0x8004AB06
Format of Feature line is invalid AB_E_LC_FORMATERR 0x8004AB07
Bad encryption code AB_E_LC_BADCODE 0x8004AB08
Feature found, but wrong Machine ID AB_E_LC_WRONGMID 0x8004AB09
Feature found with a wrong version number AB_E_LC_WRONGVERSION 0x8004AB0A
Feature found, but wrong option string AB_E_LC_WRONGOPTION 0x8004AB0B
Software/Feature Expired AB_E_LC_FEATUREEXPIRED 0x8004AB0C
Bad date in license file AB_E_LC_BADDATE 0x8004AB0D
Duplicate license entry AB_E_LC_DUPLICATE 0x8004AB0E
Software Key does not match parameters AB_E_LC_BADSWKEY 0x8004AB0F
License entry not found AB_E_LC_NOTFOUND 0x8004AB10
Cannot write to server AB_E_LC_CANTWRITE 0x8004AB11
Request for more licenses than supported AB_E_LC_TOOMANY 0x8004AB12
Cannot read license file AB_E_LC_NOREADLIC 0x8004AB13
Start date for feature not reached AB_E_LC_TOOEARLY 0x8004AB14
Machine ID not found AB_E_LC_MIDNOTFOUND 0x8004AB15
Machine ID type not found AB_E_LC_NOKEYDATA 0x8004AB16
Machine ID type not supported AB_E_LC_KEYNOTSUPPORTED 0x8004AB17
ETHERNET MAC Address not found AB_E_LC_NOETHERNET 0x8004AB18
Could not open net device AB_E_LC_NETOPENFAIL 0x8004AB19
Error getting Hard Disk Drive info AB_E_LC_HDDVOLINFOFAIL 0x8004AB1A
Disk is not a fixed disk AB_E_LC_HDDNOTFIXEDDRV 0x8004AB1B
Error in registry entry for license file AB_E_LC_LICFILE_REG 0x8004AB1C
Error in registry setting for HW Key AB_E_LC_MID_REG 0x8004AB1D
The nmapi32.dll is not in the path AB_E_LC_PWDLLNOTFOUND 0x8004AB1E
The Ethernet address functions cannot be found in AB_E_LC_PWFUNCNOTFOUND 0x8004AB1F
nmapi32.dll
Problem encountered while retrieving Ethernet AB_E_LC_PWFUNCPROBLEM 0x8004AB20
address using Pathworks
Buffer is too small AB_E_LC_BUFFERTOOSMALL 0x8004AB32
Can't allocate memory AB_E_LC_ALLOC 0x8004AB33
Warning AB_E_LC_WARNING 0x8004AB34
Key data has expired AB_E_LC_EXPIREDKEYS 0x8004AB35
Not enough quantity remaining AB_E_CLS_NOTENOUGHQUANTITY 0x8004AB81
Request already exists AB_E_CLS_DUPLICATEREQUEST 0x8004AB82
Not enough floating licenses AB_E_CLS_NOTENOUGHFLOATING 0x8004AB83
The request to be refreshed can not be found AB_E_CLS_REQUESTNOTFOUND 0x8004AB84
New request cannot be processed AB_E_CLS_CANNOTCREATEREQUEST 0x8004AB85

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 17 (21)

The CLS is in the process of starting up AB_E_CLS_STARTUPINPROGRESS 0x8004AB86
General Authentication failure AB_E_CLS_GENERAL_AUTH_FAILURE 0x8004AB87
The CLS has received an invalid request from the AB_E_CLS_INVALID_REQUEST 0x8004AB88
LCC. Usually manifests as unable to load the request
object.
The LCC making the feature request is not in the AB_E_CLS_INVALID_SYSTEM 0x8004AB89
same system as the active SFA.
The CIV on the license file failed to validate. AB_E_CLS_INVALID_CIV 0x8004AB8A
The System is running without an active SFA. AB_E_CLS_NO_ACTIVE_SFA 0x8004AB8B
A hardware key has stopped functioning, please AB_E_CLS_BAD_MID 0x8004AB8C
replace hardware key.
SFA Report is incomplete. AB_E_CLS_SFA_REPORT_INCOMPLETE 0x8004AB8D
The client has been granted temporary licenses. AB_E_LCC_TEMPORARY_LICENSE 0x8004ABF0
The client has invalid licenses. AB_E_LCC_INVALID_LICENSE 0x8004ABF1
The LCC has received a response from the CLS AB_E_LCC_VERIFY_FAILED 0x8004ABF2
where the MAC was not verified as authentic.
The client has received a response from the CLS with AB_E_LCC_INVALID_MAC 0x8004ABF3
an invalid Message Authentication Code.
The CLS is not responding. AB_E_LCC_NO_LICENSE_SERVICE 0x8004ABF4
The error translation service is not responding. AB_E_LCC_NO_TRANSLATION_SERVICE 0x8004ABF5
The LCC received an error translation file that could AB_E_LCC_BAD_TRANSLATION 0x8004ABF6
not be parsed.
The LCC has received an invalid response from the AB_E_LCC_INVALID_RESPONSE 0x8004ABF7
CLS. Usually manifests as an XML parse error.
The LCC has encountered an internal error condition. AB_E_LCC_INTERNAL_ERROR 0x8004ABF8
The client has requested status for a feature that has AB_E_LCC_FEATURE_NOT_FOUND 0x8004ABF9
no current request from any of the async calls.
The CLS has responded with a SOAP Fault. AB_E_LCC_LICENSE_SERVICE_FAULT 0x8004ABFA
The Requested SFA does not exist. AB_E_LCC_INVALID_SFA_ID 0x8004ABFB
The SFA request object is not in a valid state for the AB_E_LCC_INVALID_SFA_REQUEST_STA 0x8004ABFC
requested action. TE

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 18 (21)

D. Error Codes Returned From Microsoft IIS 0x80072xxxx
Could be in popups, system event logs and C:\Program Files\ABB Industrial IT\ABBLicense\Licenses\
CLSErrors.log

INTERNET_ERROR_BASE 80072EE0
ERROR_INTERNET_OUT_OF_HANDLES 80072EE1
ERROR_INTERNET_TIMEOUT 80072EE2
ERROR_INTERNET_EXTENDED_ERROR 80072EE3
ERROR_INTERNET_INTERNAL_ERROR 80072EE4
ERROR_INTERNET_INVALID_URL 80072EE5
ERROR_INTERNET_UNRECOGNIZED_SCHEME 80072EE6
ERROR_INTERNET_NAME_NOT_RESOLVED 80072EE7
ERROR_INTERNET_PROTOCOL_NOT_FOUND 80072EE8
ERROR_INTERNET_INVALID_OPTION 80072EE9
ERROR_INTERNET_BAD_OPTION_LENGTH 80072EEA
ERROR_INTERNET_OPTION_NOT_SETTABLE 80072EEB
ERROR_INTERNET_SHUTDOWN 80072EEC
ERROR_INTERNET_INCORRECT_USER_NAME 80072EED
ERROR_INTERNET_INCORRECT_PASSWORD 80072EEE
ERROR_INTERNET_LOGIN_FAILURE 80072EEF
ERROR_INTERNET_INVALID_OPERATION 80072EF0
ERROR_INTERNET_OPERATION_CANCELLED 80072EF1
ERROR_INTERNET_INCORRECT_HANDLE_TYPE 80072EF2
ERROR_INTERNET_INCORRECT_HANDLE_STATE 80072EF3
ERROR_INTERNET_NOT_PROXY_REQUEST 80072EF4
ERROR_INTERNET_REGISTRY_VALUE_NOT_FOUND 80072EF5
ERROR_INTERNET_BAD_REGISTRY_PARAMETER 80072EF6
ERROR_INTERNET_NO_DIRECT_ACCESS 80072EF7
ERROR_INTERNET_NO_CONTEXT 80072EF8
ERROR_INTERNET_NO_CALLBACK 80072EF9
ERROR_INTERNET_REQUEST_PENDING 80072EFA
ERROR_INTERNET_INCORRECT_FORMAT 80072EFB
ERROR_INTERNET_ITEM_NOT_FOUND 80072EFC
ERROR_INTERNET_CANNOT_CONNECT 80072EFD
ERROR_INTERNET_CONNECTION_ABORTED 80072EFE
ERROR_INTERNET_CONNECTION_RESET 80072EFF
ERROR_INTERNET_FORCE_RETRY 80072F00
ERROR_INTERNET_INVALID_PROXY_REQUEST 80072F01
ERROR_INTERNET_NEED_UI 80072F02
ERROR_INTERNET_HANDLE_EXISTS 80072F04
ERROR_INTERNET_SEC_CERT_DATE_INVALID 80072F05
ERROR_INTERNET_SEC_CERT_CN_INVALID 80072F06
ERROR_INTERNET_HTTP_TO_HTTPS_ON_REDIR 80072F07
ERROR_INTERNET_HTTPS_TO_HTTP_ON_REDIR 80072F08
ERROR_INTERNET_MIXED_SECURITY 80072F09

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 19 (21)

ERROR_INTERNET_CHG_POST_IS_NON_SECURE 80072F0A
ERROR_INTERNET_POST_IS_NON_SECURE 80072F0B
ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED 80072F0C
ERROR_INTERNET_INVALID_CA 80072F0D
ERROR_INTERNET_CLIENT_AUTH_NOT_SETUP 80072F0E
ERROR_INTERNET_ASYNC_THREAD_FAILED 80072F0F
ERROR_INTERNET_REDIRECT_SCHEME_CHANGE 80072F10
ERROR_INTERNET_DIALOG_PENDING 80072F11
ERROR_INTERNET_RETRY_DIALOG 80072F12
ERROR_INTERNET_HTTPS_HTTP_SUBMIT_REDIR 80072F14
ERROR_INTERNET_INSERT_CDROM 80072F15
ERROR_HTTP_HEADER_NOT_FOUND 80072F76
ERROR_HTTP_DOWNLEVEL_SERVER 80072F77
ERROR_HTTP_INVALID_SERVER_RESPONSE 80072F78
ERROR_HTTP_INVALID_HEADER 80072F79
ERROR_HTTP_INVALID_QUERY_REQUEST 80072F7A
ERROR_HTTP_HEADER_ALREADY_EXISTS 80072F7B
ERROR_HTTP_REDIRECT_FAILED 80072F7C
ERROR_INTERNET_SECURITY_CHANNEL_ERROR 80072F7D
ERROR_INTERNET_UNABLE_TO_CACHE_FILE 80072F7E
ERROR_INTERNET_TCPIP_NOT_INSTALLED 80072F7F
ERROR_HTTP_NOT_REDIRECTED 80072F80
ERROR_HTTP_COOKIE_NEEDS_CONFIRMATION 80072F81
ERROR_HTTP_COOKIE_DECLINED 80072F82
ERROR_INTERNET_DISCONNECTED 80072F83
ERROR_INTERNET_SERVER_UNREACHABLE 80072F84
ERROR_INTERNET_PROXY_SERVER_UNREACHABLE 80072F85
ERROR_INTERNET_BAD_AUTO_PROXY_SCRIPT 80072F86
ERROR_INTERNET_UNABLE_TO_DOWNLOAD_SCRIPT 80072F87
ERROR_HTTP_REDIRECT_NEEDS_CONFIRMATION 80072F88
ERROR_INTERNET_SEC_INVALID_CERT 80072F89

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 20 (21)

 Revision History
Rev. Date Author Changed
A 27-Jan-2006 R Kupiec Original
B 30-Jan-2006 R Kupiec Section 22
added
C 25-Apr-2006 R Kupiec Section 23-29
added

ABB Inc.

Doc. Id. Rev. A Date. 4/11/2025 21 (21)