Message Class 1006 - DCOM Wrapper

The method SetInfo() is called with the wrong data type for user ID.

Check access to user ID. The correct data type for user ID is the automation data type BSTR.

The user ID is too long.

Check access to user ID. Maximum length of user ID is 32 characters.

The method SetInfo() is called with the wrong data type for password.

Check access to password. The correct data type for password is the automation data type BSTR.

The password is too long.

Check access to password. Maximum length of password is 32 characters.

The method SetInfo() is called with the wrong data type for new password.

Check access to new password. The correct data type for new password is the automation data type BSTR.

The new password is too long.

Check access to new password. Maximum length of new password is 32 characters.

The RPC user ID is too long.

Check access to RPC user ID. Maximum length of RPC user ID is 32 characters.

The RPC password is too long.

Check access to RPC password. Maximum length of RPC password is 32 characters.

The method SetInfo() is called with the wrong data type for token.

Check access to token. The correct data type for token is the automation data type BSTR.

The token is too long.

Check access to token. Maximum length of token is 16 characters.

The security token is too long.

Check access to security token. Maximum length of security token is 32 bytes.

The method SetInfo() is called with the wrong data type for Broker ID.

Check access to server address. The correct data type for Broker ID is the automation data type BSTR.

The Broker ID is too long.

Check access to server address. Maximum length of Broker ID is 32.

The method SetInfo() is called with the wrong data type for server class.

Check access to server address. The correct data type for server class is the automation data type BSTR.

The server class is too long.

Check access to server address. Maximum length of server class string is 32 characters.

The method SetInfo() is called with the wrong data type for server name.

Check access to Server Address. The correct data type for server name is the automation data type BSTR.

The server name string is too long.

Check access to server address. Maximum length of server name string is 32 characters.

The method SetInfo() is called with the wrong data type for service name.

Check access to server address. The correct data type for service name is the automation data type BSTR.

The service name string is too long.

Check access to server address. Maximum length of service name string is 32 characters.

The format of server address is invalid.

Check access to server address. The correct format is <brokerID>[:<port>]@server class/server name/service name.

The server address string is invalid.

Check access to server address. The correct format is <brokerID>[:<port>]@server class/server name/service name.

The library name is too long.

Check access to Library. Maximum length of library name is 8 characters.

The method SetInfo() is called with the wrong data type for Natural Logon.

Check access to Natural Logon. The correct data type for Natural Logon is the automation data type BSTR.

The Natural Logon consists of more than one character.

Check access to Natural Logon. Values for Natural Logon are 'N' or 'Y', or use the definition in ERX.H ERX_NATURAL_LOGON_NO or ERX_NATURAL_LOGON_YES, respectively.

The method SetInfo() is called with the wrong data type for compression.

Check access to compression. The correct data type for compression is the automation data type BSTR.

The Compression consists of more than one character.

Check access to compression. Values are ' ' or '2', or use the definition in ERX.H ERX_COMPRESSION_NO or ERX_COMPRESSION_YES, respectively.

The method SetInfo() is called with the wrong data type for timeout.

Check access to timeout. The correct data type for timeout is the automation data type LONG.

Wrong data type for ForceLogon attribute.

Check access to ForceLogon. The correct data type for ForceLogon is the automation data type BSTR.

Wrong length of ForceLogon attribute.

Check access to ForceLogon. Maximum length of ForceLogon is 1 character.

Wrong data type for EncryptionLevel attribute.

Check access to EncryptionLevel. The correct data type for EncryptionLevel is the automation data type BSTR.

Wrong length of EncryptionLevel attribute.

Check access to EncryptionLevel. Maximum length of EncryptionLevel is 1 character.

Wrong data type for SSL string

Check access to SSL string. The correct data type for SSL string is the automation data type BSTR.

The string is longer than determined in the IDL file.

Check access to attributes inside a group definition.

An attempt is made to set a property for an array which contains at least one corrupt element.

Check and correct the application.

The property is accessed with a null pointer.

Check and correct the application.

Wrong data type for date attribute.

Check variables used in method call. The automation data type for date is double.

Wrong data type for time attribute.

Check variables used in method call. The automation data type for time is double.

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.

Check and correct the application.

The number string contains more than one sign.

Check and correct the application.

The number string contains more than one decimal point.

Check and correct the application.

The number string contains unexpected characters.

Check and correct the application.

The number format is invalid, the number string has more digits than expected.

Correct the application.

The format of number is invalid, the number has more digits before the decimal point than expected.

Correct the application.

The format of the number is invalid, the number has more digits after the decimal point than expected.

Correct the application.

A value of N/P data type is cut or rounded during conversion.

Check your N/P data types. Resize these data types in the Software AG IDL file or change the feature setting.

A value is cut or rounded during conversion.

Check your values. Correct values in your application or change feature setting.

A numeric data type is used with a value which exceeds the valid range.

Correct values in your application.

A K data type is not correctly specified in the IDL file for the used codepage.

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.

The conversion from Natural data type Packed or Non-packed failed.

Check the values of the attributes with N or P declaration in the IDL file.

The conversion from a string to Natural data type Packed or Non-packed failed.

Check the values of the attributes with N or P declaration in the IDL file.

The conversion from local character set to wide character set failed.

Internal or user error. Retry method call.

1. Converted string is longer than size of data type specified in the IDL file.

2. Conversation method cannot convert the input wide-character string to multibyte-character string. The input string may have invalid characters.

3. The codepage used does not exist.

1. Check the length of the input string.

2. Check the input string.

3. Check the codepage number entered in the CodePage property.

The automation server cannot allocate a string.

Increase your free memory, for example by closing another application.

The automation server cannot reallocate a string.

Increase your free memory, for example by closing another application.

The conversion method received a null pointer and cannot handle this situation.

Check and initialize this pointer with a valid value.

The automation server cannot allocate the required memory.

Increase your free memory, for example by closing another application.

The array has an at least one unexpected dimension.

Correct your program.

An array is corrupt.

Correct your program.

An array has at least one corrupt element.

Check and correct your program.

The array or one of its elements is corrupt.

Correct your program.

Something went wrong during the registration of the ERX runtime.

Make sure that the ERX runtime and the DCOM Wrapper template have the same version.

User has tried to redim a fixed-size array or the dimension of the accessed array is wrong.

Check and correct the application.

A scalar data type was used, where an array was expected.

Check and correct the application.

User has tried to redim a fixed-size array

Check and correct the application.

Property put was attempted to an index number out of range.

Check and correct the application.

The array received from the server does not fit into the array data structure defined on the client side.

Check if client and server use the same data stuctures.

User has tried to redim an array in an undefined dimension.

Check and correct the application.

User has tried to redim an array and the new size exceeds the defined size.

Check the maximum size allowed in the IDL file and correct the application.

The variable array is not defined or not accessible.

Internal or user error. Retry method call.

The index of the array is not defined or not accessible.

Check and correct the application.

The accessed dimension of the array does not exist.

Check and correct the application.

The variable is not an array or the type of the array is not correct.

Check and correct the application.

The accessed variable is not an array

Check and correct the application.

The accessed dimension of the array does not exist.

Please redim the 1st dimension of the array first.

The accessed dimension of the array does not exist

Internal or user error. Retry method call.

The array is not defined or not accessible.

Internal or user error. Retry method call.

The accessed index of the array exceeds the upper bound.

Check and correct the application.

The accessed structure does not exist.

Check and correct the application.

The accessed index of the structure does not exist.

Check and correct the application.

The ERX.DLL does not exist in the EntireX installation.

Check if the EntireX RPC Runtime was installed correctly.

The data type is not supported by the DCOM Wrapper. Programs with this data type will be ignored.

No action required.

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.

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.

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".

Refer to the Microsoft Visual Studio documentation. Select supported wizard type and retry.

The EntireX DCOM Wrapper Microsoft Visual Studio Wizard requires an EntireX installation to work.

Install EntireX and retry.

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.

Check your EntireX installation or install Java runtime and retry.

The chosen IDL file in the EntireX DCOM Wrapper Microsoft Visual Studio Wizard main panel does not exist.

Check the IDL file name and choose a valid file name.

The input field for the IDL file in the EntireX DCOM Wrapper Microsoft Visual Studio Wizard main panel is empty.

Check the IDL file name and choose a valid file name.

The generated DCOM Wrapper object could not be found after generation the object.

Check the DCOM Wrapper object file.

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.

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.

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.

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.

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.

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.

The Visual Studio project file could not be created. See the <text> for detailed information about the reason of this problem.

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.

The Visual Studio solution file could not be created. See the <text> for detailed information about the reason of this problem.

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.

The generation of the DCOM Wrapper object could not be completed. The selected IDL file might be not valid.

Check the IDL file.

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.

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.

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.

None.

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.

None.

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.

None.