This message class is returned if an error occurred in the DCOM Wrapper. Messages of this class have the format:
1006nnnn
where | 1006 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999. |
10060001 | 10060002 | 10060003 | 10060004 | 10060005 | 10060006 | 10060008 | 10060010 | 10060011 | 10060012 | 10060014 | 10060015 | 10060016 | 10060017 | 10060018 | 10060019 | 10060020 | 10060021 | 10060022 | 10060023 | 10060024 | 10060026 | 10060027 | 10060028 | 10060029 | 10060030 | 10060031 | 10060033 | 10060034 | 10060035 | 10060036 | 10060037 | 10060039 | 10060040 | 10060041 | 10060042 | 10060043 | 10060044 | 10060045 | 10060046 | 10060047 | 10060048 | 10060050 | 10060051 | 10060052 | 10060053 | 10060054 | 10060055 | 10060057 | 10060058 | 10060059 | 10060060 | 10060061 | 10060062 | 10060063 | 10060064 | 10060065 | 10060066 | 10060067 | 10060068 | 10060069 | 10060070 | 10060071 | 10060072 | 10060073 | 10060074 | 10060080 | 10060081 | 10060082 | 10060083 | 10060084 | 10060085 | 10060086 | 10060090 | 10060091 | 10060092 | 10060093 | 10060096 | 10060097 | 10060100 | 10060101 | 10061001 | 10061002 | 10061003 | 10061004 | 10061005 | 10061006 | 10061007 | 10061008 | 10061009 | 10061010 | 10061011 | 10061012 | 10061013 | 10061014 | 10061015 | 10061016 | 10061017
10060001 | User ID - invalid type |
Explanation |
The method |
Action |
Check access to user ID. The correct data type for user ID is the
automation data type |
10060002 | User ID - invalid length (maximum length is 32 characters) |
Explanation |
The user ID is too long. |
Action |
Check access to user ID. Maximum length of user ID is 32 characters. |
10060003 | Password - invalid type |
Explanation |
The method |
Action |
Check access to password. The correct data type for password is the
automation data type |
10060004 | Password - invalid length (maximum length is 32 characters) |
Explanation |
The password is too long. |
Action |
Check access to password. Maximum length of password is 32 characters. |
10060005 | New password - invalid type |
Explanation |
The method |
Action |
Check access to new password. The correct data type for new password is
the automation data type |
10060006 | New Password - maximum length is 32 characters |
Explanation |
The new password is too long. |
Action |
Check access to new password. Maximum length of new password is 32 characters. |
10060008 | RPC user ID - maximum length is 32 characters |
Explanation |
The RPC user ID is too long. |
Action |
Check access to RPC user ID. Maximum length of RPC user ID is 32 characters. |
10060010 | RPC password - maximum length is 32 characters |
Explanation |
The RPC password is too long. |
Action |
Check access to RPC password. Maximum length of RPC password is 32 characters. |
10060011 | Token - invalid type |
Explanation |
The method |
Action |
Check access to token. The correct data type for token is the automation
data type |
10060012 | Token - maximum length is 16 characters |
Explanation |
The token is too long. |
Action |
Check access to token. Maximum length of token is 16 characters. |
10060014 | Security token - maximum length is 32 bytes |
Explanation |
The security token is too long. |
Action |
Check access to security token. Maximum length of security token is 32 bytes. |
10060015 | Broker ID - invalid type |
Explanation |
The method |
Action |
Check access to server address. The correct data type for Broker ID is
the automation data type |
10060016 | Broker ID - maximum length is 32 characters |
Explanation |
The Broker ID is too long. |
Action |
Check access to server address. Maximum length of Broker ID is 32. |
10060017 | Server Class - invalid type |
Explanation |
The method |
Action |
Check access to server address. The correct data type for server class is
the automation data type |
10060018 | Server Class - maximum length is 32 characters |
Explanation |
The server class is too long. |
Action |
Check access to server address. Maximum length of server class string is 32 characters. |
10060019 | Server Name - invalid type |
Explanation |
The method |
Action |
Check access to Server Address. The correct data type for server name is
the automation data type |
10060020 | Server Name - maximum length is 32 characters |
Explanation |
The server name string is too long. |
Action |
Check access to server address. Maximum length of server name string is 32 characters. |
10060021 | Service Name - invalid type |
Explanation |
The method |
Action |
Check access to server address. The correct data type for service name is
the automation data type |
10060022 | Service Name - maximum length is 32 characters |
Explanation |
The service name string is too long. |
Action |
Check access to server address. Maximum length of service name string is 32 characters. |
10060023 | Invalid server address format |
Explanation |
The format of server address is invalid. |
Action |
Check access to server address. The correct format is <brokerID>[:<port>]@server class/server name/service name. |
10060024 | Invalid server address |
Explanation |
The server address string is invalid. |
Action |
Check access to server address. The correct format is <brokerID>[:<port>]@server class/server name/service name. |
10060026 | Library name - maximum length is 8 characters |
Explanation |
The library name is too long. |
Action |
Check access to Library. Maximum length of library name is 8 characters. |
10060027 | Natural Logon - invalid type |
Explanation |
The method |
Action |
Check access to Natural Logon. The correct data type for Natural Logon is
the automation data type |
10060028 | Natural Logon - invalid length |
Explanation |
The Natural Logon consists of more than one character. |
Action |
Check access to Natural Logon. Values for Natural Logon are 'N' or 'Y',
or use the definition in |
10060029 | Compression - invalid type |
Explanation |
The method |
Action |
Check access to compression. The correct data type for compression is the
automation data type |
10060030 | Compression - invalid length |
Explanation |
The Compression consists of more than one character. |
Action |
Check access to compression. Values are ' ' or '2', or use the definition
in |
10060031 | Timeout - invalid type |
Explanation |
The method |
Action |
Check access to timeout. The correct data type for timeout is the
automation data type |
10060033 | Force Logon - invalid type |
Explanation |
Wrong data type for |
Action |
Check access to |
10060034 | Force Logon - invalid length |
Explanation |
Wrong length of |
Action |
Check access to |
10060035 | Encryption Level - invalid type |
Explanation |
Wrong data type for |
Action |
Check access to Note: |
10060036 | Encryption Level - invalid length |
Explanation |
Wrong length of |
Action |
Check access to Note: |
10060037 | SSL String - invalid type |
Explanation |
Wrong data type for SSL string |
Action |
Check access to SSL string. The correct data type for SSL string is the
automation data type |
10060039 | Property: string too long |
Explanation |
The string is longer than determined in the IDL file. |
Action |
Check access to attributes inside a group definition. |
10060040 | Property: get invalid array |
Explanation |
An attempt is made to set a property for an array which contains at least one corrupt element. |
Action |
Check and correct the application. |
10060041 | Property: get null pointer |
Explanation |
The property is accessed with a null pointer. |
Action |
Check and correct the application. |
10060042 | Date format is invalid |
Explanation |
Wrong data type for date attribute. |
Action |
Check variables used in method call. The automation data type for date is double. |
10060043 | Time format is invalid |
Explanation |
Wrong data type for time attribute. |
Action |
Check variables used in method call. The automation data type for time is double. |
10060044 | Sign found that is not in first position of alpha-string |
Explanation |
The alpha-string to be converted to a Natural data type Packed or Non-packed contains a sign character on first position of the alpha string. |
Action |
Check and correct the application. |
10060045 | Alpha string with multiple signs found |
Explanation |
The number string contains more than one sign. |
Action |
Check and correct the application. |
10060046 | Alpha string with multiple precisions found |
Explanation |
The number string contains more than one decimal point. |
Action |
Check and correct the application. |
10060047 | Alpha string contains invalid character |
Explanation |
The number string contains unexpected characters. |
Action |
Check and correct the application. |
10060048 | Alpha string with more digits than defined |
Explanation |
The number format is invalid, the number string has more digits than expected. |
Action |
Correct the application. |
10060050 | More digits before decimal point than defined |
Explanation |
The format of number is invalid, the number has more digits before the decimal point than expected. |
Action |
Correct the application. |
10060051 | More digits after decimal point than defined |
Explanation |
The format of the number is invalid, the number has more digits after the decimal point than expected. |
Action |
Correct the application. |
10060052 | Loss of precision during conversion |
Explanation |
A value of N/P data type is cut or rounded during conversion. |
Action |
Check your N/P data types. Resize these data types in the Software AG IDL file or change the feature setting. |
10060053 | Number/string is too long |
Explanation |
A value is cut or rounded during conversion. |
Action |
Check your values. Correct values in your application or change feature setting. |
10060054 | Parameter out of range |
Explanation |
A numeric data type is used with a value which exceeds the valid range. |
Action |
Correct values in your application. |
10060055 | Length of K data type must be an even number for the current codepage |
Explanation |
A K data type is not correctly specified in the IDL file for the used codepage. |
Action |
Check the K data type in the IDL file. Change the length of the K data type in the IDL file to an even number and re-generate the object. |
10060057 | Conversion from Numeric to Alpha failed |
Explanation |
The conversion from Natural data type Packed or Non-packed failed. |
Action |
Check the values of the attributes with N or P declaration in the IDL file. |
10060058 | Conversion from Alpha to Numeric failed |
Explanation |
The conversion from a string to Natural data type Packed or Non-packed failed. |
Action |
Check the values of the attributes with N or P declaration in the IDL file. |
10060059 | MultiByte to WideCharacter conversion failed |
Explanation |
The conversion from local character set to wide character set failed. |
Action |
Internal or user error. Retry method call. |
10060060 | WideCharacter to MultiByte conversion failed |
Explanation |
|
Action |
|
10060061 | String allocation failed |
Explanation |
The automation server cannot allocate a string. |
Action |
Increase your free memory, for example by closing another application. |
10060062 | String reallocation failed |
Explanation |
The automation server cannot reallocate a string. |
Action |
Increase your free memory, for example by closing another application. |
10060063 | Corrupt pointer |
Explanation |
The conversion method received a null pointer and cannot handle this situation. |
Action |
Check and initialize this pointer with a valid value. |
10060064 | Memory allocation failed |
Explanation |
The automation server cannot allocate the required memory. |
Action |
Increase your free memory, for example by closing another application. |
10060065 | Wrong dimension of array |
Explanation |
The array has an at least one unexpected dimension. |
Action |
Correct your program. |
10060066 | Invalid array |
Explanation |
An array is corrupt. |
Action |
Correct your program. |
10060067 | Access to array failed |
Explanation |
An array has at least one corrupt element. |
Action |
Check and correct your program. |
10060068 | Invalid group array |
Explanation |
The array or one of its elements is corrupt. |
Action |
Correct your program. |
10060069 | Registration failed |
Explanation |
Something went wrong during the registration of the ERX runtime. |
Action |
Make sure that the ERX runtime and the DCOM Wrapper template have the same version. |
10060070 | Unexpected method call |
Explanation |
User has tried to redim a fixed-size array or the dimension of the accessed array is wrong. |
Action |
Check and correct the application. |
10060071 | A scalar value is used as array |
Explanation |
A scalar data type was used, where an array was expected. |
Action |
Check and correct the application. |
10060072 | Illegal attempt to redim a fixed-size array |
Explanation |
User has tried to redim a fixed-size array |
Action |
Check and correct the application. |
10060073 | Property put to an index number out of range |
Explanation |
Property put was attempted to an index number out of range. |
Action |
Check and correct the application. |
10060074 | Bad array index |
Explanation |
The array received from the server does not fit into the array data structure defined on the client side. |
Action |
Check if client and server use the same data stuctures. |
10060080 | Variable-size array contains substructure with wrong dimension |
Explanation |
User has tried to redim an array in an undefined dimension. |
Action |
Check and correct the application. |
10060081 | Variable-size array exceeded the maximum for one dimension |
Explanation |
User has tried to redim an array and the new size exceeds the defined size. |
Action |
Check the maximum size allowed in the IDL file and correct the application. |
10060082 | Null pointer exception |
Explanation |
The variable array is not defined or not accessible. |
Action |
Internal or user error. Retry method call. |
10060083 | Access of variable-size array with bad index |
Explanation |
The index of the array is not defined or not accessible. |
Action |
Check and correct the application. |
10060084 | Number of dimensions of a variable-size array too small |
Explanation |
The accessed dimension of the array does not exist. |
Action |
Check and correct the application. |
10060085 | Variable-size array has an element with unexpected type |
Explanation |
The variable is not an array or the type of the array is not correct. |
Action |
Check and correct the application. |
10060086 | Variable-size array |
Explanation |
The accessed variable is not an array |
Action |
Check and correct the application. |
10060090 | Wrong usage of redimension method |
Explanation |
The accessed dimension of the array does not exist. |
Action |
Please redim the 1st dimension of the array first. |
10060091 | Out of bounds exception |
Explanation |
The accessed dimension of the array does not exist |
Action |
Internal or user error. Retry method call. |
10060092 | Null pointer exception |
Explanation |
The array is not defined or not accessible. |
Action |
Internal or user error. Retry method call. |
10060093 | Index exceeded maximum value |
Explanation |
The accessed index of the array exceeds the upper bound. |
Action |
Check and correct the application. |
10060096 | Access of a structure with null pointer |
Explanation |
The accessed structure does not exist. |
Action |
Check and correct the application. |
10060097 | Illegal index of required structure |
Explanation |
The accessed index of the structure does not exist. |
Action |
Check and correct the application. |
10060100 | RPC runtime is not available |
Explanation |
The ERX.DLL does not exist in the EntireX installation. |
Action |
Check if the EntireX RPC Runtime was installed correctly. |
10060101 | IDL data type <data type> not supported: <text> |
Explanation |
The data type is not supported by the DCOM Wrapper. Programs with this data type will be ignored. |
Action |
No action required. |
10061001 | Unhandled exception caught. <text> |
Explanation |
There was an unexpected exception caught. The exception might be reported by any used runtime component of EntireX or Microsoft Visual Studio. Please refer the <text> to get detailed information about the reason of this problem. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061002 | Unsupported wizard type |
Explanation |
The Microsoft Visual Studio tries to uses an unsupported wizard type. The EntireX DCOM Wrapper Microsoft Visual Studio Wizard supports only the following wizard types: "Create New Solution" and "Add to Solution". |
Action |
Refer to the Microsoft Visual Studio documentation. Select supported wizard type and retry. |
10061003 | EntireX installation was not found |
Explanation |
The EntireX DCOM Wrapper Microsoft Visual Studio Wizard requires an EntireX installation to work. |
Action |
Install EntireX and retry. |
10061004 | Java Runtime not found |
Explanation |
The EntireX DCOM Wrapper Microsoft Visual Studio Wizard requires a Java runtime installation to work. Typically a Java runtime will be installed together with the EntireX installation. |
Action |
Check your EntireX installation or install Java runtime and retry. |
10061005 | Software AG IDL file not found |
Explanation |
The chosen IDL file in the EntireX DCOM Wrapper Microsoft Visual Studio Wizard main panel does not exist. |
Action |
Check the IDL file name and choose a valid file name. |
10061006 | Cancel execute, because no IDL file is chosen |
Explanation |
The input field for the IDL file in the EntireX DCOM Wrapper Microsoft Visual Studio Wizard main panel is empty. |
Action |
Check the IDL file name and choose a valid file name. |
10061007 | Generation of a DCOM Wrapper object has failed |
Explanation |
The generated DCOM Wrapper object could not be found after generation the object. |
Action |
Check the DCOM Wrapper object file. |
10061008 | Problem while adding a reference to the project. <text> |
Explanation |
The generated DCOM Wrapper object could not be added to the project references. See the <text> for detailed information about the reason of this problem. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061009 | Problem reading template file. <text> |
Explanation |
The project source code template file could not be added to the project. See the <text> for detailed information about the reason of this problem. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061010 | Problem writing template file. <text> |
Explanation |
The project source code template file could not be copied into the project directory. See the <text> for detailed information about the reason of this problem. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061011 | Problem to create a new project file from template. <text> |
Explanation |
The Visual Studio project file could not be created. See the <text> for detailed information about the reason of this problem. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061012 | Problem to create a new solution. <text> |
Explanation |
The Visual Studio solution file could not be created. See the <text> for detailed information about the reason of this problem. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061013 | Problem to generate DCOM Wrapper Object. <text> |
Explanation |
The generation of the DCOM Wrapper object could not be completed. The selected IDL file might be not valid. |
Action |
Check the IDL file. |
10061014 | Internal Problem! Please see log file for more details |
Explanation |
The EntireX DCOM Wrapper Microsoft Visual Studio Wizard has detected an internal problem. The reason for this problem will be added to the log file. |
Action |
Please see the generated log file for detailed information. The log will be automatically generated into your Microsoft Visual Studio environment. Contact Software AG support. |
10061015 | IDL program has a client-side mapping (CVM). DCOM RPC clients not supported: <library>/<program> |
Explanation |
RPC clients generated with the DCOM Wrapper do not support client-side mapping files (Natural | COBOL). The appendix of the message gives you the IDL library and IDL program name causing the error. |
Action |
None. |
10061016 | IDL types N/NU/P/PU with more than 29 digits are not supported: <library>/<program>/<parameter> |
Explanation |
The DCOM Wrapper does not support IDL N/NU/P/PU data types with more than 29 digits (before and after decimal point). The appendix of the message gives you the IDL library, IDL program name and IDL parameter causing the error. |
Action |
None. |
10061017 | IDL types N/NU/P/PU with more than 7 digits after decimal point are not supported: <library>/<program>/<parameter> |
Explanation |
The DCOM Wrapper does not support IDL N/NU/P/PU data types with more than 7 digits after decimal point. The appendix of the message gives you the IDL library, IDL program name and IDL parameter causing the error. |
Action |
None. |